Payments - Introduction / Learning brief
Parties in a Payment System
Your notes
In simple terms / 01
What this means in plain language
Identifies the customers, banks, intermediaries, and market infrastructures that initiate, route, settle, and receive payments.
A payment connects more parties than the payer and payee. The originator requests the transfer, and the beneficiary is meant to receive it. Their payment service providers validate customers, manage accounts, create or receive instructions, and communicate outcomes. Intermediary or correspondent institutions may bridge routes when the endpoint PSPs lack a direct relationship. Clearing and settlement infrastructures exchange transactions and complete obligations. Service providers can support compliance, messaging, processing, and technology. Mapping each party's role, account relationship, identifier, and responsibility prevents ambiguity during design and investigation.
Complete lesson / 02
Understand the full idea, step by step
Before you can follow the money, you have to know who is standing around it. Every payment — a rent transfer, a supplier invoice, a card tap — involves the same small cast of roles, and the industry has precise names for each. Learn the cast once and every diagram, message, and rulebook you meet afterwards becomes readable.
Roles, not companies
The first thing to fix in your mind: these labels name roles, not organizations. One institution can play several roles at once — Bank Alfa is the payer's bank in both of our payments, and in another payment it might be the receiving bank, or the bank in the middle. The second thing: each role is anchored to a question about whose books hold which account. Riya's account is a row in Bank Alfa's ledger; Arjun's is a row in Nordbank's. No bank can reach into another bank's books, which is precisely why payments need this cast at all — each participant does the part only it can do.
Agent
In formal payments language, the banks in a payment are called agents — they act on behalf of the customer parties. ISO 20022 (the international standard for financial messages, covered in a later lesson) names them by whom they serve: the payer is the debtor (the party that owes), so the payer's bank is the debtor agent; the payee is the creditor (the party owed), so the payee's bank is the creditor agent. A bank in the middle, serving neither customer directly, is an intermediary agent. These exact words appear as field names in real interbank messages, which is why they are worth learning early.
| Everyday name | ISO 20022 role name | In this lesson |
|---|---|---|
| Payer / sender | Debtor | Riya · Asha Traders |
| Payer's bank | Debtor agent | Bank Alfa |
| Payee / recipient | Creditor | Arjun · the supplier |
| Payee's bank | Creditor agent | Nordbank · the supplier's bank |
| Bank in the middle | Intermediary agent | Meridian Bank (Asha Traders' payment only) |
Read the steps as text
- 01MessageThe payer asks their bank to payPayer → Bank Alfa (payer's bank)
Using an app or a branch, the payer gives their bank an instruction: pay this person, at that bank, this amount. Nothing has moved yet — it is only a request.
- 02ProcessingBank Alfa checks the instructionBank Alfa (payer's bank)
Is the account number valid? Is there enough money? Is anything suspicious? Banks check before they promise.
- 03PostingThe payer's balance goes downBank Alfa (payer's bank)
Bank Alfa reduces the payer's balance. Important: the payee does not have the money yet — it has only left the payer.
- DR Payer's account at Bank Alfa — EUR 200.00
- 04MessageThe instruction travels to the clearing systemBank Alfa (payer's bank) → Clearing system
Banks do not call each other one by one. They send payment messages to a shared clearing system that connects them all.
- 05Clearing obligationThe clearing system adds everything upClearing system
Thousands of payments flow both ways between the banks. The clearing system works out who owes whom overall — a tally, not yet a movement of money.
Clearing decides who owes what. Settlement — the next step — actually moves the money.
- 06SettlementThe banks settle upBank Alfa (payer's bank) → Nordbank (payee's bank)
Bank Alfa's account at the central bank goes down; Nordbank's goes up. Now — and only now — has money truly moved between the banks.
- DR Bank Alfa's account at the central bank — EUR 200.00
- CR Nordbank's account at the central bank — EUR 200.00
- 07MessageNordbank receives the detailsClearing system → Nordbank (payee's bank)
The message tells Nordbank exactly whose account to credit and with how much.
- 08PostingThe payee's balance goes upNordbank (payee's bank)
Nordbank credits the payee. The journey is complete: payer down, banks settled, payee up.
- CR Payee's account at Nordbank — EUR 200.00
You may be wondering: is the clearing system a party too? Nobody banks there.
It is a participant of a different kind — market infrastructure rather than a customer or an agent. A clearing system (like our fictional Clearing System Delta) carries messages between banks and works out what they owe each other; a settlement institution — typically the central bank, our Central Bank Omega — holds the accounts across which banks discharge those obligations. Neither serves Riya or Arjun directly. Infrastructure serves the banks; the banks serve the customers.
COMMON CONFUSION
“Meridian Bank, sitting in the middle of Asha Traders' payment, must have some relationship with Asha Traders — perhaps it even holds part of the money for them.”
Meridian Bank has never heard of Asha Traders and holds no account for them. Intermediary agents face banks, not the customers of those banks: Meridian's relationship is with Bank Alfa and with the supplier's bank, and the accounts it touches are accounts those banks hold. Each participant in the chain deals only with its immediate neighbours — which is also why fixing a stalled payment means finding which link currently holds it, not calling every name in the chain.
STRICTLY SPEAKING
Strictly speaking, the full ISO 20022 cast is larger. There is an ultimate debtor and ultimate creditor for payments made on someone else's behalf — if Asha Traders paid an invoice for its subsidiary, the subsidiary would be the ultimate debtor. Messages also name an instructing agent and instructed agent for each hop — relative labels that shift as the message moves, the way "speaker" and "listener" do in a conversation. And a role is not a licence category: whether a participant is a bank, a payment institution, or an infrastructure operator is a legal question that varies by jurisdiction.
REMEMBER IT
Anchor every role to an account: the debtor owes, the creditor is owed, and each agent is simply the bank whose books hold that party's account. If a bank in the chain holds an account for neither customer, it is an intermediary. Whose books? is the question that sorts the whole cast.
FOR NOW, REMEMBER
- Payment labels name roles, not companies — one institution can be debtor agent in the morning and intermediary by afternoon.
- ISO 20022 names the cast precisely: debtor and creditor for the customers, debtor agent and creditor agent for their banks, intermediary agent for banks in between.
- Every role anchors to a ledger: an agent is the bank whose books hold a party's account, and no bank can edit another bank's books.
- Clearing systems and settlement institutions are market infrastructure — they serve the banks, and the banks serve the customers.
TRY IT YOURSELF
In a later payment, Asha Traders pays a supplier whose bank can only be reached through Cassia Bank. Cassia holds no account for Asha Traders and none for the supplier — it holds accounts for the two banks on either side of it. In ISO 20022 role terms, Cassia Bank is the…
You can now name every player. Next, arrange them into the industry's favourite shape — the four-corner model — and see why one connection in the middle lets any bank reach every other.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
Customer, PSP, intermediary, and infrastructure roles are distinct.
- 02
The information path may include different parties from the funds path.
- 03
Role and account maps clarify ownership when payments fail.
Practical use cases / 04
Where you would use this
A business analyst draws party and account maps for a correspondent banking route.
An investigator identifies which intermediary last confirmed a payment before it stalled.
A data mapper assigns payer, beneficiary, agent, and account information to the correct fields.
Worked example / 05
Put the idea into a real situation
A retailer pays a foreign supplier. The retailer and supplier are the customer parties, while their banks provide payment services. Because the banks do not settle directly with each other, one or more correspondents support the route. A messaging network carries instructions, and account entries between institutions reflect the value transfer. The supplier's bank finally credits the supplier. This simplified example shows possible roles; not every payment needs an intermediary.
Evidence & review / 07
Evidence & review
ISO 20022 role names apply wherever ISO 20022 payment messages are used (SEPA, CBPR+, many domestic systems); the underlying role concepts are scheme- and jurisdiction-neutral.
What this brief simplifies: Presents the core five roles and defers the full party cast (ultimate parties, initiating party, instructing/instructed agents per hop) to the strictly-speaking note; treats clearing and settlement infrastructure as single generic entities.
Sources for this brief3
- Market practice
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · Debtor/creditor, agent, ultimate party, and instructing/instructed agent roles
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Market practiceMarch 2003 edition
A glossary of terms used in payments and settlement systems ↗ — CPSS (now CPMI), Bank for International Settlements · Payment system participant and market infrastructure terminology
Terminology has evolved since this edition; newer CPMI publications refine some definitions.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal · Fictional cast and two-payment scenario
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.