TCH 5.0 support

This version supports the TCH (The Clearing House) 5.0 specification. Before deploying TCH 5.0 in production environment, review its specification and documentation to understand whether it meets your requirements. You can configure your environment to activate support for the TCH 5.0 specification.

For example, before you deploy TCH 5.0 in a production environment, review the following considerations:
  • Verify that the TCH certification criteria and testing were available in time for you to perform sufficient testing for your Financial Transaction Manager for The Clearing House Real Time Payments implementation.
  • Review the updated TCH 5.0 XML Schema Definition (XSD) to confirm it is fully compatible with earlier versions of the TCH specifications. Because TCH can change compatibility with earlier versions at any time, review the XSD carefully or confirm compatibility with TCH.

The TCH 5.0 support in The Clearing House Real Time Payments is based on RTP Message Specifications – Version 5.0 (The Clearing House RTP document library).

TCH 5.0 supports the following functions:
Credit Transfer Information
Mapping and transmission support for Previous Instructing Agents (PrvsInstgAgt1, PrvsInstgAgt2 and PrvsInstgAgt3) for pacs.008.
Mapping and transmission support for Intermediatory Agents (IntrmyAgt1, IntrmyAgt2 and IntrmyAgt3) for pacs.008.
Mapping and transmission support for Agent Accounts (DbtrAgtAcct, CdtrAgtAcct, PrvsInstgAgt1Acct, PrvsInstgAgt2Acct, PrvsInstgAgt3Acct, IntrmyAgt1Acct, IntrmyAgt2Acct, IntrmyAgt3Acct) for pacs.008.
Mapping and transmission support for Ultimate Debtor/Creditor to include AnyBIC as choice between BIC Code, LEI, and Generic Organisation Id for pacs.008.
Mapping and transmission support for IBAN accounts under all account elements for pacs.008.
Purpose
Mapping and transmission support for Code, Proprietary fields for pacs.008 and pain.013.
Cancellation Reason Information
Mapping and transmission support for “UAPA” code for pacs.008 and pain.013.
To use TCH 5.0 in FTM, complete the following steps:
  1. Download the TCH 5.0 XML Schema Definitions (XSDs) from TCH
  2. Deploy the XSDs into the FTM The Clearing House Real Time Payments runtime.
  3. Configure your environment and confirm that the TCH 5.0 specification is active.

Activate or deactivate TCH 5.0 support

Before you enable TCH 5.0 in a production environment, review the TCH 5.0 specification and documentation to confirm that it meets your requirements.

To enable TCH 5.0, complete the following steps:
  1. Get the TCH 5.0 XML Schema Definitions (XSDs) from TCH.
  2. Deploy the XSDs into the FTM The Clearing House Real Time Payments IBM® App Connect Enterprise runtime. The new XSDs replace the existing TCH XSDs that are being used. The tested TCH 5.0 XSDs are compatible with earlier TCH XSDs.
Note: Before deploying TCH 5.0 XSDs, remove any existing TCH 3.0 XSDs. After upgrading FTM TCH RTP to use the TCH 5.0 specification, you cannot revert to the TCH 3.0 specification on this installation.
The following table shows the configuration in the RSA Model and Value table to use to activate or deactivate TCH 5.0.
Table 1. Activate and deactivate configuration
Category Key Value
TCH ACTIVATE_5.0 The timestamp when the TCH 5.0 specification is to be activated. Specify the timestamp in Coordinated Universal Time and in the following format YYYY-MM-DDTHH:MM:SSZ. For example, 2023-09-23T12:35:18Z.
By default, the initial configuration uses a future date to schedule activation for TCH 5.0. This prevents TCH 5.0 from starting immediately after installation or deployment. If you do not include the ACTIVATE_5.0 key, TCH 5.0 activates immediately. You can set the key in two ways:
  • To activate TCH 5.0 immediately, set the ACTIVATE_5.0 key to null or to a past date, or remove the key from the database.
  • To schedule activation for a later date, set the ACTIVATE_5.0 key to a future date. TCH 5.0 remains inactive until that date. You can change this value at any time if you configured FTM TCH RTP to poll and reload configuration changes.
  • Before you set ACTIVATE_5.0, check for any existing ACTIVATE_x.x keys (for example, ACTIVATE_3.0). Remove the old keys first. At any time, keep only one ACTIVATE_x.x key in the configuration.
Note: When you activate TCH 5.0, you must also deploy the correct TCH 5.0 XSDs, and FTM must accept and process all incoming messages that comply with TCH TCH 5.0 standards.
For outgoing messages, suppress TCH 5.0 fields if this version is not active. FTM does not reject or fail outgoing messages in this case. Instead, it ignores any content that is invalid for the current version.