Skip to content
Try one-tap loginBook a demo

Moment 01 · Sign-up

Bind the real person to their own phone and SIM.

Try one-tap loginBook a demo
// 001The real person, bound to their own phone and SIM.Sign-up// 002One tap, and the SIM bound at sign-up is checked.Login// 003The face from sign-up, checked before anything is bound again.New phone or SIM// 004The payee scored, from the phone and SIM already bound.New payee// 005The SIM bound at login is the SIM expected at payment.Payment

What sign-up checks. Against what came before.

  • Bound here

    The face

    A live person on a real camera, matched to Aadhaar or the document’s portrait.

  • Bound here

    The number and SIM

    The network confirms the number belongs to the SIM in this phone, with no code sent.

  • Bound here

    The phone

    The phone gets an ID that survives reinstalls and resets, and is checked for emulators.

  • Not read here

    The payee

    Not read yet.

  • Not read here

    The session

    Not read yet.

Where fraud shows. And the decision.

BlockA virtual camera or a deepfakeA generated face is fed in through a virtual camera or an emulator.BlockOne face behind many accountsFace search finds the same live face on other customers’ accounts.
Step upA number that is not theirsThe network cannot confirm the number on the SIM in this phone.
BlockAn emulator or a tampered phoneThe account is being opened from an emulator, a rooted phone or a cloned app.

What DeepID reads. One call, one decision.

The decision. Allow, in the example.

Everything holds

  • Why

    Number confirmed by the network, SIM and phone bound, a live person on a real camera, and no face or device seen on other accounts.

  • The customer sees

    “You’re verified. No code was needed.”

  • A good customer

    A good customer takes a selfie and is done. No code is sent while the network can confirm the number.

Your FRM receivesALLOW · number verified · SIM bound · live person

What to measure. Agreed before the pilot.

Where they start
  • CompletionWho starts sign-up and finishes.
  • Drop-offAt the number, the ID, the selfie.
  • CodesHow often a code is still sent.
  • ReviewWhat goes to a person, and the wait.

Use cases. Step by step.

Rules it supports.

  • India and Malaysia

    SIM and device binding at onboarding and re-binding on change, with the number confirmed by the network and device integrity read every session.

    The rules, market by market

  • India, Singapore, the UAE, Malaysia and the Philippines

    One-tap login that tries the network check, the SIM check and Aadhaar consent before any one-time code, and face checks with injection defence where identity is in doubt.

    The rules, market by market

  • India, Malaysia and the Philippines

    A payee and mule graph across accounts and devices, with recipient risk scored before the payment is sent.

    The rules, market by market

Start with sign-up, login or payments.

Pick one, test it on your own traffic before you commit, and add the others on the same SDK when you’re ready.

Book a demoTry one-tap login