Skip to content
Try one-tap loginBook a demo

More sign-ups finished, and the right person bound from day one.

Onboarding teams start with eKYC, a live face check and the number confirmed by the network, on one SDK. What is bound at sign-up, the face, the number, the SIM and the phone, is what every later moment checks.

Try one-tap loginBook a demo

What you measure

On your own traffic

  1. 01Completion: the share who start sign-up and finish it
  2. 02Drop-off at each step: the number, the ID, the selfie
  3. 03How often a one-time code is still sent at sign-up, and what it costs against SMS today
  4. 04Cases sent to manual review, and how long they wait
  5. 05Deepfake and injected-camera attempts stopped at the selfie
  6. 06Time to go live, from sandbox access to the first real sign-up

Agreed in writing before the pilot, against what you see today.

What you start with.

The first question we hear: “Will more genuine customers finish sign-up, without letting a deepfake through?” Most teams start at sign-up, with these modules.

  1. Identity and eKYC

    Verification

    Aadhaar through DigiLocker, PAN and CKYC, checked against the records that issue them.

  2. Liveness and face match

    Verification

    Catches photos, videos, masks, deepfakes and injected cameras, with an instant verdict on the phone and the final one from the server.

  3. Silent network verification

    Authentication

    The network confirms the number at sign-up, so no code is sent while it can.

  4. SIM and device binding

    Authentication

    The account is bound to this SIM and this phone from the first session.

What you add next.

The same SDK reads the next moment, so each one you add is checked against what is already bound.

  1. 1

    Login

    The SIM and phone bound at sign-up become the login: one tap, and no code to steal.

  2. 2

    New phone or SIM

    The face matched at sign-up is the face checked when the phone changes.

  3. 3

    Payee and mule graph

    A phone seen at sign-up that later receives money from many unrelated senders is linked back to it.

Three things to know.

  1. One SDK for eKYC, documents, liveness and the number, in place of several point vendors.
  2. Liveness fails closed: when in doubt it denies or sends for review, and never passes.
  3. Every face check leaves a signed record that can be replayed for audit.

Pages to read first.

Where to go next, in the order most onboarding teams read them, then the teams who sign off with you.

All eight teams

Try one-tap login on your own number.

See the network confirm your number with nothing to type, and the next check take over when it can’t. Then plan a shadow proof on one journey, measured on your own traffic.

Try one-tap loginBook a demo