Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


ADD A NEW IDEA

FTM for Digital Payments

Showing 65

Monitor and suggest Gateway Threads

FTM for Digital Payments should offer ways to monitor Gateway Threads and indicate optimal thread values.
19 days ago in FTM for Digital Payments / Alerting & Notification 0 Submitted

Automatically scale gateway threads

FTM for Digital Payments should be able to automatically scale Gateway threads to achieve optimal performance based on load.
19 days ago in FTM for Digital Payments / Performance 0 Submitted

During Credit Transfer Segment threshold check when using CT API, a negative acknowledgement (pacs002) should be generated and sent to the sender.

During Credit Transfer Segment threshold check when using MQ channel, a negative acknowledgement (pacs002) is generated and sent tothe sender. When we use CT API in the same flow, a negative acknowledgement (pacs002) is not generated.

FTM needs the ability to prioritize Distribution messages in order of the Processing Window the batches are assigned to

If a large number of files come into the system just before and just after the cutoff time for a processing window, depending on the makeup of the files, some files after the cutoff that will be assigned to the next window can be sent to distribut...
about 2 months ago in FTM for Digital Payments / Transaction Processing - Distribution 0 Under review

Trace logging for Zelle Ready Contacts API (ZPSS) interaction

Why? Because we need logs in order to triage issues for Zelle Ready Contacts/EWS interactions.
about 1 year ago in FTM for Digital Payments / Other 1 Not under consideration

Sender’s rolling 30-day limit information in the payment flow

Can Sender’s rolling 30-day limit information be exposed in the cxcpayment object , so that it can be used in the fraud detection user exit and thereby supplied to fraud analytics team . Currently , there is no straightforward way to retrieve this...
10 months ago in FTM for Digital Payments / APIs & SDKs 1 Not under consideration

TCH admn.008 (response to partrep msg) need to stored in database and should be able see from OAC

TCH admn.008 (response to partrep msg) need to stored in database and should be able see from OAC The issue is When the connectors were started, they all sent an participant report request to TCH. The two TCH sites, however, do not report the same...
10 months ago in FTM for Digital Payments / Integration 0 Not under consideration

Recipient name match score needs to be exposed.

With FTM 3.2.9.1 , from logs , I see that, EWS provides Recipient name match score in ValidateRecipientResponse . Example : <ns4:first-name-match-score>49</ns4:first-name-match-score><ns4:last-name-match-score>15</ns4:last-nam...
almost 2 years ago in FTM for Digital Payments / APIs & SDKs 0 Not under consideration

Block Traffic capability in FTM

Hello , At Truist , we use FTM DP cxc webservices for zelle transactions. All these webservices are exposed in the mobile app or web interface supported by our UI team. Whenever we are experiencing service degradation, we are required to ask UI te...
12 months ago in FTM for Digital Payments / Usability 0 Planned for future release

Gracefully block or refuse out-going traffic when operational conditions are not optimal or degraded.

During times when messages are held at EWS for several hours and suddenly released FTM is unable to keep up with incoming and outgoing traffic. This situation causes our DB to be pegged at 100% utilization for several hours. Thousands of transacti...
12 months ago in FTM for Digital Payments / Financial Management (Accounting, Settlement, etc.) 0 Planned for future release