IBM Support

Release notes for IBM Sterling Transformation Extender, Pack for Financial Payments, V11.0.2.0

Release Notes


Abstract

These release notes contain the information required to install and configure the IBM Sterling Transformation Extender, Pack for Financial Payments, version V11.0.2.0

Content

Pack for Financial Payments V11.0.2.0 release notes.

© Copyright IBM Corporation 2005, 2016. All Rights Reserved.
© Copyright HCL Technologies Ltd, 2017, 2025. All Rights Reserved.

=====================================================================
CONTENTS
=====================================================================

=====================================================================
ABOUT THIS RELEASE
====================================================================

Where to find the software to download

To download the software for this version of the IBM Sterling Transformation Extender Pack for Financial Payments, go to Passport Advantage. This location will direct you to the Passport Advantage (PA) and Passport Advantage Express (PAE) overview page. Passport Advantage (PA) and Passport Advantage Express (PAE) are comprehensive IBM programs by which Clients may order Eligible Products. Customers can search PA and PAE for the following part numbers to download files for windows install and Red Hat OpenShift which include the project files used with the Design Server and certified containers.

Part numbers for Financial Payments V11.0.2.0, search:

  • Windows install - M0VS0ML
  • Red Hat OpenShift - M0VS1EN

What's new in this release
SWIFT component:
  • Support is provided for 2025 SRG Standards
  • Corresponding updates are as follows:
    • SWIFT type trees
    • LMF maps and trees
    • Java Validation Component and support for ISO 20022 Contingency Measures (ICM) additional network rules for SWIFT MT Category 1 and 2 payment instruction messages
    • MX schemas, type trees, and validation framework
  • For ITX version 11.0.2 and later:
    • IFD deployment script will need to save .msl to <TX_INSTALL_DIR>/system folder.
    • As a prerequisite, users will need to edit the property file to replace generic PACK_INSTALL_DIR with the actual location where the ZIP distro was unzipped.
    • Utility jvcsetup.sh in swiftMTjvcConfig.tar.gz is for Docker and Podman based installations.
    • For Design Server installation:
      • Copy the jvalccyy.jar and jvcwrap.jar into the directory set in the config.yaml server.persistence.libs, by default, this is set to /opt/txlibs. then restart the tx-server, for example ./ITX stop and then ./ITX start.
    • Configuring JVC on Design Server:
      • After importing the swiftMTCompliance.zip project, the jvalccyy.prop file must be copied into the workdir directory above directory set in the config.yaml server.persistence.files, default settings is /opt/txfiles/workdir.
      • On the project, update the map rule on the validate_message map, on output card #1 item JvalPropPath. Change the map rule from =NONE to the location of the jvalccyy.prop.
        For example:
        On UNIX
         ="DS_DATA_DIR/workdir"
        On WINDOWS, 
         ="DS_DATA_DIR\\workdir"
        DS_DATA_DIR refers to the Design Server data directory, set in the config.yaml server.persistence.files previously TX_FILE_DIR.
    • Post EAP updates:
      • Updated swift_iso15022_2025.mtt to change Tag 94a in MT524 Sequence B and MT543 Sequence C from mandatory to optional.
      • Updated MT566.xml to modify Tag 97D in Sequence D2, allowing the “Identification of Blockchain or Wallet” field a maximum length of 140 characters.
      • Updated MT300.xml to change Tag 22U format to 12x.
      • Updated swift_iso7775_2025.mtt
        • MT097 updated to remove Tags 433 and 434.
        • MT030 removed from Live System Messages list.
        • MT199 and MT299 updated to remove CASE structure.
      • Updated descriptions for error codes C44 and C47 to reference Sequence B.
      • Updated and clarified network rules for error codes E62 and C71 on MT567.
      • Field 70 ICM rules enforced for: MT103 COR/STP, MT202 COV, and MT205 COV.
      • Field 72 ICM rules enforced for: MT200, MT202 COR/COV, and MT205 COR/COV.
      • Field 72 NOT STP ICM rules enforced for: MT103, MT202 COV, and MT205 COV.
      • Update swift_mt567_tolmf to handle multiple occurrences of tag 36a on Sequence A2 on MT567.
NACHA component:
Support 2025 NACHA Operating Rules related to Company Entry Description were previously implemented in ACH 2024 type trees, no ACH 2025 type trees for this release.
FIX component:
Support FIX 5.0 SP2 Extension Packs (FIX Latest) up to EP299
SEPA component:
  • Support 2025 EPC SCT/SDD schemas, including both structured and hybrid formatted addresses
  • Enhanced SEPA compliance map configuration to support UNIFI validation and to allow unstructured address formats
  • Update SEPA EPC example with SDD Core and B2B test files, along with improved documentation for setup and configuration
  • Original Message name identification for matching will be restricted to message variants and versions supported by this Pack
