Cat-19 · T577 · Payment Scheme & Network

Swift MT101 Coexistence Readiness Diff

Swift CBPR+ retires MT101 (FIN) for FI-to-FI bulk and multiple payment initiation on 2026-11-14, after which only pain.001v9 (ISO 20022 MX) is accepted. Declare the message format your system runs today and a structural self-declared readiness checklist (does it already emit pain.001v9 for bulk FI-to-FI, is a fallback path staged, has the correspondent confirmed it can receive pain.001v9), and get a deterministic ready/not-ready verdict plus days to the deadline, recomputed from a fixed deadline constant and the date you supply, never a wall-clock guess.

⚠ Deterministic evaluation of what you declare, not a Swift, correspondent-bank, or regulator submission, and not legal or compliance advice. Distinct from the Fedwire/CHIPS Remediation Diff Receipt (art-548, structured-address remediation, deadline 2026-11-16), a different sub-mandate one day apart.

Coexistence Readiness Swift CBPR+ · MT101 Zero PII Client-Side

Scope & reliance: 🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only. Digests are computed with the browser SubtleCrypto SHA-256. Deterministic logic · no inference · zero PII · CC BY 4.0.

1 · Current message format

What does your system run today for FI-to-FI bulk/multiple payment initiation?

2 · Evaluate as of 3 · Readiness checklist

Already emits pain.001v9 for bulk FI-to-FI (relevant if you selected pain.001v9 above)

A fallback pain.001v9 path is staged (relevant if you selected MT101 above)

Correspondent has confirmed it can receive pain.001v9 (relevant if you selected MT101 above)