Transaction monitoring

The most popular use case for Vouchsafe is transaction monitoring, as it’s where it really comes into its own as a real-time fraud intelligence network.

The transactions might be:

• products or services being applied for/used
• money being moved between accounts
• payments being made

1. Call the core Risk API

Before you authorise or process a transaction, call the [Risk API] with all the data you have about the transaction.

The more data you provide, the lower the likelihood of false positives or negatives

Vouchsafe will return an instant risk score that represents the likelihood of fraud.

If the score is above threshold, allow the transaction to proceed as normal.

If it is below threshold, proceed to step 2.

2. Step-up verification

Vouchsafe helps you get synthetic identity and impersonation risk under control by performing step-up verification.

First, publish an appropriate [verification flow] for your use case and regulatory context using one of our templates.

Don’t forget to define [onward URLs] for the customer to return to once done.

Then, based on the result of step 1, call the [CreteVerification endpoint] to get a unique verification URL to send the customer to.

Challenged customers will prove who they are, usually with digital evidence and official data.

✅

Pass as much information about the customer as you can, to make sure that you are verifying the right person.

Vouchsafe makes sure the name, date of birth and address on evidence match what you expect.

3. Handle the result

Once the customer completes verification, they will be returned to the URL you specify.

At this point, you should either call out to the [GetVerification endpoint], or listen for a webhook event, and update your database with the outcome of the verification.

If the result is good, you can then process the transaction.

4. Listen for alerts

Vouchsafe works in real-time, and proactively monitors customer details for you using the Alerts.

If another business makes a fraud report, or an anomaly is spotted that might indicate a stolen or made-up identity, you find out instantly.

By default you’ll get an email, but you can automate it by listening for the relevant webhook events.

If you get an alert webhook, you will normally want to either:

• trigger step-up verification
• block further transactions until your team can investigate