Miscellaneous:
  • For ITX 11.0.2,
    • build JVC jars using IBM Semeru JAVA 17
    • Execute <TX_INSTALL_DIR>\DTXcommon.bat script prior to running any of the scripts to avoid errors
      • build_deploy_mx_validation.bat
      • build_mt_mx_translation.bat
      • build_deploy_lmf.bat
      • build_deploy_jvc.bat
      • build_epc_mapsandschemas.bat
  • ZIP distros are digitally signed 
Deprecated components:
  • SWIFT MT-MX translation example maps
  • SWIFT Sterling B2B Integration examples
  • SEPA EPC rules related to ‘matching’ elements with original messages

=====================================================================
DOCUMENTATION NOTES
====================================================================

View the latest product documentation
See the online documentation for the latest documentation for this product.
Financial Payments latest V11.0.2.0 documentation is available in the V11.0.2.0 online documentation, see What's new in Packs V11.0.2.0 for more details.

ACH_ISO Mapping Assumptions spreadsheets:

The ACH_ISO Mapping Assumptions spreadsheets are used with the examples in the NACHA component of the pack. You can download these tables from this location:

ACH_ISO Mapping Assumptions spreadsheets

LMF mapping tables

The LMF mapping tables used with the SWIFT component of the pack can be downloaded from this location:

LMF Mapping Tables

Translated documentation

The online documentation is provided in these languages:
  • English (United States)
  • French

Viewing translated documentation

To display translated content in the online documentation:

  1. Open the online documentation. A typical URL to the documentation is shown below:
    https://www.ibm.com/docs/en/ste
  2. Edit the URL to include the desired language code immediately after "/ibm.com/docs":
    https://www.ibm.com/docs/<language code>/ste
  3. As an example, enter the language code "/fr" to display French content.
  4. Remove the "/<language code>" to return to the English display. 

=====================================================================
INSTALLATION
====================================================================
Installation prerequisites

One of the following versions of the base product must be installed:
  • 11.0.2.0
  • 11.0.1.1
  • 11.0.0.0
  • 10.1.2.1
  • 10.1.1.1
  • 10.1.0.2
For IBM Transformation Extender Advanced: See the Release Notes for IBM Transformation Extender Advanced.

Note: This product is supported on the same platforms as the prerequisite products.

Deploying the pack to other operating systems
See the individual component documentation for information on deploying to other operating system platforms.

Installing the pack on Windows systems
Follow these steps to install the pack on Windows systems:

  • Obtain the image from Passport Advantage.
  • The pack will not require any installation program.
Using with Design Studio, the following signed ZIP files will be available per supported TX version:
  • finpay_11.0.2.0_v1010.zip.signed.zip
  • finpay_11.0.2.0_v1011.zip.signed.zip
  • finpay_11.0.2.0_v1012.zip.signed.zip
  • finpay_11.0.2.0_v1100.zip.signed.zip
  • finpay_11.0.2.0_v1101.zip.signed.zip
  • finpay_11.0.2.0_v1102.zip.signed.zi
Using with Design Studio, the following signed ZIP files will be available per supported TX-RS/TX-LS version:
  • finpay_11.0.2.0_v1010_4c.zip.signed.zip
  • finpay_11.0.2.0_v1011_4c.zip.signed.zip
  • finpay_11.0.2.0_v1012_4c.zip.signed.zip
  • finpay_11.0.2.0_v1100_4c.zip.signed.zip
  • finpay_11.0.2.0_v1101_4c.zip.signed.zip
  • finpay_11.0.2.0_v1102_4c.zip.signed.zip
     
To install:
  1. Select signed zip based on preferred TX version.
  2. Unzip the signed.zip file to a temporary folder.
  3. Navigate to the temporary folder, select the .zip file.
  4. Right-click to select Extract All, and then Select a Destination and Extract Files on Files will be extracted to this folder:
  5. Click Browse and navigate under <TX_install_dir>
    For TX V11.0.2, define folder C:/IBM/TransformationExtender_11.0.2
  6. Select the packs folder (create folder if needed).
  7. Click Extract.
  8. Verify folder was created, that is
    <install_dir>/packs/financial_payments_vn.n.n.n
     For TX V11.0.2, under C:/IBM/TransformationExtender_11.0.2/ packs/financial_payments_v11.0.2.0
  9. Read the license files.
To uninstall:
  1. Delete the 'financial_payments_v11.0.2.0' folder that was created in the previous step.
  2. Delete the temporary folder and all its contents after extraction.
