Previous:   Decoding MT to MX Migration: Common Terms Unveiled

The trouble in hand : Coexistence of MT and MX messages

As we know, CBPR+ has already started phase wise migration for Category 1, 2 and 9 messages when used for cross border payments and this process will continue for the coming future.

Now, you can understand that since different payment infrastructures are migrating at different times, there is a big period of time when both MT and MX messages will coexist in the payment world. Thus, it's very important to find ways to handle this coexistence of MT and MX messages efficiently. Otherwise, it will result in a complete mayhem! 

Let's see some solutions -

Transaction Management Platform (TMP)

SWIFT has built a Transaction Management Platform (Release 1) which aims to perform end to end handling of payment messages in a payment chain. It will keep a copy of all the messages exchanged in its database in such a way that, even if a MX-capable bank receives a truncated MT message from a previous bank, which still is not capable to send MX message, it will have the option of retrieving the actual full length MX message copy from the TMP. Here Unique End-to-end Transaction Reference (UETR) is going to play a vital role to track the whole payment chain. In this way, even banks which are yet to migrate to MX can participate and the message flow remains continuous, which otherwise would have been broken after reaching the weakest bank.

TMP will also be able to generate a multi format MX message, which is a MX message which contains information both in XML as well as an MT equivalent format embedded in the same message. So, if a bank receiving the multi format message has any legacy systems like an Anti - Money Laundering (AML) software which still can process only MT messages, it can still continue to function smoothly by consuming only the MT portion of the multi format message. TMP will also provide many other value-added services like pre-validation of messages, sanction screening and fraud detection etc.

SWIFT Translator

SWIFT also provides a translator which can provide message translations from MX to MT and thus provide a way for participants who are yet to migrate still function effectively. The translations follow a priority logic and occur in such a way that the most important information which is must for the payment to be effected correctly is accommodated in the MT message first, and if more space is available in the message then the rest information gets a place.

Other related migrations of infrastructures

Last but not the least keep in mind that when we talk about migration, it's not just the messages that are getting migrated. This whole process requires other infrastructures associated with message sending and receiving which also requires an upgrade to handle the messages migration. 

1. Upgradation of Connectivity - The connectivity used for MT messages is the SWIFT FIN network. For MX either InterAct or FinPlus network is necessary. 
2. Upgradation of RMA - The Relationship management or RMA needs to be upgraded and in the new RMA the authorisation will not take place at the message level but at the business profile level. So, if a RMA is agreed for customer credit transfers then not only the MT messages used for customer credit transfers like MT 103 but also MX messages like pacs.008 will also be automatically allowed under that RMA. 
3. Upgradation of SWIFT Database - The primary database of the RMA management is becoming cloud based and maintained by SWIFT instead of the banks handling the primary database.

WANT TO READ MORE?

Sign Up to get notifications of future blog posts 

Sign up/ Login

Already signed up/ logged in? Then you are all set!

Next:    Navigating On-Behalf-Of (OBO) Transactions with ISO 20022 MX Messages: Unveiling New Roles