The Message That Moves First: ISO 20022 Part 1
You pay, and it feels like money has instantly left your account and landed in someone else’s. But the truth is far less dramatic.
Every payment starts its life not as money, but as a message: a structured instruction that tells the bank
· Who is sending money,
· Who should receive it, and
· How much to transfer.
Without this message, nothing moves, and the success of the transaction depends entirely on it being clear and correctly understood. Today, most of these payment instructions follow ISO 20022, a global standard that ensures every bank reads and processes payments in the same way.
The Payment’s First Step
Think of this message like a courier label. Before a package moves, it needs details: sender, recipient, and contents. The payment’s message works the same way. When you initiate a transfer, the bank reads this instruction, validates it, and prepares it for the journey ahead.
The most common type of instruction is called pain.001. It’s used whenever a customer or business tells a bank to send money. It includes the essentials:
· Who is paying,
· Who is receiving,
· The amount, and
· Sometimes the purpose of the transfer.
Payroll, for example, is often sent this way, with a single file telling the bank to credit salaries to dozens or hundreds of accounts.
At this stage, the payment has been defined and documented and ready to begin its journey.
Sending Money Across Banks
Once the bank understands the instruction, the payment moves on to the receiving bank. Here, the message type changes to something called pacs, short for Payments Clearing and Settlement. A common one is pacs.008, used for credit transfers between institutions.
You can think of this as handing the package over to the courier. The instructions are clear, so the receiving bank knows exactly what to do: credit this account with that amount. Networks like SWIFT carry these messages across countries and institutions, ensuring the payment moves safely and reliably toward its destination.
Confirming the Arrival
Finally, when the receiving bank processes the payment, it reports back using camt messages, Cash Management messages that provide updates and confirmations.
For example:
- camt.054 lets the recipient know funds have arrived
- camt.053 updates the bank statement to reflect the transaction
At this point, the payment has officially arrived and becomes part of the account records and the journey from instruction to movement to confirmation is complete.
A Quick Look at the Journey
Even though the messages have different names and functions, they work together to make sure every payment is tracked, validated, and correctly recorded.
Why It Matters?
While a payment may look simple from the outside, it involves multiple systems that need to understand the same instruction in exactly the same way. Any gap in that understanding can lead to delays, errors, or additional checks.
ISO 20022 addresses this by providing a consistent structure for payment messages. It ensures that the information created at the start of the transaction remains clear and usable as it moves across banks and systems. This is what allows payments to be processed smoothly and recorded accurately.
What Comes Next?
So far, we’ve looked at how a payment moves: starting as an instruction, traveling between banks, and finally being confirmed.
But this raises a bigger question.
Why did the industry need a standard like ISO 20022 in the first place? What problems was it trying to fix, and why is it now becoming the foundation for modern payment systems?
That’s where the next part begins!
P.S: What topic do you think we should explore next? Let us know in the comments.