Using with Design Server User Interface, the following signed ZIP file will contain all projects that can be imported:
  • IBM_financialpayments_11.0.2.0.zip.signed.zip
To install:
  1. Unzip the signed.zip file to a temporary folder.
  2. Navigate to the temporary folder, select the .zip file, and extract content from the temporary folder.
  3. Read the license files.
  4. Select and import project zip using Design Server UI.
     
To uninstall:
  1. Delete the project previously imported.
  2. Delete the temporary folder and all its contents after extraction.
Additional configuration for MT JVC validation
Pre-requisites:
The swiftMTjvcConfig.tar.gz file is contained within the UIProjecImports directory.
The UIProjectImports directory is located in the following location:
<install_dir>/packs/financial_payments_vn.n.n.n/UIProjectImports
Where, <install_dir> is the location where the pack zip distro was extracted and n.n.n.n is the current version of the pack.
Extract the following from swiftMTjvcConfig.tar.gz file.
  • jvcwrap.jar
  • jvalccyy.jar
For Design Studio, will require administrative rights:
Copy jars to <TX_install_dir>/extjar
For Design Server installation:
See section ‘CONFIGURATION FILES FOR DESIGN SERVER’

=====================================================================
USING THE PACK WITH THE IBM DESIGN SERVER
=====================================================================

  1. Login to the Design Server.
  2. Click the Import Project icon.
  3. In the Import Project dialog, drag the .zip file into the Project Zip File box.
  4. Click the Import button to import the project.
 

=====================================================================
PROJECT FILES
=====================================================================

The following projects are available either in: 

  • IBM_financialpayments_11.0.2.0.zip when the file is unzipped or 
  • Installation directory UIProjectImports 
    <install_dir>/packs/financial_payments_vn.n.n.n/UIProjectImports

The project import files are provided as a convenience and should not be used with Windows based Design Studio implementations.
You must have administrative privileges to import the projects.
Each of the projects is described briefly in the following section:

