Message Selection Guide
Choose the pacs family by business event first, then by scheme and operating model.
Quick decision matrix
| Message type | Description | Overview |
|---|---|---|
pacs.002.001.12 | FI to FI Payment Status Report | 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 | The pacs.003 message carries a customer direct debit between banks. It lets the creditor bank collect funds from the debtor bank. |
pacs.004.001.11 | Payment Return | The pacs.004 message returns a payment that has already settled. It sends funds back when a payment cannot be applied. |
pacs.007.001.11 | FI to FI Payment Reversal | 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 | The pacs.008 message is the main customer credit-transfer instruction between banks. It carries party, amount, and remittance data. |
pacs.009.001.10 | Financial Institution Credit Transfer | The pacs.009 message moves funds between banks on their own behalf. It supports funding, cover payments, and liquidity management. |
pacs.010.001.05 | Financial Institution Direct Debit | 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 | 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. |
Common comparison points
| Compare | Key distinction |
|---|---|
pacs.008 vs pacs.009 | Customer payment versus institution / cover movement |
pacs.004 vs pacs.007 | Return from receiving side versus reversal from instructing side |
pacs.002 vs pacs.028 | Status report versus status request |
Supported message pages
Supported message pages are listed in Message Types.
How to choose fast
- Start with the business event.
- Check who owns the payment at that stage.
- Check whether value is moving, being reported, being returned, or being queried.
- Confirm the scheme and counterparty rules before freezing the template.
2026 implementation signals
- Structured address quality is moving from best practice to release gate.
- Banks want less manual repair, so status design and field quality matter as much as XML generation.
- Multi-rail teams need one clear map across customer, treasury, and exception flows.