Yes. For the actual video, I would use this version. It is built around your repository’s **30-episode Swift Saga**, but tells one continuous payment story instead of trying to advertise 30 separate topics.
## SWIFT SAGA — 60-SECOND CINEMATIC VIDEO SCRIPT
**Style:** premium banking documentary, realistic financial infrastructure, dark navy/blue environment, crisp white typography, subtle cyan data flows, smooth cinematic camera movement. No cartoon banks, coins, crypto imagery, random stock charts or fake futuristic screens.
**0–5 sec — THE HOOK**
Visual: A customer enters a payment and presses **SEND**. Everything freezes. Camera dives inside the transaction.
Voiceover:
> “You press Send. A payment leaves your screen… but the real journey has only begun.”
On-screen:
**WHAT REALLY HAPPENS NEXT?**
---
**5–14 sec — INSIDE THE BANK**
Visual:
Customer
↓
Channel
↓
Payment Engine
↓
Validation
↓
Fraud & Sanctions
↓
Routing
↓
Messaging Hub
Voiceover:
> “Inside the bank, the instruction is validated, enriched, screened, routed and transformed before it can travel beyond the bank.”
Keep the flow technically clean. Show systems exchanging data, not money magically flying between screens.
---
**14–22 sec — ENTERING THE SWIFT WORLD**
Visual: BIC → identity → PKI/security → RMA → Swift connectivity → FIN / FINplus.
Voiceover:
> “The institution must be identified. Trust must be established. The messaging relationship must be authorised. Then the financial message can enter the Swift world.”
On-screen words appearing individually:
**Identity. Trust. Authorisation. Connectivity.**
---
**22–32 sec — ISO 20022 & CBPR+**
Visual: An older MT-style message transitions elegantly into structured ISO 20022 XML.
Highlight:
**pacs.008**
**pacs.009**
**pacs.002**
**pacs.004**
**camt.056**
Then show:
**Business Application Header → CBPR+ validation → Financial message**
Voiceover:
> “Today, that journey increasingly speaks ISO 20022 and CBPR+ — where structured data, business rules and message context matter as much as connectivity.”
---
**32–41 sec — MESSAGE ≠ MONEY**
This must be the strongest visual.
Split screen.
Left:
**Swift message**
Sender Bank → Swift → Receiver Bank
Right:
**Value / Settlement**
Bank A → Correspondent / Nostro → Market Infrastructure → Bank B
Voiceover:
> “And this distinction matters: Swift carries trusted financial messages. Swift does not itself move the money.”
Large on-screen statement:
**MESSAGE ≠ SETTLEMENT**
Then:
**Messaging tells the story.
Settlement moves the value.**
---
**41–49 sec — TRACKING THE PAYMENT**
Visual: One glowing identifier follows the payment across several banks.
Display:
**UETR**
Bank A → Correspondent → Bank B → Beneficiary
Voiceover:
> “Across the chain, the UETR helps correlate the payment journey — while acknowledgements, statuses and responses reveal different parts of what actually happened.”
Do not display “UETR = settlement confirmation.”
---
**49–56 sec — WHEN THINGS GO WRONG**
Suddenly interrupt the perfect flow.
Show branches:
**Rejected**
**Returned**
**Timeout**
**Repair**
**Investigation**
**Reconciliation**
Voiceover:
> “Because real payments don't always follow the happy path. They reject, return, time out, require repair, investigation and reconciliation.”
Visual: operations user traces the payment back through the chain.
---
**56–60 sec — THE REVEAL**
All previous payment lines zoom outward and form a global network.
Network transforms into:
# **SWIFT SAGA**
Below:
**30 EPISODES • ONE CONNECTED JOURNEY**
Voiceover:
> “Swift Saga connects it all. Thirty episodes. One journey. From message… to payment reality.”
Final frame:
**MALLA BANKING APP**
**Learn Banking. Understand Payments.**
Small footer:
**Swift Saga**
---
### Exact voiceover only
Use this if ToMotion asks for only the narration:
> “You press Send. A payment leaves your screen — but the real journey has only begun. Inside the bank, the instruction is validated, enriched, screened, routed and transformed before it can travel beyond the bank. The institution must be identified. Trust must be established. The messaging relationship must be authorised. Then the financial message can enter the Swift world. Today, that journey increasingly speaks ISO 20022 and CBPR+ — where structured data, business rules and message context matter as much as connectivity. And this distinction matters: Swift carries trusted financial messages. Swift does not itself move the money. Across the chain, the UETR helps correlate the payment journey, while statuses and responses reveal what actually happened. Because real payments don't always follow the happy path. They reject, return, time out, require repair, investigation and reconciliation. Swift Saga connects it all. Thirty episodes. One journey. From message to payment reality.”
This is the version I would use for **Swift Saga**. The central **“MESSAGE ≠ SETTLEMENT”** scene is what will make the video stand apart from a generic Swift promotional video.