fixFMLadv.zip - FIX mapping from/to FIXML Advertisement example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML Advertisement example”.
fixFMLallocinstrctn.zip - FIX mapping from/to FIXML Allocation Instruction example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML Allocation Instruction example”.
fixFMLallocinstrctnack.zip - FIX mapping from/to FIXML Allocation Instruction Acknowledgement example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML Allocation Instruction Acknowledgement example”.
fixdktrdFML.zip - FIX mapping from/to FIXML Don’t Know Trade example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML Don’t Know Trade example”.
fixFMLemail.zip - FIX mapping from/to FIXML Email example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML Email example”.
fixFMLexecrpt.zip - FIX mapping from/to FIXML Execution Report example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML Execution Report example”.
fixFMLioi.zip - FIX mapping from/to FIXML Indication of Interest example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML Indication of Interest example”.
fixFMLlistcxlreq.zip - FIX mapping from/to FIXML List Cancel Request example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML List Cancel Request example”.
fixFMLlistexct.zip - FIX mapping from/to FIXML List Execute example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML List Execute example”.
fixFMLliststat.zip - FIX mapping from/to FIXML List Status example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML List Status example”.
fixFMLliststatreq.zip - FIX mapping from/to FIXML List Status Request example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML List Status Request example”.
fixFMLnewordlist.zip - FIX mapping from/to FIXML New Order List example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML New Order List example”.
fixFMLnews.zip - FIX mapping from/to FIXML News example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML News example”.
fixFMLordcxlreq.zip - FIX mapping from/to FIXML Order Cancel Reject example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML Order Cancel Reject example”.
fixFMLorder.zip - FIX mapping from/to FIXML New Order Single example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML New Order Single example”.
fixFMLorderstatreq.zip - FIX mapping from/to FIXML Order Status Request example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML Order Status Request example”.
fixFMLquot.zip - FIX mapping from/to FIXML Quote example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML Quote example”.
fixFMLquotreq.zip - FIX mapping from/to FIXML Quote Request example.
Contains the files, schemas, and maps required to run the “FIX mapping from/to FIXML Quote Request example”.
fixSchemas.zip - FIX schemas
Contains common FIX example schemas.
nachaContestedDishonoredReturn.zip - ACH Contested Dishonored Return example
Contains the files, schemas, and maps required to run the NACHA “ACH Contested Dishonored Return example”.
nachaDishonoredReturn.zip - ACH Dishonored Return example
Contains the files, schemas, and maps required to run the NACHA “ACH Dishonored Return example”.
nachaEDI.zip - ACH EDI example
Contains the files, schemas, and maps required to run the NACHA “ACH EDI example”.
nachaISO20022CreditTransfer.zip - ACH ISO20022 Credit Transfer example
Contains the files, schemas, and maps required to run the “ACH ISO20022 Credit Transfer example”.
nachaISO20022DirectDebit.zip - ACH ISO20022 Direct Debit example
Contains the files, schemas, and maps required to run the “ACH ISO20022 Direct Debit example”.
nachaISO20022Rejects.zip - ACH ISO20022 Rejects example
Contains the files, schemas, and maps required to run the “ACH ISO20022 Rejects example”.
nachaISO20022 Returns.zip - ACH ISO20022 Returns example
Contains the files, schemas, and maps required to run the “ACH ISO20022 Returns example”.
nachaPaymentRelatedInfo.zip - ACH Payment Related Information example
Contains the files, schemas, and maps required to run the “ACH Payment Related Information example”.
nachaRefusedNotificationOfChange.zip - ACH Refused Notification of Change example
Contains the files, schemas, and maps required to run the “ACH Refused Notification of Change example”.
nachaReturnedEntriesReport.zip - ACH Returned Entries Report example
Contains the files, schemas, and maps required to run the “ACH Returned Entries Report example”.
nachaReturnNotificationOfChange.zip - ACH Return Notification of Change example
Contains the files, schemas, and maps required to run the “ACH Return Notification of Change example”.
nachaSchemas.zip - NACHA schemas
Contains common NACHA example schemas.
nachaSWIFT.zip - ACH mapping from/to SWIFT example
Contains the files, schemas, and maps required to run the “ACH mapping from/to SWIFT example”.
nachaValidation.zip - ACH Validation example
Contains the files, schemas, and maps required to run the “ACH Validation example”.
nachaXML.zip - XML to ACH PPD example
Contains the files, schemas, and maps required to run the “XML to ACH PPD example”.
sepaCompliance.zip - SEPA compliance validation
This validation framework will take in any UNIFI 20022 formatted XML message and validate UNIFI rules and the set of rules published by the EPC.
sepaDE.zip - DTAUS SEPA Example
Contains the files, schemas, and maps required to run the “DTAUS SEPA Example”. (German example.)
sepaEPC.zip - SEPA EPC Validation Example
Contains the files, schemas, and maps required to run the “SEPA EPC Validation Example”.
sepaFR.zip - MINOS/CFONB SEPA Example
Contains the files, schemas, and maps required to run the “MINOS/CFONB SEPA Example”. (French example.)
sepaIT.zip - RNI SEPA Example
Contains the files, schemas, and maps required to run the “RNI SEPA Example”. (Italian example.)
sepaPainPacs.zip - PAIN/PACS Example
Contains the files, schemas, and maps required to run the “PAIN/PACS Example”.
sepaSchemas.zip - SEPA schemas
Contains common SEPA example schemas.
sepaSwiftFin.zip - SWIFTNet FIN/ SEPA Example
Contains the files, schemas, and maps required to run the “SWIFTNet FIN/ SEPA Example”.
sepaUK.zip - BACS / SEPA Example
Contains the files, schemas, and maps required to run the “BACS / SEPA Example”. (U.K. example.)
swiftBankFileXML.zip - SWIFT BIC/CCY files to XML
Contains common SWIFT bictoxml and currencytoxml executable maps.
swiftFromLMF.zip - SWIFT from LMF
Contains maps that facilitate mapping data to SWIFT from Logical Message Format.
swiftJVCReport.zip - SWIFT MT JVC Report example
Contains the files, schemas, and maps required to run the “SWIFT MT JVC Report example”.
swiftMT950Split.zip - SWIFT MT950 example
Contains the files, schemas, and maps needed to run the SWIFT MT950 Splitter map example.
swiftMTCompliance.zip - SWIFT MT Java Validation Component (JVC)
Contains the files, schemas, and maps required to run SWIFT MT compliance.
swiftMTmxTranslation.zip - SWIFT MT to MX Translation example
Contains the files, schemas, and maps required to run the “SWIFT MT to MX Translation maps example”.
swiftMXmtTranslation.zip - SWIFT MX to MT Translation example
Contains the files, schemas, and maps required to run the “SWIFT MX to MT Translation maps example”.
swiftMTSchemas.zip - SWIFT MT schemas
Contains schemas that provide a full syntactic definition of the SWIFT MT user-to-user messages.
swiftMXCompliance.zip - SWIFT MX compliance schemas
Contains schemas that are needed to run the SWIFT Compliance example.
swiftMXmsgPackage.zip - SWIFT MX Message Bundle and Unbundle map example
Contains the files, schemas, and maps required to run the “SWIFT MX Message Bundle and Unbundle map example”.
swiftMXschemas.zip - SWIFT MX schemas
Contains schemas that provide a full syntactic definition of the SWIFT MX user-to-user messages,
swiftToLMF.zip - SWIFT to LMF
Contains maps that facilitate mapping data to SWIFT to Logical Message Format.
swiftUCapi.zip - SWIFT Universal Confirmation API example 
Contains maps that generate Universal Confirmation MT199 from SWIFT Tracker PaymentStatusRequest API. 
swiftUCcsv.zip - SWIFT Universal Confirmation CSV example 
Contains maps that generate Universal Confirmation MT199 from CSV File Structure payment confirmation. 
swiftUCfin.zip - SWIFT Universal Confirmation SWIFT FIN example 
Contains maps that generate Universal Confirmation MT199 from SWIFT FIN MT103. 

