Truncation
MT fields are shorter than the matching MX elements. Part of the content does not survive the conversion. Neither sender nor receiver sees that it was lost.
The terminal sits with the sender. The gateway sits in the bank’s contour. Two install places, one product, not one network. MT and ISO 20022 for the transition. Data is checked where it can still be fixed. The bank’s core accounting system is not changed.
Library and rules, not a generative model.
From a local check in the client terminal to processing on the bank operations desk — without changing the core accounting system.
MT fields are shorter than the matching MX elements. Part of the content does not survive the conversion. Neither sender nor receiver sees that it was lost.
Data is stored as a line. The network needs street, building, post code, town, country as fields. A translator cannot invent a structured address from unstructured text — the elements are not there.
The network and many correspondents require an ISO purpose code. MT has no separate field for it. Free text in the old style is not a code.
A missing status, cover, or reply is often not tracked. Delay is learned from the client.
The client terminal puts the payment in order on your side, before it goes to the bank. You see which field will fail — then you send. Structured data goes by keys when connected, or as pain.001 as a file. The bank forms pacs.008.
The gateway is installed in the bank’s contour. It unpacks what still arrives as MT, forms outbound pacs.008 in full, and if a correspondent still takes MT — shows the losses before send. The operations desk is a human decision, not a silent rewrite.
ODG-PASS prepares and checks messages. The bank executes the payments. Compliance, sanctions screening, and regulator reporting stay with the bank.
Questions or issues — use Support, or contact us below. Testing phase: no pricing here; tariffs are agreed separately.