Quickly and easily parse SWIFT MT messages

Parse messages in SWIFT format and output them into native  Java object models. In Java form the object model delivers a simple way to query any message element without worrying about the complexity of SWIFT message syntax.

Create SWIFT MT messages in Java object form

Rapidly create messages as Java objects. Test at high volume and at high velocity without creating a SWIFT format messages.

Transform SWIFT messages to XML, JSON or Tag-Value-Pair

Transform SWIFT messages to XML, JSON, Tag-Value-Pair and of course its original Textual format allowing for easy integration with other systems. 

Validate SWIFT messages 

With a simple licensed upgrade you can bring the power of C24 SWIFT message validation to your application. Updated annually to support the latest SWIFT Standards Release, the validation extension parses and highlights erroneous fields to help you prevent invalid messages being posted on the SWIFT network.

To learn more speak with a sales representative.


Download the Open Edition SWIFT Libraries


Quick Start Guide

The Swift Open Edition libraries require the C24 runtime libraries for parsing and transformation. You can quickly get started by using maven to manage the dependencies and build lifecycle.

Add the C24 nexus repository:

            <name>C24 Nexus</name>

You can deploy the C24 Swift 2015 jar to your own repository or reference it from the local file system:


Add the dependency on the C24 Runtime library:


Sample Usage:

public class Application {

    public static void main(String[] args) {
    try {
//Parse the valid file
MT103Message parsedMessage = C24.parse(MT103Message.class).from(new FileReader("src/test/resources/data/valid/MT103i-valid_1.dat"));
System.out.println("The original format:");
//Write out the Swift message as XML
System.out.println("The original message represented as XML:");
//Write out the Swift message as JSON
System.out.println("The original message represented as JSON:");
catch(Exception e) {


For more examples visit our Knowledge Base.