Payment-Components
Payment-Components
demo-iso20022
Java

Demo project using ISO20022 Message validation library

Last updated Jun 30, 2026
37
Stars
21
Forks
1
Issues
0
Stars/day
Attention Score
76
View on GitHub ↗ Open in github.dev
Topics
#aciworldwide#demo#finaplo#fintech#iso20022#java#sdk#swift-mx
Language breakdown
Java 100.0%
▸ Files click to expand
README

ISO20022 Message Validator Demo

This project is part of the FINaplo product and is here to demonstrate how our SDK for SWIFT MX (ISO20022) Messages Validation works. For our demonstration we are going to use the demo SDK which can parse/validate/generate a pacs.002.001.XX message.

It's a simple maven project, you can download it and run it, with Java 1.8 or above.

Table of Contents

- SEPA-EPC Credit Transfer - SEPA-EPC Direct Debit - SEPA-EPC Instant Payment - SEPA-EBA Credit Transfer - SEPA-DIAS Credit Transfer - SEPA-SIBS Credit Transfer - SEPA-SIBS Direct Debit

SDK setup

Incorporate the SDK jar into your project by the regular IDE means. This process will vary depending upon your specific IDE and you should consult your documentation on how to deploy a bean. For example in Eclipse all that needs to be done is to import the jar files into a project. Alternatively, you can import it as a Maven or Gradle dependency.
Maven
Define repository in the repositories section 
<repository>
    <id>paymentcomponents</id>
    <url>https://nexus.paymentcomponents.com/repository/public</url>
</repository>
Import the SDK 
<dependency>
    <groupId>gr.datamation.mx</groupId>
    <artifactId>mx</artifactId>
    <version>24.24.0</version>
    <classifier>demo</classifier>
</dependency>
Gradle
Define repository in the repositories section 
repositories {
    maven {
        url "https://nexus.paymentcomponents.com/repository/public"
    }
}
Import the SDK git push https://gantoniadispc14:hGgxJztpi8HNFTZ@github.com/Payment-Components/demo-iso20022.git main 
implementation 'gr.datamation.mx:mx:24.24.0:demo@jar'
In case you purchase the SDK you will be given a protected Maven repository with a user name and a password. You can configure your project to download the SDK from there.

Other dependencies

There is a dependency in groovy-all library which is required for some of the included features (version 2.4.8 or later). There is also a dependency in classgraph library which is required for some of the included features (version 4.8.153 or later). You can use maven or gradle to add the dependencies below or manually include the jar to your project.
Maven 
<dependency>
    <groupId>org.codehaus.groovy</groupId>
    <artifactId>groovy-all</artifactId>
    <version>2.5.11</version>
</dependency>
<dependency>
   <groupId>io.github.classgraph</groupId>
   <artifactId>classgraph</artifactId>
   <version>4.8.153</version>
</dependency>
Gradle 
compile group: 'org.codehaus.groovy', name: 'groovy-all', version: '2.4.8'
compile group: 'io.github.classgraph', name: 'classgraph', version: '4.8.153'

HOW-TO Use the SDK

All ISO20022 messages are identified by a code id and a name. The code id (FIToFIPmtStsRpt) and the name (FIToFIPaymentStatusReportV11) are located in the .xsd file that describes the XML schema of each message. Both the name and the code id of the message are available in the ISO20022 messages catalogue.

Inside pacs.002.001.11.xsd 

<xs:complexType name="Document">     <xs:sequence>         <xs:element name="FIToFIPmtStsRpt" type="FIToFIPaymentStatusReportV11"/>     </xs:sequence> </xs:complexType>

Message objects

For every ISO20022 message there is an equivalent class in our SDK. The name of the class is equivalent to the name of the message. For example the name of the class for the message named FIToFIPaymentStatusReportV11 is FIToFIPaymentStatusReport11 (using version 11 of FIToFIPmtStsRpt). Each message has its own versions which are all maintained according to the yearly ISO20022 guidelines.

Building and validating messages

There are three steps the user must follow in order to build a new Swift MX message:
  • ##### Initialize the class corresponding to the message.
The initialization of the class is as simple as initializing any class in Java. For the example message we are using here (FIToFIPaymentStatusReport11) the initialization would be 
FIToFIPaymentStatusReport11 message = new FIToFIPaymentStatusReport11();
The above command will initialize a class for this message named FIToFIPaymentStatusReport11 which is initially empty. Validating a text 
ValidationErrorList errorList = message.validateXML(new ByteArrayInputStream("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +
                                                                                 "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.11\">\n" +
                                                                                 "  <FIToFIPmtStsRpt>\n" +
                                                                                 "     ............\n" +
                                                                                 "  </FIToFIPmtStsRpt>\n" +
                                                                                 "</Document>".getBytes()));
Parsing a text 
message.parseXML("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +
                     "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.11\">\n" +
                     "  <FIToFIPmtStsRpt>\n" +
                     "     ............\n" +
                     "  </FIToFIPmtStsRpt>\n" +
                     "</Document>");

###### Auto parse and validate In case we do not know the class of the message, we can use the auto parse and validate from the xml. Auto validating a text 

ValidationErrorList errorList = MXUtils.autoValidateXML(new ByteArrayInputStream("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +                                                                                      "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.11\">\n" +                                                                                      "  <FIToFIPmtStsRpt>\n" +                                                                                      "     ............\n" +                                                                                      "  </FIToFIPmtStsRpt>\n" +                                                                                      "</Document>".getBytes()));
Auto parsing a text 
Message message = MXUtils.autoParseXML("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" +                                             "<Document xmlns=\"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.11\">\n" +                                             "  <FIToFIPmtStsRpt>\n" +                                             "     ............\n" +                                             "  </FIToFIPmtStsRpt>\n" +                                             "</Document>");

  • ##### Add data to the class.
The next step is to add data to the new message. In order to add some data to the message, user must know which element in the message tree he wants to add. The element he wants to add is identified by an XML path. The value of the element user wants to add may be a String, a Boolean or a complex type that is described in the SWIFT MX type catalog. So to enter some data into the message, user must call the following method of the previously instantiated object where the path argument is a String identifying the element to add and the value argument is an Object. 
message.setElement("path/to/field", "value");
User can also work with the XSD defined classes that represent a tag. e.g. GroupHeader91 for GrpHdr tag. 
message.getMessage().setGrpHdr(new GroupHeader91()); // setGrpHdr() method accepts iso.pacs002001_11.GroupHeader91 objects
  • ##### Validate the message.
After building a Swift MX message using the appropriate class, user may want to validate this message. Of course validation is not mandatory but is the only way to prove that the message is correct. Validation is performed by calling the validate() method and internally is a two step process: - Validation against the schema of the message in order to ensure that the message is a well-formed instance of it. - Validation against any Validation Rule as described for that message by the ISO20022 rules. The validate() method returns an ArrayList containing the validation errors that may occur. Each error is contained in the ArrayList as a ValidationError object describing the error. 
ValidationErrorList errorList = message.validate();

Resolve Paths

For each message object we can call the resolvePaths() method on the object. This method returns the xml as paths, from root element to the leaf. It returns a List and each element of the List is a String array consisted of 3 elements:
  • Field Path excluding the leaf code
  • Leaf code
  • Leaf value
  • Leaf attributes (e.g. Ccy=EUR;)
