[Huawei Developers] Freemind R:
Currently, many apps in e-commerce, finance, social networking, and other fields, primarily use account + SMS verification codes to verify the user's identity. This is because SMS verification is easy to use, secure, and cost-effective, which makes it broadly applicable for user registration, login, and mobile number linking.

In general, the user needs to take at least five steps to complete SMS verification: exit the current app, access the received message, copy or remember the verification code, re-open the app, and then paste or enter the verification code.

Fortunately, there's Account Kit, which endows your app with the ability to automatically read an SMS verification code, dramatically streamlining the verification process for countless numbers of users. If your app requires the user to enter a mobile number, and have their identify verified via an SMS verification code, you can integrate the ReadSmsManager API of Account Kit to ensure that your app will automatically read any SMS verification code, and bring its users a better experience.

Account Kit provides two distinct SMS verification code reading capabilities.

In addition to the capability of automatically reading an SMS verification code without the user's authorization, Account Kit 5.0.5 enables an app to automatically read an SMS verification code after obtaining the user's authorization.

This new capability helps ensure that the automatic SMS verification code reading function is available, even if your app has strict requirements for the SMS template, which cannot be modified randomly. For example, for some finance apps, if the SMS template is fixed and unable to be modified, an additional identifier for automatically reading the SMS verification code cannot be added to the app. In this case, the new capability can be applied, to ensure that the app will automatically read an SMS verification code after obtaining the user's authorization.

In which scenarios can we apply these two capabilities?

1. Automatically reading an SMS verification code without the user's authorization.

Applicable scenarios

There are no relevant requirements for the SMS template, which can be modified and added with additional identifiers.

Steps (With user login as an example.)

Tap Get code on the screen > Receive the sent SMS message > Verification code will automatically fill in > Tap LOG IN.

Pro: Fewer operations are required for a better user experience.

Con: The SMS template needs to be modified.

2. Automatically reading an SMS verification code after obtaining the user's authorization.

Applicable scenarios

There are certain requirements for the SMS template, which prevents it from being modified.

Steps (With user login as an example.)

Tap Get code on the screen > A popup for user authorization will display > Tap ALLOW > Verification code will automatically fill in > Tap LOG IN.

Pro: The SMS template does not need to be modified.

Con: Users need to grant the app permission to read SMS verification codes.

How can I integrate these capabilities?

For details about the integration process, please visit our official website by clicking

Automatically Reading an SMS Verification Code Without User Authorization

Automatically Reading an SMS Verification Code After User Authorization

Other Highlights in Account Kit

Effortless login: One-click login and authorization for all usage scenarios, which helps reduce the user churn rate.

Global presence: Over 360 million monthly active users in more than 190 countries and regions, with support for 70+ different languages.

Privacy safeguards: Requires both the account information and verification code, which complies with the EU GDPR standards for user privacy and security.

For more information about Account Kit, please visit our official website.