Risk-based step-up
Trigger a quick face check only on high-risk transactions.
Industry · Payments
Payments face verification.
Fraud falls, conversion holds. Apply a face check only when risk signals say so — new device, unusual amount, unfamiliar payee.
Use cases
Where SIMSIM helps.
Account-takeover defence
Re-verify on new devices or after credential resets.
Chargeback evidence
Keep a verifiable record that the account holder authorised the action.
Merchant onboarding
Verify merchants and beneficial owners at sign-up.
Regulatory context
Built to support your compliance programme.
Under PSD2 strong customer authentication in the EU and UK, biometrics can serve as the "inherence" factor alongside possession or knowledge.
SIMSIM stores irreversible face templates, never your customers' photos.
Every plan includes all five endpoints — no add-on fees for liveness.
A Data Processing Agreement is available on every paid plan.
Recommended APIs
The building blocks.
FAQ
Payments questions.
How do payments teams usually start?
Most start on the free plan with verification and liveness, test on real traffic, then move to Pro or Business for production volume.
Do you store our customers' photos?
No — only irreversible templates, which you can delete by API at any time.
Which regions do you support?
The US, Canada, Australia, the UK, Western Europe and India. See regional requirements.
Add face verification to payments?
Start free with 250 requests a month, or talk to us about volume, DPAs and SLAs.