The real cost of payments
Uses a hypothetical bank and transaction volumes to estimate the operating economics and potential profitability of domestic and cross-border payment services.
Topic archive
Articles
Plain-language learning briefs that route you to the key ideas, operational questions, and practical context for this part of the payment ecosystem.
21briefs indexed
Latest first
All Articles briefs
The Payment Engine Problem
Examines the practical challenges banks face when selecting, implementing, maintaining, and modernizing a payment engine.
The ISO 20022 message model
ISO 20022 is an international standard that organises financial messages around business areas, reusable data components, and a shared dictionary, giving families such as pacs, pain, and camt a common structured XML foundation.
The camt family: cash management and reporting
The camt (cash management) family reports on accounts and handles payment investigations. It includes intraday reports, end-of-day statements, entry notifications, and the cancellation-request and resolution messages used to recall payments and answer those requests.
CBPR+: ISO 20022 for cross-border payments
CBPR+ (Cross-Border Payments and Reporting Plus) is a set of usage guidelines that apply ISO 20022 to cross-border interbank payments over SWIFT, defining exactly how each message field is populated during and after the MT-to-MX transition.
Translating MT to MX
Message translation converts between legacy MT and ISO 20022 (MX) formats. It preserves core payment data but can truncate the richer structured detail that MX carries, so a full round trip does not always survive intact.
Serial and cover in ISO 20022: pacs.008 and pacs.009 COV
How cross-border payments route through correspondent banks in ISO 20022: a single pacs.008 passed bank to bank along the chain, versus a pacs.008 sent directly plus a pacs.009 COV cover message that repeats the customer details so every bank can screen the real parties.
The pain.001 payment initiation
How a customer or corporate instructs one or many credit transfers with a pain.001 message: what it carries, from the debtor and creditors to amounts and a requested execution date, and how the pain.002 status report replies.
The Business Application Header (BAH)
What the ISO 20022 Business Application Header is: a standard envelope, the head.001 message, that carries the sender, receiver, message type, and a unique business message identifier, kept separate from the message body it accompanies.
Structured remittance information
The difference between structured and unstructured remittance information in a payment: why structured references such as invoice numbers improve automatic reconciliation, and what detail can be truncated when a message is translated to a legacy MT format.
Structured and hybrid addresses in ISO 20022
ISO 20022 payments are moving postal addresses out of free-text lines into labelled fields for street, town, and country. A hybrid address keeps a structured town and country while allowing some detail on address lines during the transition.
Purpose codes in payments
Purpose codes and category-purpose codes are standard ISO 20022 external code lists that state why a payment is being made. They can influence routing, regulatory reporting, and screening, but a code is self-declared context, not proof.
High-value payments and HVPS+
High-value payment systems are usually central-bank real-time gross settlement systems that settle large payments individually and with finality. The HVPS+ (High Value Payments Plus) guidelines align how ISO 20022 messages are used across them, so a payment reads the same across borders.
Reversals, returns, recalls, and cancellations
A consolidated view of undoing a payment: rejects before settlement, returns and reversals after it, and recall requests that ask the receiving side to send funds back. Each has a different trigger, message, and outcome.
Batch and file-based payments
How bulk payments group many instructions into one file or message, using a group header and transaction counts, and how banks validate, split, and process those batches through a payment operations day.
High-value, netting, and instant settlement systems compared
A comparison of the main interbank settlement models — real-time gross settlement, deferred multilateral netting, and instant retail settlement — across speed, liquidity use, finality, and settlement risk.
Settlement through central banks
Why final settlement of interbank payments takes place in central-bank money, how direct and indirect participants are tiered, who may hold a settlement account, and why central-bank money is treated as the safest settlement asset.
Payment hub reference and standing data
Reference and standing data are the lookup tables a payment hub relies on to validate, enrich, and route payments. This article explains what they contain, how they are kept current, and why stale data causes repairs and delays.
TARGET2-Securities: DvP Settlement in Central-Bank Money
TARGET2-Securities settles the securities and cash legs of a trade together in central-bank money, applying delivery-versus-payment — the securities analogue of payment-versus-payment.
Other Payment Message Standards Beyond SWIFT
A short map of payment message families that sit outside the SWIFT world: card-transaction messaging with International Organization for Standardization (ISO) 8583, the trade-oriented UN/EDIFACT, North American ANSI ASC X12, and the United Kingdom's Bacs Standard 18 file layout.
CGI-MP: Common ISO 20022 Practice for Corporates
Common Global Implementation – Market Practice (CGI-MP) is a multi-bank forum that agrees a shared way to use ISO 20022 for corporate-to-bank messages, so a company can build one payment profile instead of a different variant for every bank.