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,
Post an idea
Upvote ideas that matter most to you
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.
Allow the passing of non-text attribute values into overwritable text attributes
Non-text attribute values (numeric, timestamps, amounts, etc) are unable to be passed into overwritable inputs or outputs which are defined as text. Would like the ability to pass the output of any attribute into an attribute defined as text.
Allow rules to add entries to risk lists with dynamic filter criteria
When an entry is added to a risk list via a rule, filter criteria defined as part of the risk list is static. For example, if an account number is added to a risk list which has filter criteria defined as "Merchant State equal to [Destination Stat...
In attribute field choices, Shift the standard expressions to the bottom of the list
There are standard expressions ( , ValueA ~ValueB, Exp) used in rule writing that are displayed in the field dropdown. These appear first and your customer's field values are last. It should be reversed- field values first, expressions second. E...
Resuming support for duplet detection and not storing identical sequence values
In Safer Payments 6.3.0.01 it seems that duplet detection and the option for not storing identical sequence values for indexes are still not present. In the index create/edit page the "store entries with identical sequence values" checkbox is not ...
Currently, the computation methods available within SP for profiling attributes is limited. For example, for calendar profiles all that is available is: average amount, frequency, total amount . Standard Deviation is available for this category of...
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...
Support multi-sort and multi-filters within Queries
The old UI supported multi-sort within query results but that is no longer supported in the new UI. Additionally, being able to further customize filters with multiple values or a "does not contain" option would be beneficial.
Do not place IBM confidential, company confidential, or personal information into any field.