| Field | Meaning | Required |
|---|---|---|
GrpHdr | The header of the message, holding the message identification, creation date and time, number of transactions and control sum. It identifies the file or message | M |
PmtId | The identification block holding instruction identification, end to end identification and transaction identification. End to end identification stays unchanged | M |
IntrBkSttlmAmt | The amount and currency settled between banks for this payment, for example USD 25,000. It is the amount the debtor agent transfers to the creditor agent. It ma | M |
IntrBkSttlmDt | The date on which settlement between banks takes place. It is the value date for the interbank leg and drives liquidity planning and nostro funding. The date mu | O |
SttlmInf | Information about how settlement will occur, including the settlement method, settlement account and clearing system. Values include INDA for instructed agent s | M |
Dbtr | The customer who ordered the payment, with structured name, postal address and identification. Rich debtor data supports sanctions screening and anti money laun | M |
DbtrAcct | The account of the debtor from which the payment is debited, identified by IBAN or other account identification. It links the payment to the correct customer ac | O |
DbtrAgt | The bank holding the debtor account and sending the payment instruction onward. It is identified by BIC and sometimes by name and address. The debtor agent is r | M |
CdtrAgt | The bank holding the creditor account and receiving the payment for onward credit. It is identified by BIC and sometimes by name and address. The creditor agent | M |
Cdtr | The final beneficiary of the payment, with structured name, postal address and identification. The creditor agent credits this party on receipt of funds. Comple | M |
CdtrAcct | The account of the creditor to be credited, identified by IBAN or other account identification. It tells the creditor agent exactly where to post the funds. A w | O |
ChrgsInf | Details of the charges applied to the payment, including the amount, currency, bearer and the agent that applied each charge. The bearer can be debtor, creditor | O |
Meridian Bank London sends a pacs.008.001.08 for USD 25,000 value 5 November 2026 to Harbour Bank Singapore, with a UETR, full structured debtor and creditor names and addresses, charge bearer SHAR, and remittance reference INV-1187. Harbour Bank screens the payment, credits Bright Logistics, and reports the status in a pacs.002.Valid example from the message catalogue. Scheme rules: pacs.008 is a base ISO 20022 message: the structure and fields below are the base definition, and each scheme adds or restricts elements for its rail. Under CBPR+ the message must carry a UETR for end
Market Practice: PMPG, CBPR+, SEPA, Fedwire, CHAPS and FedNow
What you will learn
Your objective. By the end of this lesson, you will be able to explain market practice: pmpg, CBPR+, SEPA, FEDWIRE, CHAPS and FEDNOW. The Payments Market Practice Group, known as the PMPG, is an industry group that writes market practice guidelines on top of the ISO 20022 standard.
Why it matters. A business analyst should treat the PMPG guidelines as requirements, because the development team will ask which practice applies, and the answer decides the field mapping.
Chapter objective: How the standard is built, read and validated in real systems
Key learning points
- Payments Market Practice Group
- Business analyst should treat the PMPG guidelines
- CBPR+ requires full debtor
- SEPA payment
- Business analyst must not copy
- US instant payment service
Key terms
Remittance information: Information that explains what a payment is for, such as invoice numbers, contract references or salary month.
Sanctions screening: Checking payment parties, countries and references against sanctions lists published by governments and international bodies.
Market practice: An agreed way of using a message standard in a particular market or community, covering field usage, codes and validation rules.
ISO 20022 XML explorer showing Market Practice: PMPG, CBPR+, SEPA, Fedwire, CHAPS and FedNow.
Practise this lesson
Exercise
Read the ISO 20022 standard message described in this lesson and identify its key parts.
Use the message structure, fields and example in this lesson.
- What to do. List the main blocks of the message, name the field that carries the amount, and name the field that identifies the payment.
Correct result. The message is made of blocks, each carrying a part of the payment instruction. The amount field and the identification field are the two a receiving bank checks first, because without them it cannot process or reconcile the payment.
Why. A message is only useful if you can read it. The blocks tell the receiving bank what to do, and the amount and identification fields are what it checks first.
Check your understanding
Practice question
Which of the following best describes market practice: pmpg, CBPR+, SEPA, FEDWIRE, CHAPS and FEDNOW?
Takeaway and next step
What to remember
A SEPA pacs.008 is therefore simpler than a CBPR+ one, because the data is standardised, the currency is always euro, and the settlement is domestic to the euro area.
Open the message type from this lesson and inspect its fields, then find the field that carries the amount.
Open the ISO 20022 Message Explorer →
Builds on "UTC Offsets and Timestamps: Why Every Time Is UTC with Offset".
Transcript and full text
Show transcript
The Payments Market Practice Group, known as the PMPG, is an industry group that writes market practice guidelines on top of the ISO 20022 standard. The standard says what is possible, and the PMPG says what banks should actually do, for example which fields are mandatory for a cross border payment, how the debtor and creditor data must be populated, and how charges and returns should be handled. The PMPG guidelines are not law, but banks follow them because a payment that ignores market practice is likely to be rejected or delayed by the next bank in the chain. A business analyst should treat the PMPG guidelines as requirements, because the development team will ask which practice applies, and the answer decides the field mapping. CBPR+ is the market practice for cross border payments and reporting on SWIFT, and it defines how pacs.008, pacs.002, pacs.004 and camt messages are used between banks. Since the coexistence period ended on 22 November 2025, cross border payments on SWIFT are ISO 20022 native, and MT messages are no longer accepted for the migrated flows. CBPR+ requires full debtor and creditor data, including names and addresses, a UETR for tracking, and a structured approach to charges and returns. A payment that met the old MT standard may fail under CBPR+, because the old format allowed truncated addresses and missing data that CBPR+ does not accept. The change is not cosmetic, it is a data quality change, and banks spent years cleaning their customer data to meet it. SEPA is the euro area market practice, and it defines how pacs.008 is used for SEPA Credit Transfer and SCT Inst. A SEPA payment uses the IBAN, a BIC that is optional in many cases, and a structured or unstructured remittance, and it settles through a SEPA clearing system. The Instant Payments Regulation, now in force, requires instant euro payments to be available, to be priced no higher than a standard credit transfer, and to include verification of payee. A SEPA pacs.008 is therefore simpler than a CBPR+ one, because the data is standardised, the currency is always euro, and the settlement is domestic to the euro area. A business analyst must not copy a CBPR+ mapping into a SEPA flow, because the mandatory fields differ. Fedwire, CHAPS and FedNow each add their own market practice on top of the same ISO 20022 base. Fedwire, the US real time gross settlement system, went live with ISO 20022 in July 2025, and it requires the full party data and the extended remittance information that US banks need for sanctions screening and reconciliation. CHIPS, the US private clearing system, migrated in April 2024, and CHAPS, the UK high value system, uses ISO 20022 with its own usage guidelines for sterling payments. FedNow, the US instant payment service, uses ISO 20022 from the start, with its own message usage rules for instant settlement. The same EUR or USD 10,000 payment will therefore carry different mandatory fields, different character sets, and different cut off rules on each rail, and the mapping must be built per rail, not once for all rails.
The Payments Market Practice Group, known as the PMPG, is an industry group that writes market practice guidelines on top of the ISO 20022 standard. The standard says what is possible, and the PMPG says what banks should actually do, for example which fields are mandatory for a cross border payment, how the debtor and creditor data must be populated, and how charges and returns should be handled. The PMPG guidelines are not law, but banks follow them because a payment that ignores market practice is likely to be rejected or delayed by the next bank in the chain. A business analyst should treat the PMPG guidelines as requirements, because the development team will ask which practice applies, and the answer decides the field mapping.
CBPR+ is the market practice for cross border payments and reporting on SWIFT, and it defines how pacs.008, pacs.002, pacs.004 and camt messages are used between banks. Since the coexistence period ended on 22 November 2025, cross border payments on SWIFT are ISO 20022 native, and MT messages are no longer accepted for the migrated flows. CBPR+ requires full debtor and creditor data, including names and addresses, a UETR for tracking, and a structured approach to charges and returns. A payment that met the old MT standard may fail under CBPR+, because the old format allowed truncated addresses and missing data that CBPR+ does not accept. The change is not cosmetic, it is a data quality change, and banks spent years cleaning their customer data to meet it.
SEPA is the euro area market practice, and it defines how pacs.008 is used for SEPA Credit Transfer and SCT Inst. A SEPA payment uses the IBAN, a BIC that is optional in many cases, and a structured or unstructured remittance, and it settles through a SEPA clearing system. The Instant Payments Regulation, now in force, requires instant euro payments to be available, to be priced no higher than a standard credit transfer, and to include verification of payee. A SEPA pacs.008 is therefore simpler than a CBPR+ one, because the data is standardised, the currency is always euro, and the settlement is domestic to the euro area. A business analyst must not copy a CBPR+ mapping into a SEPA flow, because the mandatory fields differ.
Fedwire, CHAPS and FedNow each add their own market practice on top of the same ISO 20022 base. Fedwire, the US real time gross settlement system, went live with ISO 20022 in July 2025, and it requires the full party data and the extended remittance information that US banks need for sanctions screening and reconciliation. CHIPS, the US private clearing system, migrated in April 2024, and CHAPS, the UK high value system, uses ISO 20022 with its own usage guidelines for sterling payments. FedNow, the US instant payment service, uses ISO 20022 from the start, with its own message usage rules for instant settlement. The same EUR or USD 10,000 payment will therefore carry different mandatory fields, different character sets, and different cut off rules on each rail, and the mapping must be built per rail, not once for all rails.
Full lesson text (all scenes)
Completing a lesson updates your progress dashboard on the homepage.
Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.