Payments Training Hub
FieldMeaningRequired
GrpHdrThe header of the message, holding the message identification, creation date and time, number of transactions and control sum. It identifies the file or messageM
PmtIdThe identification block holding instruction identification, end to end identification and transaction identification. End to end identification stays unchangedM
IntrBkSttlmAmtThe 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 maM
IntrBkSttlmDtThe 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 muO
SttlmInfInformation about how settlement will occur, including the settlement method, settlement account and clearing system. Values include INDA for instructed agent sM
DbtrThe customer who ordered the payment, with structured name, postal address and identification. Rich debtor data supports sanctions screening and anti money launM
DbtrAcctThe 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 acO
DbtrAgtThe 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 rM
CdtrAgtThe 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 agentM
CdtrThe final beneficiary of the payment, with structured name, postal address and identification. The creditor agent credits this party on receipt of funds. CompleM
CdtrAcctThe 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 wO
ChrgsInfDetails of the charges applied to the payment, including the amount, currency, bearer and the agent that applied each charge. The bearer can be debtor, creditorO
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

0:00 / 3:14 Step 1 of 5

Interbank Space: pacs.008, pacs.002 and pacs.004 Step by Step

SEPA Credit Transfer Deep Dive, Lesson 4 of 7, Narration 3:14, D05 Domestic payment systems

Charge bearerSettlementValue date

What you will learn

Your objective. By the end of this lesson, you will be able to explain interbank space: pacs.008, pacs.002 and pacs.004. Once Meridian Bank Paris has debited the Loire Components account, it builds the pacs.008.001.08 Customer Credit Transfer message for the interbank leg.

Why it matters. The pacs.008 message and the settlement are separate things, and a business analyst must keep them separate in any design.

Chapter objective: Message flows, exchange periods and the 2024 transition

Key learning points

  • Once Meridian Bank Paris has debited
  • Instructed amount
  • Clearing system calculates what each bank owes
  • Credit EUR 48,250 to Rhine Metals
  • Suppose the Rhine Metals account

Key terms

Charge bearer: A code that states who pays the charges for a payment. In ISO 20022 the values are DEBT for debtor, CRED for creditor, SHAR for shared and SLEV for service level.

Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.

Value date: The date on which funds become available to the beneficiary and on which interest starts to accrue. It is the date used for settlement and for nostro posting.

ISO 20022 XML explorer showing Interbank Space: pacs.008, pacs.002 and pacs.004 Step by Step.

Practise this lesson

Exercise

Read the pacs.008 message described in this lesson and identify its key parts.

Use the message structure, fields and example in this lesson.

  1. What to do. List the three levels of the message and name the field that carries the amount and the field that carries the end-to-end reference.

Correct result. The amount is carried in the instructed amount element and the reference in the end-to-end identification. The three levels are the group header, the payment information, and the credit transfer transaction information.

Why. A message is only useful if you can read it. The group header identifies the message, the payment information identifies the batch, and the transaction information carries the single payment.

Check your understanding

Practice question

Which of the following best describes interbank space: pacs.008, pacs.002 and pacs.004?

Takeaway and next step

What to remember

The pacs.008 copies the debtor, creditor, amount, currency, and end to end identification from the pain.001, and it adds interbank fields that the customer never sees.

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 "Customer to Bank Space: pain.001, pain.002 and the Exchange Periods".

Transcript and full text

Show transcript

