MX message format

Each MX message type consists of one major element, for example:

<Doc:Document
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:Doc="urn:swift:xsd:acmt.001.001.02">
  <Doc:AcctOpngInstrV02>
    <Doc:MsgId>
      <Doc:Id>ABCDEFGHIJKLMNOPQRST123456789012345</Doc:Id>
      <Doc:CreDtTm>2015-12-21T08:35:30</Doc:CreDtTm>
    </Doc:MsgId>
    <Doc:OrdrRef>
      <Doc:OrdrRef>ABCDEFGHIJKLMNOPQRST123456789012345</Doc:OrdrRef>
      <Doc:MstrRef>ABCDEFGHIJKLMNOPQRST123456789012345</Doc:MstrRef>
    </Doc:OrdrRef>
    ⋮
  </Doc:AcctOpngInstrV02>
</Doc:Document>

FTM SWIFT does not provide XML schema definition (XSD) files for MX message types. However, XSD files can be retrieved from the SWIFT website and are included in SWIFT User Handbook. These files can be integrated into the message broker tooling to make it easier to use a Route node to route FIN messages.

Notes:

The names of the XSD file that corresponds to a particular MX message type contains the version number of that message type. Consequently, the name of the namespace changes with each new version. Be prepared to adapt your programs to reflect the new namespace name, if necessary.
An XML document that is to be processed by FTM SWIFT services must adhere to the XML 1.0 specification.
For CBPR+ messages of message domain DNIFINPLUS, starting with message definition set finplus2021, the ComIbmDni.MsgStandardInfo.Option is used to maintain the usage identifier as defined by SWIFT Standards. For messages passed to FTM SWIFT it has to be contained in the request message.