Message Types

pacs008 covers pacs.008 and the related pacs messages that teams use to start, track, return, reverse, and query payments.

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 carries a customer direct debit between banks. 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.
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 banks. It carries party, amount, and remittance data.
pacs.009.001.10	Financial Institution Credit Transfer	2019	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	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 reuse the same assets in local tests, CI pipelines, and internal payment services.

Choosing the right message

Start with the business event, not the message code.

• pacs.008 starts the customer credit-transfer flow.
• pacs.009 handles institution-own-account credit transfers and cover flows.
• pacs.002 reports processing status.
• pacs.028 requests status when a proactive query is needed.
• pacs.004 returns settled funds.
• pacs.007 reverses an earlier payment instruction.

Use the message selection guide for a one-page view across the supported pacs flows.

Keep the payment owner, settlement stage, and exception path clear before picking a message.

2026 market context

• SEPA SCT / SCT Inst: pacs.008 remains central to credit transfers and instant payments.
• CBPR+: richer pacs.008 data keeps replacing MT103-style cross-border traffic and pushes better field-level validation.
• Structured addresses: Swift guidance points to a November 2026 move away from fully unstructured postal addresses in key payment flows.
• STP and repair control: banks still want fewer manual fixes, so clear routing, status design, and clean party data matter more in 2026.

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.