For example if we call the resolvePaths() on a pacs.002.001.12 
FIToFIPaymentStatusReport12 pacs002 = new FIToFIPaymentStatusReport12();
//fill the message object or parse from an xml
List<String[]> paths = pacs002.resolvePaths();
for (String[] path: paths)
        System.out.println("Field path: " + path[0] + " | " + "Field code: " + path[1] +  " | " + "Field value: " + path[2] + " | " + "Field attributes: " + path[3]);
part of the output we will receive is 
Field path: /Document/FIToFIPmtStsRpt/GrpHdr | Field code: MsgId | Field value: ABABUS23-STATUS-456/04 | Field attributes: null
Field path: /Document/FIToFIPmtStsRpt/GrpHdr | Field code: CreDtTm | Field value: 2015-06-29T09:56:00 | Field attributes: null
Field path: /Document/FIToFIPmtStsRpt/OrgnlGrpInfAndSts | Field code: OrgnlMsgId | Field value: AAAA100628-123v | Field attributes: null
Field path: /Document/FIToFIPmtStsRpt/OrgnlGrpInfAndSts | Field code: OrgnlMsgNmId | Field value: pacs.003.001.09 | Field attributes: null
Field path: /Document/FIToFIPmtStsRpt/TxInfAndSts | Field code: OrgnlEndToEndId | Field value: VA060327/0123 | Field attributes: null
Field path: /Document/FIToFIPmtStsRpt/TxInfAndSts | Field code: OrgnlTxId | Field value: AAAAUS29/100628/ad458 | Field attributes: null
Field path: /Document/FIToFIPmtStsRpt/TxInfAndSts | Field code: TxSts | Field value: RJCT | Field attributes: null
In case the child of an xml element is an array, we will receive an index of the element. In our case, if pacs.002 had more than one FIToFIPmtStsRpt, the path would have an index. E.g. 
/Document/FIToFIPmtStsRpt[0]/TxInfAndSts
/Document/FIToFIPmtStsRpt[1]/TxInfAndSts

Get Element

For each message object we can call the getElement() method on the object. This method receives a field path until leaf and returns the field value. The value could be a simple String or a complex Object. For example we can call the below in a pacs.002 message 
pacs002.getElement("TxInfAndSts[0]/TxSts");
the output will be a "RJCT" String. If we call 
pacs002.getElement("TxInfAndSts[0]");
the output will be a PaymentTransaction130 Object. The use of index is necessary in case the element is an array.

Code Samples

In this project you can see code for all the basic manipulation of an MX message, like:

Auto Replies

Additional Dependencies

In order to use auto-replies, the use of gson is required Maven 

<dependency>    <groupId>com.google.code.gson</groupId>    <artifactId>gson</artifactId>    <version>2.8.9</version> </dependency>

The library supports the creation of reply message. For example, for a pacs.008 message, you can create a pacs.004 message. The correspondent classes belong to gr.datamation.replies package and extends the CoreMessageAutoReplies abstract Class. This class contains the abstract <R extends CoreMessage> R autoReply(R replyMessage, List<MsgReplyInfo> msgReplyInfo) method. MsgReplyInfo contains information for the reply and is a list because some reply messages may contain many transactions. For example, for a pacs.008.001.10, the class for replies should be FIToFICustomerCreditTransferAutoReplies that extends CoreMessageAutoReplies. We initiate this class with the source message. For a pacs.008.001.10, the initialization should be: 

FIToFICustomerCreditTransfer10 pacs008 = new FIToFICustomerCreditTransfer10(); //fill the message object or parse from an xml FIToFICustomerCreditTransferAutoReplies<FIToFICustomerCreditTransfer10, PaymentReturn11> pacs008Replies =      new FIToFICustomerCreditTransferAutoReplies<>(pacs008);
If we want to create a pacs.004.001.11 reply for this pacs.008, we should call the autoReply() like this: 
MsgReplyInfo msgReplyInfo = new MsgReplyInfo(); ReasonInformation reasonInformation = new ReasonInformation(); msgReplyInfo.setRsnInf(reasonInformation);


reasonInformation.setType(ReasonInformation.Type.CD); reasonInformation.setValue("AC01"); reasonInformation.setAddtlInf(Collections.singletonList("Additional info"));


msgReplyInfo.setOrgnlInstrId("instrId"); msgReplyInfo.setReplyId("pacs008Reply"); msgReplyInfo.setIntrBkSttlmDt(new Date());


ChargesInformation chargesInformation = new ChargesInformation(); chargesInformation.setAmount(new BigDecimal("2.00")); chargesInformation.setAgentBic("AAAAGB2L"); msgReplyInfo.setChargesInformation(Collections.singletonList(chargesInformation));


msgReplyInfo.setChargeBearer("SLEV");


PaymentReturn11 pacs004 = pacs008Replies.autoReply(new PaymentReturn11(), Collections.singletonList(msgReplyInfo));

The following replies for generic iso20022 messages are supported:

| Source Message | Reply Message | Source Class | Reply Class | AutoReplies Class | |-----------------|-----------------|--------------------------------------|------------------------------------|-----------------------------------------------| | pacs.008.001.xx | pacs.004.001.xx | FIToFICustomerCreditTransferXX | PaymentReturnXX | FIToFICustomerCreditTransferAutoReplies | | pacs.008.001.xx | pacs.002.001.xx | FIToFICustomerCreditTransferXX | FIToFIPaymentStatusReportXX | FIToFICustomerCreditTransferAutoReplies | | pacs.008.001.xx | camt.056.001.xx | FIToFICustomerCreditTransferXX | FIToFIPaymentCancellationRequestXX | FIToFICustomerCreditTransferAutoReplies | | pacs.008.001.xx | camt.027.001.xx | FIToFICustomerCreditTransferXX | ClaimNonReceiptXX | FIToFICustomerCreditTransferAutoReplies | | pacs.008.001.xx | camt.087.001.xx | FIToFICustomerCreditTransferXX | RequestToModifyPaymentXX | FIToFICustomerCreditTransferAutoReplies | | pacs.008.001.xx | camt.106.001.xx | FIToFICustomerCreditTransferXX | ChargesPaymentRequestXX | FIToFICustomerCreditTransferAutoReplies | | pacs.009.001.xx | pacs.004.001.xx | FinancialInstitutionCreditTransferXX | PaymentReturnXX | FinancialInstitutionCreditTransferAutoReplies | | pacs.009.001.xx | camt.056.001.xx | FinancialInstitutionCreditTransferXX | FIToFIPaymentCancellationRequestXX | FinancialInstitutionCreditTransferAutoReplies | | camt.056.001.xx | camt.029.001.xx | FIToFIPaymentCancellationRequestXX | ResolutionOfInvestigationXX | FIToFIPaymentCancellationRequestAutoReplies | | camt.056.001.xx | pacs.028.001.xx | FIToFIPaymentCancellationRequestXX | FIToFIPaymentStatusRequestXX | FIToFIPaymentCancellationRequestAutoReplies | | camt.027.001.xx | camt.029.001.xx | ClaimNonReceiptXX | ResolutionOfInvestigationXX | ClaimNonReceiptAutoReplies | | camt.087.001.xx | camt.029.001.xx | RequestToModifyPaymentXX | ResolutionOfInvestigationXX | RequestToModifyPaymentAutoReplies | | pacs.003.001.xx | pacs.004.001.xx | FIToFICustomerDirectDebitXX | PaymentReturnXX | FIToFICustomerDirectDebitAutoReplies | | pacs.003.001.xx | pacs.002.001.xx | FIToFICustomerDirectDebitXX | FIToFIPaymentStatusReportXX | FIToFICustomerDirectDebitAutoReplies | | pacs.003.001.xx | pacs.007.001.xx | FIToFICustomerDirectDebitXX | FIToFIPaymentReversalXX | FIToFICustomerDirectDebitAutoReplies | | pacs.007.001.xx | pacs.004.001.xx | FIToFIPaymentReversalXX | PaymentReturnXX | FIToFIPaymentReversalAutoReplies |