Once Meridian Bank Paris has debited the Loire Components account, it builds the pacs.008.001.08 Customer Credit Transfer message for the interbank leg. The pacs.008 copies the debtor, creditor, amount, currency, and end to end identification from the pain.001, and it adds interbank fields that the customer never sees. Those fields include the debtor agent, Meridian Bank Paris, the creditor agent, Harbour Bank Frankfurt, the settlement method, the clearing system reference, the interbank settlement date, and the charge bearer. The instructed amount is EUR 48,250, and the interbank settlement amount is the same, because this is a single currency SEPA payment with shared charges. The pacs.008 is sent into the clearing system during the next exchange period, and the clearing system routes it to Harbour Bank Frankfurt. Settlement of the obligation between the two banks happens through central bank money, usually on a net basis across many payments in the same exchange period. Meridian Bank Paris does not send EUR 48,250 directly to Harbour Bank Frankfurt as a single wire. Instead, the clearing system calculates what each bank owes the others after netting all payments in the period, and the net amounts settle on central bank accounts. The pacs.008 message and the settlement are separate things, and a business analyst must keep them separate in any design. Harbour Bank Frankfurt receives the pacs.008 and runs its own checks before crediting Rhine Metals. It validates the message structure, checks the creditor IBAN against the account it holds, screens the payment for sanctions, and confirms that the account is open and able to receive funds. If the checks pass, it credits EUR 48,250 to the Rhine Metals account on the value date of Tuesday 10 November 2026, and it records the credit with the end to end identification LOIRE-RHINE-2026-1148. It then sends a pacs.002.001.10 Payment Status Report back to Meridian Bank Paris with status ACCP, confirming that the payment was accepted for customer payment. ACCP does not mean the beneficiary account was credited; the status that confirms settlement completion is ACSC, and the status that confirms the creditor account was credited is ACCC. Source: ISO 20022 pacs.002.001.10 transaction status code set. A pacs.004 Payment Return is the message that sends funds back when the beneficiary bank cannot credit the payment. Suppose the Rhine Metals account had been closed the week before the payment arrived. Harbour Bank Frankfurt could not credit EUR 48,250, so it would return the funds with a pacs.004.001.09 message, carrying the original end to end identification, the returned amount, and a reason code such as AC04 for a closed account. The pacs.004 is a separate settlement instruction, not a copy of the pacs.008, and it moves the money back through the clearing system to Meridian Bank Paris, which then credits Loire Components and reports the return in a pain.002 message. Worked example with numbers: Meridian Bank Paris debits the Loire Components account for EUR 48,250 and builds a pacs.008.001.08 for the interbank leg, copying the debtor, creditor, amount, currency and end to end identification from the pain.001, and adding the interbank settlement date and the settlement method. The pacs.008 travels through the clearing system to Harbour Bank Frankfurt, and the obligation between the two banks settles through central bank money on a net basis across many payments in the same exchange period. Harbour Bank receives the pacs.008, validates it, and sends a pacs.002.001.10 reporting ACCP, then ACSC when the settlement is complete, and finally ACCC when the Rhine Metals account is credited for EUR 48,250 in full. Failure and recovery: the interbank leg fails when the pacs.008 is rejected, when the beneficiary account cannot be credited, or when the settlement fails. If Harbour Bank cannot find the Rhine Metals account, it returns the payment with a pacs.004 carrying reason code AC01, and Meridian Bank must tell Loire Components that the payment has come back. If the clearing system cannot settle the net obligation because a bank is short of funds, the payment waits in a queue until liquidity arrives, and the value date may slip to the next business day. The recovery for a return is a corrected instruction with the right IBAN, and the recovery for a settlement delay is a liquidity transfer, but both cost time, and the customer must be told the new credit date. For a business analyst, product owner or subject matter expert, the interbank requirement must state the status codes correctly, ACCP means accepted for processing, ACSC means settlement is complete, and ACCC means the creditor account is credited, because confusing them is the most common error in status reporting. The requirement must name the messages on the interbank leg, pacs.008 out, pacs.002 for the status, and pacs.004 for a return, and must state that the beneficiary is credited in full. The test pack must include a payment that is rejected, a payment that is returned for a closed account, and a payment that queues for liquidity, because each case exercises a different status path. Source: EPC SCT Rulebook 2025 version 1.1; ISO 20022 pacs.002.001.10; last reviewed 7 November 2026.

Once Meridian Bank Paris has debited the Loire Components account, it builds the pacs.008.001.08 Customer Credit Transfer message for the interbank leg. The pacs.008 copies the debtor, creditor, amount, currency, and end to end identification from the pain.001, and it adds interbank fields that the customer never sees. Those fields include the debtor agent, Meridian Bank Paris, the creditor agent, Harbour Bank Frankfurt, the settlement method, the clearing system reference, the interbank settlement date, and the charge bearer. The instructed amount is EUR 48,250, and the interbank settlement amount is the same, because this is a single currency SEPA payment with shared charges.

