One-Time Passwords (OTPs) are widely used for verifying identity during logins, payments, and account recovery. These codes are usually sent via SMS, voice call, or authentication apps.

However, users sometimes face a confusing issue: the OTP works on one phone but not on another, even when using the same mobile number or service.

This situation is usually caused by differences in network conditions, device settings, SIM status, or app behavior, rather than a single fault. This article explains what is actually known and documented about why OTPs may behave differently across devices.

How OTP Delivery Works

An OTP is typically generated by a service provider (such as a bank or app) and sent to the user through:

• SMS (most common)
• Voice call
• Authenticator apps

For SMS-based OTPs, the message is sent through telecom networks and must be received by the SIM card associated with the phone number. If any part of this process is disrupted, the OTP may not arrive or may not work correctly.

In technical terms, SMS delivery also depends on the device’s configured SMS Service Center (SMSC) number, which acts as a relay point between the telecom network and your phone. If this setting is incorrect or missing (rare but possible), OTP messages may fail on one device but work on another.

SIM, Device Binding, and Network Dependency

One of the most important factors is that OTPs are linked primarily to the SIM card—but in modern systems, they are also influenced by device-level verification.

If the SIM is inserted in one device and not another:

• Only the device with the active SIM will receive the OTP
• The other device will not receive SMS-based OTPs

However, in 2026, many telecom systems and apps also track SIM–device (IMEI) pairing. If a SIM is moved to a new phone:

• OTP delivery may be delayed or temporarily blocked
• The system may treat it as a suspicious activity
• Re-verification may be required

This is why OTPs may work on one phone but fail on another immediately after switching devices.

Delays Due to SIM Swap or Security Restrictions

If a SIM has recently been:

• Swapped to a new device
• Replaced with a new SIM
• Ported to another network

OTP delivery may be temporarily restricted.

In many real-world cases, banks and apps delay OTP functionality for 24–48 hours (or longer) after a SIM swap. This is a security measure designed to prevent SIM swap fraud. This means OTP failure is not always a technical issue; it may be an intentional security restriction.

Network Signal and Coverage Issues

OTP delivery depends heavily on network connectivity.

If one phone has:

• Weak signal
• Poor indoor coverage
• Temporary network issues

It may fail to receive OTP messages, while another phone in a better signal area receives them without issue. Even within the same location, signal strength can vary depending on device hardware and antenna quality.

Dual SIM and Default SMS Settings

Phones with dual SIM support can create confusion.

If:

• The OTP is sent to SIM 1
• But the phone is set to use SIM 2 for SMS

there may be delays or issues in receiving or detecting OTP messages.

Additionally, some apps automatically read OTPs. If the wrong SIM is set as the default, auto-detection may fail.

SMS Filtering, Short Codes, and Carrier Blocking

OTP messages are often sent using short codes (5–6 digit numbers) and fall under A2P (Application-to-Person) SMS.

Telecom providers may:

• Block or filter these messages
• Classify them as spam
• Restrict high-volume senders

Other factors include:

• Spam filters in messaging apps
• Blocked sender lists
• “Do Not Disturb” (DND) or Focus modes
• Premium SMS blocking settings

If filtered, the OTP may not appear at all, even though it was sent.

Silent SMS and Auto-Verification Failures

Some apps use silent SMS or automatic verification systems.

These messages:

• May not appear in your inbox
• Are used to auto-detect OTPs

On one phone, this may work perfectly. On another:

• Permissions may be missing
• OS restrictions may block it
• Carrier may not support silent SMS

This can cause OTP verification to fail without any visible message.

Device-Specific App Permissions

Many apps rely on permissions to read OTP messages automatically.

If permissions such as:

• SMS access
• Notification access

is disabled; the app may not detect the OTP even if it has been received.

On another phone where permissions are enabled, the OTP may work normally.

Google Play Services / App-Level Detection Issues

On many Android devices, OTP auto-detection depends on system services.

If these services are:

• Outdated
• Disabled
• Not functioning properly

The OTP may arrive but not be recognized by the app.

Time Synchronization Issues

For app-based OTPs (such as authenticator apps), device time is critical.

If the phone’s:

• The date or time is incorrect
• The time zone is not synchronized

The generated OTP may not match the server’s expected value.

Messaging System Conflicts (RCS, iMessage, etc.)

Modern smartphones use advanced messaging systems like:

• RCS (Android)
• iMessage (iPhone)

In rare cases:

• Messages may be routed incorrectly
• SMS fallback may fail

This can affect OTP delivery when switching devices.

eSIM vs Physical SIM Differences

With increasing use of eSIMs, some additional issues may occur:

• eSIM activation delays
• Incomplete provisioning
• Carrier compatibility issues

This can result in OTP working on one device (physical SIM) but failing on another (eSIM).

Storage, SIM, and Hardware Limitations

Some device-level issues can affect OTP delivery:

• Full SMS inbox or low storage
• Damaged or old SIM card
• Incorrect network settings

A Simple Way to Identify the Cause

Move the SIM card to another phone:

• If OTP works → issue is device-related
• If OTP fails → issue is network or carrier-related

Common Misunderstandings

“OTP is linked to the phone.”
→ OTP is linked to the number/SIM, not the device itself.

“OTP systems are broken.”
→ Most failures are due to network, device, or security restrictions.

Quick Troubleshooting Table

Issue	Likely Cause	Fix
OTP received, but app doesn’t detect it	SIM-device re-verification	Wait 24–48 hours or re-verify
Missing permissions/system issue	Disable DND, contact the carrier	Enable SMS & notification permissions
OTP not arriving at all	Carrier filtering / DND	Wait or contact the service provider
Works on one phone only	Device compatibility or settings	Check network, reset settings
OTP fails after SIM swap	Security restriction	OTP received, but the app doesn’t detect it
Authenticator OTP not working	Incorrect time	Enable automatic date & time

Practical Steps to Fix the Issue

• Restart the device
• Toggle airplane mode
• Check signal strength
• Verify SIM placement
• Disable DND or Focus modes
• Enable app permissions
• Ensure correct date and time
• Check SMS inbox/spam
• Update apps and system
• Contact the telecom provider

Conclusion

When an OTP works on one phone but not another, the issue is usually caused by differences in SIM status, device verification, network conditions, or app behavior.

In many modern cases, OTP failures are not just technical; they are intentional security measures designed to prevent fraud.

Understanding how OTP systems interact with telecom networks, devices, and security policies can help users identify the cause and resolve the issue more effectively.

FAQs:

1. Why does OTP stop working after switching phones?

Because modern systems verify both the SIM and the device. After switching, the system may temporarily block OTPs until the new device is trusted.

2. Can OTPs be blocked intentionally by banks or apps?

Yes. Many services delay or block OTPs after SIM swaps or suspicious activity to prevent fraud.

3. Why do I receive OTP, but the app doesn’t detect it?

This usually happens due to missing permissions, disabled system services, or auto-detection failures, not because the OTP itself is wrong.