pacs.007.001.11 — FI to FI Payment Reversal

ISO name	FIToFIPaymentReversalV11
Registration status	Registered
Year	2019
Version	11

Overview

The pacs.007 message reverses an earlier payment instruction. Unlike pacs.004, it starts from the original sender.

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

Key data elements

• GrpHdr — Group Header with message identification and creation timestamp.
• TxInf — Transaction Information with reversal amount and parties.
• OrgnlGrpInf — Original Group Information referencing the source message.
• RvslRsnInf — Reversal Reason Information with structured reason codes.
• OrgnlTxRef — Original Transaction Reference for end-to-end traceability.

Business context

• Used when the original sender finds an error before or after settlement.
• Used in fraud cases that need fast reversal.
• Supports both full and partial reversal of original payment amounts.
• Carries structured reversal reason codes.

Key data elements	Business context
GrpHdr — Group Header with message identification and creation timestamp	Used when the original sender finds an error before or after settlement
TxInf — Transaction Information with reversal amount and parties	Used in fraud cases that need fast reversal
OrgnlGrpInf — Original Group Information referencing the source message	Supports both full and partial reversal of original payment amounts
RvslRsnInf — Reversal Reason Information with structured reason codes	Carries structured reversal reason codes
OrgnlTxRef — Original Transaction Reference for end-to-end traceability	The instructing agent sends pacs.007 forward through the payment chain to reverse an earlier payment. Each agent processes the reversal and adjusts settlement.

CBPR+ and scheme context

• It differs from pacs.004 by direction: reversals move forward, returns move back.
• CBPR+ requires pairing with original message identifiers for automated matching.
• Structured reason codes replace free-text narratives from legacy MT messages.
• Used more often in instant-payment recall and fraud workflows.

Message flow

The instructing agent sends pacs.007 forward through the payment chain to reverse an earlier payment. Each agent processes the reversal and adjusts settlement.

Version commentary

ISO 20022 last updated this business area on 2025-02-27. This site documents pacs.007.001.11. The latest catalogue version is pacs.007.001.13.

Use this page for the version that pacs008 implements today, and review the newer catalogue version for roadmap planning.

Version-diff table

Version range	Why it matters	Implementation takeaway
pacs.007.001.11	Current implementation in pacs008	Good baseline for reversal workflow modelling.
pacs.007.001.12-13	Later catalogue revisions	Check later revisions for current market-infrastructure alignment.

Scheme-specific notes

• pacs.007 is closer to recall and reversal handling than to beneficiary-side returns, so do not collapse it into the same process model as pacs.004.
• It is often used for fast exception handling in instant-payment and fraud-response contexts.

When to use this message

Use pacs.007 when the original sender needs to reverse an earlier payment instruction.

When not to use this message

Do not use pacs.007 to report status or to process a beneficiary-side return.

Implementation notes

• Make reversal timing explicit.
• Keep reversal reasons structured.
• Track partial and full reversals separately.

Common failure modes

• Modeling pacs.007 as just another return message.
• Not preserving the original transaction chain in reconciliation records.
• Using inconsistent reversal reason mapping across channels.

Worked XML fragment

<FIToFIPmtRvsl>
  <GrpHdr>
    <MsgId>RVSL-2026-0007</MsgId>
  </GrpHdr>
  <TxInf>
    <OrgnlInstrId>PAY-2026-8841</OrgnlInstrId>
    <RvslRsnInf>
      <Rsn><Cd>DUPL</Cd></Rsn>
    </RvslRsnInf>
  </TxInf>
</FIToFIPmtRvsl>

Field commentary

• MsgId: The reversal needs its own identifier.
• OrgnlInstrId: Preserve the original payment reference to avoid reconciliation breaks.
• RvslRsnInf: Use structured reversal reasons so cases can be routed correctly.

Decision flow

Is the instructing side requesting reversal of an earlier instruction?
Yes -> Use pacs.007.
No -> Has the receiving side already returned settled funds?
Yes -> Consider pacs.004 instead.
No -> Check whether the case is status, investigation, or recall handling.

Compare pacs.007 vs pacs.004

Dimension	pacs.007.001.11	Comparison message
Primary purpose	Reverse a previously instructed payment	Return settled funds
Initiated by	Original instructing side	Receiving / beneficiary side
Direction of flow	Forward through the chain	Back through the chain
Best fit	Recall, error, or fraud-driven reversal handling	Post-settlement return handling

Implementation FAQ

Is pacs.007 only for fraud scenarios?

No. Fraud is a major use case, but any instructing-side need to reverse a payment can trigger it.

Can it be handled like a normal return?

No. Reversal timing, reason capture, and reconciliation differ materially from returns.

Primary references

• ISO 20022 message definitions catalogue for pacs.007.001.11
• Swift CBPR+ ISO 20022 usage-guidelines announcement
• Swift CBPR+ migration roadmap PDF

Related messages

Message type	Description	Overview
pacs.008.001.13	FI to FI Customer Credit Transfer	The pacs.008 message is the main customer credit-transfer instruction between financial institutions. It carries party, amount, and remittance data.
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 or must be sent back.
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.