This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
Enhance MT to MX Mappers to Support Additional ISO Payment Schemes
The existing MT to MX translation correctly translates MT to CBPR+ messages. However, not all ISO schemes have the same fields as CBPR+. The existing MT to MX implementation will not create a syntactically correct Target2 message. The following pa...
Enhance MT Outbound Post Mapper to Support Changing of MT Field Values
The current MT Outbound Post Mapper already has the MT message converted to a blob and so there is no easy way to change an MT field value. The MT Post Mapper should work more like the ISO Post Mappers in the sense that the Post Mapper can add, de...
Support Mapping PACS.008 Group Header Control Sum Field
Enhance the product PACS.008 inbound and outbound mapper to support the mapping of ISO200222's generic PACS.008 /Document/FIToFICstmrCdtTrf/GrpHdr/CtrlSum field. Ideally, all generic group header fields would be supported.
FTM IP Process Steps Have User Exit Enabling "Routing Ticket" on Per Message Basis
Background The current FTM Immediate Payments products of TCH, SCT and HVP allow a bank to customize the Services called at each workflow step (e.g. PreCheck, PreSubmit, PostAccept, etc). The limitation is the customization is limited to a payment...
Enhance HVP Send to Channel Actions to Support for Routing based upon the Combination of Rank & Role
Enhance the existing HVP Send to Channel actions to allow a user exit to override and identify which FTM Service Participants the transaction needs to be sent to. The user exit should allow the customer custom code to identify zero to many FTM Ser...
The current HVP implementation treats all MT payment messages as the same subtype of PAY_ORIG. The OAC does not provide a user friendly label for these payment transactions. HVP provides different labels and searching by PACS.008/9 (Payment Instru...
User Exit(s) Allowing the Enrichment of OAC/CC Created Transactions
Background HVP user interfaces allow a bank operator to create request for recall (CAMT.056), respond to a request for recall (CAMT.029) or return a payment (PACS.004). HVP works the created transaction through the same workflow as if a "bank chan...
the idea is to include Lynx related positive and negative acknowledgement for Canadian high value payment traffic. Currently MT012 and MT019 are delivered from LVTS, where in the future, Lynx will deliver XSYS001 and XSYS002, respectively. If the ...
Do not place IBM confidential, company confidential, or personal information into any field.