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,
Post an idea
Upvote ideas that matter most to you
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 offering manager 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
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...
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...
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
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...
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
Do not place IBM confidential, company confidential, or personal information into any field.