The payment lifecycle
From capture to confirmation: the stages every payment passes through, and where clearing and settlement fit in the journey.
L0 Explain simply
A payment is a journey with checkpoints, not a single event. Analogy: an online order. You place the order (the payment is captured), the shop checks stock and your details (validation), the warehouse hands it to a courier network that agrees the delivery details (the banks exchange and confirm what is owed), the courier delivers (the money actually moves), and you get a confirmation. Two checkpoints matter most and are easy to confuse: agreeing exactly what is owed between the banks, and actually handing over the money. The first is called clearing, the second settlement. Your app may say 'sent' long before the last checkpoint is reached — which is why 'where is my payment?' is rarely a one-word answer.
L1 Core concepts
The lifecycle runs: initiation — the debtor's instruction is captured through a channel; validation — format, account, and balance checks; risk controls — sanctions screening and fraud checks; clearing — the instruction is exchanged between the institutions involved, reconciled, and the resulting obligations are established, sometimes netted across many payments; settlement — the obligation is discharged by transferring funds, for interbank payments usually in central bank money; and posting and confirmation — the creditor's account is credited and both customers can be told. Clearing establishes who owes what; settlement pays it. On some rails the stages take seconds, on others days — but the sequence is recognizably the same everywhere.
L2 Practitioner view
Operations teams experience the lifecycle as statuses and queues inside a payment engine: captured, validated, released, sent, settled, confirmed — names differ by institution. Each stage has a queue that can back up, and cut-off times decide whether an instruction makes today's clearing cycle or waits. Most volume is straight-through processing; the exceptions define the workload. A validation failure becomes a repair item, a screening hit becomes an alert to investigate, a reject from the other side arrives after 'sent' and must be matched back to the original. A useful habit: for any incident, first establish which stage the payment last completed — the answer determines who can still act, whether funds are at risk, and what the customer should be told.
L3 Technical details
Each lifecycle stage has message families attached. Initiation from a corporate customer typically arrives as a pain.001 credit-transfer initiation; the interbank clearing leg is carried by pacs.008 (or an MT103 on the older correspondent rail); status flows back as pacs.002; a payment that settled but must come back travels as a pacs.004 return. End-to-end tracking hangs on identifiers that survive every hop — notably the UETR, a unique end-to-end transaction reference carried unchanged across the chain. The clean mapping of one stage to one message is a simplification, though: on-us payments may skip interbank messaging entirely, and instant rails compress clearing and settlement into a single timed exchange. The message references in this academy show each format field by field.
SEE THE PAYMENT MOVE
Read the steps as text
- 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
- 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
- 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
Sources for this topic2
- Market practiceMarch 2003 edition
A glossary of terms used in payments and settlement systems ↗ — CPSS (now CPMI), Bank for International Settlements · definitions of clearing and settlement
Terminology has evolved since this edition; newer CPMI publications refine some definitions.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The staged lifecycle model is our teaching construction: real payment engines use institution-specific stage names, may merge or reorder stages, and on-us or instant payments skip some stages entirely.
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.