IBM Data and AI Ideas Portal for Customers

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

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

IBM Employees:

The correct URL for entering your ideas is:



FTM for Digital Payments

Showing 78

API for business rules

Provide CRUD API for managing Business Rules
over 1 year ago in FTM for Digital Payments / Administration & Configuration 1 Delivered

Payee management

provide CRUD APIs for management of Payees

scheduled payment independent of payment type

provide ability to schedule future dated paymentthis feature should not be dependent on the payment type

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 P...
over 1 year ago in FTM for Digital Payments / Financial Management (Accounting, Settlement, etc.) 0 Future consideration

Ability to lookup the comments added against transactions on the FTM DP screens

FTM provides the abilility to add comments against the transaction. However these are recorded against the transaction in the FTM.AUDIT_INFO table but these comments are no where to be looked up in the FTM DP screen. It will be a very useful featu...
over 1 year ago in FTM for Digital Payments / Financial Management (Accounting, Settlement, etc.) 0 Future consideration

Easier method to enter temporary limits

The ability to add temporary limits from the Partner's Exposure Limit Monitoring Details screen is really convenient. However, the drawback is the partner has to have made a payment that day for temporary limits to be established. Recommend havin...
over 1 year ago in FTM for Digital Payments / Usability 0 Future consideration

Exposure Limit Monitor Start/End Date should allow for year to be specified

On the Partner Details screen, Risk Management/Exposure Limit Monitors- you can specify an Effective Begin Date (MM/dd) and an Effective End Date (MM/dd) but you cannot specify the year. In principle, the idea of having the ability to have monitor...
almost 2 years ago in FTM for Digital Payments / Usability 0 Future consideration

FTM for TCH - Considers weekends as holidays by default - Remove this default configs to allow clients to make the decision

Huntington has used the out of the box Product Deadlines provided by IBM for TCH Receive (TCHI – Product Code). This setup indicates that Saturday and Sunday are to be treated as business days. These days are not treated as business days by busine...

Zelle - create (or fix) a timeout value that takes the entire payment flow into consideration

We currently have a problem where the front end has a 20 second time and Zelle has a 15 second timeout but because of the way the product is designed the15 second time applies to multiple components (applying that 15 sec timeout to each component)...
about 2 years ago in FTM for Digital Payments / Performance 1 Delivered

FTM allows user searches via FTM UI to impact transaction performance

This defect was reported in case TS002616911. IBM L3 will not address this defect via the PMR process. We are looking for a permanent fix to configure a timeout for FTM user searches where FTM/DB would kill the database work after X seconds an...
about 2 years ago in FTM for Digital Payments / Performance 1 Delivered