Major features

Build for 24/7 operation and 99.999% availability

Safer Payments is operated as a cluster of 3 instances, depending on data center operations. Each instance is independently able to run the full production volume and they all automatically replicate all data. This "triple redundancy" ensures that operations continues even if an instance, a server, or an entire data center fails. It also allows software and hardware maintenance without any disruption of production.

Horizontal and vertical scalability

Using a clustered architecture and parallel programming techniques, multi-core commodity servers are utilized most efficiently. Even low end 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).

Full configurability

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

Fully API and microservice

Used as microservice, all of Safer Payments functions are accessible from the outside via https. This allows for any other system or programming environment to access and customize any of the functions of Safer Payments.

Product Flyer

Read the brochure

Customer case studies

Case study image

Protecting an entire country from payment fraud

STET, Paris
Read the case study
Case study image

Multi-channel fraud prevention at a payment switch

Indue, Brisbane
Read the case study
Case study image

Protecting e-commerce from fraud

Borgun, Reykjavik
Read the case study

How customers use it

  • Real-time payments fraud prevention

    Real-time payments fraud prevention

    Problem

    RTP are low margin, high risk. Transactions have few describing data elements. Criminals structure payments and smurf them through mule accounts to disguise the flow of money.

    Solution

    We have developed "peer profiling" that profiles each originator and beneficiary of a payment as both sender and recipient of payments in the past. This enables Safer Payments to reconstruct the true flow of monies in real-time.

  • Model factory

    Model factory

    Problem

    Not one machine learning and artificial intelligence is great in detecting all types of fraud. It has been shown in data science, and it is the experience of our customers and our specialists, that often only a combination of techniques is efficient.

    Solution

    To enable the combination of the nest data science techniques, we have created the "model factory" concept. It allows Safer Payments users to pick the combination of techniques best suited to solve their fraud problem.

  • Online and Mobile Banking

    Online and Mobile Banking

    Problem

    Most account-to-account transactions will migrate to immediate payments in the next decade. Since the digital channel is the major initiation point for these transactions, it must be hardened to maximum protection from fraudulent manipulation.

    Solution

    Safer Payments utilizes data from the actual online/mobile banking session. A build-in device identification capability, with device behavior profiling and a device reputation database as well as biometric parameter recognition hardens this channel.

  • Utilize open source data science

    Utilize open source data science

    Problem

    Our customers want to participate in the huge amount of innovation that comes from the open source data science movement. They want to be entirely free in their choice of technology and modelling tools.

    Solution

    We have created Safer Payments to be the "most open data science platform for payment fraud prevention” on the market". We can export and import models in portable PMML format, and we can ingest models or feature extractions as Python code.

  • Multi-tenancy and multi-channel configuration

    Multi-tenancy and multi-channel configuration

    Problem

    Many or our customers are processing multiple portfolios of the same payment instrument and/or different channels.

    Solution

    Safer Payments provides hierarchical multi-tenancy. This allows to efficiently manage multiple hundreds of different tenants that each can have their own data and customization. Inheritance allows to also maintain "central" models and configurations.

Technical details

Software requirements

Requires bare Linux operating system. RHEL recommended. Installs on OS or as Dockers container. Real-time database, application server, and replication layer all fully embedded in product and must bot be provided.

    Hardware requirements

    Runs on commodity servers (x86). Physical or virtual. Recommend three servers for triple redundancy. Sizing depends on data volumes and retention periods.

      Technical specifications

      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.

        See a complete list of technical specifications