SEPA / Learning brief
SEPA Payment Messages
Your notes
In simple terms / 01
What this means in plain language
Introduces the ISO 20022 pain, pacs, and camt message families and explains how SEPA schemes adapt them for euro payments.
SEPA processes use selected ISO 20022 messages under scheme-specific rules. The pain family generally supports exchanges involving customers and their banks, such as initiation or customer status. The pacs family supports financial-institution payment and settlement exchanges. The camt family supports cash-management reporting, notifications, and investigations. A message name alone is not enough to implement a service: teams must also use the applicable scheme guidance, field rules, identifiers, and process states. Mapping the families to business events makes complex XML structures easier to understand and test.
Complete lesson / 02
Understand the full idea, step by step
Say the word SEPA and it is tempting to imagine one machine humming somewhere in Europe. There is no such machine. SEPA is an area and a family of schemes, and the messages that run across it are ISO 20022 messages you have already begun to meet. This lesson lines up the three families around a single euro payment.
SEPA is an area plus schemes, not one system
The Single Euro Payments Area (SEPA) is a geography of countries where euro payments follow common rules. Those rules come as schemes — rulebooks published by the European Payments Council (EPC), such as the SEPA Credit Transfer. A scheme is not a machine: it says how participants must behave. Clearing and settlement run on separate infrastructures underneath. What the schemes share is a common message language — ISO 20022 — adapted for euro payments by SEPA implementation guidelines.
The three ISO 20022 families SEPA uses
SEPA leans on three business areas, each for a different leg. pain (payment initiation) is customer-to-bank: the instruction and its status reply. pacs (payments clearing and settlement) is interbank: the messages banks exchange to carry and settle a payment. camt (cash management) is reporting and investigation: statements, notifications, and the messages used to query or recall. Learn them by the conversation each holds — customer↔bank, bank↔bank, bank↔account-holder — not as isolated names.
Following the event across the families
- INSTRUCTION
Asha Traders sends a pain.001 to Bank Alfa requesting the payment. Bank Alfa replies with a pain.002 status. (pain — customer to bank.)
- MESSAGE
Bank Alfa creates an interbank pacs.008 and sends it, via the clearing and settlement mechanism, toward Nordbank. (pacs — bank to bank.)
- VALIDATION
Nordbank answers with a pacs.002 status — accepted or rejected — back along the interbank chain. (pacs, again — the status reply.)
- NOTIFICATION
Next morning, Bank Alfa sends Asha Traders a camt.053 statement; the debit is there to reconcile. (camt — reporting.)
Read the steps as text
- 01MessageThe debtor initiates the transferDebtor (payer) → Bank Alfa (debtor agent) · pain.001
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.
- 02ProcessingBank Alfa validates the instructionBank Alfa (debtor agent)
The debtor agent checks the format, the IBAN, available funds, and runs compliance screening before accepting the instruction for execution.
Screening checkpoint: Debtor-agent transaction screening — Names and remittance data are screened against sanctions lists before the payment goes interbank.
- 03PostingThe debtor's account is debitedBank Alfa (debtor agent)
Once accepted, Bank Alfa books the debit. The customer's money has left their account, but no money has yet moved between banks.
- DR Debtor's current account at Bank Alfa — EUR 12,500.00
- 04MessageBank Alfa submits the interbank transferBank Alfa (debtor agent) → Clearing & settlement mechanism · pacs.008
The debtor agent converts the customer instruction into an interbank pacs.008 and submits it to the clearing and settlement mechanism.
- 05Clearing obligationThe CSM calculates positionsClearing & 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.
- 06SettlementPositions settle in central bank moneyBank Alfa (debtor agent) → Nordbank (creditor agent)
The calculated positions settle across the banks' settlement accounts at the central bank. Only now has money finally moved between Bank Alfa and Nordbank.
- DR Bank Alfa settlement account — EUR 12,500.00
- CR Nordbank settlement account — EUR 12,500.00
- 07MessageThe CSM delivers the transfer to NordbankClearing & settlement mechanism → Nordbank (creditor agent) · pacs.008
The creditor agent receives the pacs.008 with full payment details so it can credit the right account.
- 08ProcessingNordbank validates and screens the incoming paymentNordbank (creditor agent)
The creditor agent checks that the account exists and can be credited, and runs its own sanctions screening on the incoming payment.
Screening checkpoint: Creditor-agent inbound screening — The receiving bank screens independently — it cannot rely on the sender's screening alone.
- 09PostingThe creditor's account is creditedNordbank (creditor agent)
Nordbank credits the beneficiary. The transfer is complete end to end: customer debited, banks settled, beneficiary credited.
- CR Creditor's current account at Nordbank — EUR 12,500.00
| Family | Between | Carries |
|---|---|---|
| pain | Customer and their bank | The initiation request and its status reply |
| pacs | Bank and bank | The interbank instruction, settlement information, and status |
| camt | Bank and account holder (and bank to bank for recalls) | Statements, notifications, and investigations |
COMMON CONFUSION
“The message names are the payment — send the pacs.008 and the euros travel inside it.”
Message names label business exchanges; they do not move value. A pacs.008 tells Nordbank what is required; the euros move only when balances change and the banks settle between themselves. Reading a family name tells you which conversation you are in, not that money has arrived.
STRICTLY SPEAKING
Strictly speaking, SEPA does not use raw ISO 20022 messages — it uses them as narrowed by EPC rulebooks and their implementation guidelines, which fix mandatory fields, allowed values, and the R-transaction messages for returns and recalls. Different schemes (standard and instant) and different clearing mechanisms sit underneath the same family names. Confirm the current rulebook and guideline for the scheme in question before relying on any field rule.
FOR NOW, REMEMBER
- SEPA is an area plus a family of EPC schemes, not a single system; clearing and settlement run on infrastructures underneath the rulebooks.
- Three ISO 20022 families do the work: pain (customer↔bank), pacs (bank↔bank), camt (reporting and investigation).
- Follow a payment as an event and each message falls into place: pain.001/002, then pacs.008/002, then a camt statement.
- The names label conversations; value moves through postings and settlement, not inside the messages.
TRY IT YOURSELF
Asha Traders' accountant wants to confirm, the morning after, that yesterday's EUR 12,400.00 debit actually posted to the account. Which ISO 20022 family answers that, and why?
You have placed camt at the end of the flow as the reporting family. It does more than report — it also carries recalls and investigations. That double life is the next lesson.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
Pain, pacs, and camt serve different communication contexts.
- 02
SEPA rules specialize the broader ISO 20022 definitions.
- 03
Business events should drive message selection and field mapping.
Practical use cases / 04
Where you would use this
A corporate channel accepts a pain initiation and shows the resulting customer status.
A bank gateway validates a pacs payment before routing it to a SEPA mechanism.
A reconciliation team uses camt reporting to match account movements with processed instructions.
Worked example / 05
Put the idea into a real situation
A company submits a payment file to its bank using a customer initiation message. After validation, the bank creates the appropriate interbank payment for the chosen SEPA route. Later, account reporting helps the company reconcile debits and outcomes. The business event changes at each boundary, so the message family changes too. This illustration shows the relationship between families; exact message variants and reporting choices depend on the bank and scheme implementation.
Evidence & review / 07
Evidence & review
SEPA euro-area schemes and their ISO 20022 usage; field rules are set by the EPC rulebook and implementation guideline version in force.
What this brief simplifies: Shows one representative message per leg rather than every exchange (e.g. R-transactions); maps families to conversations as a teaching model.
Sources for this brief4
- Scheme-specific rule2025 version 1.1 (EPC125-05)
2025 SEPA Credit Transfer rulebook ↗ — European Payments Council · SEPA Credit Transfer scheme
Version 1.1 replaced version 1.0 at publication on 5 October 2025 and is stated to remain in effect up to 21 November 2027. It moves the date from which the unstructured address format is no longer permitted to 15 November 2026.
- Scheme-specific rule2025 version 1.0 (EPC115-06)
SEPA Credit Transfer Inter-PSP Implementation Guidelines ↗ — European Payments Council · SEPA ISO 20022 implementation guidelines
Based on version 1.1 of the 2025 SCT rulebook. Companion Customer-to-PSP guidelines cover the pain.001 initiation leg.
- Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pain, pacs, camt business areas
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.