Help and frequently asked questions

On the order page, as soon as the SMS arrives. If you ordered through the API, you read the code by requesting the order.

Up to 20 minutes from the moment it is issued. If a code arrives in that time the order completes. If none does, the order closes and is refunded in full.

It depends on the route and on the service sending the SMS, so we do not promise a time. What we publish instead is a measurement: for every rated route, the performance page shows the share of delivered codes that arrived within 60 seconds.

Check that you entered the number exactly as shown and ask the service to send the code again. If nothing arrives you do not need to do anything: the order closes when its window ends and the full price returns to your balance. You can also cancel it yourself once two minutes have passed.

Then compare the routes for that service on the performance page and try a country with a better delivery rate.

Some services refuse some numbers. Cancel the order once two minutes have passed since it started, as long as no code has arrived, and the full price is refunded.

A cancelled order still counts as an undelivered order in that route's figures, so numbers that get rejected show up in its delivery rate.

No. An order closes when its first code arrives. For another code, place a new order.

No. The number is yours for one verification only. You will not be able to receive later messages on it, so do not rely on it for future logins or for recovering an account. Set up another recovery method inside the service once you are signed in.

No, and nobody honestly can: delivery depends on the service sending the SMS and on the networks in between. What FastOTP does is measure how often each route delivers, publish the figure, refund every order that ends without a code, and stop selling routes that stay below the bar.

No. FastOTP delivers the verification SMS. Whether a service lets you register, and what it does with the account afterwards, is that service's decision.

When you place the order. The price is taken from your balance before a number is requested. If your balance is lower than the price, the order is refused and nothing is charged.

You get a full, automatic refund in each of these cases: no number could be issued for your order; the order's window closed without a code, which takes up to 20 minutes; you cancelled the order before a code arrived; or the number was withdrawn on the supply side before a code arrived.

In short, every way an order can end without a code refunds the full price. The exact wording is in the refund terms.

Cancel it from the order page. Cancelling is allowed once two minutes have passed since the order started, and only while no code has arrived. A cancel request before the two minutes are up is refused, and you can try again when they have passed.

A cancelled order is refunded in full.

No. Once a code has arrived the order is complete and its price is not refunded, whether or not you go on to use the code. See the refund terms.

It goes back to your FastOTP balance at the moment the order closes. There is no form to fill in and no ticket to open, and you can spend the refunded amount on another order straight away.

An order that was charged but never received a number is refunded automatically. If the failure happens while the number is being requested, the refund is immediate. If the order stalls before that step finishes, a background check finds it and refunds it within a few minutes.

Send the order ID to [email protected] or use the contact page to reach support, and we will look at that order.

It is the number of orders that delivered a code divided by the number of orders where a number was issued, over the last 30 days. It is always shown with the number of orders behind it. The full method is on the delivery performance page.

A route gets a delivery rate only once it has at least 20 orders in the last 30 days. Below that the sample is too small to mean anything, so the route shows its order count instead of a percentage. It stays on sale while it collects orders.

Only orders where a number was issued, and only once they have closed. An order that ended with a code counts as delivered. An order that expired, was cancelled by the customer or had its number withdrawn counts as not delivered.

Orders where no number could be issued are left out, because nothing was delivered or missed. Orders still waiting for a code are counted as soon as they close.

When its delivery rate stays below 80% for 7 days in a row. The route is then taken off sale and marked as suspended, with the delivery rate and the order count that caused it. Each de-listing is recorded in the public de-listing log.

Only by a human decision. A suspended route never returns on its own, however much stock it has. When the supply behind it has been fixed, a person puts it back on sale and writes a note saying what changed, and that note is published in the same log.

The thresholds cannot be changed without a written reason, and every change is published with that reason in the threshold change log. We do not lower a threshold to keep a failing route on sale.

Because every route listed here is one we measure and are prepared to stop selling. A long list of untested routes costs nothing to publish, and the customer finds out which ones work by paying for them. We would rather list fewer routes and publish how each one performs.

You pay per code from a prepaid balance. Each route has its own price, shown before you order, and that price is the whole cost of the order. Current prices are on the pricing page.

No. There is no plan, no monthly fee and nothing to cancel. You add balance and spend it one code at a time.

From your account, before you order. The payment options open to you are shown there when you add balance.

US dollars.

Prices follow live supply and are refreshed every few minutes, so a route can cost a little more or less than it did earlier. If the price has gone up since you looked, the order is refused rather than charged at the higher price, and you can decide again at the new price.

Yes. The website and the API read one catalogue and one price list.

Yes. The API sells the same routes at the same prices as the website. The API overview explains what it covers, and the API quickstart walks through a first order.

Yes. Website and API orders go through the same order path, so the charge, the window, cancelling and refunds behave identically, and API orders count towards the published delivery rates in the same way.

The request comes back with a named error you can branch on, such as no numbers available, price changed, balance too low or cancel requested too early. The error reference lists each one and what to do about it.

Yes. They are set out, with advice on retrying safely, in the API limits documentation.

Receiving verification codes for accounts you are entitled to create. Typical uses are keeping your personal number out of a sign-up, and testing the sign-up or login flow of a product you build or test.

Yes. FastOTP is not affiliated with any of the services it lists, and a number from FastOTP gives you no right that a service's own terms do not. Whether an account is allowed under those terms is for you to check before you order.

Fraud, impersonating another person or organisation, spam, harassment, anything unlawful, and anything that breaks the terms of the service the number is used with. The full rules are in the terms of use.

No. We do not give advice on evading bans, blocks or limits set by any service, and that is not what FastOTP is for.

It can be suspended. The terms of use set out how, and how to contact us about an account decision.