=====================================================================
CONFIGURATION FILES FOR DESIGN SERVER
=====================================================================

The swiftMTjvcConfig.tar.gz file is contained within the UIProjectImports directory.

The UIProjectImports directory is located in the following location:
<install_dir>/packs/financial_payments_vn.n.n.n/UIProjectImports
Where <install_dir> is the location where the pack zip distro was extracted and n.n.n.n is the current version of the pack.
Use these steps to run this file:

Before you import the swiftMTCompliance.zip file, follow these steps.
Perform the steps in the same directory location as the Design Server is installed:
  1. Create a temp directory called packs.
    Example: /home/user/packs
  2. For UNIX environment, FTP (in binary mode) the swiftMTjvcConfig.tar.gz to the pack's directory defined in step 1.
  3. Untar the swiftMTjvcConfig.tar.gz file
    Example:
    $ tar -zxf swiftMTjvcConfig.tar.gz
  4. For container based Design Server installation,
    Run the jvcsetup.sh script.
    For example:
    $ ./jvcsetup.sh
    The script copies the following to the ITX server:
    jvcwrap.jar
    jvalccyy.jar
    packs/swift folder and sub-folders, includes the jvalccyy.prop and XML metadata.
    OPTIONAL: Run the cleanjvc.sh script.
    For example:
    $ ./cleanjvc.sh
    The script removes the following to the ITX server:
    jvcwrap.jar
    jvalccyy.jar
    packs/swift folder and sub-folders, includes the jvalccyy.prop and XML metadata.
  5. For Native based Design Server installation,
    Copy the following into the directory defined in config.yaml server.persistence.libs, by default, this is set to /opt/txlibs.
    jvcwrap.jar
    jvalccyy.jar
    Restart the running application ./ITX stop, and then ./ITX start.
  6. After importing the swiftMTCompliance.zip project, 
    • The jvalccyy.prop file must be copied into the ‘workdir’ directory under directory set in the config.yaml server.persistence.files, default settings is /opt/txfiles/workdir.
    • On the project, update the map rule on the validate_message map, on output card #1 item JvalPropPath. Change the map rule from =NONE to the location of the jvalccyy.prop.
    • Example:
      • On UNIX
        ="DS_DATA_DIR/workdir"
      • On WINDOWS
        ="DS_DATA_DIR\\workdir"
        DS_DATA_DIR refers to the Design Server data directory, set in the config.yaml server.persistence.files previously TX_FILE_DIR
  7. Restart Design Server: ./ITX stop and ./ITX start
    NOTE: To reflect any jvalccyyy.prop updates then repeat step 7.

=====================================================================

USING THE SEPA EPC VALIDATION EXAMPLE
=====================================================================
Follow these procedures to use the SEPA EPC Validation example.

Before using this example, the EPC Technical Validation Set schemas must be downloaded.

These schemas come with an EPC disclaimer:
Disclaimer: SEPA XSDs are not developed for ‘production’ purposes, they are to instantiate the business rules and restrictions contained in the implementation guidelines in a formal interchange format, sometimes referred to as Technical Validation Subsets (TVSs). Production instantiations should refer to the default ISO 20022 namespaces.

For Direct Debit implementation:
Download the Direct Debit schemas and unzip them into the directory:
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data

Following the links below (all the schema files will need to be renamed to match the name of the ISO20022 schema name):

Direct Debit Core Scheme Customer-to-PSP Schemas:
Download "EPC130-08 SDD Core C2PSP 2025 V1.0 XSD.zip" from:
https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-direct-debit-core-customer-psp-implementation-1  
Rename the schemas included in this .zip file to remove the prefix - 'EPC130-08_2025_V1.0_' from each of the file names.

Direct Debit Core Scheme Inter-PSP Schemas:
Download "EPC114-06 SDD Core Inter-PSP IG 2025 V1.0 XSD.zip" from  
https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-direct-debit-core-inter-psp-implementation-1  
Rename the schemas included in this .zip file to remove the prefix - 'EPC114-06_2025_V1.0_' from each of the file names.

