GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
03 / PAYMENTS FOUNDATIONS11 MIN

The parties in a payment

Debtor, creditor, and their agents: the standard names for everyone in a payment, and why precise role names prevent expensive confusion.

NOT STARTED

L0 Explain simply

Every payment has a cast: the person paying, the person being paid, and the institutions acting for each of them. Analogy: sending a parcel. You are the sender, your friend is the recipient. You hand the parcel to your local courier depot, and a depot near your friend delivers it. Sometimes a sorting hub in between passes it along. Payments work the same way: your bank — or, more generally, your payment service provider — acts for you, the receiver's institution acts for them, and sometimes an institution in the middle connects the two. The industry uses precise names for these roles because 'the bank' is dangerously vague when four or five institutions touch one payment — and a mistake about who plays which role sends money, and blame, to the wrong place.

L1 Core concepts

The standard vocabulary comes in pairs. The debtor is the party whose account is debited; the creditor is the party whose account is credited. The debtor agent is the institution servicing the debtor's account; the creditor agent services the creditor's account. Agents are payment service providers — banks most often, but in many jurisdictions also licensed non-bank institutions. When the two agents have no direct relationship, one or more intermediary agents sit between them and pass the payment along. These role names are anchored in the ISO 20022 data model, which is why they appear identically across schemes, formats, and this academy. Older message formats use different words — ordering customer, beneficiary — for the same underlying roles.

L2 Practitioner view

Role precision is operational, not academic. Screening systems check every party in a payment, so a name placed in the wrong field can trigger a false alert or, worse, mask a true one. Investigators chasing a missing payment must know which agent to contact — asking the creditor agent about a payment stuck at an intermediary wastes days. Two roles change with perspective: at any single hop, the instructing agent is the institution sending the message and the instructed agent is the one receiving it, so the same bank is instructed on one leg and instructing on the next. Ops teams live in this hop-by-hop view. Note also that one institution can be debtor agent in the morning and intermediary agent in the afternoon — roles belong to payments, not to institutions.

L3 Technical details

In ISO 20022 payment messages the roles are explicit elements: Dbtr, Cdtr, DbtrAgt, CdtrAgt, InstgAgt, InstdAgt, plus intermediary agent slots in the interbank pacs.008. Agents are identified primarily by BIC, and account-holding parties by account identifiers such as IBAN where the scheme uses them. The MT world spreads the same cast across numbered fields: the ordering customer in field 50a, the beneficiary customer in field 59a, the ordering institution in 52a, and the account-with institution in 57a of an MT103. Mapping between the two vocabularies is a routine — and error-prone — part of translation work, which is why investigations often begin by tabulating which party landed in which element on each leg of the chain.

SEE THE PAYMENT MOVE

A simple domestic transfer — swimlane diagramOne person pays another at a different bank in the same country. The simplest complete journey: instruct, check, move the message, move the money, credit. The full step-by-step description follows this diagram as text.
MESSAGECLEARING OBLIGATIONSETTLEMENTPOSTING
A simple domestic transfer. A deliberately generic domestic scheme. Real systems (instant rails, batch ACH, RTGS) differ in timing and mechanics — later topics cover those differences. PLAY IT STEP BY STEP →
Read the steps as text
  1. 01Message
    The 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.

  2. 02Processing
    Bank 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.

  3. 03Posting
    The 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 AlfaEUR 200.00
  4. 04Message
    The 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.

  5. 05Clearing obligation
    The 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.

  6. 06Settlement
    The 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 bankEUR 200.00
    • CR Nordbank's account at the central bankEUR 200.00
  7. 07Message
    Nordbank receives the detailsClearing system → Nordbank (payee's bank)

    The message tells Nordbank exactly whose account to credit and with how much.

  8. 08Posting
    The 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 NordbankEUR 200.00
Sources for this topic2
  1. Official requirement

    ISO 20022 Catalogue of messagesISO 20022 Registration Authority · payment party and agent role definitions

    Defines the current versions of all ISO 20022 message definitions, including the pain, pacs, and camt messages taught on this site. · Checked 2026-07-12

    Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.

  2. Simplified educational illustration

    Payments Signal editorial teaching modelsPayments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    What this simplifies: The four-party diagram in the linked flow shows one debtor agent, one creditor agent, and at most one intermediary; real chains can involve more agents and the same institution in multiple roles.

    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.

Deepest material on this page: L3 Technical details. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.