What Is a SWIFT MX Message?
The SWIFT FIN component also supports the SWIFT Standards MX messages. MX messages are represented using eXtensible Markup Language (XML). With MX messages, you can transport structured information using XML and specify the structure of the message. At the highest level, an MX message is categorized by its business area, represented by four letters. For example, in camt.029.001.01, “camt” specifies the Cash Management business area. The three numbers that follow the letters identify the message functionality. The next three numbers identify the Variant ID, and the last two numbers show the version number.
An MX message contains the business area specific payload. Its structure is defined by the corresponding XML schema. The MX message is wrapped as the RequestPayload within the XML envelope. This request payload also contains the ApplicationHeader. This application header contains general information, and its usage is specific to the context of the service.
Sample SWIFT MX Message
<AppHdr xmlns="urn:swift:xsd:$ahV10">
<MsgRef>TRNREF001</MsgRef>
<CrDate>2009-05-08T22:02:36.218+02:00</CrDate></AppHdr>
<tns:Document xmlns:tns="urn:swift:xsd:setr.010.001.03">
<tns:SbcptOrdrV03><tns:MsgId>
<tns:Id>TRNREF001</tns:Id>
<tns:CreDtTm>2007-04-25T10:10:30.000+02:00</tns:CreDtTm></tns:MsgId>
<tns:MltplOrdrDtls><tns:InvstmtAcctDtls>
<tns:AcctId><tns:Prtry><tns:Id>1111
</tns:Id></tns:Prtry></tns:AcctId>
<tns:AcctDsgnt>SMART INVESTOR</tns:AcctDsgnt>
</tns:InvstmtAcctDtls>
<tns:IndvOrdrDtls><tns:OrdrRef>TRNREF001</tns:OrdrRef>
<tns:FinInstrmDtls><tns:Id><tns:ISIN>GB1234567890</tns:ISIN></tns:Id>
</tns:FinInstrmDtls>
<tns:GrssAmt Ccy="GBP">1050</tns:GrssAmt>
<tns:IncmPref>CASH</tns:IncmPref>
<tns:PhysDlvryInd>false</tns:PhysDlvryInd>
<tns:ReqdSttlmCcy>GBP</tns:ReqdSttlmCcy>
<tns:ReqdNAVCcy>GBP</tns:ReqdNAVCcy>
</tns:IndvOrdrDtls></tns:MltplOrdrDtls>
</tns:SbcptOrdrV03></tns:Document>
For information about MX messages, see SWIFT User Handbook.