⚠ SCOPE: SWIFT/ISO 20022 BAH signature migration ONLY. This tool covers BAH-level PQC readiness and message size modelling. It does NOT cover pacs/camt payments message conformance — those belong to cbpr-cutover/rca-03.

ART-87 · Wave 18 · Post-Quantum Cryptography · SWIFT/ISO 20022

SWIFT / ISO 20022 PQC Readiness Checker

Scores SWIFT/ISO 20022 PQC readiness using the BIS Project Leap Phase 2 model (ML-DSA ≈ 12.9× RSA payload at BAH level). Models new message sizes against current limits and flags breaches. Reuses HNDL priority from tool 500. Part of the pqc-swift-iso20022 chain.

BIS Project Leap Phase 2 ML-DSA BAH bloat NOT pacs/camt

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

Messaging Configuration

Current signature scheme

BAH present in message flow

Maximum message size (bytes)

PQC Target

Target PQC algorithm

HNDL priority reference (optional, from tool 500)

–

Readiness Score

–

Size Breach

–

Bloat Factor

Signature Size Comparison

Current signature scheme	–
Current signature size	–
Target PQC algorithm	–
New (PQC) signature size	–

Message Size Analysis

Max message size limit	–
Estimated new message size	–
BAH wrapper overhead	–
BIS Leap bloat factor (BAH-level ref)	12.9× RSA BIS Project Leap Phase 2 — verify current

Affected Message Types

–

Flags

–

References: BIS Project Leap Phase 2 (verify current BIS publication) · NIST FIPS 204 (Aug 2024) ML-DSA sizes · SWIFT BAH overhead ≈512 bytes (verify current SWIFT guidance). DECISION-SUPPORT DRAFT — not a conformance certificate.

OpenChainGraph v0.4 artifact · execution_hash:

–

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.

Run the AINumbers MCP tool `check_iso20022_pqc_readiness`. Task: Score SWIFT/ISO 20022 PQC readiness with BAH signature-bloat sizing per the BIS Project Leap Phase 2 model (ML-DSA ~12.9x RSA payload at BAH level).
Call it with arguments: {"policy_parameters":{}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-87-iso20022-pqc-readiness-checker.html#p=v1.H4sIAAAAAAAA_wECAP3_e31Dv6ajAgAAAA