Compliance4 min readUpdated October 15, 2026

What Is ISO 20022?

ISO 20022 explained: first published in 2004, how to read pain.001.001.11, the pain, pacs and camt areas, and when each payment system adopted it.

Nick Bonnassies, CMO at Tagada · checked against 13 sources

Article summary

TL;DR

ISO 20022 is the international standard that financial institutions use to build their electronic messages. It gives them one dictionary of business terms and one method to turn models into XML or ASN.1 messages. ISO first published it in December 2004. SEPA, CHAPS, CHIPS, Fedwire and Swift cross-border payments now run on it.

ISO 20022 is a method and a shared dictionary, not a single file format. Its catalogue listed 802 current message definitions in October 2026.
Every message has a four-part name. In pain.001.001.11, pain is the business area, 001 the message, 001 the variant and 11 the version.
Payments use three main areas: pain (customer to bank), pacs (bank to bank) and camt (cash management, such as statements).
Adoption came system by system: mandatory for SEPA euro transfers from 2014, then T2 and CHAPS in 2023, CHIPS in 2024, Fedwire and Swift cross-border payments in 2025.
In the EU, a business that sends bundled euro transfers to its bank must use ISO 20022 XML, under the SEPA Regulation.

Want to go further? Ask

On this page

What is ISO 20022?

ISO 20022 is a multi-part international standard prepared by ISO Technical Committee 68, Financial Services. It is called the "Universal financial industry message scheme".1 It does not fix one file format. It gives the industry three things:1

a modeling method that describes business areas, transactions and message flows without tying them to a syntax,
a central dictionary of business items, such as "debtor" or "remittance information",
design rules that turn those models into XML or ASN.1 schemas.

ISO first published the standard in December 2004 (ISO 20022-1:2004).2 The current edition has nine parts, published in April 2026.1 The resulting messages sit in a public catalogue, which listed 802 current message definitions in October 2026.3

How to read an ISO 20022 message name

Every message has a four-part identifier. Take pain.001.001.11:

Part	Value	Meaning
Business area	pain	Payments Initiation3
Message number	001	CustomerCreditTransferInitiation5
Variant	001	The global message, not a restricted variant4
Version	11	Version 11 (V11)5

A business sends this message to its bank "to request movement of funds from the debtor account to a creditor", and one file can carry several transfers.5 Version 11 came from the 2020-2021 maintenance cycle.5 The catalogue now lists version 13 as current.3 A variant number other than 001 marks a restricted version of the message, for example one that drops options needing manual handling. Up to 998 variants are possible.4

The three areas you will meet in payments:3

Area	Name	Example message	Used for
pain	Payments Initiation	pain.001 CustomerCreditTransferInitiation	Customer orders transfers from its bank
pacs	Payments Clearing and Settlement	pacs.008 FIToFICustomerCreditTransfer	Bank sends the customer transfer to the next bank
camt	Cash Management	camt.053 BankToCustomerStatement	Bank sends the account statement to its customer

Who uses ISO 20022, and since when

System	ISO 20022 since
SEPA transfers and direct debits (euro)	ISO 20022 XML mandatory between banks from February 1, 20147. SEPA Credit Transfer itself went live on January 28, 20086
T2 (euro large-value payments)	March 20, 20239
CHAPS (UK)	June 19, 202310
CHIPS (US)	April 8, 2024, the first US high-value system to switch11
Fedwire Funds Service (US)	July 14, 202512
Swift cross-border payments	End of MT coexistence in November 2025: see straight-through processing

US instant rails such as FedNow also use ISO 20022 messages. For instant payments in general, see real-time payments.

Card payments are a separate world. Messages between acquirers and card issuers follow ISO 8583, "Financial transaction card originated messages".13

What it changes for an online business

Paying suppliers in euros. If you are not a consumer or a microenterprise and you send bundled transfers to your bank, the SEPA Regulation requires the ISO 20022 XML format, in practice a pain.001 file.7
Following your bank's guide. SEPA's implementation guidelines are binding supplements to its rulebook, and SEPA moved to the 2019 version of ISO 20022 on March 17, 2024.8 Build the version your bank asks for, not the latest one in the catalogue.
Matching payments. The SEPA remittance field must allow 140 characters.7 Put the invoice number there, and match incoming funds from the camt.053 statement. For what breaks automatic matching, see straight-through processing. For reading processor payouts, see how to read a merchant statement.

Updated on October 15, 2026

Nick Bonnassies

CMO at Tagada

CMO at Tagada. Before Tagada, Nick built direct-to-consumer brands that generated over $115M in sales, raised over $25M in crowdfunding and sold two of them. He also works as a fractional CMO on marketing operations and AI systems.

Frequently asked questions

What is ISO 20022 and when was it introduced?

ISO 20022 is the international standard for building financial messages: a shared dictionary of business terms plus rules to turn message models into XML or ASN.1. ISO published its first part in December 2004. The current edition has nine parts, published in April 2026.

What is pain.001.001.11?

It is version 11 of CustomerCreditTransferInitiation, the message a business sends to its bank to order one or more credit transfers. It came out of the 2020-2021 maintenance cycle. The catalogue has since moved on to version 13 (pain.001.001.13), but banks state which versions they accept in their own guides.

Is ISO 20022 used for card payments?

Card authorizations between acquirers and issuers have their own ISO standard, ISO 8583, whose latest edition dates from 2023. ISO 20022 also has card message areas, such as caaa (acceptor to acquirer) and cain (acquirer to issuer).

Which version of an ISO 20022 message should I use?

The one your bank or payment scheme asks for. Each scheme publishes implementation guidelines that pick a version and restrict the fields. SEPA, for example, moved to the 2019 version of ISO 20022 on March 17, 2024.

Sources

Checked October 15, 2026

TagadaPay

Payments that land with clean, matchable data

Tell us what you sell and how you sell it. Each application is underwritten, and approval is not guaranteed.

Apply for processing See pricing

01Tell us what you sell and how
02Underwriting reviews your business
03Process through TagadaPay alongside your other processors