SWIFT MT→MX Field Migration Decoder

Maps legacy SWIFT MT message fields to ISO 20022 MX XML equivalents. Identifies truncation risks, character limit breaches, and unmapped fields across the SWIFT coexistence period (Nov 2022–Nov 2025). Select an MT type, optionally paste a synthetic message block, and get a field-by-field migration analysis with remediation guidance.

SWIFT ISO 20022 MT→MX Mapping Zero PII Client-Side

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

MT Message Type

Migration Target (MX)

Paste MT Message Fields (optional — synthetic data only) Paste a synthetic MT message block. Field tags (:XX:) will be highlighted in the mapping. Leave blank to see the full mapping table for the selected MT type.

Migration Summary

Field-by-Field Mapping

MT Field	Field Name	MX XML Element	Data Type	Truncation Risk	Action Required

Regulatory Basis

Mapping data derived from SWIFT ISO 20022 Migration Programme guidelines, HVPS+ Usage Guidelines (2023), ECB TARGET2/TIPS migration specifications, and the CBPR+ Rulebook (2022–2025 coexistence period). Character limits reflect ISO 20022 Base Schema and CBPR+ local rules. Verify all mappings against current SWIFT published schemas before production implementation.

{
  "name": "decode_swift_mt_mx_field_migration",
  "description": "Maps SWIFT MT message fields to ISO 20022 MX XML elements with truncation risk analysis.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "mt_type":   { "type": "string", "description": "MT103|MT202|MT202COV|MT940|MT950|MT101|MT300|MT760" },
      "mx_target": { "type": "string", "description": "pacs.008|pacs.009|camt.053|camt.052|pain.001" },
      "fields":    { "type": "string", "description": "Optional pasted MT field block (synthetic data only)" }
    },
    "required": ["mt_type", "mx_target"]
  }
}