MT message formats

A FIN message can have one of the following formats:

MTFIN

This format is used when a FIN message is to be transferred as a FIN APDU. For example, a FIN MT999 message in MTFIN representation might look like this:

{1:F01MYLOCALLTXXX0000000000}{2:I999IBMADEFFAXXXN}{4:
:20:009
:79:009
-}

This format is described in SWIFT User Handbook.

MTXML

This format lets applications and services exploit the capabilities provided by XML when processing FIN messages. For example, the FIN MT999 message shown previously in MTFIN format looks like this in MTXML format:

<FinMessage xmlns="urn:swift:xsd:mtmsg.2018"> 
 <Block1> 
  <ApplicationIdentifier>F</ApplicationIdentifier> 
  <ServiceIdentifier>01</ServiceIdentifier> 
  <LogicalTerminalAddress>MYLOCALLTXXX</LogicalTerminalAddress>
  <SessionNumber>0000</SessionNumber> 
  <SequenceNumber>000000</SequenceNumber> 
 </Block1> 
 <Block2> 
  <InputIdentifier>I</InputIdentifier> 
  <MessageType>999</MessageType> 
  <DestinationAddress>IBMADEFFAXXX</DestinationAddress> 
  <MessagePriority>N</MessagePriority> 
 </Block2> 
 <Block4> 
  <Document xmlns="urn:swift:xsd:fin.999.2018"> 
   <MT999> 
    <F20a> 
     <F20>009</F20> 
    </F20a> 
    <F79a> 
    <F79> 
     <Narrative> 
      <Line>009</Line> 
     </Narrative> 
    </F79> 
    </F79a> 
   </MT999> 
  </Document> 
 </Block4> 
</FinMessage>

Notes:

An XML document that is to be processed by FTM SWIFT services must adhere to the XML 1.0 specification.

Each XML element of a message in MTXML format belongs to one of the following namespaces:

Prefix Namespace and XSD file Description

mtmsg

Prefix	Namespace and XSD file	Description
mtmsg	Namespace: `urn:swift:xsd:mtmsg.year` XSD file: `mtmsg.year.xsd`	This namespace represents the entire message.
mt	Namespace: `urn:swift:xsd:fin.mt.year` XSD file: `fin.mt.year.xsd`	This namespace represents the business data, which corresponds to FIN block 4. It provides a way for you to integrate the structure of the appropriate FIN message type into the message.

Namespace:

urn:swift:xsd:mtmsg.year

XSD file:

mtmsg.year.xsd

This namespace represents the entire message.

Namespace:

urn:swift:xsd:fin.mt.year

XSD file:

fin.mt.year.xsd

This namespace represents the business data, which corresponds to FIN block 4. It provides a way for you to integrate the structure of the appropriate FIN message type into the message.

where:

mt: The message type to which the file applies, for example, 103 or 999.
year: The year of the SWIFTNet FIN message standard to which the file applies.

As a consequence of this naming scheme, the name of the corresponding namespace changes with each new release of the SWIFTNet FIN message standard. Be prepared to adapt your programs to reflect the new namespace name, if necessary.

For the MTXML format, FTM SWIFT provides a set of XSD files for both types of FIN system messages (category 0 for FIN and GPA) and FIN financial messages (categories 1 through 9). These files can be integrated into the IBM® Integration Bus tooling to make it easier to use a message management routing node to route FIN messages.

The semantics (that is, the fields and the meaning of each field) of the MTXML and MTFIN formats are identical. Consequently, the best way to understand the meaning of an MTXML element is to refer to the corresponding MTFIN field in SWIFT User Handbook. The FTM SWIFT Standards Processing Node DniStandardsProcessing can be used to transform a FIN message from MTFIN format to MTXML or vice versa.