The pain family: payment initiation

IN ONE LINE

Analogy: a pain.001 is the order slip a customer hands across the counter — "please pay these people, these amounts, from this account." It is not the payment itself, and it never travels between banks; it goes only from the customer to their own bank.

The pain.002 is the bank's note back across the counter: "we received your order; items one to fourteen are accepted, item fifteen is refused because the account number fails its check." Everything that happens afterwards — the interbank freight, the clearing, the settlement — uses different paperwork that the customer never sees.

The order slip starts the journey; it does not make the journey.

WHAT IT ACTUALLY IS

pain stands for payment initiation: the customer-to-bank space of ISO 20022.

The two messages met most often are pain.001, the customer credit transfer initiation, and pain.002, the payment status report the bank returns.

A pain.001 can carry one payment or thousands: a group header with control totals, one or more payment information blocks (debtor account, requested execution date), and individual transactions beneath each block.

The debtor's bank validates the file, reports status via pain.002, and converts accepted instructions into interbank pacs messages.

The family also covers direct debit initiation and mandate handling, but credit transfer initiation is the usual entry point for learning it.

HOW IT WORKS

Operationally, pain.001 is corporate territory: payroll runs, supplier batches, and treasury payments submitted through online channels or host-to-host connections.

Structure matters for control: the debtor account, requested execution date, and charge instructions sit at batch level, so one file can carry several batches with different settings.

Status reporting varies more than people expect — some banks send a pain.002 per file, some per batch, some per transaction, and some only on rejection.

The status codes come from ISO code sets, but which lifecycle points trigger a report is a bank-by-bank service decision, not a standard rule.

Reconciling a submitted file against later statements relies on the end-to-end identifier the customer set on each transaction.

THE WORDS

pain family

The ISO 20022 message family used between customers and their banks to initiate payments and report what happened to them.

pain.001

The ISO 20022 message a customer sends its bank to initiate one or more credit transfers.

READ FIRST

• The ISO 20022 message model

CONNECTED TO

• FLOW SEPA Credit Transfer
• FLOW CBPR+ corporate payment — full MX lifecycle
• pain.001 pain.001 — Customer Credit Transfer Initiation
• pain.002 pain.002 — Customer Payment Status Report
• CHECKPOINT pain, pacs, and camt checkpoint
• COMPARE MX vs MT corporate payment lifecycle

SOURCES

• ISO 20022 Catalogue of messages — ISO 20022 Registration Authority
• Payments Signal editorial teaching models — Payments Signal