pacs.008.001.13 — FI to FI Customer Credit Transfer

Overview

The pacs.008 message is the main customer credit-transfer instruction between banks. It carries party, amount, and remittance data.

Reviewed 23 March 2026. ISO catalogue date: 2025-02-27.

Key data elements

• GrpHdr — Group Header with message ID, creation date, number of transactions, and settlement information.
• CdtTrfTxInf — Credit Transfer Transaction Information with amount, charges, and purpose.
• Dbtr / DbtrAgt — Debtor and Debtor Agent identification and account details.
• Cdtr / CdtrAgt — Creditor and Creditor Agent identification and account details.
• RmtInf — Remittance Information for structured or unstructured payment references.

Business context

• Main message for customer credit transfers.
• Used across SEPA, CBPR+, and national clearing systems.
• Carries remittance data for reconciliation.
• Supports serial, cover, and direct settlement methods.

CBPR+ and scheme context

• Replaces MT103 and MT103+ for cross-border customer credit transfers.
• The November 2026 structured-address deadline applies to party addresses.
• SWIFT gpi uses pacs.008 for UETR-based tracking.
• Version 13 is the current catalogue revision.

Message flow

The debtor agent sends pacs.008 to the creditor agent, either directly or through intermediaries. Each agent checks and forwards the instruction until the creditor agent credits the beneficiary.

Version commentary

ISO 20022 last updated this business area on 2025-02-27. This site documents pacs.008.001.13, which still matches the latest catalogue version.

Use this page for current implementation work, but still check scheme guidance before production use.

Version-diff table

Scheme-specific notes

• For SEPA credit transfers, pacs.008 is part of the SCT stack in the EPC SCT rulebook.
• For instant payments, pacs.008 is also central to SCT Inst in the EPC SCT Inst rulebook.
• For CBPR+, pacs.008 replaces MT103-style customer payment instructions. See SWIFT CBPR+ pacs.008 overview, serial method, and cover method.
• The November 2026 structured-address change affects cross-border pacs.008 data quality. See the SWIFT CBPR+ roadmap.

When to use this message

Use pacs.008 for customer credit transfers moving between banks.

When not to use this message

Do not use pacs.008 for institution-own-account funding transfers or for status, return, or investigation messages.

Implementation notes

• Address quality, party identifiers, and remittance structure often matter more than the XML.
• Model payment purpose, charge bearer, settlement method, and party roles in source data before rendering.
• Treat version selection as a deployment decision tied to the market and counterparties.

Common failure modes

• Assuming one pacs.008 mapping works unchanged across CBPR+, SEPA, RTGS, and instant-payment contexts.
• Using free text where structured remittance or address fields are expected.
• Leaving exception-handling design until after XML generation works.

Worked XML fragment

<FIToFICstmrCdtTrf>
  <GrpHdr>
    <MsgId>MSG-2026-001MsgId>
    <CreDtTm>2026-01-15T10:30:00ZCreDtTm>
  GrpHdr>
  <CdtTrfTxInf>
    <PmtId>
      <EndToEndId>E2E-INV-2026-001EndToEndId>
      <UETR>123e4567-e89b-12d3-a456-426614174000UETR>
    PmtId>
    <IntrBkSttlmAmt Ccy="EUR">25000.00IntrBkSttlmAmt>
    <Dbtr><Nm>Acme Corp GmbHNm>Dbtr>
    <Cdtr><Nm>Widget Industries SANm>Cdtr>
  CdtTrfTxInf>
FIToFICstmrCdtTrf>
 

Field commentary

• MsgId: This should identify the message envelope, not the end-customer payment reference.
• EndToEndId: Keep customer-facing traceability stable across downstream systems where possible.
• UETR: Use this consistently in cross-border and tracking-heavy environments; do not generate it ad hoc in later workflow stages.
• IntrBkSttlmAmt: Validate amount and currency using business rules before schema validation.
• Dbtr / Cdtr: Party quality, address structure, and identifiers are usually the main determinants of repair rates.

Decision flow

Is this a customer credit-transfer instruction between banks?
Yes -> Use pacs.008.
No -> Is it an institution funding leg or cover payment?
Yes -> Consider pacs.009 instead.
No -> Re-check whether the case is status, return, or reversal.
 

Compare pacs.008 vs pacs.009

Implementation FAQ

Is pacs.008 enough on its own for production payments?

No. Production readiness also depends on scheme rules, address quality, party data, status handling, and exception flows.

What causes the most repair work?

Weak party data, poor address structuring, inconsistent identifiers, and unstructured remittance content are common causes.

Primary references

• ISO 20022 message definitions catalogue for pacs.008.001.13
• SWIFT CBPR+ ISO 20022 usage-guidelines announcement
• SWIFT CBPR+ migration roadmap PDF
• EPC SEPA Credit Transfer rulebook
• EPC SEPA Instant Credit Transfer rulebook
• SWIFT CBPR+ pacs.008 overview
• SWIFT CBPR+ serial-method pacs.008 guidance
• SWIFT CBPR+ cover-method pacs.008/pacs.009 guidance
• SWIFT CBPR+ roadmap and standards programme

Supported versions

Related messages