Skip to content

Identity verification

Ask for proof only when the risk calls for it.

Coming soon

When an event looks risky, send that one customer through a quick document and selfie check, or an age check, and let the result flow straight back into your rules and your policy. Everyone else carries on without friction.

Status

Identity verification is not available yet. We are building it now and opening it to a small group of early users first.

Join the early access list

What it will check

Documents, a live selfie and age, in one guided flow.

Pick the checks each moment needs. A payout to new details might need a document and a selfie; an age-restricted order might need an age check alone.

Identity documents

Passports, ID cards, driving licences and residence permits, checked for tampering, expiry and the details your rules care about.

Selfie and liveness

A short selfie confirms a real person is there and matches the photo on the document. It is built to catch printed photos, screens and masks.

Age checks

Confirm a customer is over the age you set, from their document or from a selfie-only age estimate, without asking for more than you need.

How it fits

Verification that works with your decisions, not beside them.

Identity verification plugs into the same scoring API, identity profile and policy you already use.
  1. 01

    Your policy decides when

    A rule returns a challenge for the moments that matter: a first large payout, new payout details, an age-restricted order, a login after a takeover.

  2. 02

    One call starts the check

    Your backend asks FRAPE for a verification link and sends the customer through a guided flow on web or mobile.

  3. 03

    The result becomes signals

    Approved, declined or sent for review, with plain fields such as document country, liveness and age verified, ready for your rules and for Decision Core.

  4. 04

    Your policy makes the call

    Retry the action and FRAPE decides with the verification in context, explained like every other decision.

New to how FRAPE decides? See how a decision is made.

Private by design

We keep the answer, not the passport.

Identity checks touch the most sensitive data your customers have. FRAPE is designed to hold as little of it as possible.
No document images in FRAPE
FRAPE keeps the outcome and a reference to the check. Document images, selfies and biometric data are never stored in FRAPE.
Only what the decision needs
Decision Core sees a handful of yes-or-no and country fields. Never names, dates of birth or document numbers.
Checked on the server
Results are fetched and validated server-side, then reach you as signed webhooks. A browser redirect never carries a result.
Friction only where it pays
Most customers never see a check. Verification is kept for the events your policy flags as risky.

Where it helps

Built for the moments where a check pays for itself.

  • Account opening

    Verify applicants for lending and wallets before credit or balances are granted.

    See the use case

  • Payouts to new details

    Ask the seller to prove who they are before the first payout to a new account.

    See the use case

  • Age-restricted goods

    Gate alcohol, gaming and adult content with an age check sized to the risk.

    See the use case

  • Account recovery

    Let the real owner back in after a suspected takeover, and keep the attacker out.

    See the use case

Get started

Be first to verify with FRAPE.

Coming soon

Identity verification is not available yet. Tell us where you need it and which checks matter to you. We will share timelines and invite early users first.

Join the early access listStart free with fraud decisions