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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


ADD A NEW IDEA

FILTER BY CATEGORY

IBM Safer Payments

Showing 19

Allow functionality to navigate left/right in a data table using keyboard keys, specifically in the case selection page.

Currently in 5.7 you can navigate up/down/left/right in any data table using the keyboard keys however in 6.3 you can only up/down on the overall page with the keyboard, you cannot up/down/left/right in a table result. The main place we would like...
3 months ago in IBM Safer Payments / Operational 0 Future consideration

Provide Condition Capabilities to Latency KPIs

It would be beneficial if the latency KPIs had the same condition capabilities as the transaction message rate KPIs. This would allow us to separate different message types in the dashboard and keep track of the latency separately instead of in a ...
about 1 year ago in IBM Safer Payments 0 Future consideration

Job and query execution by predefined time intervals

Create the possibility of executing queries, jobs and other data selection operations by a set of predefined time intervals like "last hour", "last day", "last week", "last month", etc.. It should be possible to apply these predefined time period ...
over 1 year ago in IBM Safer Payments 0 Future consideration

Have an option to configure the session timeout and user logout redirect urls

issue with how SP interacts with our app portal's SSO
about 1 year ago in IBM Safer Payments 0 Future consideration

Add SASL Support for Kafka Interface

Currently Kafka Supports only SSL, We have a requirement for Kafka interface to support SASL for comply with banking security requirement.
4 months ago in IBM Safer Payments / Technical 0 Future consideration

Provide doublet detection at the message type level, not just at the mandator level

The feature would allow doublets to have different configurations based on the type of message being processed. It would remove complexities of having to develop doublet detections across a wide variety of message types. It would reduce chance of ...
over 1 year ago in IBM Safer Payments 0 Future consideration

Special Fraud Index

We intend to have a special Fraud Index that is updated when a transaction is set as fraudulent. Currently, when we set transactions as fraudulent (using a merge) SaferPayments does not re-compute/insert indexes. We intend to have a new index typ...
almost 2 years ago in IBM Safer Payments 0 Future consideration

Use hexadecimal attributes as reference attribute in counters

Currently, Safer Payments only allows the usage of Numeric and Text attributes as reference attributes in counters. This limits the usage of counters with computation "Most occurrence value" to those two types.
about 1 year ago in IBM Safer Payments 0 Future consideration

Replace JSON script for Case Actions with a more user friendly UI

There are several business reasons that require a manual out going message. The current UI for manual outgoing messages is via case actions; the case actions UI requires the analyst to interact with JSON script
about 1 year ago in IBM Safer Payments 0 Future consideration

Upload Files

Upload Files - In the SP front end, when we tag one transaction as fraud, the name of the user who made it, doesn’t appears in the field “FRAUD_CLASSIFICATION_USER_NAME”. It must appears.Create meta attributes (FRAUD_CLASSIFICATION_DATETIME, FRAUD...
over 2 years ago in IBM Safer Payments / Operational 0 Future consideration