Built for 24/7 operation and 99.999% availability
Safer Payments is usually implemented as a cluster of three instances. Each instance is independently able to run the full production volume and together they automatically replicate all data. This "triple redundancy" ensures that operations continue even if an instance, a server, or an entire data center fails. It also allows for software and hardware maintenance without any disruption of production.
All aspects of Safer Payments are fully configurable from its web user interface. This includes payment instruments, data streams, the model data dictionary, and the actual detection models. This enables ultra-short implementation times (3 to 6 months typical), since Safer Payments is configured according to the existing environment and not the other way around.
Horizontal and vertical scalability
Using a clustered architecture and parallel programming techniques, multi-core commodity servers are utilized most efficiently. Even low end Intel Xeon-cores deliver 1000+ transactions per second. Our customers operate up to 12,000 transactions per second sustained peak volume with Safer Payments (financial and non-financial transactions).
Fully accessible API and microservices
Used as microservice, all of Safer Payments functions are accessible from the outside via https enabling any other system or programming environment to access and customize any of the Safer Payments functions. This allows your data scientists to bring their preferred machine learning modeling and runtime frameworks, including open source, to Safer Payments.
Requires on any bare Linux operating system. Red Hat Enterprise Linux recommended. Installs on OS or as Docker container. Real-time database, application server, and replication layer all fully embedded in product and must not be provided.
Runs on commodity servers (x86). Physical or virtual. Recommend three servers for triple redundancy. Sizing depends on data volumes and retention periods.
To deliver performance of this magnitude, Safer Payments utilizes massive parallel computing—critical computations scale linearly with the number of CPU cores available. IBM Safer Payments is written in C/C++, the programming language of choice for any application requiring massive performance.