Skip to content
toden

Use case · Strong customer authentication for PSD3 · $0.2128 per payment approved

Strong customer authentication for PSD3

A one-time codecan be read outto a fraudster.

The EU's proposed payment rules, PSD3 and the Payment Services Regulation, raise the bar on strong customer authentication and move more of the cost of impersonation fraud onto providers. Toden adds a live face check to the payments that carry risk, and scores every payment as it happens.

The workflow

A live face check on risky payments, and a fraud score on all of them. This is a starting point: add, remove or reorder any step in the workflow builder.

Step 01

$0.02

Transaction assessment

Scores the payment against the customer's history

Step 02

$0.01

Account activity assessment

Scores the login and device around it

Step 03

$0.10

3D Active Motion

Head turn or blink prompts

Step 04

$0.0828

Biometric re-authentication

A live selfie against the verified photo on file

Step 05

Included

Decision rules

Release, review or block on your rules

Then your rules decide

A starting rule set

  • An ordinary payment to a known payeeApprove
  • A new payee and the face matchesApprove
  • A new payee from a device never seen beforeReview
  • The face does not match the customerDecline

Every rule is yours to change on a visual canvas, and each result records which rule decided it. Publishing a new version needs no release.

Try the workflow builder

What it costs

Added up from the published rate card as this page loaded. It is what one production run of the workflow above deducts from your credit.

$0.2128per payment approved

  • Transaction assessment$0.02
  • Account activity assessment$0.01
  • 3D Active Motion$0.10
  • Biometric re-authentication$0.0828

How it works

1

Score every payment

Each payment is scored against the customer's history, device and location.

2

Ask for a face when the risk is real

A new payee or an unusual amount starts a face check in your app.

3

Release on a match

The selfie is matched to the verified customer and your backend receives pass or fail.

What powers it

  1. A face cannot be read out over the phone or forwarded in a message.

Integrate

Mount the SDK with the workflow you published, or send a hosted link and write no code. The result arrives by signed webhook, and changing the workflow never needs a release.

Verify.tsxTypeScript · React
import { TodenVerification } from "@todenhq/sdk-react";
 
export function Verify({ userId }) {
  return (
    <TodenVerification
      apiKey="pk_test_..."
      workflowId="wf_AbC123dEf456"
      userId={userId}
      onSubmit={(s) => save(s.verificationId)}
    />
  );
}
verification.completedWebhook · JSON
{
  "event": "verification.completed",
  "data": {
    "verificationId": "ver_8fk2...",
    "status": "verified",
    "assuranceLevel": "gov_db",
    "idType": "bvn",
    "country": "NG",
    "dataMatch": true,
    "facialMatch": true,
    "facialConfidence": 91
  }
}

Products involved

This solution combines products you can use on their own too.

Beta

Risk Intelligence

Monitor transactions and account activity against your own rules, then investigate what they flag.

Learn more
Compliance

Transaction Monitoring

Score each transaction as it arrives against rules you control, and route what they flag to alerts and cases.

Learn more
KYC

Identity Verification

Verify a person from their ID, a live selfie and, in five African markets, the government record. One SDK, one signed result.

Learn more

Related use cases

High-value payment approval

A decision on every payment, and a face check on the few that deserve one.

Learn more

Account takeover protection

Score each login as it happens, and step up to a face check only when the risk is real.

Learn more

Fraud Detection

One engine that turns identity, behaviour, device and screening signals into a live, explainable risk decision.

Learn more

Coverage

Pick a country to see the IDs you can verify there, which documents carry a chip we read, and whether business checks are available.

All countries we cover

Frequently asked

  • A face is an inherence factor. Combined with the customer's own device, it gives you two independent factors.

Strong customer authentication for PSD3,in one workflow.

The sandbox opens when you sign up. Usage-based pricing, no sales call.

Start freeTalk to us