iGTB Intellect

11 1

MXMTMX S.W.I.F.T ISO 20022 Converter​

2 Mins

The S.W.I.F.T mandate that banks must accept and respond to MX (ISO 20022) XML-formatted messages by November 2021 gives IT teams a problem. Avoid that problem and take ISO 20022 messaging off the critical path with MXMTMX, sitting alongside your SWIFT gateway and protecting your MT-based systems

Convert MX messages to your formats and back again

MXMTMX Diagram 850x850 29012020
  • Meet the regulatory requirement painlessly
  • Fast and simple to implement
  • Affordable solution avoiding the need for S.W.I.F.T conversion
    bureau fees
  • Can map to any legacy format not just MT
  • Complete out-of-the-box, for message categories 1, 2 and 9.

Secure, fast and scalable

A solution you can rely on

  • Communication within and outside applications secured using https and 2-way SSL protocols
  • NoSQL database layer for superior performance adding and retrieving complex structured ISO data
  • Microservice-based architecture and containerized deployment for high performance
  • Operators architecture for seamless elastic scalability

How MXMTMX integrates

  • MXMTMX receives ISO 20022 files from S.W.I.F.T or a bureau
  • Mapping configurations drive conversion to MT format
  • For other legacy or custom formats additional configurations can be created easily
  • The bank’s payment systems generate the payment response file in MT (or legacy) format
  • MXMTMX converts it to ISO 20022 and sends it to S.W.I.F.T.
  • Additional MX data can be captured in sister Remittance Repository product

Handle rich client remittance data

Handle Rich Diagram 850x850 29012020

Convert MX messages to your formats and back again

With sister product Remittance Repository, the structured data in MX messages (or supplied by API, file upload or online link) an be held for client and bank use

  • Don’t lose all that useful information
  • Enrich payment services with information on part payments, order numbers, supply chain data and other valuable information
  • On performance-critical payment processing