IBM Data and AI RegTech 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:

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 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

Shorter URL for this site is: or

Status Submitted
Workspace IBM Safer Payments
Component Technical
Created by Guest
Created on Sep 2, 2021

Safer Payments purge outdated entries limit

Problem Description:

Purge outdated entries of indexes inside IBM IRIS Safer Payments does not support the concept of span control to limit the scope of removal of all index entries that are older than a defined maximum lifetime period.

Supporting Details/Description:

The IBM Safer Payments uses a fully automated system for cleaning outdated entries within the limit of maximum lifetime. The lack of limiting the scope of entries to clean does not allow for IBM Safer Payments user control closing the Start End of Day (EoD) job before high traffic time, as the procedure does not stop until it completes purging whole data. For example: The amount of records marked for purging by the system is 50 million, the Start End of Day (EoD) job does not stop until it deletes all unnecessary data, and IBM Safer Payments enters the high traffic period with job running.

Recommended solution:

Customizing the number of entries to be purged will solve the crucial issue. With proper analysis and configuration, closing the task Start End of Day (EoD) job before peak load period is guaranteed and index will not intensely increase in size without creating unwanted load on CPU.

Needed By Month