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 76

In FTM DP 3.2.4 USA Version, we are trying to process incoming Canada ACH CPA005 PAD files via FTM. CPA005 is converted to ISF and then feed to Digital Payments. But in the digital payments screen, some of the fields are not populated\mapped as shown in screenshot. We are unsure about the fields to be mapped in ISF, in order to get below highlighted fields populated in DP screen.

FTM-DP UI Field NameInbound Transmission Hierarchy -> Parties -> Originator -> IdentifierInbound Transmission Hierarchy -> Parties -> Originator -> NameInbound Transmission Hierarchy -> Total Credit DifferenceAlso IBM team sha...
9 months ago in FTM for Digital Payments / Mapping & Translation 0 Planned for future release

Request to add PAYMENT_ID field/value to the JMS_TEXT in our logs. Also, to be clear, one of our main goals it to be able to count and/or omit H50 payment ids so we are looking to see the full payment id/orig seq number added to the JMS_TEXT.​

HUNTINGTON BANK - Business Justification - Idea SubmissionTS004601479 - HOPS ZELLE - Request to add PAYMENT_ID field/value to the JMS_TEXT in our logsWe are looking to use our log entries to calculate and track payment SLAs while excluding certain...

Support LDAP configuration for ADU deployment on single WAS server environments.

Please refer to IBM case TS003932375 for more details
12 months ago in FTM for Digital Payments / Installation & Upgrades 1 Not under consideration

Cloud Native Architecture for FTM

Need timeline to implement using micro service architecture vs current pattern of monolith style architecture.Circuit Breaker design pattern – FTM as an application to provide out of box Retries, Timeout, Store & Forward abilities when integra...
12 months ago in FTM for Digital Payments / Other 0 Future consideration

Other APIs to support business functions

Other APIs to support business functionsLimitHolidayFeeRouting CodeBusiness cut-offs.
12 months ago in FTM for Digital Payments / Transaction Processing - Distribution 0 Future consideration

Payment / Schedules

We need single Payment API with support of immediate, Future and recurring payments based on ISO data model with custom attribute support.Single API to create / retrieve information across all payment types.Single API for payments with all frequen...
12 months ago in FTM for Digital Payments / Transaction Processing - Distribution 0 Future consideration

Payee Management (for all payment types)

We need single API to create payee information across all payment types. API should allow user to enter Customer ID(mapping to Customer 360) , Recipient information and Recipient Account in a single API call.We need single API to retrieve/update/d...
12 months ago in FTM for Digital Payments / Transaction Processing - Distribution 0 Future consideration

The Funds Reversed flag should be working on camt.056 messages aswell. Currently it is working on pacs.008 messages only.

Our Bank sends a PACS.008 to other FIOur Customer requests for "Return of Funds" for any reason (incorrect account number was used)Our Bank initiates a CAMT.056 to get the funds backThe other FI accepts the CAMT.056 but is unable to send through P...
12 months ago in FTM for Digital Payments / Administration & Configuration 0 Future consideration

please delete it, it's a dup

please delete it, it's a dup
about 1 year ago in FTM for Digital Payments / Transaction Processing - Distribution 1 Functionality already exists

Recipient Management

Recipient management should provide a UI for maintenance of recipient data. There currently is no UI that can allow an Ops user to maintain this informationUI come up read only in 3.2.5, we need UI for editing