IBM Safer Payments

Showing 93

In Case Management, allow visibility of fired rules for only the mandator level they fired in.

Currently, in a Case all rules that fired will be shown in that case, even if another case class was raised by the same or other rules firing at the same time. Therefore, if there are sensitive rules from 1 department firing, these would be visibl...

6 months ago in IBM Safer Payments / Business 1 Submitted

9 VOTE

Masked Data Customization

Allow more customization around which users can view the values of each encrypted attribute. This is currently handled at the user account level and a user may either view all encrypted/masked values or none of them. We need additional flexibility...

over 1 year ago in IBM Safer Payments / Operational 0 Future consideration

6 VOTE

Automatically remove expired risk lisk entries

Currently we need to manually select and delete expired risk list entries. We would like to see an option to enable this for a lisk and have the daily maintenance job wipe the expired entries from the list.

12 months ago in IBM Safer Payments / Business 0 Future consideration

1 VOTE

Add Case Close Code attribute to Case history section in case investigation

The "Case history" table in cases only shows the "fraud status" assigned to a case not the case close code itself. In case you have multiple case close codes with the same fraud status configured to them you can NOT discern - in the otherwise help...

2 months ago in IBM Safer Payments / Business 0 Submitted

1 VOTE

Permission on (specific) query based on user role, user group or user

It should be possible to restrict a query or a group of queries within a mandator to specific user roles, user groups (for cases) or even specific users (e.g. private queries). Currently every user that has the "view query" permission sees and can...

2 months ago in IBM Safer Payments / Business 0 Future consideration

10 VOTE

Have Templates for column selection+order in queries

Typically you have dozens or hundres of queries, many using an identical configuraton of columns. You need to specifiy those columns in every query. When changing the order or adding/removing columnsit is a pain to update them. When creating you q...

almost 2 years ago in IBM Safer Payments 1 Future consideration

6 VOTE

Allow CPP Change on Bulk Transition

We use CPP tags to show which investigator is assigned to a case, even if that investigator was not the last one to transition the case. When an investigator conducts a bulk transition, they are not able to change the CPP tag through the bulk tran...

over 1 year ago in IBM Safer Payments / Operational 0 Future consideration

6 VOTE

GUI workflow editor

Problem Description: Editing case workflows as plain text is not obvious and it may lead to human factor errors. The proper way of creating complex workflows now is drawing them on paper and carefully transferring element by element to Safer Payme...

over 1 year ago in IBM Safer Payments / Operational 0 Future consideration

4 VOTE

Export Function for Model Revision Audit Log

Adding an export function to the Audit Log screens under Model Revision would allow users to easily/cleanly document their model changes outside of the application and provide a means of easily supplying such information to auditors or other non-u...

about 1 year ago in IBM Safer Payments / Operational 0 Not under consideration

5 VOTE

Random Sampling of Alerts

Allow for random sampling of alerts from the case selection page. We conduct monthly QA processes that require us to pull a random selection of cases worked by each investigator. Currently we need to download all alerts worked by an investigator a...

over 1 year ago in IBM Safer Payments / Operational 0 Future consideration

Please enter your email address

FILTER BY CATEGORY