Fetching this page. The payment is mid-rail.
Follow real payment journeys step by step, decode the messages that carry them, trigger the exceptions, investigate screening alerts — and trace every claim to the standard behind it. From your first transfer to implementation depth.
The customer instructs their bank to pay. A corporate typically sends a pain.001 file; a retail customer uses a banking channel that creates the same instruction internally.
The debtor agent checks the format, the IBAN, available funds, and runs compliance screening before accepting the instruction for execution.
Once accepted, Bank Alfa books the debit. The customer's money has left their account, but no money has yet moved between banks.
Money, accounts, ledgers, the people and institutions in every payment, and the lifecycle an instruction follows from capture to posting.
EXPLORE TOPIC →How obligations between banks are calculated and how they are finally discharged — gross versus net, RTGS versus deferred settlement, and the liquidity that makes it work.
EXPLORE TOPIC →The SWIFT network, BICs, the MT message family, and how correspondent banks route customer and institution transfers serially or with cover.
EXPLORE TOPIC →What sanctions are, who imposes them, what obligations they create, and how sanctions screening differs from AML monitoring and fraud detection.
EXPLORE TOPIC →Annotated MT103, pain.001, pacs.008, pacs.002, and camt.056 samples — click any field to see what it means, who owns it, and how it goes wrong.
OPEN MESSAGE LAB →EXCEPTION LABRejects, returns, recalls, timeouts, and holds — each one answers where the money is, whether settlement happened, and who acts next.
OPEN EXCEPTION LAB →SCREENING LABFully fictional cases from alert to disposition: see why the name matched, which evidence mattered, and how analysts document decisions.
OPEN SCREENING LAB →A resident individual in India sends dollars to a friend's US account: Form A2 and the Liberalised Remittance Scheme, currency conversion at the sending bank, and a serial MT103 that carries both currencies through one US correspondent to the beneficiary's bank.
Every ISO 20022 payment carries two kinds of metadata: coded fields that declare what the payment is — service level, local instrument, category purpose, purpose — and an agent chain that names who moves it, bank by bank. This article reads a fictional pacs.008 field by field: what each code means, why there are four purpose-ish fields and not one, and how the instructing, previous-instructing, intermediary and reimbursement agents thread a payment across borders.
The move from MT to ISO 20022 is a dated schedule, not a single switch: CBPR+ coexistence from March 2023, CHIPS in 2024, Fedwire's cut-over on 14 July 2025, the end of cross-border MT coexistence in November 2025, mandatory structured or hybrid addresses from 15 November 2026, and later statement-message retirements through 2027-2028.
The debtor agent converts the customer instruction into an interbank pacs.008 and submits it to the clearing and settlement mechanism.
The CSM validates the message and includes it in a clearing cycle. Each participant's obligations are calculated — this creates who-owes-whom, not yet a movement of money.
Clearing produces obligations. The banks do not have their money yet — that only happens at settlement.
The calculated positions settle across the banks' settlement accounts at the central bank. Only now has money finally moved between Bank Alfa and Nordbank.
The creditor agent receives the pacs.008 with full payment details so it can credit the right account.
The creditor agent checks that the account exists and can be credited, and runs its own sanctions screening on the incoming payment.
Nordbank credits the beneficiary. The transfer is complete end to end: customer debited, banks settled, beneficiary credited.
Uses a hypothetical bank and transaction volumes to estimate the operating economics and potential profitability of domestic and cross-border payment services.
Examines the practical challenges banks face when selecting, implementing, maintaining, and modernizing a payment engine.
Maps the main SEPA Instant exception flows, including pacs.002 rejections, camt.056 recall requests, and pacs.004 returns.