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
On the Inbound Transmission Hierarchy screen, there are multiple tabs for a transaction, one of which is the Raw Data tab. This tab is not getting populated in the 188.8.131.52. code. This should populate with the EWS request-response data.
HNB requests IBM to find a better solution for more exact triggering for Missing or Late files; FTM can't provide the detail we expect and creates too many false positives when used for this. We want to be able to specify the Incoming ACH verses t...
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 integr...
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 frequ...
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/...
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 FI Our Customer requests for "Return of Funds" for any reason (incorrect account number was used) Our Bank initiates a CAMT.056 to get the funds back The other FI accepts the CAMT.056 but is unable to send throug...
Do not place IBM confidential, company confidential, or personal information into any field.