What the BANNED Order Status Means
Learn when a MangoOTP activation order can be marked BANNED, how cancellation and refund confirmation work, and what the status does not mean.
A specific result for one activation order
BANNED is a final result used when the target application reports that the assigned number is not accepted because that number is banned for the selected service. It describes the outcome of one MangoOTP activation order. It does not say that your MangoOTP account is suspended, and it does not automatically place the phone number on an operational blacklist.
Use this result only when the application you are registering with clearly reports that the assigned number is banned. Messages such as invalid number, unsupported region, too many attempts, network error, or an unknown error can have different causes. Selecting BANNED for an unrelated message may prevent support from understanding what actually happened.
When BANNED can be selected
The option is available only while an activation has reached the stage where a number is assigned and is still eligible to be released. When you select it, MangoOTP sends a cancellation request for the current activation. The order is marked BANNED only after the release is confirmed. This protects the order and account ledger from showing a final result that has not actually completed.
If confirmation is temporarily unavailable, the order remains in its current processing state. Do not press the action repeatedly and do not open several replacement orders at the same time. Refresh the order detail after a short wait. If the status does not change, keep the order number and contact support.
How the refund is handled
A confirmed BANNED result follows the same financial rule as a confirmed cancellation. The amount charged for that activation is returned through a separate refund transaction linked to the same business order. The original charge remains visible, and the refund appears as its own account entry so the full history can be reconciled.
Check the final order status first, then open the balance history and locate the matching order reference. Compare the refund amount and time with the order price. A change in the total balance alone is not sufficient evidence because other deposits, purchases, or refunds may happen at the same time.
A repeated click, page refresh, or delayed result must not create a second refund. If the order shows a confirmed BANNED result but the corresponding refund entry is missing after a refresh, stop retrying and send the order number to support.
What BANNED does not mean
BANNED is not a review of every historical order associated with that phone number. It is not a public report against another user, and it does not change the status of other orders. Operational decisions about whether a number should be blocked from future sale are separate administrative work and are not shown in your order.
It also does not guarantee that every registration problem is refundable. If the application message is ambiguous, the number has already delivered a verification code, or the order cannot be released, MangoOTP must keep the verifiable result instead of guessing. This avoids displaying a successful refund when the activation is still active or already completed.
A safe checklist
Read the application message carefully and capture a screenshot that does not expose your password or verification code. Confirm that the country and service in the MangoOTP order match the page where you are registering. Select BANNED once only when the message explicitly concerns a banned number. Wait for the final result, then verify the refund in the balance history.
When contacting support, provide the MangoOTP order number, displayed status, approximate time, order amount, and a redacted screenshot of the application message. Never send a password, two-factor authentication code, access token, or API key. More order guidance is available in the MangoOTP Help Center.