The pacs.008 is sent into the clearing system during the next exchange period, and the clearing system routes it to Harbour Bank Frankfurt. Settlement of the obligation between the two banks happens through central bank money, usually on a net basis across many payments in the same exchange period. Meridian Bank Paris does not send EUR 48,250 directly to Harbour Bank Frankfurt as a single wire. Instead, the clearing system calculates what each bank owes the others after netting all payments in the period, and the net amounts settle on central bank accounts. The pacs.008 message and the settlement are separate things, and a business analyst must keep them separate in any design.

Harbour Bank Frankfurt receives the pacs.008 and runs its own checks before crediting Rhine Metals. It validates the message structure, checks the creditor IBAN against the account it holds, screens the payment for sanctions, and confirms that the account is open and able to receive funds. If the checks pass, it credits EUR 48,250 to the Rhine Metals account on the value date of Tuesday 10 November 2026, and it records the credit with the end to end identification LOIRE-RHINE-2026-1148. It then sends a pacs.002.001.10 Payment Status Report back to Meridian Bank Paris with status ACCP, confirming that the payment was accepted for customer payment. ACCP does not mean the beneficiary account was credited; the status that confirms settlement completion is ACSC, and the status that confirms the creditor account was credited is ACCC. Source: ISO 20022 pacs.002.001.10 transaction status code set.

A pacs.004 Payment Return is the message that sends funds back when the beneficiary bank cannot credit the payment. Suppose the Rhine Metals account had been closed the week before the payment arrived. Harbour Bank Frankfurt could not credit EUR 48,250, so it would return the funds with a pacs.004.001.09 message, carrying the original end to end identification, the returned amount, and a reason code such as AC04 for a closed account. The pacs.004 is a separate settlement instruction, not a copy of the pacs.008, and it moves the money back through the clearing system to Meridian Bank Paris, which then credits Loire Components and reports the return in a pain.002 message.

Worked example with numbers: Meridian Bank Paris debits the Loire Components account for EUR 48,250 and builds a pacs.008.001.08 for the interbank leg, copying the debtor, creditor, amount, currency and end to end identification from the pain.001, and adding the interbank settlement date and the settlement method. The pacs.008 travels through the clearing system to Harbour Bank Frankfurt, and the obligation between the two banks settles through central bank money on a net basis across many payments in the same exchange period. Harbour Bank receives the pacs.008, validates it, and sends a pacs.002.001.10 reporting ACCP, then ACSC when the settlement is complete, and finally ACCC when the Rhine Metals account is credited for EUR 48,250 in full.

Failure and recovery: the interbank leg fails when the pacs.008 is rejected, when the beneficiary account cannot be credited, or when the settlement fails. If Harbour Bank cannot find the Rhine Metals account, it returns the payment with a pacs.004 carrying reason code AC01, and Meridian Bank must tell Loire Components that the payment has come back. If the clearing system cannot settle the net obligation because a bank is short of funds, the payment waits in a queue until liquidity arrives, and the value date may slip to the next business day. The recovery for a return is a corrected instruction with the right IBAN, and the recovery for a settlement delay is a liquidity transfer, but both cost time, and the customer must be told the new credit date.

For a business analyst, product owner or subject matter expert, the interbank requirement must state the status codes correctly, ACCP means accepted for processing, ACSC means settlement is complete, and ACCC means the creditor account is credited, because confusing them is the most common error in status reporting. The requirement must name the messages on the interbank leg, pacs.008 out, pacs.002 for the status, and pacs.004 for a return, and must state that the beneficiary is credited in full. The test pack must include a payment that is rejected, a payment that is returned for a closed account, and a payment that queues for liquidity, because each case exercises a different status path. Source: EPC SCT Rulebook 2025 version 1.1; ISO 20022 pacs.002.001.10; last reviewed 7 November 2026.

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.