IBM Safer Payments

Showing 135 of 15533

Increased functionality of the "Close to" and "Not Close to" operators

When using the "close to" operators in a condition, would like the ability to specify whether or not the tolerance is only positive or only negative, in addition to the current setting which always works in both a positive and negative direction.

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

3 VOTE

Safer Payments & http protocol

Safer Payments server stops responding when sending requests with HTTP header "Transfer-encoding: chunked" Use case Sample: curl -k \ -X POST https://safer-payments.uat.feci.geci:37911/ \ -H "X-SP-Protocol-Version: 1" \ -H "Accept: application/jso...

almost 3 years ago in IBM Safer Payments / Technical 0 Not under consideration

3 VOTE

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

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

3 VOTE

Automatic transfer of parametrizations and new versions

Currently, all parametrizations, made in test environment, have to be transferred manually to production (the parametrization has to be repeated). The same is for version transfers. We would like to have a process for automatic transfer. The requi...

over 3 years ago in IBM Safer Payments / Technical 0 Future consideration

3 VOTE

Create error message or revert back to SS home page when a user is not configured in Guardian.

When a user has SS access, but is not configured in SP, the SP log in screen displays. The user will attempt to log in here and will not be able to continue- this can be very confusing and cause phone calls to our support team. We need either an e...

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

3 VOTE

Force the system to register specific characters as normal text

Characters which provide specific function within Safer Payments such as (),{},~,*,? cannot be interpreted as plain text for rule writing. Merchant names, for example, may enter the system with these characters.

over 3 years ago in IBM Safer Payments 0 Future consideration

3 VOTE

Allow for the reference of Rule Name, Rule UID, and Rule Comment within a conclusion

Would like the ability to reference the Rule Name, Rule UID, or Rule Comment within a conclusion. For rule auditing, we may assign unique values to an overwritable input on a rule by rule basis. Safer Payments already inherently assigns a Unique V...

over 3 years ago in IBM Safer Payments 0 Future consideration

3 VOTE

Automatic reconciliation of references when an attribute is deleted

When an attribute needs to be deleted, the UI will throw an error advising of any references to said attribute. There could be multiple queries, rules, or other model components using a particular attribute, resulting in dozens or even hundreds of...

over 3 years ago in IBM Safer Payments 0 Future consideration

3 VOTE

Separate Mandater/user privileges for Intercept vs Monitoring models/rules

Providing access to Model writing provides access to both intercept or case creation models. Would like these unlinked.

over 3 years ago in IBM Safer Payments 0 Functionality already exists

3 VOTE

Separate mandator/user privileges for Rule Generation and Simulation

Simulation and Generation are tied together, if you can access one you get the other. Would like these unlinked.

over 3 years ago in IBM Safer Payments 0 Future consideration

Please enter your email address

FILTER BY CATEGORY