If your app logs users in with a mobile OTP, the Apple App Store and Google Play reviewers need a way to get past that screen. They cannot receive an SMS on your users’ numbers, and an app they cannot open is often rejected. The usual fix is a review test number: one phone number and one fixed code that your server accepts without sending a real OTP. This page explains how to set it up safely with Fast2SMS Smart OTP, and what to write in the review notes.
Why reviewers get stuck at the OTP screen
- The reviewer types a phone number, and the OTP goes to that number. The reviewer does not have your test phone.
- Reviewers may test from outside India, and your OTP flow may expect an Indian number.
- Both stores ask for a way to sign in when part of the app is behind a login. Apple has a sign-in section in the App Review information, and Google Play has an App access section in the Play Console.
How a review test number works
You pick one phone number that you own, and one fixed code, for example a 6-digit code that is not used anywhere else. Your server keeps both in its settings. Then:
- When someone asks for an OTP for the review number, your server does not call the Fast2SMS Send OTP API. It answers as if the code was sent.
- When someone submits a code for the review number, your server compares it with the fixed code instead of calling the Verify OTP API.
- Every other number goes through Smart OTP as normal.
Smart OTP does not have a test-number list of its own, so this check lives in your server code. That is the right place for it anyway, because the app on the phone should never decide who is logged in.
Set it up step by step
-
Choose a number and a code
Use a number your business owns, such as a company SIM. Never use a real customer’s number or a random number that someone else may own. Pick a code that is hard to guess.
-
Keep both in server settings
Store them as environment variables or in your config, not in the app. Then you can change them after the review without a new app release.
-
Add the check before the Fast2SMS calls
Put a small check in front of your send and verify functions. The example below is Node.js. The same idea works in PHP, Python, Java or any language.
const REVIEW_MOBILE = process.env.REVIEW_MOBILE; // e.g. a company number const REVIEW_OTP = process.env.REVIEW_OTP; // fixed code for reviewers const KEY = process.env.FAST2SMS_API_KEY; const OTP_ID = process.env.FAST2SMS_OTP_ID; async function sendOtp(mobile) { if (REVIEW_MOBILE && mobile === REVIEW_MOBILE) { return { ok: true }; // no SMS sent, no charge } const r = await fetch('https://www.fast2sms.com/dev/otp/send', { method: 'POST', headers: { authorization: KEY, 'Content-Type': 'application/json' }, body: JSON.stringify({ mobile, otp_id: OTP_ID }) }); const data = await r.json(); return { ok: r.ok, message: data.message }; // HTTP 200 = success } async function verifyOtp(mobile, otp) { if (REVIEW_MOBILE && mobile === REVIEW_MOBILE) { return { ok: otp === REVIEW_OTP }; } const r = await fetch('https://www.fast2sms.com/dev/otp/verify', { method: 'POST', headers: { authorization: KEY, 'Content-Type': 'application/json' }, body: JSON.stringify({ mobile, otp: String(otp) }) }); const data = await r.json(); return { ok: r.ok, message: data.message }; // HTTP 200 = success }Your Fast2SMS API key stays on the server. The app only talks to your own server.
-
Write the review notes
In App Store Connect, give the number and code in the sign-in section of the App Review information, and add a short note. In the Play Console, add the same in App access. A note like this works:
“This app logs in with a mobile OTP. For review, enter the phone number 9XXXXXXXXX and the code XXXXXX. No SMS is sent to this number. All other numbers receive a real OTP by SMS or WhatsApp.”
-
Test it on a release build
Before you submit, install the release build and log in with the review number and code. Then log in with a real number to check that real OTPs still arrive.
Keep the review number safe
- One number only. Do not allow ranges or patterns.
- A limited account. Link the review number to a demo account with sample data, not a real customer account.
- Change the code after each review, or turn the bypass off when no review is open.
- Log every login with the review number, so you notice if someone else uses it.
- Keep your other limits on. The resend wait and max verify attempts in OTP Settings still protect real numbers. See Smart OTP settings.
Testing during development
For your own testing, send real OTPs to your team’s phones. Every send through Smart OTP is a real message and is charged, so the ₹50 signup credit is the easy way to test. You can also send a single OTP from the panel with the Test OTP button, without the app. See send an OTP to a mobile number online.
If the review build should read the OTP from the SMS automatically on Android, check your template first. See OTP autofill on Android and iPhone.
Frequently asked questions
Will Apple or Google reject an app that uses OTP login?
OTP login is common and accepted. Problems come when the reviewer cannot sign in. Give them a working test number and code in the review notes.
Does the review number cost anything in Fast2SMS?
No. Your server skips the Send OTP call for that number, so no message is sent and nothing is charged.
Can I use a number that does not exist, like 9999999999?
Use a number your business owns. A made-up number may belong to someone, and other apps may use the same one.
Can Fast2SMS send the review code to the reviewer?
No, because you do not know the reviewer’s number in advance. The fixed test number solves this.
Do I need a separate OTP template for testing?
No. Test with the same OTP ID you use in production, so you test what your users will get.
Where should the bypass live, in the app or on the server?
On the server. Code in an app can be read by anyone who downloads it, and the server must decide who is logged in.