ISO 20022 Payment Lifecycle — Part 1: Foundations + STP Backbone
Payment Talks
0:00 / 0:00
ISO 20022 Payment Lifecycle — Part 1: Foundations + STP Backbone
1 628 просмотров · 2 мес. назад
Payment Talks
2,32 тыс. подписчиков
1 628 просмотров · 2 мес. назад
What actually happens inside a cross-border ISO 20022 payment?
Before we explore rejects, cancellations, FI-to-FI payments, Cover, Advice, and Direct Debit, we need to understand the foundation — the actors, the payment flow, and the Straight-Through Processing (STP) backbone that everything else builds on.
In Part 1 of the PaymentTalks ISO 20022 Payment Lifecycle Series, we establish the common canvas used throughout the entire series and then walk through a complete happy-path CBPR+ payment from initiation to final credit.
In this video, you'll learn:
🔹 The 7 actors in a cross-border payment
Debtor
Debtor Agent
Sender Correspondent
PMI
Receiver Correspondent
Creditor Agent
Creditor
🔹 How to read the payment lifecycle diagrams
What the red and black flows represent
Where the PMI fits into the settlement process
How the payment moves across the correspondent chain
🔹 How the SWIFT gpi Tracker works
trck.001 — processing completion reported to the Tracker
trck.002 — Tracker update broadcast to upstream agents
The important rule: acknowledge → forward → report to Tracker
🔹 The complete STP happy path
We follow a real-world example:
Northwind Traders → Meridian Bank → Atlas Bank → PMI → Harbor Bank → Crestline Bank → Ridgeline Supplies
And see how the key ISO 20022 messages fit together:
pain.001 → pain.002 → pacs.008 → pacs.002 → camt.054 → camt.053
You'll also see why Meridian sends the camt.054 notification immediately after its network acknowledgment — before the downstream bank has confirmed the payment.
The pattern that repeats throughout the series
RECEIVE → VALIDATE → ACK → PROCESS → FORWARD → TRACKER REPORT
Once you understand this pattern, the rest of the ISO 20022 payment lifecycle becomes much easier to follow.
And there's one important takeaway:
STP isn't a separate message type. It's what happens when the payment encounters no exception.
In the next video, we break that happy path — and look at Rejects, Returns, and Cancellation, including Serial Cancellation and SRP (Stop and Recall Payment).
📺 This is Part 1 of 4
Part 1: Foundations + STP Backbone
Part 2: Non-STP + Cancellation
Part 3: FI-to-FI Payments + Cover vs. Advice
Part 4: Direct Debit + Reference & Administrative Messages
Subscribe to PaymentTalks for practical, architect-level explanations of ISO 20022, CBPR+, SWIFT, payment orchestration, and cross-border payments.