* Where XX represents the version of the message. Sample code for FIToFICustomerCreditTransferAutoReplies can be found here. Sample code for FinancialInstitutionCreditTransferAutoReplies can be found here. Sample code for FIToFIPaymentCancellationRequestAutoReplies can be found here.

Universal Confirmations

You can create Universal Confirmations trck.001.001.03 for a pacs.008 messages. It is the equivalent of creating MT199 Universal Confirmation for an MT103. First, you need to initiate FIToFICustomerCreditTransferAutoReplies class since the method for Universal Confirmation exists there. A Universal Confirmations message is represented by UniversalConfirmationsMessage and consists of the ApplicationHeader(head.001.001.02) and the Document(trck.001.001.03). Available statuses are: ACCC, ACSP and RJCT. Available paymentScenario are: CCTR and RCCT. Below you can see how to use it. 

//initiate a UniversalConfirmationsMessage instance String status = "ACSP"; String paymentScenario = "CCTR"; ReasonInformation rsnInf1 = new ReasonInformation(); rsnInf1.setValue("G001"); MsgReplyInfo msgReplyInfo1 = new MsgReplyInfo(); msgReplyInfo1.setRsnInf(rsnInf1); msgReplyInfo1.setOrgnlInstrId("BBBB/150928-CCT/JPY/123/0"); msgReplyInfo1.setChargeBearer("CRED"); //optional msgReplyInfo1.setChargesInformation(new ArrayList<>()); //optional msgReplyInfo1.getChargesInformation().add(new ChargesInformation()); //optional msgReplyInfo1.getChargesInformation().get(0).setAmount(new BigDecimal("1")); //optional


//OR String status = "ACCC"; String paymentScenario = "CCTR"; MsgReplyInfo msgReplyInfo1 = new MsgReplyInfo(); msgReplyInfo1.setOrgnlInstrId("BBBB/150928-CCT/JPY/123/0");


//OR String status = "RJCT"; String paymentScenario = "CCTR"; ReasonInformation rsnInf1 = new ReasonInformation(); rsnInf1.setValue("AM06"); MsgReplyInfo msgReplyInfo1 = new MsgReplyInfo(); msgReplyInfo1.setRsnInf(rsnInf1); msgReplyInfo1.setOrgnlInstrId("BBBB/150928-CCT/JPY/123/0");          UniversalConfirmationsMessage universalConfirmationsMessage =    new UniversalConfirmationsMessage(new BusinessApplicationHeader03UniversalConfirmations(), new PaymentStatusTrackerUpdate03UniversalConfirmations());


//initiate the Reply Class instance UniversalConfirmationsAutoReplies<FIToFICustomerCreditTransfer08> universalConfirmationsAutoReplies =    new UniversalConfirmationsAutoReplies<>(pacs008);


//call method that generates the universal confirmation universalConfirmationsAutoReplies.autoReply(universalConfirmationsMessage, Arrays.asList(msgReplyInfo1), status, paymentScenario);

CBPR+ messages

SDK Setup

Maven

<!-- Import the CBPR+ demo SDK-->
<dependency>
    <groupId>gr.datamation.mx</groupId>
    <artifactId>mx</artifactId>
    <version>24.24.0</version>
    <classifier>demo-cbpr</classifier>
</dependency>

Gradle

implementation 'gr.datamation.mx:mx:24.24.0:demo-cbpr@jar'
Please refer to General SDK Setup for more details.

Parse & Validate CBPR+ Message

In case you need to handle CBPR+ messages, then you need to handle objects of CbprMessage class. 
//Initialize the cbprMessage
CbprMessage<BusinessApplicationHeader02, FIToFICustomerCreditTransfer08> cbprMessage = new CbprMessage<>(new BusinessApplicationHeader02(), new FIToFICustomerCreditTransfer08());
//Fill the cbprMessage with data from xml validate CBPR+ against the xml schema. We can also exit in case of errors in this step.
ValidationErrorList validationErrorList = cbprMessage.autoParseAndValidateXml(new ByteArrayInputStream(validCbprPacs008String.getBytes()));
//Perform validation in both header and message object using cbprMessage
//Use CbprMessage.CbprMsgType enumeration object to select the matching schema (check the table of supported CBPR messages below
//CbprMessage.extractCbprMsgType() can also be used
validationErrorList.addAll(cbprMessage.validate(CbprMessage.CbprMsgType.PACS_008));

