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.

Responder Name should continue to be a valid field in ZellePaymentRequest as it is today in CXCPaymentRequest

Currently responderName is a field used in CXCPaymentRequest which also populates in CXCParticipantView in the Outgoing Payment Request section. This allows us to use the name the customer saves in their contact list (FTM Recipients). We provide an activity log to the customer which is pulled from CXCParticipantView and the responderName is whatever the customer names their contact. For a better user experience we request this information also be available in ZellePaymentRequest, which we will be moving to in the future.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Nov 8 2019
  • Shipped
Component Usability
Priority Medium - Important
  • Attach files
  • Admin
    Craig Rector commented
    24 Feb 08:49pm

    This was delivered in FTM for ACH v3.0.6.11 on Friday February 21st, 2020

  • Admin
    Craig Rector commented
    16 Jan 03:16am

    We are targeting to implement this in v3.0.6.11 in the February 2020 timeframe and include this also in the v3.2.4 level in the May 2020 timeframe.