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 77

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...
about 1 year ago in FTM for Digital Payments / Administration & Configuration 0 Future consideration

FTM should have logic to understand and fix the different states a payment should be and also have logic to re-try if a payment is in an out-of sync status between FTM and EWS.

Examples: HNB customer receives money, FTM attempted to make the PaymentStatusUpdate call to EWS as Delivered and experienced a connection issue and did not get a success/failure back from EWS. FTM treated this as a success and marked the payme...

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

Recurring payments for ACH

Schedule management API’s from FTM need to support configuring recurring payments for ACH.There's currently only one payment type which allows recurrent which is Zelle. it won't work for ACH
about 1 year ago in FTM for Digital Payments / Transaction Processing - Distribution 2 Future consideration

Adding dual approval process to the schedule management

discussed on the call with Craig on 9/18/2020 the following change is needed in FTM for Dual Approval:Life-cycle management of scheduled payments Record list of approvers, approver decision, approval deadlineOn reaching approval deadline, the futu...

cancel batch

cancel batch functionality that would clear any transactions that were not processed so those could be resubmitted in a new batch.
about 1 year ago in FTM for Digital Payments / Transaction Processing - Distribution 3 Planned for future release

Broadcast message was failing for event ID

provide ability to change TCH participants status from UI in a situation when Broadcast messages failed to update DP status of a participant in any event failure

Update schedule – there is a set of fields which we need to store while setting up schedules

update schedule – there is a set of fields which we need to store while setting up schedules and current FTM API does not allow to send those fields during schedule update. Missing Field List:Payer accountMemoPurpose