Your phone number.
One tap to sign in.

Confirm your device number, review and agree to the relevant terms, then tap to sign in. On a supported, successful one-tap journey, there is no need to type a phone number or SMS code.

  • Review the number
  • User consent
  • Server verification
  • Keep alternatives
  • Test before launch
01 / LESS FRICTION, MORE FLOW

Make signing in
feel simple again.

Bring number confirmation, clear consent and sign-in into one focused entry. Users review and choose first; a successful one-tap journey avoids looking up an SMS code.

Less manual typing

On a supported and successful one-tap journey, there is no need to manually enter a phone number or SMS code.

No SMS lookup on success

A successful one-tap journey does not require the user to open SMS, find a code or copy it. The sign-in action stays in the App.

A clear number choice

Show a masked number first so users can confirm the account and give consent before number verification continues.

Keep another way in

When users want another number, the network is unsupported or verification fails, keep integrated alternatives such as SMS-code login available.

Review and agree

Review the user terms, privacy policy and carrier verification information, then choose whether to agree.

Application server interface

The server must process the authentication result and complete account login. Do not create a session solely from client-side return values; follow the integration requirements.

Show the number, then let users choose.

Bring number confirmation, clear consent and sign-in into one focused entry. Users review and choose first; a successful one-tap journey avoids looking up an SMS code.

Check your number

Review the masked number and confirm it is the account you want. On dual-SIM devices, check which SIM is used for mobile data.

Review and agree

Review the user terms, privacy policy and carrier verification information, then choose whether to agree.

What changes compared with SMS-code login?

Keep verification on your server.

For integration discussions. Your application handles account creation, matching and sessions; interfaces and SDK versions depend on the agreed scope.

Mobile app SDK

The client SDK handles environment checks and authorization, fitting into the app’s visual design and login entry point while handling cancellation, failures and switching login methods.

Application server interface

The server must process the authentication result and complete account login. Do not create a session solely from client-side return values; follow the integration requirements.

Discuss SDK integration
How does one-tap login differ from SMS-code login?

One-tap login verifies the current mobile-data SIM number through carrier capabilities and continues after user consent, reducing number entry, SMS waiting and manual code entry. SMS verification remains an alternative or fallback.

Which number is used on a dual-SIM phone?

Verification uses the current mobile-data SIM number. To use another number, switch the data SIM or choose another method such as SMS verification. Include SIM switching in integration tests.

Does it need permission to read SMS?

The documented App SDK approach does not require SMS access permission. Confirm permissions and data processing for the current SDK version and provide the appropriate disclosures in your App.

What happens if verification fails?

Connect an SMS-code fallback and configure and test unsupported environments, verification failures and user-selected alternatives. Fallback must be integrated rather than assumed to work automatically.

Which application formats and networks are supported?

The current materials describe an App SDK and do not establish H5 or mini-program support. Confirm carriers, devices, system versions and network requirements before integration and test against your target users’ environments.

How long does integration take, and how is it priced?

Timing and pricing depend on the client, server, existing account flow and expected verification volume. Agree on the scope before confirming the plan, quote, delivery schedule and billing terms.

Build a login journey that fits your App.

Share your App platforms, existing sign-in methods and expected verification volume to define availability, integration steps and SMS fallback.

Discuss one-tap login