Direct Debit Core Scheme e-Mandate Service Schemas:
Download "EPC002-09 SDD Core e-Mandate Service IG 2025 V1.0 XSD.zip" from  
https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-direct-debit-core-e-mandate-service-1  
Rename the schemas included in this .zip file to remove the prefix - 'EPC002-09_2025_V1.0_' from each of the file names.
Note: Copy all the schema .mtx files from subdirectory <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd/core to <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd

Direct Debit Business-to-Business (B2B) Scheme Customer-to-PSP Schemas:
Download "EPC131-08 SDD B2B C2PSP IG 2025 V1.0 XSD.zip" from  
https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-direct-debit-business-business-customer-psp-1  
Rename the schemas included in this .zip file to remove the prefix -
            'EPC131-08_2025_V1.0_' from each of the file names.

Direct Debit Business-to-Business (B2B) Inter-PSP Schemas:
Download "EPC301-07 SDD B2B Inter-PSP IG 2025 V1.0 XSD.zip" from  
https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-direct-debit-business-business-inter-psp-1  
Rename the schemas included in this zip file to remove the prefix -
   'EPC301-07_2025_V1.0_' from each of the file names.

Direct Debit Business-to-Business Scheme e-Mandate Service Schemas:
Download "EPC129-09 SDD B2B e-Mandate Service IG 2025 V1.0 XSD.zip" from  
https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-direct-debit-business-business-e-mandate-service-1  
Rename the schemas included in this zip file to remove the prefix - 'EPC129-09_2025_V1.0_' from each of the file names.

Note: Copy all the schema .mtx files from subdirectory
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/b2b to 
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd

For Credit Transfer implementation:
Download the Credit Transfer schemas and unzip them into a directory:
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/ct
Following the links below:
Credit Transfer Scheme Inter-PSP Schemas:
Download "EPC115-06 SCT Inter-PSP IG 2025 V1.0 XSD Update.zip" from
https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-credit-transfer-inter-psp-implementation-1
Rename the schemas included in this zip file to remove the prefix -
   'EPC115-06_2025_V1.0_' from each of the file names.

Credit Transfer Scheme Customer-to-PSP Schemas:
Download "EPC132-08 SCT C2PSP IG 2025 V1.0 XSD Update.zip" from  
https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-credit-transfer-customer-psp-implementation-1  
Rename the schemas included in this zip file to remove the prefix -
  'EPC132-08_2025_V1.0_' from each of the file names.
Note:

  • For schema pain.001.001.09_TB.xsd, replace existing line 793 
    <xs:enumeration value=""/> with <!--xs:enumeration value=""/-->
  •  For schema pacs.008.001.08_F&C.xsd, rename to pacs.008.001.08_FC.xsd before adding to the ct directory
  • For schema camt.029.001.09_NegReCall.xsd, rename to 
    camt.029.001.09_NegReRecall.xsd before adding to the ct directory
    (this from errata updates).
Directory structure:
The following directory structure is used:
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data - sample input test data for valid, invalid schema, and invalid rule tests. This folder  contains all the SCT input test files and by default also all the SDD CORE input test files
 
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/ct - sample SCT input test data for valid, invalid schema, and invalid rule tests

<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/dd - location of the test .xml files copied from either core or b2b subdirectories files.
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/dd/core - sample SDD CORE input test data for valid, invalid schema, and invalid rule tests.
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/dd/b2b - sample SDD B2B input test data for valid, invalid schema, and invalid rule tests.

<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas - example validation maps and deploy script.

<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/ct - schemas .mtx files and storage for the user downloaded EPC credit transfer schemas.

<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd - location of the schema .mtx files copied from either core or b2b subdirectories schemas. By default it will contain the file from the core subdirectory.

<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd/core - schema .mtx files and storage for the user downloaded EPC direct debit core schemas.

<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd/b2b - schema .mtx files and storage for the user downloaded EPC direct debit b2b schemas.

For schema pain.001.001.03_TransferBack.xsd, replace existing line 732 <xs:enumeration value=""/> with <!--xs:enumeration value=""/-->

Note: If use of b2b is desired, copy all the schema .mtx files from subdirectory
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd/b2b to 
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd

and all input  test files from subdirectory
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/dd/b2b to 
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data. 


If use of core is desired and has previously been replaced with b2b, copy all the schema .mtx files from subdirectory
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd/core to 
<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd

and copy all input test files from subdirectory 

<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/dd/core to

<install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data.

Run the SEPA EPC Validation example on Design studio
These steps describe how to run the Validation using the EPC schemas example:

