IBM Support

Release Notes for IBM Financial Transaction Manager for Immediate Payments V3.2.9

Release Notes


Abstract

Release Notes for IBM Financial Transaction Manager for Immediate Payments 3.2.9

Content


Accessing the latest version of the release notes

Always use the latest version of this release notes file, which is available at:
www.ibm.com/support/pages/node/6527908


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:
If you are downloading IBM Financial Transaction Manager from Passport Advantage, see the download document for IBM Financial Transaction Manager for Immediate Payments.


Product documentation
The online product documentation is available in IBM Documentation.
Financial Transaction Manager for Multiplatforms documentation.
 


Support
 

Defects:

These release notes might contain references to defect numbers. These numbers refer to internal IBM problem numbers that you might find useful when you are discussing problems with your IBM service representative. Information about fixed issues can be obtained from Fix / Feature List for IBM Financial Transaction Manager for Immediate Payments.

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 product name. This web page provides links to the latest available maintenance for the in-service IBM Financial Transaction Manager family of products.


Feature updates


For more information about features, see the Feature List section.


Known issues
This section outlines the known issues and their workarounds (if any).

Issue 1

Users affected: Customers that use IBM Integration Bus toolkit 10.0.0 fix pack 11

Summary:

BAR build fails with java.lang.ArrayIndexOutOfBoundsException in the details.

Resolution:

The fix for this issue (APAR IT23841) is available in IBM Integration Bus 10.0.0 fix pack 12

Other workarounds include

  • Building BAR files in IBM Integration Bus 9.0 or IBM Integration Bus 10.0, up to and including V10.0.0 fix pack 10
  • Building BAR files by using mqsipackagebar on the command line.

Issue 2

Users affected: Customers that use IBM Integration Bus toolkit 10.0.0 fix pack 12

Summary:

BAR build fails with java.lang.IllegalStateException in the details.

Resolution:

Request fixes for IBM Integration Bus APAR IT24755 from IBM Support.

Other workarounds include

  • Building BAR files in IBM Integration Bus 9.0 or IBM Integration Bus 10.0, up to and including V10.0.0 fix pack 10
  • Building BAR files by using mqsipackagebar on the command line.

Issue 3

Users affected: Customers that use SCT Inst scheme of FTM Immediate Payments

Summary:

pacs.028 related to camt.056 is currently not supported.

Resolution:

n/a

Issue 4

Users affected: Customers that use the TCH scheme of FTM Immediate Payments with FTM Base 3.2.8 or earlier.

Summary:

For some Outgoing Batch scenarios, the 'MILESTONE' batch status report is missing, only 'FIRST_ACCEPT' and 'COMPLETION' are generated.

Resolution:

This issue is in the maintenance plan for FTM Base, and will be addressed in a future release.


Feature List
This section documents the supported features.

 

Zelle Payments/IDs over TCH RTP

FTM Immediate Payments has been enhanced to better support Zelle payments settled over TCH RTP.

Support for Incoming Payments and RFPs was largely available because they are still valid TCH RTP payments and FTM IP generally processes these as normal.

However, when settling outgoing RFPs and Payments over TCH RTP (outgoing to TCH) there are specific rules with respect to the primary message/payment identifiers that must adhere to the Zelle/TCH RTP specification to allow the recipient to correlate the payments to the original Zelle messages.

Scope

The scope of this applies to 3 types of outgoing messages.

  • Outgoing Payments (including potentially Returns) (pacs.008)
  • Outgoing RFP (pain.013)
  • Outgoing Payment Acknowledgement (camt.035) – response to an Incoming Zelle Payment

In all 3 scenarios LclInstrm is used to detect the Zelle usage (LclInstrm = ZELLE).

For a non Zelle payment, FTM IP computes new IDs for many of the payment IDs to ensure they are TCH RTP compliant. In the Zelle usage, FTM IP will apply different replacement rules and the channel application may need to format the IDs per the TCH RTP Zelle rules.

Outgoing Payment (pacs.008)

  • LclInstrm  set to proprietary code ZELLE
  • FIToFICstmrCdtTrf/GrpHdr/CreDtTm (passed as-is from channel)
  • FIToFICstmrCdtTrf/GrpHdr/MsgId  (1-24 passed as-is from channel, last 11 replaced)
  • FIToFICstmrCdtTrf/CdtTrfTxInf/PmtId/InstrId (passed as-is from channel)
  • FIToFICstmrCdtTrf/CdtTrfTxInf/PmtId/TxId (passed as-is from channel)

