Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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 https://ideas.ibm.com



Status Submitted
Workspace IBM Safer Payments
Components Business
Created by Guest
Created on Jul 8, 2025

Healing of Transactional Records - Data Maintenance / Data Quality

Safer Payments has the capability of healing/fixing masterdata through processing (and optionally curtailing) batch feeds. However, for transactional records there doesn't seem to be a viable approach.


This would be required to provide accurate data to the investigators for any of the following scenarios:

  • incorrect data mapping (initial or updated behavior in channels)

  • bad formatting of batch feed where columns are swapped

  • data elements requiring hard adjustments

Real life examples:

  1. A payment processor is upgraded, and the amount field was noticed to have a bug where the decimal point is not present. 3.00 would be 300. It would be possible to target the message type ID and reprocess said txns by dividing by 100 and overwriting the records.

  2. A new business requirement dictates that certain transactional attributes are to be redacted post-processing of people of high profiles. It would be possible to implement the change from that point forward based on a new flag; however, there wouldn't be a viable way to apply the change on existing data.

While SP maintains a non-traditional database, such manipulation features are not built-in or made accessible to the system administrator. As it may be so by design, there is a need for it as not to resort to clearing out the entire database DDC/MDC.


Such low-level manipulation should be possible by targetting any masterdata element or at the very least the UID of the transactional records.

Idea priority High