Resource center · Structured Data & Messaging

Message types in ISO 20022: pain, pacs and camt.

Name: Message types in ISO 20022: pain, pacs and camt
Creator: REGREP Regulatory Team
Published: 2026-03-22

Three letters, a number, and two version suffixes. Once the naming convention is clear the message set stops looking arbitrary and starts looking like a flow.

Dataset ISO 20022 · Multi-jurisdiction · message reference REGREP Regulatory Team · Reviewed 2026-06-09

Reading a message identifier

An identifier such as pacs.008.001.08 has four parts: the business area, the message number within it, the variant, and the version. The business area tells you who is talking to whom. The number identifies the message. The variant is almost always the base one. The version is the part that changes over time, and the part a scheme pins.

Version is not a detail. Two parties can agree on the message and still fail, because a scheme mandates one version and a counterparty implements another. Always record the full identifier including the version, never just the three-letter group and number.

Payments initiation

pain — between a customer and their bank
Message	Purpose
pain.001	Customer credit transfer initiation — the instruction to move funds. The entry point for most corporate payment flows.
pain.002	Customer payment status report — the bank’s acceptance or rejection returned to the initiating party.
pain.008	Customer direct debit initiation — the collection instruction.

Clearing and settlement

pacs — between financial institutions
Message	Purpose
pacs.008	Financial institution to financial institution customer credit transfer — the interbank leg of a customer payment.
pacs.002	Payment status report between institutions — acceptance, rejection or pending status.
pacs.004	Payment return — funds sent back where the original could not be applied.
pacs.009	Financial institution credit transfer — bank to bank, with no underlying customer instruction.

Cash management

camt — reporting and investigation
Message	Purpose
camt.052	Bank to customer account report — intraday movement.
camt.053	Bank to customer statement — the end-of-day statement.
camt.054	Bank to customer debit or credit notification — advice of an individual entry.
camt.056	Request to cancel a payment.

How they fit together

A single customer credit transfer typically touches all three groups in sequence: the originator sends an initiation message to its bank; the bank returns a status report; the bank constructs an interbank message and sends it into the clearing infrastructure; the beneficiary bank notifies its customer of the credit; and both parties receive an end-of-day statement carrying the entry. The exception path uses the same groups — returns, cancellation requests and investigation messages — and is where most operational cost accumulates, because it is the part implementations tend to leave manual.

The identifier assigned by the originator at the start is intended to appear in the statement entry at the end. If it does not, something in the chain regenerated it.

Using this reference safely

The scheme decides. Which messages are permitted, in which versions, with which elements mandatory, is set by the scheme or market infrastructure usage guidelines — not by the standard alone.
Versions move. Record the full identifier including variant and version in any specification or interface agreement.
This is a subset. The standard covers business areas well beyond payments, and the payment groups contain more messages than the common ones shown here.

Official sources

Primary instruments only. Each is named in full so the reference remains traceable even if a link moves.

ISO 20022 — message definitions and the message identifier convention, maintained by the registration authorityISO · the authoritative catalogue of message definitions
Regulation (EU) No 260/2012 establishing technical and business requirements for credit transfers and direct debits in euroEUR-Lex · Regulation · the standard’s role in euro payments
The applicable scheme rulebook and implementation guidelinesScheme · permitted messages, versions and mandatory elements

REGREP is an independent software provider. This record explains a reporting framework in plain language and is not legal, tax or regulatory advice. Confirm scope, thresholds and submission dates with your competent authority before you file.

At a glance

Naming: A four-letter business area, a message number, a variant and a version.
pain: Payments initiation — between a customer and their bank.
pacs: Payments clearing and settlement — between financial institutions.
camt: Cash management — reporting, statements and investigations.
Caution: Scheme usage guidelines constrain which messages and versions are permitted. This sheet is orientation, not a scheme specification.