Wholesale Settlement · Fedwire & CHIPS

Getting ready for the Fedwire/CHIPS structured-address cutover

For payments operations, ISO 20022 migration teams, and correspondent banking staff preparing origination systems for the November 2026 structured-address mandate on Fedwire and CHIPS.

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Scope. This guide covers three tools that work together as one workflow: a single-message linter, a payment-file batch sweep, and a before/after remediation receipt. None of the three connects to a live payment rail or moves funds.

The deadline and what's changing

2026-11-16. The Federal Reserve's Fedwire Funds Service and The Clearing House's CHIPS both remove the fully-unstructured postal address option on this date. Every message must carry a hybrid or fully-structured address: Town Name and Country are always required, plus up to two supplemental address lines of 70 characters each. An address that is only free-text lines, with no structured Town Name or Country, is rejected. The two networks share the same rule set: a message built for one network passes the same lint as the other.

How the three tools fit together

  1. Lint a single message with the Structured Address Linter while building or reviewing origination logic. It classifies the address as FULLY_STRUCTURED, HYBRID, UNSTRUCTURED, or EMPTY, and flags the failure mode migration teams miss most often: an address line that silently duplicates a structured field (for example, repeating the town name in a free-text line), which passes a naive check but still triggers an STP rejection because the two representations disagree.
  2. Sweep a whole payment file with the Payment-File Address Sweep once origination logic is in place. Paste or drop a CSV of outbound messages and get a rejection-risk report (violation counts by rule, the worst-offending records) plus a remediation worksheet receipt that binds a digest of the file to a digest of the findings, so the sweep result can't be silently edited after the fact.
  3. Remediate, then prove it with the Remediation Diff Receipt. Feed in the original file and the corrected file side by side. The tool diffs them record by record and issues a receipt binding both file digests together with the rule-clearance delta: how many failures went to zero. This is the artifact a bank shows its regulator or its correspondents as evidence the migration work was actually done.

Fedwire and CHIPS in one lint

The linter takes a network parameter (fedwire or chips) rather than shipping as two separate tools. The structured-address rules were verified byte-identical between the two networks at build time (CHIPS aligns its ISO 20022 implementation to Fedwire's address rules), so one kernel is the single source of truth for both, and the network parameter only changes which regulatory citation appears in the output.

Running the whole workflow as a chain

The Fedwire/CHIPS Structured-Address Migration chain composes all three tools into one gated workflow: lint, then a gate that ends the chain immediately if the message is already compliant, otherwise continuing to the batch sweep and the remediation diff receipt. Each stage exposes an MCP call, so an agent can drive the same workflow programmatically against the AINumbers MCP server.

Scope note. These tools check structural conformance to the November 2026 address rules only. They do not validate the rest of a pacs.008 message, screen for sanctions, or confirm a payment will actually settle. Confirm end-to-end readiness with your Fed contact or clearing house ahead of the cutover.