Message Types
pacs008 covers the core pacs.008 message and the related pacs messages used for status, returns, reversals, and enquiries.
Included support
| Message type | Description | Year | Overview |
|---|---|---|---|
pacs.002.001.12 | FI to FI Payment Status Report | 2019 | The pacs.002 message reports the status of an earlier payment instruction. It tells another institution whether the payment was accepted, rejected, pending, or settled. |
pacs.003.001.09 | FI to FI Customer Direct Debit | 2019 | The pacs.003 message executes a customer direct debit between financial institutions. It lets the creditor bank collect funds from the debtor bank. |
pacs.004.001.11 | Payment Return | 2019 | The pacs.004 message returns a payment that has already settled. It sends funds back when a payment cannot be applied or must be sent back. |
pacs.007.001.11 | FI to FI Payment Reversal | 2019 | The pacs.007 message reverses an earlier payment instruction. Unlike pacs.004, it starts from the original sender. |
pacs.008.001.13 | FI to FI Customer Credit Transfer | 2023 | The pacs.008 message is the main customer credit-transfer instruction between financial institutions. It carries party, amount, and remittance data. |
pacs.009.001.10 | Financial Institution Credit Transfer | 2019 | The pacs.009 message moves funds between financial institutions on their own behalf. It supports funding, cover payments, and liquidity management. |
pacs.010.001.05 | Financial Institution Direct Debit | 2019 | The pacs.010 message lets one financial institution debit another institution's own account. It is for bank-to-bank collections, not customer direct debits. |
pacs.028.001.05 | FI to FI Payment Status Request | 2019 | The pacs.028 message asks another institution for the status of an earlier payment. It is a targeted status query for delayed, unclear, or missing payment updates. |
Delivery model
Each supported message comes with templates and validation rules. Teams can use the same assets in local tests, CI, and internal payment services.
Choosing the right message
Start with the business event, not the message code.
pacs.008starts the customer credit-transfer flow.pacs.009handles institution-own-account credit transfers and cover flows.pacs.002reports processing status.pacs.028requests status when a proactive query is needed.pacs.004returns settled funds.pacs.007reverses an earlier payment instruction.
Use the message selection guide for a one-page view across the supported pacs flows.
2026 market context
- SEPA SCT / SCT Inst: pacs.008 remains central to credit transfers and instant payments.
- CBPR+: pacs.008 keeps replacing MT103-style cross-border traffic with more structured data.
- Structured addresses: market guidance points to a November 2026 move away from fully unstructured postal addresses.
- Serial method and STP: multi-leg bank chains still matter, and straight-through processing still drives efficiency.
Operational capabilities
pacs008 provides template-backed generation and validation across supported message definition revisions:
- compare versions.
- regression-test scheme updates.
- strengthen outbound payment message data before release.
- support product, operations, and migration teams from one codebase.