About this task:

If you use the deploy script, the example maps are deployed to <install_dir>/packs/financial_payments_vn.n.n.n/sepa/mapsandschemas from the example directory. The deployed maps replace any existing compiles of the sepa_validation map source. The maps are run using sepvalid.mmc the same way as instructed in the Pack for Financial Payments user documentation. Several steps to use the correct data files and schemas need to be executed before running the deploy script, as described in steps below.

Procedure:

  1. Download the SCT and SDD schemas from SEPA.
  2. Choose ONE of the following options based on your SDD schema type:
    • If using SDD CORE schemas: Add the downloaded schemas to the following folders:Download the schemas from SEPA from the location(s) described in the previous section.
      • <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/ct (SCT schemas)
      • <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd/core (SDD CORE schemas)
      • <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd (SDD CORE schemas)
    • If using SDD B2B schemas: Add the downloaded schemas to the following folders:
      • <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/ct (SCT schemas)
      • <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd/b2b (SDD B2B schemas)
      • <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd (SDD B2B schemas)
  3. Choose ONE of the following options based on your SDD schema type:
    • If using SDD CORE schemas: Copy the .mtx files from <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd/core to <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd. Also, copy the .xml files in
      <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/dd/core to <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/dd
    • If using SDD B2B schemas: Copy the .mtx files from
      <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd/b2b to <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd. Also, copy the .xml files in
      <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/dd/b2b to
      <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/mapsandschemas/dd. Also, copy the .xml files in
      <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/dd/b2b to <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas/data/dd
    • Note: By default, the .mtx files and the .xml data files correspond to CORE schemas.
  4. Execute the deploy script build_epc_mapsandschemas.bat on
    <install_dir>/packs/financial_payments_vn.n.n.n/sepa/examples/epc_mapsandschemas. This step must be repeated when switching between SDD/CORE and SDD/B2B.
  5. Use the Design Studio to open the following map source file:
    <install_dir>/packs/financial_payments_vn.n.n.n/sepa/mapsandschemas/sepa_validation.mms
  6. Open map sepvalid.
  7. Verify the input and output card settings to ensure the correct files are being used.
  8. Build the following maps in the source file:
    • sepvalid
    • seplib05_extract_error_msg
  9. Run the following transformation map:
    • sepvalid
Run the SEPA EPC Validation example on Design Server:
Before you can run the SEPA EPC Validation example and import the sepaEPC.zip into Design Server, you must add the schemas that you download from SEPA to several folders within the sepaEPC.zip file, as described in steps below.
About this task:
These steps describe how to run the EPC SEPA Validation example.
Procedure:
  1. Download the SCT and SDD schemas from SEPA.
  2. Unzip the contents of the sepaEPC.zip.
  3. Choose ONE of the following options based on your SDD schema type:
    • If using SDD CORE schemas: Add the downloaded schemas to the following folders:
      1. filedata/schemas/ct (SCT schemas)
      2. filedata/schemas/dd/core (SDD CORE schemas)
      3. filedata/schemas/dd (SDD CORE schemas)
      4. schemadata/schemas/ct (SCT schemas)
      5. schemadata/schemas/dd/core (SDD CORE schemas)
      6. schemadata/schemas/dd (SDD CORE schemas)
    • If using SDD B2B schemas: Add the downloaded schemas to the following folders:
      1. filedata/schemas/ct (SCT schemas)
      2. filedata/schemas/dd/b2bcore (SDD B2B schemas)
      3. filedata/schemas/dd (SDD B2B schemas)
      4. schemadata/schemas/ct (SCT schemas)
      5. schemadata/schemas/dd/b2b (SDD B2B schemas)
      6. schemadata/schemas/dd (SDD B2B schemas)
  4. Choose ONE of the following options based on your SDD schema type:
    • If using SDD CORE schemas: Copy the .mtx files from schemadata/schemas/dd/core to schemadata/schemas/dd. Also, copy the .xml files from filedata/data/dd/core to filedata/data.
    • If using SDD B2B schemas: Copy the .mtx files from schemadata/schemas/dd/b2b to schemadata/schemas/dd. Also, copy the .xml files from filedata/data/dd/b2b to filedata/data.
      Note: By default, when opening the sepaEPC.zip project, the .mtx files and the .xml data files correspond to CORE schemas.
  5. Compress the following folders into a compressed file called: sepaEPC_updt.zip.
    • filedata
    • files
    • maps
    • schemadata
    • schemas
    • __description__
  6. Import into the Design Server as described in Importing projects.
  7. Create a package for the project and build all the maps.
  8. Open the sepaEPC_updt.zip project.
  9. Run the following map: sepvalid
  10. View the output. Go to the map Diagram-Result, and hover the cursor over Target, then select View Data.
  11. To download the output file, see How to download output files.

