Skip to Main Content
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:

Status Delivered
Components Performance
Created by Guest
Created on Jan 15, 2020

Zelle - create (or fix) a timeout value that takes the entire payment flow into consideration

We currently have a problem where the front end has a 20 second time and Zelle has a 15 second timeout but because of the way the product is designed the15 second time applies to multiple components (applying that 15 sec timeout to each component).  In our situation the front end times out but Zelle FTM continues to process.    I believe there should be a timeout value for the entire process:


See notes from L3 in the case we created: TS002779121


Version:1.0 StartHTML:000000273 EndHTML:000070665 StartFragment:000068366 EndFragment:000070537 StartSelection:000068366 EndSelection:000070531 SourceURL: - FTM - clarification on the Zelle timeout value - Cases - IBM Support

spscott (IBM)
28 Oct 2019    ‎02‎:‎46‎ ‎PM

Response from L3:


No, we do not have a timeout for the entire process.

The Timeout value is used twice - Once when we send the payment to Gateway for processing. (We will wait the default 15 seconds for Gateway to process the file).

The timeout value is used again after the payment is successfully ingested by Gateway, to wait for the ITS workflow through Risk processing.

So the full amount of time we can wait (only for the J2SE application processing) is 2 times the configured value.


The timeout does not include any timing of the user exit processing.

If this is something that is desired, it would have to be implemented inside the User Exit and time out if you have not received a response in a reasonable amount of time.


I believe your implementation of the Notification User Exit uses MQ, so we likely are not spending a material amount of extra time in this User Exit.

Funds Transfer and Fraud I believe are both synchronous Web Service calls, where you could implement a timeout within your user exit code.



Additional information:


Version:1.0 StartHTML:000000273 EndHTML:000069467 StartFragment:000068727 EndFragment:000069333 StartSelection:000068727 EndSelection:000069333 SourceURL: - FTM - clarification on the Zelle timeout value - Cases - IBM Support

No, the Zelle Payment Processing Timeout does not count the time for user exits.  

When we send the "file" to Gateway, we wait that amount of time for the payment to process through Gateway.  Then, we use that timeout value again for it to make it through the ITS workflow (through Risk processing).

  • Admin
    Craig Rector
    Oct 6, 2020

    This has been addressed in v3.2.3 and above.