RFP (pain.013)

  • LclInstrm set to proprietary code ZELLE
  • CdtrPmtActvtnReq/PmtInf/CdtTrfTx/PmtId/InstrId (passed as-is from channel)
  • CdtrPmtActvtnReq/PmtInf/PmtInfId (passed as-is from channel)
  • CdtrPmtActvtnReq/PmtInf/CdtTrfTx/PmtId/EndToEndId   (passed as-is from channel)
  • CdtrPmtActvtnReq/GrpHdr/MsgId (1-24 passed as-is from channel, last 11 replaced)
  • CdtrPmtActvtnReq/GrpHdr/CreDtTm (passed as-is from channel)

Payment Ack (camt.035) (internally generated only)

  • PrtryFrmtInvstgtn/Assgnmt/Id
  • PrtryFrmtInvstgtn/PrtryData/Data/OrigRefs/InstrId

TCH RTP Zelle Formatting Rules

Outgoing Payment (pacs.008)

LclInstrm set to proprietary code ZELLE

Used by FTM IP to determine it is a Zelle payment.

FIToFICstmrCd tTrf/GrpHdr/CreDtTm

With respect to Zelle it must be set to match the ZELLE initiation time.

FIToFICstmrCdtTrf/GrpHdr/MsgId 

Position

Description

01

M

02-09

File creation date in format YYYYMMDD

10-20

FI Identifier (11 digit RTP Participant ID)

21

B

22-24

Zelle Recipient Organization ID

25-35

Message serial number (11 numeric characters)*

* By default, the last 11 characters will be replaced by FTM to ensure uniqueness & numeric digits.

FIToFICstmrCdtTrf/CdtTrfTxInf/PmtId/InstrId

Position

Description

01-08

Creation date in format YYYYMMDD

09-19

Participant ID (11 digits)

20

B

21-23

Zelle Product Type (3 digits, e.g. “P2P”)

24-26

Zelle Sender Org ID (3 digits)

27-35

Unique Zelle Identifier (9 digits)

FIToFICstmrCdtTrf/CdtTrfTxInf/PmtId/TxId

Position

Description

01-08

Transaction Creation date in format YYYYMMDD

09-19

Participant ID (11 digits)

20

B

21-22

Message serial identifier (2 digits)

23-35

Zelle Payment Request ID* (13 digits)

Note*. This is only valid for response to a Zelle RFP.  When there is no RFP InstrId & TxId still match.

 

Outgoing RFP (pain.013)

LclInstrm set to proprietary code ZELLE

Used by FTM IP to determine it is a Zelle RFP.

CdtrPmtActvt nReq/PmtInf/CdtTrfTx/PmtId/InstrId

Zelle Customer Event ID

CdtrPmtActvt nReq/PmtInf/PmtInfId

Position

Description

01-08

File creation date in format YYYYMMDD

09-19

FI Identifier (11 digit RTP Participant ID)

20

B

21-23

Alphabetic serial identifier (3 characters)

24-26

Zelle Requestor Org ID (3 digits)

27-35

Unique Zelle Identifier (9 digits)

CdtrPmtActvtnReq/PmtInf/CdtTrfTx/PmtId/EndToEndId

Zelle Invoice Number

CdtrPmtActvt nReq/GrpHdr/MsgId

Position

Description

01

M

02-09

File creation date in format YYYYMMDD

10-20

FI Identifier (11 digit RTP Participant ID)

21

B

22-24

Zelle Responder Organization ID

25-35

Message serial number (11 numeric characters)*

* By default, the last 11 characters will be replaced by FTM to ensure uniqueness & numeric digits.

CdtrPmtActvt nReq/GrpHdr/CreDtTm

With respect to Zelle it must be set to match the ZELLE initiation time.

 

Outgoing Payment Ack (camt.035) (Internally generated)

PrtryFrmtInvstgtn /Assgnmt/Id

In response to a Zelle payment (LclInstrm = ZELLE), FTM IP will ensure the following:

Pos. 22-24 - Discretionary bank field will be populated with “ZEL”

PrtryFrmtInvstgtn/PrtryData/Data/OrigRefs/InstrId

No change because FTM already uses the original Payment InstrId which should already be Zelle compliant (as received from TCH).

 

Configuration to Control Handling of Zelle MsgId’s

By default, FTM IP will take responsibility for generating a unique 11 digits for the digits 25-35.

In the event that the customer prefers to retain the full channel provided MsgId the following configuration entry may be created:

Category

Key

VALUE

IP_CONFIG

UPDATE_ZELLE_MSGID

N = disabled

Y = enabled

NULL = default = enabled.

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9GGC","label":"IBM Financial Transaction Manager for Immediate Payments"},"ARM Category":[{"code":"a8m0z0000001eplAAA","label":"Planning"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2.9"}]

Document Information

Modified date:
02 June 2022

UID

ibm16527908

Page Feedback