Release Notes
Abstract
Release notes for IBM Financial Transaction Manager for Immediate Payments 3.2.11 Multiplatforms
Content
Before installation
System requirements
Check the IBM Financial Transaction Manager system requirements to ensure that your installation platform is supported for the product edition that you plan to install. For more information about the system requirements for all of the different versions of the product, see the IBM Financial Transaction Manager system requirements website.
Downloading the product
For information about how to download IBM Financial Transaction Manager for Immediate Payments for Multiplatforms see the download document for IBM Financial Transaction Manager for Immediate Payments.
Product documentation
- Release information (this document)
- Fix list (key defects fixes in this release)
- Financial Transaction Manager online product documentation
- Resources (support links for this and other releases of this offering)
- Entitled documentation fix pack (download from Fix Central)
Support
Defects:
These release notes might contain references to defect numbers. These numbers refer to internal IBM problem numbers that you might find helpful when you are discussing problems with your IBM Support representative.
Technotes:
For more information about available fixes, see the IBM Support web page. To find the information, click the Fix Central link in the Download section of the page. Then, enter the name of the product. This web page provides links to the latest available maintenance for the in-service IBM Financial Transaction Manager family of products.
| Back to contents | 3.2.11 Fix pack 2 |
New features and updates
- Support for the TCH 5.0 Specification - the FTM for Immediate Payments implementation is now certified.
Known issues
| Back to contents | 3.2.11 Fix pack 1 |
New features and updates
- Support for the TCH 3.0 Specification - the FTM for Immediate Payments implementation is now certified.
- RFP Warranty - this includes support for Request for Payment (RFP) warranty claims as per the specification.
Known issues
| Back to contents | 3.2.11 |
New features and updates
- Support for the TCH 3.0 Specification
Note: The TCH RTP certification criteria and tools are not yet available from TCH. Therefore, the FTM for Immediate Payments implementation is not yet certified.
Known issues
This section outlines the known issues and their workarounds (if any).
Issue 1
- Summary: TCH RTP maintenance
- Details: To support true 24x7 operation, individual connectors can be quiesced when maintenance needs to be done on a participant site. When a connector is set to quiesce mode it stops sending requests to TCH RTP, and stops responding to echo requests received from RTP. However, the connector still processes business requests from RTP and makes sure that responses to those requests are routed to RTP by using an alternative connector. Quiesce mode works because RTP stops sending messages to a particular connector only after it does not receive any messages from that connector for more than 90 seconds. Therefore, the connector can safely be shut down 90 seconds after it enters the quiescing state without experiencing timeouts for any of the in-flight transactions. Ensure that all outgoing requests are then routed through the active connectors.
Issue 2
- Users affected: Customers that use the SCT Inst scheme of FTM for Immediate Payments
- Summary: pacs.028 related to camt.056 is not supported.
- Resolution: N/A
Issue 3 - Defect 141858
- Problem: SL12 is a valid reason code in pain.014. However, the TCH provided pain.014 XSD (schema) does not include SL12 in the list of permitted reason codes. According to the TCH 3.0 specification, a user who does not want to receive RFP messages (pain.013) needs to reject them with an RFP response (pain.014) reason code SL12.
- Resolution: FTM for Immediate Payments cannot support this scenario until TCH updates the TCH 3.0 schema.
Issue 4 - Defect 140267
- Problem: A camt.035 Payment Ack coming from TCH RTP fails to correlate to the original outgoing payment when the payment was originated as an API call.
Issue 5 - Defect 142902
- Problem: After an incoming RequestForPayment (pain.013) that contains a UETR tag is received, the matching CancelRFP (camt.056) with OrgnlUETR gets stuck in the transaction mapped status. Avoid the use of the optional OrgnlUETR tag until this issue is resolved in a new or maintenance version of FTM for Immediate Payments.
Was this topic helpful?
Document Information
Modified date:
25 October 2025
UID
ibm16839169