How to procedures

Use the how to procedures to complete common procedures in IBM® Safer Payments.

Manually marking a fraud
When manually marking a record as fraud, users are prompted to select a fraud value and a fraud timestamp.
Viewing a count of scored transactions
Configure and view a count of how many transactions have been scored.
Rebuilding an index
Rebuild an index if it is corrupted.
Configuring remote operation with curl
Operational processes and maintenance tasks can be operated remotely from a central data center environment by using the IBM Safer Payments application programming interface (API) and a shell script, such as curl.
Running IBM Safer Payments as a service
Configure a script to run IBM Safer Payments as a service on Red Hat® Enterprise Linux® 8 (RHEL 8).
Estimating disk space for challenger revision
Estimate the disk space that is needed before a challenger revision goes live.
Changing the number of parallel threads for FLI
It might be needed to change the number of parallel threads for the FastLink Interface (FLI).
Canceling a golive
Whether a golive for a model revision can be canceled depends on the status of the golive.
Backing up IBM Safer Payments
A backup can be used if an upgrade fails or for disaster recovery if all instances are corrupted.
Shutting down IBM Safer Payments
A shut down might be needed if an instance is deadlocked or stuck. A shutdown must complete so that data is not lost.