Real-Time Fraud Detection and Resolution for Financial Switch

  • Copy link to clipboard
  • Email link
  • Print
Diagram of a credit card application posting its transactions to an active NonStop database, with Shadowbase uni-directional replication sending the transaction changes from the active database to the passive database. If the active NonStop fails for some reason, users are connected to the passive database by the credit card company's IT team.

Figure 1 – Shadowbase Disaster Recovery (DR) Architecture

Situation

One of the largest U.S. processors of credit card transactions provides transaction authorization and settlement services for thousands of attached devices using a home-grown application on a pair of HPE NonStop systems.

The processor recently upgraded its servers and implemented an HPE Shadowbase Disaster Recovery architecture (Figure 1).

Problem

  1. The processor wanted to add additional servers and distribute them around the U.S. for disaster tolerance while efficiently utilizing these servers’ capacity.
  2. Additionally, fraudulent transaction activity was increasing and costing the processor a great deal of money.
  3. The processor needed to integrate real-time fraud detection into its transaction authorization services to identify suspicious activity.
  4. Directly modifying the authorization application processing would involve extensive and complex changes and require a lengthy testing cycle.

Solution

Additional Notes About this Architecture

Since the databases are kept synchronized via asynchronous replication, data collisions can occur. As a request is received, it is applied and the application updates the record’s “update-timestamp” field, and then the change is asynchronously replicated to the other node so that all copies of the database are kept up-to-date.

When data collisions occur (due to the nature of asynchronous replication), they are automatically resolved by a predetermined algorithm, which looks at a request’s record contents and applies the request with the most recent update timestamp (the other change loses and is logged to a reject log for record).

Note: HPE Shadowbase software supports other data collision resolution algorithms such as choosing the highest or lowest value of a specified field, or choosing the earlier update, depending on the underlying application’s need.

Outcomes

HPE Shadowbase Products of Interest for Business Continuity (Step 1 above)

HPE Shadowbase Products of Interest to Support Real-time Fraud Detection (Step 2 above)


Contact us or your HPE Shadowbase representative, and learn how Shadowbase software will benefit you.

Further Reading

Related Case Study: Payment Authorization — A Journey to Continuous Availability

Related White Papers: