IBM RegTech Ideas Portal

 Welcome!

 

Our team welcomes any feedback and suggestions you have for improving our offerings. This forum allows us to connect your product improvement ideas with IBM product and engineering teams.

 

For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

 

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

 

The shorter URL for this site is:   http://ibm.biz/WFS-Ideas

IBMers, please visit the WFSS Internal Ideas portal https://ibm.biz/WFS-Internal-Ideas

 

note: The IBM ICM IDEAS Portal is no longer available at this location. If you have reached this page, please look for a new link in the Varicent Administrator. Direct links are found under the "?" in the upper right corner.
A period of transition is likely to impact this service, while ICM becomes Varicent. Please contact Varicent support if you have additional challenges or concerns.

Placeholders to store custom data on the FTM "Inbound Transactions" Screen for TCH-RTP Payment rail

TCH-RTP uses a 35 character value to identify each payment/transaction uniquely. Storing this 35 character across all the systems within the bank and presenting the same to our customers is not always reliable.

Most of the banks use their unique Posting transaction Id to identify the transactions and that is the one presented to the customers on their statements, mobile apps, notifications and what not. In case of questions/concerns, this Posting Transaction ID is what is presented by the customer to the FI's Customer service/Operations.

It is critical that FTM provides the options for recording and presenting this data on the "Inbound Transactions" screen.

On the same lines, all/most banks reconcile these transactions and with the reports that arrive from TCH and it is critical again to have a placeholder on the "Inbound Transactions" screen to record the ID generated from the reconciliation similar to what is presented for recording the Zelle reconciliation Ids.

Additional details are tracked and provided on the PMR: TS003854375

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jul 15 2020
  • Reviewing
  • Attach files