IBM Safer Payments

Showing 149 of 15039

Provide out-of-the-box Prometheus Exporters which invoke Safer Payments APIs and convert to a Prometheus format required by external Monitoring Solutions

Each client needs to integrate Safer Payments with their external Monitoring Solution. In the case of the Federal Reserve the monitoring solution is Grafana. The following are standard Safer Payments APIs that on many projects need to be integrate...

4 months ago in IBM Safer Payments / Operational 0 Submitted

5 VOTE

Improve logging/tracability options of (HTTP) Case actions

Currently when executing case actions the investigator gets no information (UI) that an error might have occured delivering the message. Also the logging of errors within a case audit trail seems only to work for HTTP error codes which are stored ...

11 months ago in IBM Safer Payments / Business 0 Submitted

5 VOTE

Provide an option to wipe all entries from a defined risk list

Currently there is no option to wipe all entries of a risk list. A risk list can also not be deleted as long as it contains entries. You have to manually select/mark all entries of a list and delete them. Setting a high amount of rows per page doe...

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

2 VOTE

Allow inclusion of sub-mandator model(s) in upper-mandator simulations.

For those using a multi-mandator structure, it is currently possible to include model components from an upper-mandator when running a simulation on the sub-mandator due to the inheritance feature. However, it is not possible to do the opposite: i...

5 months ago in IBM Safer Payments / Operational 0 Submitted

3 VOTE

Unmark button for - with fraud or genuine marked - transactions

We are using IBM Safer Payments 6.5.0.02 It should be possible to undo markings that have been set incorrectly by mistake. Today you can only replace one marker with another (Genuine <-> Fraud). The context menu should offer an unmark function.

8 months ago in IBM Safer Payments / Operational 0 Submitted

13 VOTE

Restrict Access to columns/attributes based on role

Allow admins to determine which attributes a user has access to view in queries and within a case. This could be handled at the role level. Not all users need access to the same type of data; limiting which users can see each attribute helps infor...

almost 3 years ago in IBM Safer Payments / Operational 0 Planned for future release

4 VOTE

Ability to restrict usage of an attribute defined at upper level mandator in lower level mandators in the mandator hierarchy

Currently client users can use all the attributes defined on the root mandator on rules and investigation queries . Certain attributes are defined at the root level are purely internal and we want to restrict the visibility and usage of this attri...

11 months ago in IBM Safer Payments / Technical 0 Submitted

11 VOTE

User Management as a Roles Permission

Move User Management Privileges from Global Privileges to a Role permission. Currently, user management is permissioned via a global privilege on a user's account. When the "user accounts" privilege is set to "change," the user can view and edit a...

over 2 years ago in IBM Safer Payments / Operational 0 Not under consideration

1 VOTE

Case Prioritization

Need the ability to automatically prioritize cases acrossdifferent queues based on the nature of the cases and business rules (e.g. High value transactions).

3 months ago in IBM Safer Payments / Business 0 Submitted

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

almost 3 years ago in IBM Safer Payments / Operational 0 Future consideration

Please enter your email address

FILTER BY CATEGORY