Skip to content
Try one-tap loginBook a demo

Moment 03 · New phone or SIM

The face from sign-up decides who gets bound.

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 a new phone or SIM checks. Against what came before.

  • Checked

    The face

    Checked again, against the face matched at sign-up, with the same injection defence.

  • Bound again

    The number and SIM

    The new SIM confirms the number with one text from the phone.

  • Bound again

    The phone

    The new phone is checked for tampering and bound in place of the old one.

  • Not read here

    The payee

    Not read here.

  • Not read here

    The session

    Read again from the next payee or payment, on the new phone.

Where fraud shows. And the decision.

BlockA different face on the new phoneWhoever moved the number cannot pass as the person matched at sign-up.Step upA fraudster’s phone enrolledCredentials phished from the customer are used to register the account on another phone.
Step upA recovery request moved to new handsA contact-centre or in-app recovery flow tries to move the account.

What DeepID reads. One call, one decision.

The decision. Step up, in the example.

Identity is uncertain

  • Why

    The SIM moved from the bound phone and the new phone is 4 minutes old, so the face is checked against sign-up before the cool-off starts.

  • The customer sees

    “Confirm it’s you with a quick face check.”

  • A good customer

    One face check on the new phone, then lower limits for a few hours.

Your FRM receivesSTEP_UP · SIM moved · new device 4 min · face check

What to measure. Agreed before the pilot.

Where they start
  • TakeoversThose that start with a new phone.
  • Re-bindsOwners through on the first try.
  • LossMoney lost on these journeys.
  • FrictionGood customers asked for more.

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

  • Singapore, Malaysia and the Philippines

    Cool-off and hold decisions after a new device, SIM or payee, or when a payment looks coerced, set per market and journey.

    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

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