pacs.008 ISO 20022 message

Published on

15/12/2023

Updated on

30/09/2026

Reading time

2 min

As of 30 September 2026

Definition

The pacs.008 (FIToFICustomerCreditTransfer) is the ISO 20022 message that carries a credit transfer between payment service providers. It holds the payment itself: amount, parties, accounts and remittance information.

It is often confused with the pain.001. The difference is the leg: the pain.001 is the customer’s instruction to their bank, the pacs.008 the handover between the institutions. Both describe the same payment, but from a different perspective and in different fields.

The path of a payment

As a rule the pacs.008 does not travel directly from bank to bank, but through a clearing and settlement system (the Bundesbank’s SEPA-Clearer, EBA Clearing, T2/RTGS or TIPS, for example). The message therefore appears twice: once on submission, once on delivery.

DebtorDebtor BankSEPA-ClearerCreditor BankCreditorpain.001pacs.008pacs.008camt.053The debtor instructs their bank with a pain.001.The debtor bank submits the payment to the clearing system as a pacs.008.The clearing system delivers it to the creditor bank – again as a pacs.008.The creditor bank credits the account and reports it in the camt.053.

The four environments

The same message is used in four environments, under different rules. All four currently use the same version from the ISO maintenance release 2019; versions are carried forward with the annual maintenance releases, and for T2 a change is envisaged no earlier than November 2027.

FeatureSEPA SCTSEPA SCT InstT2 / RTGSSwift CBPR+
Message versionpacs.008.001.08pacs.008.001.08pacs.008.001.08pacs.008.001.08
Transmissionbulk or single items via the SEPA-Clearer or another clearing systemsingle payment via TIPS or RT1single payment between central bank accountssingle payment over the Swift network
Currencyeuroeuroeuroany
Amount limitno scheme limitno scheme limitnonenone
Timingforwarding by the following business day at the latestfive seconds target, time-out after sevensettlement in real time during the business dayno requirement in the rulebook
Status messagepacs.002 only where the payment is rejectedpacs.002 in every case, positive (ACCP) or negative (RJCT)pacs.002 on the payment orderRJCT mandatory, positive statuses agreed bilaterally
Recallcamt.056, answered by pacs.004 or camt.029camt.056, answered by pacs.004 or camt.029camt.056camt.056, answered by pacs.004 or camt.029

Related messages

The pacs.008 is the original message that the R-transactions refer back to:

  • camt.056 – recall request from the debtor bank
  • pacs.004 – return of the money where the recall is accepted or the credit cannot be made
  • camt.029 – answer to the recall where no money flows back
  • pacs.002 – status message on the pacs.008
  • pacs.028 – enquiry about an outstanding status

What it means for banks and payment service providers

The pacs.008 carries the highest volume of any message in payments. Two things drive the effort: first, each environment has its own population rules even though the version is the same – validating against the schema is not enough, it takes the implementation guidelines of the respective rulebook. Second, every pacs.008 has to remain findable afterwards: recall, return and status enquiry point back to it through its references, which makes their uniqueness and retention the deciding factor in how well exceptions can be handled.

Sources