=====================================================================
VERIFY SIGNATURE AND CERTIFICATES 
=====================================================================

Prerequisites:

  • openssl

Notes:

Each signed ZIP (*.signed.zip) file contains:

  • Zip file that was signed
  • Signature (*.zip.sig)
  • Public key (*.pub.key)
  • Certificate (*.cer)
  • Certificate chain (*.chain)
  1. Using openssl with the signature file, public key, and the zip file distro, validate the digital signature:
    openssl dgst -sha256 -verify HCLITXkey.pem.pub.key -signature <signature file>.zip.sig <zip file distro>.zip
    Example:
    openssl dgst -sha256 -verify HCLITXkey.pem.pub.key -signature finpay_11.0.2.0_v1101.zip.sig finpay_11.0.2.0_v1101.zip
    Expected result:
    “Verified OK”.
  2. Optional: Verify that the public key comes from the provided certificate.
    1. Extract the public key from the certificate:
      openssl x509 -noout -pubkey -in HCLITXkey.pem.cer
    2. Compared to the content of the public key:
      type HCLITXkey.pem.pub.key.
      Expected result:
      Content from step 2.1 should match content of step 2.2.
  3. Optional: Validate the code signing certificate.
    1. Validate the certificate that was used to sign the zip file distro:
      openssl x509 -inform pem -in HCLITXkey.pem.cer -noout -subject -issuer -startdate -enddate
      Expected result: 
      Usage date is within “notBefore” and “notAfter” date attributes.
    2. Verify that the certificate has not been revoked:
      openssl ocsp -no_nonce -issuer HCLITXkey.pem.chain -cert HCLITXkey.pem.cer -VAfile HCLITXkey.pem.chain -text -url http://ocsp.digicert.com
      Expected result: 
      “Response verify OK”.

=====================================================================
KNOWN ISSUES AND WORKAROUNDS
=====================================================================
M202 warning:
These messages can be ignored. For example:
---------------------------------------------------------------------
M202 WARNING:
    Map: sepvalid   Output: FileType [4]:outputcard
    Parm 1 of EITHER doesn't match the required type.
---------------------------------------------------------------------
Missing occurrence index for SEPA validation reporting on repeating groups:
Some validation reports will not have the index of the repeating groups.
Workaround:
Perform search against the original message using the validation report referenced path.
Import of Design Server example projects take a long time:
Workaround:
Update the following settings from config.yaml (formerly tx-server-env.bat / tx-server.env)
from
server.resources.longTaskProcessJvmOptions "-Xmx2g”
to
server.resources.longTaskProcessJvmOptions "-Xmx6g”
Design Server project issues
Workaround:
Request for Design Server latest version and patch from customer support
 

=====================================================================
RESOLVED AUTHORIZED PROGRAM ANALYSIS REPORTS (APARS)
=====================================================================
N/A

=====================================================================
CONTACTING CUSTOMER SUPPORT
=====================================================================
Contact Customer Support at 1-800-IBM-SERV, or go to the support portal.

=====================================================================
NOTICES AND TRADEMARKS
=====================================================================
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
 

HCL
2600 Great America Way,
Suite 401, Santa Clara CA 95054
USA
Attention: Office of the General Counsel

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

HCL
2600 Great America Way,
Suite 401, Santa Clara CA 95054
USA
Attention: Office of the General Counsel

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM web sites are provided for convenience only and do not in any manner serve as an endorsement of those web sites. The materials at those web sites are not part of the materials for this IBM product and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Director of Licensing
IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US

HCL
2600 Great America Way,
Suite 401, Santa Clara CA 95054
USA
Attention: Office of the General Counsel

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Programming interface information
Programming interface information, if provided, is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Privacy Policy Considerations
IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect personally identifiable information.

If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent.

For more information about the use of various technologies, including cookies, for these purposes, see the IBM Privacy Policy , the IBM Online Privacy Statement section entitled "Cookies, Web Beacons and Other Technologies," and the IBM Software Products and Software-as-a-Service Privacy Statement.

Trademarks and service marks
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
  • Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
  • Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
  • Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
  • UNIX is a registered trademark of The Open Group in the United States and other countries.

This product includes software developed by the Eclipse Project ( http://www.eclipse.org/ ).

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSE82XJ","label":"IBM Sterling Transformation Extender Pack for Financial Payments"},"ARM Category":[{"code":"a8m0z000000bmLpAAI","label":"Pack for Financial Payments"}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"11.0.2"}]

Document Information

Modified date:
19 September 2025

UID

ibm17244029

Page Feedback