What to Do When a Target App Rejects a Number

A destination application may reject a phone number before it sends any SMS. That message describes the destination's decision, not automatically a MangoOTP system failure. The safest response is to preserve the current session, verify the number and country requirements, and use the order action that matches what actually happened.

Capture the exact rejection

Read the complete destination message before closing it. “Invalid format,” “unsupported country,” “too many attempts,” and “number blocked” describe different situations. Record the wording and time without exposing account credentials. A generic memory such as “the number did not work” is not enough to decide whether formatting, region policy, rate limiting, or a banned-number report applies.

Check country and account-region rules

Confirm that the phone number's country is accepted for the current account, storefront, billing region, or verification purpose. The MangoOTP interface language does not change the number's country. If the destination account is configured for another market, a valid number can still be rejected because the region combination is not permitted.

Verify formatting before reporting a ban

Compare the assigned number with the destination form. Determine whether the form adds the country prefix itself, then remove spaces or punctuation only when the form requires digits. Do not add a prefix twice or drop leading digits. A formatting error should be corrected in the same session; it should not be reported as a banned number.

Distinguish unsupported from banned

An “unsupported number type” or “country not available” message is a policy or compatibility result, not proof that the individual number is banned. Use the Banned action only when the destination explicitly treats the assigned number as blocked for that service and the order is Active. Accurate reporting protects both your order history and operational decisions.

Keep one destination session

Do not restart registration or create a second account while investigating the rejection. Many applications apply risk and rate controls to the session, device, network, or account. Changing all of them at once can produce a new error and hide the original cause. Preserve the page long enough to record the message and order details.

What happens after reporting Banned

A Banned report requests cancellation and release of the active order. The order becomes Banned only after the platform receives a clear confirmation that release succeeded; then the corresponding refund handling is completed. If the result is unclear or release fails, the order must not pretend that cancellation succeeded. Follow the status shown on the order page.

Do not create a replacement too early

A new order creates another number and a separate balance record. Wait until the current order reaches an appropriate final result before trying again. Otherwise the destination may rate-limit repeated numbers, the wrong order may receive a later SMS, or you may lose track of which number belongs to which account session.

Check account flow after the final result

When the order reaches Banned, Cancelled, Failed, or another final state, review the order detail and account flow rather than estimating the refund from the available balance alone. The recorded entries show the business reason and amount. If the balance result appears inconsistent, do not repeat the order; collect the identifiers and ask support to review it.

Provide safe support evidence

Share the MangoOTP order number, selected service and country, visible order state, rejection category, time, and safe traceId. A redacted screenshot can be useful. Never send the destination password, verification code, full API Key, access token, authenticator secret, or unrelated personal information.

Rejection checklist

• The exact destination message was recorded.
• Country and account-region requirements were checked.
• The number prefix and formatting were verified.
• Unsupported policy was not confused with a banned number.
• The original destination session was kept open.
• Banned was reported only from an eligible active order.
• A new order waits for the current final result.
• The account flow will be checked after completion.

Careful classification is more useful than repeatedly trying new numbers. If the final order state or balance record is unclear, use the MangoOTP Help Center and provide the order number and traceId.