Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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 (

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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

Status Not under consideration
Components FTM Common Services
Created by Guest
Created on Mar 16, 2023

FTM IP Process Steps Have User Exit Enabling "Routing Ticket" on Per Message Basis


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 subtype - the workflow cannot be tailored based upon details in the payment.  Today's limitation forces extra logic to be placed in the "IP Actions" which determine if the action should be processed on a specific payment - this complicates the ESQL code and makes production monitoring and troubleshooting more skilled and labor intensive.


Instead only having static predefined Service calls on a payment type basis, have each workflow step (e.g. PreCheck, PreSubmit, PostAccept, etc) support a user exit which lets the bank inspect the payment and return the Service calls that should be used on that step for that individual payment.

The support of a user exit will allow for more dynamic workflow processing logic that is traceable and visible while also encapsulating and simplifying programming logic.

Needed By Quarter