Skip to content
Try one-tap loginBook a demo

Try it

One-tap login, on your own number.

We set it up on your phone. You watch which check confirms it.

Ask for a session Book a demo

What happens when you sign in. The first that verifies ends it.

// 001The phone and app, before anything runs.Device check
// 002Your carrier confirms the number. Nothing to type.Network check
// 003One silent text from your own SIM.SIM check
// 004You approve in the Aadhaar app.Aadhaar consent
// 005Last of all, a code by SMS.One-time code
// 006A single-use token, redeemed by your bank.Signed in

Ask for a session.

Tell us the number and the phone. We reply to agree a time.

Your number is used only for this session. See the privacy notice.

We reply from the regional team for India, APAC or the Gulf.

What it shows. And what it can’t.

On your phoneWhich check confirms your number, on your own carrier.
Not in a sessionResults for your customers. That comes from a shadow proof.

RBI’s 2025 directions keep SMS OTP as a valid factor (RBI (Press release: directions on authentication mechanisms for digital payment transactions, opens in a new tab), Sep 2025). A code stays as the last fallback.

What to bring. A few minutes.

  1. A phoneWith your own SIM in it. Android or iPhone.
  2. Mobile dataSwitched on. Wi-Fi can stay on.
  3. Aadhaar appIf you want to see the consent step.
  4. Your teamSomeone from login or digital, if you like.

Before you ask.

Every question

Does the network check work on Wi-Fi?

Yes. The carrier confirms the number over mobile data, even when the phone is also on Wi-Fi. If mobile data is off, the SIM check or the next route takes over.

How does one-tap login work?

The strongest check the phone and network allow runs first, and the next takes over automatically when it can’t. First the network check, where the carrier confirms the number over mobile data, even on Wi-Fi. Then the SIM check, where the phone sends one text to DeepID from its own SIM. Then Aadhaar consent in the Aadhaar app, and a one-time code last. The first that verifies ends it.

A device risk gate sits in front of every route, and the bank’s server redeems a single-use token with DeepID before it signs anyone in. The bank chooses the steps for each attempt, or requires all of them.

Does RBI still allow SMS OTP?

Yes. RBI’s Authentication Mechanisms for Digital Payment Transactions Directions, 2025, in force since 1 April 2026, keep two factors as the baseline and keep SMS OTP as a valid factor. Issuers may add risk-based checks beyond it.

One-tap login moves beyond SMS codes where the network or the SIM can confirm the number, and keeps a one-time code as the last fallback. Other markets set their own rules, and DeepID follows each market’s. DeepID supports compliance and never guarantees it.

RBI press release (opens in a new tab)

Can we try one-tap login before talking to sales?

Yes. Ask to try it on your own number, and we set up a short session in which you sign in on your own phone and see which check confirmed it. Your engineers can have sandbox access before any contract.

Login success, codes sent and cost per login for your customers are measured on your own traffic in a pilot. We publish no figures for them.

Wire one moment in the sandbox, before any contract.

Sign-up or login end to end, with the decision back in the app and as an event, so your engineers see the shape of it before anyone signs anything.

Request sandbox accessBook a demo