Fedwire ISO 20022 Validator pacs.008 & AppHdr
Check an ISO 20022 payment message for the Fedwire Funds Service — header and document, schema, routing numbers and the 2026 hybrid address rule. Entirely in your browser, nothing uploaded.
What is Fedwire ISO 20022, and what changes on 16 November 2026?
The Fedwire Funds Service is the Federal Reserve's real-time gross settlement system for US dollar payments. It moved to ISO 20022 in a single big-bang cut-over on 14 July 2025: a Fedwire message is now a pair — a head.001.001.03 Business Application Header plus one of six pinned message versions (pacs.008.001.08, pacs.009.001.08, pacs.004.001.10, pacs.028.001.03, camt.056.001.08, camt.029.001.09). The next milestone is 16 November 2026, when the Federal Reserve states it intends to "remove the fully unstructured postal address option in favor of a single hybrid postal address format for all parties and agents across all message types (i.e., remove three free-text lines of 35 characters each, require town name and country, and allow the option to include other structured address elements such as two free-text lines of up to 70 characters each)". Its scope is deliberately wider than the SEPA address rule of 15 November 2026: it covers every party and every agent, in every message type. This free validator checks a message against the official ISO 20022 XSDs, verifies the ABA 3-7-1 check digit of USABA routing numbers, checks that the header names the document it actually carries, and applies the hybrid-address rule from the settlement date carried by the message — never from today's date. Everything runs in your browser; the payment never leaves your machine.
About this Fedwire ISO 20022 validator
Since the big-bang migration of 14 July 2025, a Fedwire Funds Service message is an ISO 20022 pair: a Business Application Header (head.001.001.03) that says who sends what to whom, and a Document that carries the payment. The service runs exactly six messages, each pinned to one version: pacs.008.001.08 (FI To FI Customer Credit Transfer), pacs.009.001.08 (Financial Institution Credit Transfer), pacs.004.001.10 (Payment Return), pacs.028.001.03 (FI To FI Payment Status Request), camt.056.001.08 (FI To FI Payment Cancellation Request) and camt.029.001.09 (Resolution Of Investigation).
This tool validates both halves against the official ISO 20022 schemas — the header against head.001.001.03 and the document against its own XSD, since they live in separate namespaces — then runs three checks it can actually source: the ABA 3-7-1 mod-10 check digit on every USABA routing number (a number that fails it cannot exist, so a failure is certain; a pass proves nothing about participation); the consistency of the header's MsgDefIdr with the document it really encloses; and the hybrid postal address of the 16 November 2026 release. That last check is triggered by the settlement date inside the message, never by today's date — a message settling before the cut-over is not wrong today and is not failed today.
What it does not do is just as important, and the tool says so on screen. The Fedwire Usage Guidelines live on Swift MyStandards behind a swift.com account, and the Fed's own XSD wrapper and Technical Guide go only to FedLine customers. Without them, no offline tool can know every field-level rule — so this one refuses to invent them, and lists what it could not check instead of hiding it behind a green badge. It cannot tell you that Fedwire will accept your message; it can tell you that the ISO 20022 schema, the routing-number arithmetic and the published 2026 address rule are satisfied.
What to know about the Fedwire ISO 20022 migration
- The Fedwire Funds Service cut over to ISO 20022 in a single big-bang on 14 July 2025 — there is no coexistence period to fall back on.
- A message is a pair: head.001.001.03 Business Application Header + one Document. A bare Document is only half a message.
- Six messages, versions pinned: pacs.008.001.08, pacs.009.001.08, pacs.004.001.10, pacs.028.001.03, camt.056.001.08, camt.029.001.09.
- From 16 November 2026 the fully unstructured postal address goes away, replaced by a single hybrid format — town name and country required, at most two free-text lines of up to 70 characters — for all parties AND agents, across all message types.
- That scope is wider than the SEPA hybrid-address rule of 15 November 2026, which the EPC limits to the debtor and the creditor. Do not assume one covers the other.
- A routing number that fails the ABA 3-7-1 check digit cannot exist; a routing number that passes it may still not be a Fedwire participant. Only the failure is conclusive.
Frequently asked questions
What is the Fedwire ISO 20022 message format?
Since 14 July 2025 the Fedwire Funds Service carries ISO 20022 XML. Each message is a pair: a head.001.001.03 Business Application Header and a Document — one of pacs.008.001.08, pacs.009.001.08, pacs.004.001.10, pacs.028.001.03, camt.056.001.08 or camt.029.001.09. The versions are pinned; another version of the same message is a different message.
What changes on 16 November 2026?
The Federal Reserve states it intends to remove the fully unstructured postal address option in favour of a single hybrid postal address format for all parties and agents across all message types: the three free-text lines of 35 characters go away, town name and country become required, and up to two free-text lines of 70 characters may be included alongside the structured elements. This validator flags a non-hybrid address as an error when the message settles on or after that date, and as a warning before it.
Is the Fedwire address rule the same as the SEPA one?
No, and conflating them is a common mistake. The SEPA rule (EPC153-22, effective 15 November 2026) applies to the debtor and the creditor. The Fedwire release of 16 November 2026 applies to all parties AND all agents, across all message types — a wider scope, on a different rail, one day later.
Can this tool tell me whether Fedwire will accept my message?
No, and no offline tool honestly can. The Fedwire Usage Guidelines are published on Swift MyStandards, which requires a swift.com account, and the Federal Reserve releases its proprietary XSDs and Technical Guide only to FedLine customers. This validator checks what is public — the ISO 20022 schemas, the ABA check digit, the header/document consistency and the published 2026 address rule — and lists on screen exactly what it could not check, rather than implying a verdict it cannot give.
Does it check routing numbers?
Yes. Every clearing-system member id declared as USABA is checked for the ABA 3-7-1 mod-10 check digit. A number that fails it cannot exist, so it is reported as an error — most often a typo. A number that passes may still not be a registered Fedwire participant: verifying that needs the Fed's participant directory, which is not something a browser can consult.
Is my payment message uploaded anywhere?
No. The file is parsed and validated entirely in your browser with JavaScript, including the XSD validation. No payment data is ever sent to a server.
Is this an official Federal Reserve tool?
No. ValidateFin is an independent tool, neither certified, approved, affiliated with nor endorsed by the Federal Reserve. "Fedwire" is a registered trademark of the Federal Reserve Banks and is used here nominatively, to name the message format being checked. The schemas used are the official ISO 20022 XSDs, published under the ISO 20022 IPR Policy's non-exclusive, royalty-free licence.
ValidateFin is an independent tool. It is not certified, approved, affiliated with or endorsed by the Federal Reserve, the Federal Reserve Banks or Federal Reserve Financial Services. “Fedwire” is a registered trademark of the Federal Reserve Banks, used here nominatively to identify the message format being checked. “Official” refers only to the schemas used — the ISO 20022 XSDs published by ISO 20022, under an IPR policy granting a non-exclusive, royalty-free licence — not to any accreditation of this tool. The Fedwire Usage Guidelines are published on Swift MyStandards (account required) and the Federal Reserve’s proprietary schemas and Technical Guide are released only to FedLine customers; this tool therefore cannot determine whether the Fedwire Funds Service would accept or reject a message, and lists on screen the controls it could not run. Validating a file here does not submit it to the Fedwire Funds Service.