What to Check When a Verification Code Does Not Arrive

A verification code can be delayed even when the phone number was accepted. The useful response is not to create another order immediately, but to check the current order, the destination session, and the timing in a fixed sequence. This guide separates a delayed SMS from a wrong number, a closed session, or an order that has already reached a terminal result.

Confirm that the order is still active

Open Order History and locate the exact order number used for the destination application. An active waiting state means MangoOTP is still monitoring that number. A success state means a message has already been received, while a failed, timed-out, cancelled, or banned result requires you to follow the action available for that final state. Do not rely on a browser tab left open before a refresh.

Recheck the submitted phone number

Compare the number in the destination form with the number shown in the MangoOTP order. Look for a duplicated country prefix, a missing leading digit, spaces inserted by autofill, or a number copied from an earlier order. If the destination form has its own country selector, determine whether it automatically adds the prefix. A code cannot arrive for a number that was never submitted correctly.

Keep the destination verification session open

Many applications bind a requested code to the browser session, device, account, or specific verification screen that created it. Restarting registration, switching accounts, or opening a new private window may invalidate the first request. Keep the original session active while waiting and avoid navigating backward unless the application explicitly instructs you to restart.

Allow a reasonable delivery interval

SMS delivery is not always instant. Network queues and the destination application's own sending schedule can introduce a short delay. Watch the MangoOTP order page and the destination page instead of refreshing continuously. A waiting status means the workflow has not finished; it is not evidence that the order has failed.

Use resend only when it is offered

If the destination application enables “resend code,” use it once after its countdown finishes. Repeated clicks can trigger rate limits, invalidate an earlier code, or generate several messages whose order is unclear. Stay with the same MangoOTP order and the same destination session. Do not create a second order merely because the resend button appeared.

Understand which code is current

When more than one SMS arrives, use the newest code that belongs to the current verification session. Check the sender, timestamp, and visible context rather than trying every code. Some applications invalidate the previous code as soon as a new one is issued. Never paste a code into a different account, browser session, or service.

Avoid duplicate orders during investigation

A second order produces a different phone number and a separate billing and status record. It does not accelerate the first message. Duplicate orders make it easy to submit one number while watching another order, and later codes may be matched to the wrong session. Finish or correctly close the current workflow before starting a new attempt.

Stop when the order reaches a terminal state

Once the order becomes success, failed, timeout, cancelled, or banned, treat that value as the platform result. Do not continue waiting on a terminated order. If another attempt is appropriate, start it only after reviewing the final state and the available next action. Refund handling depends on the recorded outcome; it should not be inferred from the absence of a message alone.

Collect safe evidence for support

Record the order number, service, country, visible order status, time the code was requested, and any user-facing error code or traceId. If possible, note whether resend was used and whether the destination page remained open. Do not send a password, the received verification code, a complete API key, an access token, or an authenticator secret.

Troubleshooting checklist

• The correct order number is open and its status is current.
• The destination form contains the exact assigned number.
• Country prefix behavior has been checked.
• The original verification session remains active.
• A reasonable delivery interval has passed.
• Resend was used at most once after the countdown.
• No duplicate MangoOTP order was created.
• Safe diagnostic details are ready if support is needed.

Following this order of checks prevents a temporary delay from turning into several conflicting attempts. For more guidance about orders and account access, visit the MangoOTP Help Center.