Interlayer Translator
The Interlayer translator operates at institutional boundaries, supporting the exchange of structured messages across ISO-20022, JSON and JSON-20022 so that existing systems can coordinate without creating a new platform owner or system of record.
Existing oversight, systems of record and decision-making remain with the participating institutions.
Role at the message layer
The translator supports the exchange of structured messages between existing systems and their counterparties. Its remit is limited to the message layer: it deals with how information is expressed between parties, not with balances, ledgers or business decisions.
This allows institutions to coordinate and reconcile while keeping custody, control and long-term records within their own environments or designated infrastructures.
Non-custodial posture
Formats in scope
Where the translator sits
The translator is positioned at institutional boundaries — for example between:
What we do not do
Explanatory model
For architecture, operations and oversight teams, the translator’s role can be described in three stages. This is a conceptual model rather than a disclosure of implementation detail.
Stage 1
A participating system sends a structured message under its existing controls and governance — for example, using ISO-20022 or JSON where that is already in use.
Stage 2
The message is treated in a neutral way so that its intent and relevant constraints can be understood in the agreed context between the parties, without changing any underlying legal or supervisory responsibilities.
Stage 3
A corresponding message is delivered to the receiving system in the format it expects, ready to be processed under that institution’s own rules, controls and oversight.
Example scenarios
The same neutral translator role can be applied in payments, public-interest programmes, employment pathways and infrastructure coordination, while each domain keeps its own governance arrangements.