Kumaran Systems Logo
Banking Industry Solutions

What We Offer

Kumaran Systems delivered a common framework to generate & parse various types of MTxxx messages like:

MT 202: General Financial Institution Transfer
MT 210: Notice to Receive
MT 502: Order to Buy or Sell / Cancellation
MT 509: Trade Status Message
MT 515: Client Confirmation of Purchase or Sale
MT 541: RVP/Receipt versus Payment
MT 543: DVP/ Delivery versus Payment

Kumaran Systems had developed SWIFT Common Components as a Web Service. Using this web service, SWIFT Messages can be passed through and received from different Financial Institutions via SWIFT gateway. The Web Service exposes several web methods to encode and decode SWIFT messages. To encode and decode a SWIFT Message, the SWIFT Common Component should have one structure configuration XML per message. The structure configuration XML provides more insight about Message Block, different Sequences and Tags. Also, the structure configuration XML contains information on Sequences and Tags which describe about their patterns, repetition, presence, formats and validation. In addition to the structure XML, it requires an additional data mapping XML, which is specific to the bank’s requirements, that maps data columns in source to corresponding SWIFT Sequence and/or Tag.

For encoding, it requires one or more rows of information in an excel sheet format, web services consumer code, and message id. The MT Message Engine builds the skeleton of SWIFT Message based on structure configuration XML. The data mapping XML maps the data from the source to the SWIFT message placeholder/Tags. Finally, the other blocks with header information and footer attached to the SWIFT message. For each row in the excel sheet / data source, it creates a SWIFT message. The Web Methods returns the Array of SWIFT message strings.

For decoding, the Web Service parses the SWIFT message and returns the values for the tags as defined in the data mapping XML.