Reverses an interbank payment when the initiating financial institution is correcting its own erroneous payment event. It is distinct from a receiver-initiated pacs.004 return and from a camt.056 request that may be refused.
DIRECTION: Sent by the financial institution initiating the reversal to the next agent in the original interbank chain, directly or through the relevant payment infrastructure.
Version + profile: pacs.007 is a message-family identifier, not a complete version. The numeric .001.xx definition and field rules depend on the scheme, service, usage guideline, and implementation version named in each context; sample namespaces show only the illustrated version.
EVIDENCE AT ARM'S REACH
Start with the exact message version, then apply the scheme or network profile that governs your implementation.
An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.
Choose the exact message definition in the official catalogue. The base XSD checks XML structure; it does not prove compliance with a scheme profile.
A fictional FI-to-FI reversal, shown as a generic message rather than a CBPR+ credit-transfer undo button. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.
crc32:1900355bCustomer and FI cancellation, resolution, return, reversal, and structured investigation messages.
crc32:f4772381Curated field requirements, contexts, operational meaning, and implementation cautions.
crc32:4e984c4ePositive and negative test cases across validation, rejection, return, recall, reversal, investigation, reconciliation, migration, instant payments, and screening.
crc32:98c48cc7Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.
crc32:9d2559edCurated teaching subset. The base ISO message supports group and transaction reversals plus richer party, agent, compensation, and original-transaction data; whether pacs.007 is permitted for a credit-transfer scenario is scheme-specific.
| FIELD | NAME | PRESENCE | WHAT IT MEANS |
|---|---|---|---|
GrpHdr/MsgId | Message identification | MANDATORY | Unique identifier for the reversal message. |
GrpHdr/IntrBkSttlmDt | Interbank settlement date | CONDITIONAL | Date on which the reverse interbank movement is intended to settle. |
OrgnlGrpInf/OrgnlMsgId | Original message identification | MANDATORY | Identifies the original payment message being reversed. |
TxInf/OrgnlInstrId | Original instruction identification | OPTIONAL | Original bank-to-bank instruction reference. |
TxInf/OrgnlEndToEndId | Original end-to-end identification | OPTIONAL | Customer reference preserved from the original payment. |
TxInf/OrgnlUETR | Original UETR | OPTIONAL | Network-wide reference of the payment being reversed. |
TxInf/RvsdIntrBkSttlmAmt | Reversed interbank settlement amount | MANDATORY | Amount and currency moving in the opposite direction. |
TxInf/RvslRsnInf/Rsn/Cd | Reversal reason | MANDATORY | Coded reason permitted by the applicable service or scheme. |
The whole pacs.007 laid out as a parent-child tree: every field in its nesting, with a sample value and what it means. Expand a branch to drill in. Values are fictional (SYNTHETIC / TRAINING ONLY); this is a curated practitioner view, not the full schema.
Document—The root of an ISO 20022 message — the business payload, which a Business Application Header (head.001) accompanies as a separate document.FIToFIPmtRvsl—GrpHdr—Group header — data that applies to the whole message: its identity, when it was created, how many transactions it carries, and shared settlement data.MsgIdDEMO-PACS007-001MandatoryUnique identifier for the reversal message.DEMO-PACS008-001IntrBkSttlmDt2026-07-18ConditionalDate on which the reverse interbank movement is intended to settle.<IntrBkSttlmDt>2026-07-13</IntrBkSttlmDt>OrgnlGrpInf—Original Group Information — identifies the original message a return or report refers to.OrgnlMsgIdDEMO-ORIGINAL-001MandatoryIdentifies the original payment message being reversed.OrgnlMsgNmIdpacs.003.001.11Original Message Name Identification — the message type being referred to (e.g. pacs.008.001.08).TxInf—Transaction Information — details of one original transaction being returned, cancelled, or reported on.OrgnlInstrIdDEMO-INSTR-001OptionalOriginal bank-to-bank instruction reference.OrgnlEndToEndIdDEMO-E2E-001OptionalCustomer reference preserved from the original payment.OrgnlUETR6f9619ff-8b86-4e9f-a6dd-2cce35e4b321OptionalNetwork-wide reference of the payment being reversed.RvsdIntrBkSttlmAmt1250.00Ccy=EURMandatoryAmount and currency moving in the opposite direction.RvslRsnInf—Rsn—Reason — the reason, given as a code or proprietary value.CdDUPLMandatoryCoded reason permitted by the applicable service or scheme.ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pain/pacs/camt message-definition elements
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · cross-border agent chain and structured-data usage
Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.
Swift Standards MT (annual standards releases) ↗ — Swift · FIN block structure
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.
Payments Signal editorial teaching models — Payments Signal
What this simplifies: One-line plain-language descriptions of the commonly-populated elements — a practitioner view, not the authoritative ISO 20022 / MT schema, which defines many more optional elements.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pacs.007 FIToFIPaymentReversal message definition
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
2025 SEPA Direct Debit Core rulebook version 1.1 (EPC016-06) ↗ — European Payments Council · Inter-PSP reversal process
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The reference explains the generic reversal distinction and deliberately does not imply universal CBPR+ or SCT support.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.
Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.
Loading the discussion…