What's new

IBM® Safer Payments 6.6.0.00 includes new features and enhancements.

Release highlights

  • Introduced a new feature that is called extended masterdata query. After it is configured, the new menu item, Investigations > Queries > Extended masterdata query, displays. Use it to look up masterdata values and their associated index values based on search criteria. The search criteria can comprise both conditions on masterdata and conditions on index values. For example, you can search for all accounts whose addresses contain Culver, and whose names contain ohn, if they are defined as masterdata elements in your model. You can search for exact matches and use wildcards and combinations that are allowed within the regular condition form.
  • Now, or conditions are supported everywhere that conditions are defined.
  • Significantly improved rule generation performance. On test environments, performance improved by up to 25%. Actual improvement depends on your configuration and hardware.
  • Significantly improved simulation performance. On test environments, performance improved by up to 35%. Actual improvement depends on your configuration and hardware.

Enhancements

  • Added support for dynamic function argument lists (*args) to Python code execution. Python functions can now be declared and called with a variable number of arguments. Python dynamic arguments are supported everywhere that Python function expressions are defined in IBM Safer Payments.
  • Added the consider existing intercepts but ignore already defined rules of this model revision option to the Rule generation scenario dropdown. The dropdown is located on Modeling > Model factory, then in Select type choose Rule > Select data. For more information about the new data selection scenario, see the online help for Rule Generation Data Selection.
  • Removed support for TLS 1.0 and 1.1. Now, IBM Safer Payments supports only TLS 1.2 and higher.
  • On Administration > System > Configuration > Investigation & queries > Fraud Marking, added the Enforce default timestamp checkbox. When selected, users cannot choose a different fraud timestamp when they are marking queries as fraudulent. Also, the Fraud Marking section was moved and renamed. Previously, it was under System and named Direct transaction marking in queries.
  • It is now possible to store the user who marked a transaction as fraudulent in an attribute. On Administration > System > Configuration > Investigation & queries, added a User Output field to the Fraud Marking section. It shows who marked a transaction as fraudulent.
  • Introduced mandator quotas, which allow limits to be set on the number of revision elements that are used by a mandator. Added Quotas to Administration > Mandators. If a mandator revision exceeds its quotas, golive is prevented.
  • On Model > Modeling > Analyses > Rule analysis, added two columns: Fraud amount hit only by this rule and Fraud transactions hit only by this rule.
  • On Monitoring > Defined risk lists > Defined risk lists > [defined risk list], added the Entry ID output attribute field. When an entry ID output attribute is selected for a defined risk list and a transaction matches an entry in the list, the defined risk list entry ID is saved into the selected attribute for the transaction.
  • Now, buttons on Monitoring > Defined risk lists > Defined risk lists and Monitoring > Defined risk lists > Defined risk list entries are hidden instead of disabled when a user does not have permission to use them.
  • On Model > Modeling > Analyses > Statistics, added a dropdown to select a ruleset. When a ruleset is selected, only transactions that are affected by the ruleset's rules are included in the statistics. Also, removed the Model > Modeling > Analyses > Statistics > Reminders generated tab. The reminders feature is no longer available.
  • On Model > Modeling > Analyses > Rule analysis, added ruleset summary rows and a toggle to control whether they are shown or hidden. Note that summary rows are never shown for rulesets that have only one analyzed rule.
  • On Investigation > Queries > CPP selection, added the ability to delete a CPP.
  • On Investigation > Queries > CPP selection, added the ability to filter CPPs by the date that they were created or updated.