if (validationErrorList.isEmpty()) {     System.out.println(fiToFICustomerCreditTransfer.convertToXML()); //Get the generated xml } else {     System.out.println(validationErrorList); }   //Extract the header and the core message from cbprMessage object BusinessApplicationHeader02 businessApplicationHeader = (BusinessApplicationHeader02)cbprMessage.getAppHdr(); FIToFICustomerCreditTransfer08 fiToFICustomerCreditTransfer = (FIToFICustomerCreditTransfer08) cbprMessage.getDocument();

AutoParse & Validate CBPR+ Message

//Initialize the cbprMessage
CbprMessage<?, ?> cbprMessage = new CbprMessage<>();
//Fill the cbprMessage with data from xml and validate CBPR+ against the xml schema. We can also exit in case of errors in this step.
ValidationErrorList validationErrorList = cbprMessage.autoParseAndValidateXml(new ByteArrayInputStream(validCbprPacs008String.getBytes()));

//Perform validation in both header and message object using cbprMessage validationErrorList.addAll(cbprMessage.autoValidate());


if (validationErrorList.isEmpty()) {     System.out.println(fiToFICustomerCreditTransfer.convertToXML()); //Get the generated xml } else {     System.out.println(validationErrorList); }

Construct CBPR+ Message

//Initialize the header object
BusinessApplicationHeader02 businessApplicationHeader = new BusinessApplicationHeader02();
businessApplicationHeader.parseXML(validCbprPacs008HeaderString);

//Initialize the document object FIToFICustomerCreditTransfer08 fiToFICustomerCreditTransfer = new FIToFICustomerCreditTransfer08(); fiToFICustomerCreditTransfer.parseXML(validCbprPacs008DocumentString);


//We fill the elements of the message object using setters fiToFICustomerCreditTransfer.getMessage().setGrpHdr(new GroupHeader93()); fiToFICustomerCreditTransfer.getMessage().getGrpHdr().setMsgId("1234"); //or setElement() fiToFICustomerCreditTransfer.setElement("GrpHdr/MsgId", "1234");


//Construct the CBPR message object       CbprMessage<BusinessApplicationHeader02, FIToFICustomerCreditTransfer08> cbprMessage = new CbprMessage<>(businessApplicationHeader, fiToFICustomerCreditTransfer);


//Perform validation in both header and message object using cbprMessage //Use CbprMessage.CbprMsgType enumeration object to select the matching schema (check the table of supported CBPR messages below) //CbprMessage.extractCbprMsgType() can also be used ValidationErrorList validationErrorList = cbprMessage.validate(CbprMessage.CbprMsgType.PACS_008);


if (validationErrorList.isEmpty()) {     System.out.println(fiToFICustomerCreditTransfer.convertToXML()); //Get the generated xml } else {     System.out.println(validationErrorList); }

In case you want to enclose the CBPR+ message under another Root Element, use the code below 

cbprMessage.encloseCbprMessage("RequestPayload") //In case you want RequestPayload

Code samples

Parse and validate CBPR+ message

Supported CBPR+ Message Types (v2.1)

| ISO20022 Message | CbprMsgType ENUM | Library Object class | Available in Demo | |------------------|------------------|-------------------------------------------|:-----------------:| | admi.024.001.01 | ADMI_024 | NotificationOfCorrespondence01 | | | camt.029.001.09 | CAMT_029 | ResolutionOfInvestigation09 | | | camt.052.001.08 | CAMT_052 | BankToCustomerAccountReport08 | | | camt.053.001.08 | CAMT_053 | BankToCustomerStatement08 | | | camt.054.001.08 | CAMT_054 | BankToCustomerDebitCreditNotification08 | | | camt.055.001.08 | CAMT_055 | CustomerPaymentCancellationRequest08 | | | camt.056.001.08 | CAMT_056 | FIToFIPaymentCancellationRequest08 | | | camt.057.001.06 | CAMT_057 | NotificationToReceive06 | | | camt.058.001.08 | CAMT_058 | NotificationToReceiveCancellationAdvice08 | | | camt.060.001.05 | CAMT_060 | AccountReportingRequest05 | | | camt.105.001.02 | CAMT_105 | ChargesPaymentNotification02 | | | camt.105.001.02 | CAMT105MLP | ChargesPaymentNotification02 | | | camt.106.001.02 | CAMT_106 | ChargesPaymentRequest02 | | | camt.106.001.02 | CAMT106MLP | ChargesPaymentRequest02 | | | camt.107.001.01 | CAMT_107 | ChequePresentmentNotification01 | | | camt.108.001.01 | CAMT_108 | ChequeCancellationOrStopRequest01 | | | camt.109.001.01 | CAMT_109 | ChequeCancellationOrStopReport01 | | | pacs.002.001.10 | PACS_002 | FIToFIPaymentStatusReport10 | | | pacs.003.001.08 | PACS_003 | FIToFICustomerDirectDebit08 | | | pacs.004.001.09 | PACS_004 | PaymentReturn09 | | | pacs.008.001.08 | PACS_008 | FIToFICustomerCreditTransfer08 | | | pacs.008.001.08 | PACS008STP | FIToFICustomerCreditTransfer08 | | | pacs.009.001.08 | PACS009CORE | FinancialInstitutionCreditTransfer08 | ✓ | | pacs.009.001.08 | PACS009COV | FinancialInstitutionCreditTransfer08 | | | pacs.009.001.08 | PACS009ADV | FinancialInstitutionCreditTransfer08 | | | pacs.010.001.03 | PACS_010 | FinancialInstitutionDirectDebit03 | | | pacs.010.001.03 | PACS010COL | FinancialInstitutionDirectDebit03 | | | pain.001.001.09 | PAIN_001 | CustomerCreditTransferInitiation09 | | | pain.002.001.10 | PAIN_002 | CustomerPaymentStatusReport10 | | | pain.008.001.08 | PAIN_008 | CustomerDirectDebitInitiation08 | |

Auto replies

| Source Message | Reply Message | Source Class | Reply Class | AutoReplies Class | | --------------- |-----------------| ------------------------------------ |------------------------------------| ------------------------------------------------- | | pacs.008.001.08 | pacs.004.001.09 | FIToFICustomerCreditTransfer08 | PaymentReturn09 | FIToFICustomerCreditTransferCbprAutoReplies | | pacs.008.001.08 | camt.056.001.08 | FIToFICustomerCreditTransfer08 | FIToFIPaymentCancellationRequest08 | FIToFICustomerCreditTransferCbprAutoReplies | | pacs.008.001.08 | pacs.002.001.10 | FIToFICustomerCreditTransfer08 | FIToFIPaymentStatusReport10 | FIToFICustomerCreditTransferCbprAutoReplies | | pacs.008.001.08 | camt.106.001.02 | FIToFICustomerCreditTransfer08 | ChargesPaymentRequest02 | FIToFICustomerCreditTransferCbprAutoReplies | | pacs.009.001.08 | pacs.004.001.09 | FinancialInstitutionCreditTransfer08 | PaymentReturn09 | FinancialInstitutionCreditTransferCbprAutoReplies | | pacs.009.001.08 | camt.056.001.08 | FinancialInstitutionCreditTransfer08 | FIToFIPaymentCancellationRequest08 | FinancialInstitutionCreditTransferCbprAutoReplies | | camt.056.001.08 | camt.029.001.09 | FIToFIPaymentCancellationRequest08 | ResolutionOfInvestigation09 | FIToFIPaymentCancellationRequestCbprAutoReplies |

Sample code for FIToFICustomerCreditTransferCbprAutoReplies can be found here. Sample code for FinancialInstitutionCreditTransferCbprAutoReplies can be found here. Sample code for FIToFIPaymentCancellationRequestCbprAutoReplies can be found here.

Please refer to general auto replies for more details.

MEPS+ Like4Like messages

Parse & Validate MEPS+ Like4Like Message

In case you need to handle MEPS+ Like4Like messages, then you need to handle objects of MepsMessage class. 
//Initialize the mepsMessage
MepsMessage<BusinessApplicationHeader02, FinancialInstitutionCreditTransfer08> mepsMessage = new MepsMessage<>(new BusinessApplicationHeader02(), new FinancialInstitutionCreditTransfer08());
//Fill the mepsMessage with data from xml and validate MEPS against the xml schema
ValidationErrorList validationErrorList = mepsMessage.autoParseAndValidateXml(new ByteArrayInputStream(validMepsPacs009CoreString.getBytes()));
//Perform validation in both header and message object using mepsMessage
//Use MepsMessage.MepsMsgType enumeration object to select the matching schema (check the table of supported MEPS messages below
//MepsMessage.extractMepsMsgType() can also be used
validationErrorList.addAll(mepsMessage.validate(MepsMessage.MepsMsgType.PACS009CORE));

if (validationErrorList.isEmpty()) {     System.out.println(fiToFICustomerCreditTransfer.convertToXML()); //Get the generated xml } else {     System.out.println(validationErrorList); }   //Extract the header and the core message from mepsMessage object BusinessApplicationHeader02 businessApplicationHeader = (BusinessApplicationHeader02)mepsMessage.getAppHdr(); FIToFICustomerCreditTransfer08 fiToFICustomerCreditTransfer = (FIToFICustomerCreditTransfer08) mepsMessage.getDocument();

AutoParse MEPS+ Like4Like Message

//Initialize the mepsMessage
MepsMessage<?, ?> mepsMessage = new MepsMessage<>();
//Fill the mepsMessage with data from xml and validate MEPS+ Lik4Like against the xml schema
ValidationErrorList validationErrorList = mepsMessage.autoParseAndValidateXml(new ByteArrayInputStream(validMepsPacs009CoreString.getBytes()));

//Perform validation in both header and message object using mepsMessage validationErrorList.addAll(mepsMessage.autoValidate());


if (validationErrorList.isEmpty()) {     System.out.println("Message is valid");     System.out.println(mepsMessage.convertToXML()); //Get the generated xmls for head and document } else {     handleValidationError(validationErrorList); }

Construct MEPS+ Like4Like Message

//Initialize the document object
FinancialInstitutionCreditTransfer08 financialInstitutionCreditTransfer08 = new FinancialInstitutionCreditTransfer08();
financialInstitutionCreditTransfer08.parseXML(validMepsPacs009CoreDocumentString);

//We fill the elements of the message object using setters //financialInstitutionCreditTransfer08.getMessage().setGrpHdr(new GroupHeader93()) //financialInstitutionCreditTransfer08.getMessage().getGrpHdr().setMsgId("1234")


//or setElement() //financialInstitutionCreditTransfer08.setElement("GrpHdr/MsgId", "1234")


//Construct the MEPS message object using two separate objects, header, document MepsMessage<BusinessApplicationHeader02, FinancialInstitutionCreditTransfer08> mepsMessage = new MepsMessage<>(businessApplicationHeader, financialInstitutionCreditTransfer08);


//Perform validation in both header and message object using mepsMessage //Use MepsMessage.MepsMsgType enumeration object to select the matching schema (check the table of supported MEPS messages below //MepsMessage.extractMepsMsgType() can also be used ValidationErrorList validationErrorList = mepsMessage.validate(MepsMessage.MepsMsgType.PACS009CORE);


if (validationErrorList.isEmpty()) {     System.out.println("Message is valid");     System.out.println(mepsMessage.convertToXML()); //Get the generated xmls for head and document } else {     handleValidationError(validationErrorList); }

Code samples

Parse and validate MEPS+ Like4Like message

Supported MEPS+ Like4Like Message Types (v1.2)

| ISO20022 Message | MepsMsgType ENUM | Library Object class | |------------------|------------------|--------------------------------------| | camt.029.001.09 | CAMT_029 | ResolutionOfInvestigation09 | | camt.056.001.08 | CAMT_056 | FIToFIPaymentCancellationRequest08 | | pacs.008.001.08 | PACS_008 | FIToFICustomerCreditTransfer08 | | pacs.008.001.08 | PACS008STP | FIToFICustomerCreditTransfer08 | | pacs.009.001.08 | PACS009CORE | FinancialInstitutionCreditTransfer08 | | pacs.009.001.08 | PACS009COV | FinancialInstitutionCreditTransfer08 | | camt.053.001.08 | CAMT_053 | BankToCustomerStatement08 | | camt.053.001.08 | CAMT053AOS | BankToCustomerStatement08 |

TARGET2 (RTGS) messages

SDK Setup

Maven

<!-- Import the TARGET2 (RTGS) demo SDK-->
<dependency>
    <groupId>gr.datamation.mx</groupId>
    <artifactId>mx</artifactId>
    <version>24.24.0</version>
    <classifier>demo-rtgs</classifier>
</dependency>

Gradle

implementation 'gr.datamation.mx:mx:24.24.0:demo-rtgs@jar'
Please refer to General SDK Setup for more details.

Parse & Validate TARGET2 Message

In case you need to handle TARGET2 (RTGS) messages, then you need to handle objects that extend the ISO20022 classes. 
//Initialize the message object
FIToFICustomerCreditTransfer08Rtgs fiToFICustomerCreditTransfer = new FIToFICustomerCreditTransfer08Rtgs();
//Validate against the xml schema. We can also exit in case of errors in this step.
ValidationErrorList validationErrorList = fiToFICustomerCreditTransfer.validateXML(new ByteArrayInputStream(validRtgsPacs008String.getBytes()));
//Fill the message with data from xml
fiToFICustomerCreditTransfer.parseXML(validRtgsPacs008String);
//Validate both the xml schema and rules
validationErrorList.addAll(fiToFICustomerCreditTransfer.validate());

if (validationErrorList.isEmpty()) {     System.out.println(fiToFICustomerCreditTransfer.convertToXML()); //Get the generated xml } else {     System.out.println(validationErrorList); }

AutoParse TARGET2 Message

//Validate against the xml schema without knowing the message type. We can also exit in case of errors in this step.
ValidationErrorList validationErrorList = RtgsUtils.autoValidateXML(new ByteArrayInputStream(validRtgsPacs008String.getBytes()));
//Fill the message with data from xml without knowing the message type
Message message = RtgsUtils.autoParseXML(validRtgsPacs008String);
//Validate both the xml schema and rules
validationErrorList.addAll(message.validate());

if (validationErrorList.isEmpty()) {     System.out.println(fiToFICustomerCreditTransfer.convertToXML()); //Get the generated xml } else {     System.out.println(validationErrorList); }

Construct TARGET2 Message

//Initialize the message object
FIToFICustomerCreditTransfer08 fiToFICustomerCreditTransfer = new FIToFICustomerCreditTransfer08();

//We fill the elements of the message object using setters fiToFICustomerCreditTransfer.getMessage().setGrpHdr(new GroupHeader93()); fiToFICustomerCreditTransfer.getMessage().getGrpHdr().setMsgId("1234"); //or setElement() fiToFICustomerCreditTransfer.setElement("GrpHdr/MsgId", "1234");


//Perform validation ValidationErrorList validationErrorList = fiToFICustomerCreditTransfer.validate();


if (validationErrorList.isEmpty()) {     System.out.println(fiToFICustomerCreditTransfer.convertToXML()); //Get the generated xml } else {     System.out.println(validationErrorList); }

Code samples

Parse and validate TARGET2 message

Supported TARGET2 Message Types (v2.2)

| ISO20022 Message|Library Object class | Available in Demo | | --------------- |------------------- | :---------------: | | admi.007.001.01 | ReceiptAcknowledgement01Rtgs | | | camt.025.001.05 | Receipt05Rtgs | | | camt.029.001.09 | ResolutionOfInvestigation09Rtgs | | | camt.050.001.05 | LiquidityCreditTransfer05Rtgs | | | camt.053.001.08 | BankToCustomerStatement08Rtgs | | | camt.054.001.08 | BankToCustomerDebitCreditNotification08Rtgs | | | camt.056.001.08 | FIToFIPaymentCancellationRequest08Rtgs | | | pacs.002.001.10 | FIToFIPaymentStatusReport10Rtgs | | | pacs.004.001.09 | PaymentReturn09Rtgs | | | pacs.008.001.08 | FIToFICustomerCreditTransfer08Rtgs | | | pacs.009.001.08 | FinancialInstitutionCreditTransfer08Rtgs | ✓ | | pacs.010.001.03 | FinancialInstitutionDirectDebit03Rtgs | |

Auto replies

| Source Message | Reply Message | Source Class | Reply Class | AutoReplies Class | | --------------- | --------------- | ---------------------------------------- | -------------------------------------- | ------------------------------------------------- | | pacs.008.001.08 | pacs.004.001.09 | FIToFICustomerCreditTransfer08Rtgs | PaymentReturn09Rtgs | FIToFICustomerCreditTransferRtgsAutoReplies | | pacs.008.001.08 | camt.056.001.08 | FIToFICustomerCreditTransfer08Rtgs | FIToFIPaymentCancellationRequest08Rtgs | FIToFICustomerCreditTransferRtgsAutoReplies | | pacs.009.001.08 | pacs.004.001.09 | FinancialInstitutionCreditTransfer08Rtgs | PaymentReturn09Rtgs | FinancialInstitutionCreditTransferRtgsAutoReplies | | pacs.009.001.08 | camt.056.001.08 | FinancialInstitutionCreditTransfer08Rtgs | FIToFIPaymentCancellationRequest08Rtgs | FinancialInstitutionCreditTransferRtgsAutoReplies | | camt.056.001.08 | camt.029.001.09 | FIToFIPaymentCancellationRequest08Rtgs | ResolutionOfInvestigation09Rtgs | FIToFIPaymentCancellationRequestRtgsAutoReplies |

Sample code for FIToFICustomerCreditTransferRtgsAutoReplies can be found here. Sample code for FinancialInstitutionCreditTransferRtgsAutoReplies can be found here. Sample code for FIToFIPaymentCancellationRequestRtgsAutoReplies can be found here.

Please refer to general auto replies for more details.

CGI-MP messages

SDK Setup

Maven

<!-- Import the TARGET2 (RTGS) demo SDK-->
<dependency>
    <groupId>gr.datamation.mx</groupId>
    <artifactId>mx</artifactId>
    <version>24.24.0</version>
    <classifier>{CLIENT_CLASSIFIER}</classifier>
</dependency>

Gradle

implementation 'gr.datamation.mx:mx:24.24.0:{CLIENT_CLASSIFIER}@jar'
Please refer to General SDK Setup for more details.

Parse & Validate CGI-MP Message

In case you need to handle CGI-MP messages, then you need to handle objects that extend the ISO20022 classes. 
//Initialize the message object
CustomerCreditTransferInitiation09RelayServiceCgiMp customerCreditTransfer = new CustomerCreditTransferInitiation09RelayServiceCgiMp();
//Validate against the xml schema. We can also exit in case of errors in this step.
ValidationErrorList validationErrorList = customerCreditTransfer.validateXML(new ByteArrayInputStream(validPain001String.getBytes()));
//Fill the message with data from xml
customerCreditTransfer.parseXML(validPain001String);
//Validate both the xml schema and rules
validationErrorList.addAll(customerCreditTransfer.validate());

if (validationErrorList.isEmpty()) {     System.out.println(customerCreditTransfer.convertToXML()); //Get the generated xml } else {     System.out.println(validationErrorList); }

Construct CGI-MP Message

//Initialize the message object
CustomerCreditTransferInitiation09RelayServiceCgiMp customerCreditTransfer = new CustomerCreditTransferInitiation09RelayServiceCgiMp();

//We fill the elements of the message object using setters customerCreditTransfer.getMessage().setGrpHdr(new GroupHeader85()); customerCreditTransfer.getMessage().getGrpHdr().setMsgId("1234"); //or setElement() customerCreditTransfer.setElement("GrpHdr/MsgId", "1234");


//Perform validation ValidationErrorList validationErrorList = customerCreditTransfer.validate();


if (validationErrorList.isEmpty()) {     System.out.println(customerCreditTransfer.convertToXML()); //Get the generated xml } else {     System.out.println(validationErrorList); }


Code samples

Parse and validate CGI-MP message

Supported CGI-MP Message Types


| ISO20022 Message                | Library Object class                                  | |---------------------------------|-------------------------------------------------------| | pain.001.001.09.relay.service   | CustomerCreditTransferInitiation09RelayServiceCgiMp   | | pain.001.001.09.urgent.payments | CustomerCreditTransferInitiation09UrgentPaymentsCgiMp |


SEPA-EPC Credit Transfer


SDK Setup


Maven
xml gr.datamation.mx mx 24.24.0 demo-sepa 
#### Gradle
groovy implementation 'gr.datamation.mx:mx:24.24.0:demo-sepa@jar' 
Please refer to General SDK Setup for more details.

Swiftcase messages


SDK Setup


Maven
xml gr.datamation.mx mx 24.24.0 swiftcase 
#### Gradle
groovy implementation 'gr.datamation.mx:mx:24.24.0:swiftcase@jar' 
Please refer to General SDK Setup for more details.

Parse & Validate Swiftcase Message

In case you need to handle Swiftcase messages, then you need to handle objects of SwiftcaseMessage class.
java //Initialize the swiftcaseMessage SwiftcaseMessage swiftcaseMessage = new SwiftcaseMessage<>(new BusinessApplicationHeader02(), new InvestigationRequest01()); //Fill the swiftcaseMessage with data from xml validate Swiftcase against the xml schema. We can also exit in case of errors in this step. ValidationErrorList validationErrorList = swiftcaseMessage.autoParseAndValidateXml(new ByteArrayInputStream(validSwiftcaseCamt110String.getBytes())); //Perform validation in both header and message object using swiftcaseMessage //Use SwiftcaseMessage.SwiftcaseMsgType enumeration object to select the matching schema (check the table of supported Swiftcase messages below //SwiftcaseMessage.extractSwiftcaseMsgType() can also be used validationErrorList.addAll(swiftcaseMessage.validate(SwiftcaseMessage.SwiftcaseMsgType.CAMT110OTHR));

if (validationErrorList.isEmpty()) { System.out.println(investigationRequest01.convertToXML()); //Get the generated xml } else { System.out.println(validationErrorList); } //Extract the header and the core message from swiftcaseMessage object BusinessApplicationHeader02 businessApplicationHeader = (BusinessApplicationHeader02)swiftcaseMessage.getAppHdr(); InvestigationRequest01 investigationRequest01 = (InvestigationRequest01) swiftcaseMessage.getDocument(); 

### AutoParse & Validate Swiftcase Message
java //Initialize the swiftcaseMessage SwiftcaseMessage swiftcaseMessage = new SwiftcaseMessage<>(); //Fill the swiftcaseMessage with data from xml and validate Swiftcase against the xml schema. We can also exit in case of errors in this step. ValidationErrorList validationErrorList = swiftcaseMessage.autoParseAndValidateXml(new ByteArrayInputStream(validSwiftcaseCamt110String.getBytes()));

//Perform validation in both header and message object using swiftcaseMessage validationErrorList.addAll(swiftcaseMessage.autoValidate());

if (validationErrorList.isEmpty()) { System.out.println(investigationRequest01.convertToXML()); //Get the generated xml } else { System.out.println(validationErrorList); } 

### Construct Swiftcase Message
java //Initialize the header object BusinessApplicationHeader02 businessApplicationHeader = new BusinessApplicationHeader02(); businessApplicationHeader.parseXML(validSwiftcaseCamt110HeaderString);

//Initialize the document object InvestigationRequest01 investigationRequest01 = new InvestigationRequest01(); investigationRequest01.parseXML(validSwiftcaseCamt110DocumentString);

//We fill the elements of the message object using setters investigationRequest01.getMessage().setGrpHdr(new GroupHeader93()); investigationRequest01.getMessage().getGrpHdr().setMsgId("1234"); //or setElement() investigationRequest01.setElement("GrpHdr/MsgId", "1234");

//Construct the Swiftcase message object SwiftcaseMessage swiftcaseMessage = new SwiftcaseMessage<>(businessApplicationHeader, investigationRequest01);

//Perform validation in both header and message object using swiftcaseMessage //Use SwiftcaseMessage.SwiftcaseMsgType enumeration object to select the matching schema (check the table of supported Swiftcase messages below) //SwiftcaseMessage.extractSwiftcaseMsgType() can also be used ValidationErrorList validationErrorList = swiftcaseMessage.validate(SwiftcaseMessage.SwiftcaseMsgType.CAMT110OTHR);

if (validationErrorList.isEmpty()) { System.out.println(investigationRequest01.convertToXML()); //Get the generated xml } else { System.out.println(validationErrorList); } 

In case you want to enclose the Swiftcase message under another Root Element, use the code below
java swiftcaseMessage.encloseSwiftcaseMessage("RequestPayload") //In case you want RequestPayload 
### Code samples Parse and validate Swiftcase message


Supported Swiftcase Message Types


| ISO20022 Message          | SwiftcaseMsgType ENUM | Library Object class    | Available in Demo | |---------------------------|-----------------------|-------------------------|:-----------------:| | camt.110.001.01 CCNRCONR | CAMT110CCNRCONR    | investigationRequest01  |                   | | camt.111.001.02 CCNRCONR | CAMT111CCNRCONR    | InvestigationResponse02 |                   | | camt.110.001.01 OTHR      | CAMT110OTHR         | investigationRequest01  |                   | | camt.111.001.02 OTHR      | CAMT111OTHR         | InvestigationResponse02 |                   | | camt.110.001.01 RQCH      | CAMT110RQCH         | investigationRequest01  |                   | | camt.111.001.02 RQCH      | CAMT111RQCH         | InvestigationResponse02 |                   | | camt.110.001.01 RQDA      | CAMT110RQDA         | investigationRequest01  |                   | | camt.111.001.02 RQDA      | CAMT111RQDA         | InvestigationResponse02 |                   | | camt.110.001.01 RQFICOMP | CAMT110RQFICOMP    | investigationRequest01  |                   | | camt.111.001.02 RQFICOMP | CAMT111RQFICOMP    | InvestigationResponse02 |                   | | camt.110.001.01 RQFISANC | CAMT110RQFISANC    | investigationRequest01  |                   | | camt.111.001.02 RQFISANC | CAMT111RQFISANC    | InvestigationResponse02 |                   | | camt.110.001.01 RQFIUTEX | CAMT110RQFIUTEX    | investigationRequest01  |                   | | camt.111.001.02 RQFIUTEX | CAMT111RQFIUTEX    | InvestigationResponse02 |                   | | camt.110.001.01 RQUF      | CAMT110RQUF         | investigationRequest01  |                   | | camt.111.001.02 RQUF      | CAMT111RQUF         | InvestigationResponse02 |                   | | camt.110.001.01 RQVA      | CAMT110RQVA         | investigationRequest01  |                   | | camt.111.001.02 RQVA      | CAMT111RQVA         | InvestigationResponse02 |                   | | camt.110.001.01 UTAP      | CAMT110UTAP         | investigationRequest01  |                   | | camt.111.001.02 UTAP      | CAMT111UTAP         | InvestigationResponse02 |                   |


Parse & Validate SEPA Message

In case you need to handle SEPA-EPC-CT messages, then you need to handle objects that extend the ISO20022 classes.
java //Initialize the message object FIToFIPaymentStatusReport10SepaEpcCt fiToFIPaymentStatusReport = new FIToFIPaymentStatusReport10SepaEpcCt(); //Validate against the xml schema. We can also exit in case of errors in this step. ValidationErrorList validationErrorList = fiToFIPaymentStatusReport.validateXML(new ByteArrayInputStream(validSepaPacs002String.getBytes())); //Fill the message with data from xml fiToFIPaymentStatusReport.parseXML(validSepaPacs002String); //Validate both the xml schema and rules validationErrorList.addAll(fiToFIPaymentStatusReport.validate());

if (validationErrorList.isEmpty()) { System.out.println(fiToFIPaymentStatusReport.convertToXML()); //Get the generated xml } else { System.out.println(validationErrorList); } 

### Construct SEPA-EPC-CT Message
java //Initialize the message object FIToFIPaymentStatusReport10 fiToFIPaymentStatusReport = new FIToFIPaymentStatusReport10();

//We fill the elements of the message object using setters fiToFIPaymentStatusReport.getMessage().setGrpHdr(new GroupHeader93()); fiToFIPaymentStatusReport.getMessage().getGrpHdr().setMsgId("1234"); //or setElement() fiToFIPaymentStatusReport.setElement("GrpHdr/MsgId", "1234");

//Perform validation ValidationErrorList validationErrorList = fiToFIPaymentStatusReport.validate();

if (validationErrorList.isEmpty()) { System.out.println(fiToFIPaymentStatusReport.convertToXML()); //Get the generated xml } else { System.out.println(validationErrorList); } 

### Code samples Parse and validate SEPA-EPC-CT message


Supported SEPA-EPC-CT Message Types (2023 Version 1.0)


| ISO20022 Message|Library Object class                                                   | Available in Demo | | --------------- |-------------------                                                    | :---------------: | | camt.027.001.07 | ClaimNonReceipt07SepaEpcCt                                            |                   | | camt.029.001.09 | ResolutionOfInvestigation09ConfirmationPositiveReplyCamt087SepaEpcCt  |                   | | camt.029.001.09 | ResolutionOfInvestigation09NegativeReplyCamt027SepaEpcCt              |                   | | camt.029.001.09 | ResolutionOfInvestigation09NegativeReplyCamt087SepaEpcCt              |                   | | camt.029.001.09 | ResolutionOfInvestigation09NegativeReplyRecallSepaEpcCt               |                   | | camt.029.001.09 | ResolutionOfInvestigation09NegativeReplyRfroSepaEpcCt                 |                   | | camt.029.001.09 | ResolutionOfInvestigation09PositiveReplyCamt027SepaEpcCt              |                   | | camt.029.001.09 | ResolutionOfInvestigation09PositiveReplyCamt087SepaEpcCt              |                   | | camt.056.001.08 | FIToFIPaymentCancellationRequest08RecallSepaEpcCt                     |                   | | camt.056.001.08 | FIToFIPaymentCancellationRequest08RfroSepaEpcCt                       |                   | | camt.087.001.06 | RequestToModifyPayment06SepaEpcCt                                     |                   | | pacs.002.001.10 | FIToFIPaymentStatusReport10SepaEpcCt                                  | &check;           | | pacs.004.001.09 | PaymentReturn09PositiveReplyRecallSepaEpcCt                           |                   | | pacs.004.001.09 | PaymentReturn09PositiveReplyRfroSepaEpcCt                             |                   | | pacs.004.001.09 | PaymentReturn09ReturnSepaEpcCt                                        |                   | | pacs.008.001.08 | FIToFICustomerCreditTransfer08FcSepaEpcCt                             |                   | | pacs.008.001.08 | FIToFICustomerCreditTransfer08RtiSepaEpcCt                            |                   | | pacs.008.001.08 | FIToFICustomerCreditTransfer08SepaEpcCt                               |                   | | pacs.028.001.03 | FIToFIPaymentStatusRequest03InquirySepaEpcCt                          |                   | | pacs.028.001.03 | FIToFIPaymentStatusRequest03RecallSepaEpcCt                           |                   | | pacs.028.001.03 | FIToFIPaymentStatusRequest03RfroSepaEpcCt                             |                   |


Auto replies


| Source Message  | Reply Message   | Source Class                                | Reply Class                                  | AutoReplies Class                                                      | | --------------- |-----------------|---------------------------------------------------|----------------------------------------------------------|------------------------------------------------------| | pacs.008.001.08 | pacs.004.001.09 | FIToFICustomerCreditTransfer08SepaEpcCt           | PaymentReturn09ReturnSepaEpcCt                           | FIToFICustomerCreditTransferSepaEpcCtAutoReplies     | | pacs.008.001.08 | camt.056.001.08 | FIToFICustomerCreditTransfer08SepaEpcCt           | FIToFIPaymentCancellationRequest08RecallSepaEpcCt        | FIToFICustomerCreditTransferSepaEpcCtAutoReplies     | | pacs.008.001.08 | camt.029.001.09 | FIToFICustomerCreditTransfer08SepaEpcCt           | ResolutionOfInvestigation09NegativeReplyRecallSepaEpcCt  | FIToFICustomerCreditTransferSepaEpcCtAutoReplies     | | pacs.008.001.08 | camt.027.001.07 | FIToFICustomerCreditTransfer08SepaEpcCt           | ClaimNonReceipt07SepaEpcCt                               | FIToFICustomerCreditTransferSepaEpcCtAutoReplies     | | pacs.008.001.08 | camt.087.001.06 | FIToFICustomerCreditTransfer08SepaEpcCt           | RequestToModifyPayment06SepaEpcCt                        | FIToFICustomerCreditTransferSepaEpcCtAutoReplies     | | pacs.008.001.08 | pacs.028.001.03 | FIToFICustomerCreditTransfer08SepaEpcCt           | FIToFIPaymentStatusRequest03InquirySepaEpcCt             | FIToFICustomerCreditTransferSepaEpcCtAutoReplies     | | camt.056.001.08 | camt.029.001.09 | FIToFIPaymentCancellationRequest08RecallSepaEpcCt | ResolutionOfInvestigation09NegativeReplyRecallSepaEpcCt  | FIToFIPaymentCancellationRequestSepaEpcCtAutoReplies | | camt.027.001.07 | camt.029.001.09 | ClaimNonReceipt07SepaEpcCt                        | ResolutionOfInvestigation09NegativeReplyRecallSepaEpcCt  | ClaimNonReceiptSepaEpcCtAutoReplies                           | | camt.027.001.07 | camt.029.001.09 | ClaimNonReceipt07SepaEpcCt                        | ResolutionOfInvestigation09PositiveReplyCamt027SepaEpcCt | ClaimNonReceiptSepaEpcCtAutoReplies                           | | camt.087.001.06 | camt.029.001.09 | RequestToModifyPayment06SepaEpcCt                 | ResolutionOfInvestigation09NegativeReplyCamt087SepaEpcCt | ClaimNonReceiptSepaEpcCtAutoReplies                           | | camt.087.001.06 | camt.029.001.09 | RequestToModifyPayment06SepaEpcCt                 | ResolutionOfInvestigation09PositiveReplyCamt087SepaEpcCt  | RequestToModifyPaymentSepaEpcCtAutoReplies                    |


Sample code for FIToFICustomerCreditTransferSepaEpcCtAutoReplies can be found here.   Sample code for FIToFIPaymentCancellationRequestSepaEpcCtAutoReplies can be found here.   Sample code for ClaimNonReceiptSepaEpcCtAutoReplies can be found here.   Sample code for RequestToModifyPaymentSepaEpcCtAutoReplies can be found here.


Please refer to general auto replies for more details.


SEPA-EPC Direct Debit


SDK Setup


Maven
xml gr.datamation.mx mx 24.24.0 demo-sepa 
#### Gradle
groovy implementation 'gr.datamation.mx:mx:24.24.0:demo-sepa@jar' 
Please refer to General SDK Setup for more details.

Parse & Validate SEPA Message

In case you need to handle SEPA-EPC-DD messages, then you need to handle objects that extend the ISO20022 classes.
java //Initi
README truncated. View on GitHub
🔗 More in this category
wilsonfreitas
wilsonfreitas/awesome-quant
A curated list of insanely awesome libraries, packages and resources for Quants (Quantitative Finance)
★ 27.5k
 AI4Finance-Foundation
AI4Finance-Foundation/FinGPT
FinGPT: Open-Source Financial Large Language Models! Revolutionize 🔥 We release the trained model on HuggingFace.
★ 20.8k
 AI4Finance-Foundation
AI4Finance-Foundation/FinRL
FinRL®: Financial Reinforcement Learning. 🔥
★ 15.7k
 Superalgos
Superalgos/Superalgos
Free, open-source crypto trading bot, automated bitcoin / cryptocurrency trading software, algorithmic trading bots. Visually design your crypto trading bot, leveraging an integrated charting system, data-mining, backtesting, paper trading, and multi-server crypto bot deployments.
★ 5.6k
 akaunting
akaunting/akaunting
Online Accounting Software
★ 9.9k
 StockSharp
StockSharp/StockSharp
Algorithmic trading and quantitative trading open source platform to develop trading robots (stock markets, forex, crypto, bitcoins, and options).
★ 10.3k
 lballabio
lballabio/QuantLib
The QuantLib C++ library
★ 7.3k
 ghostfolio
ghostfolio/ghostfolio
Open Source Wealth Management Software. Angular + NestJS + Prisma + Nx + TypeScript 🤍
★ 8.9k
 donoaccestag
donoaccestag/forex-mt5-trading-bot
polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot
★ 311
 imbue-bit
imbue-bit/AlphaGPT
基于深度强化学习的开源自动因子工厂。
★ 2.8k
 Gamma-Trading-Org
Gamma-Trading-Org/polymarket-trading-bot
polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot polymarket trading bot
★ 293
 apache
apache/fineract
Apache Fineract
★ 2.3k

© 2026 GitRepoTrend · Payment-Components/demo-iso20022 · Updated daily from GitHub