Why vetting matters more here
A provider that does not ask who you are usually does not tell you much about who it is either, and payment in cryptocurrency is final. That combination rewards ten minutes of checking before the first deposit. None of the checks below needs an account.
The risks are specific. A gateway can resell a grey route that works until an operator notices, it can take deposits and stop answering, or it can be a sound service with thin documentation. From the outside they look alike: a landing page, a price list, a sign-up form. What separates them is what they publish, what they let you test and what happens when a real message leaves for a real phone.
Seven checks
- Is the whole rate card public? One price per destination, visible before sign-up. "From" prices with the rest behind a login tell you nothing. Check the unit, which should be the segment, and what is billed: some providers charge for messages they refuse before sending. A price far below everyone else's on a destination known to be expensive usually means a grey route.
- Can you test without paying? A sandbox or test key that validates requests and returns real prices lets you build before money moves. A good one behaves like live traffic in everything but the sending: same errors, same prices, same webhooks.
- Is there real documentation? An API reference with error codes, webhook signatures and an OpenAPI file is hard to fake and tedious to write. A single page with one cURL example is not documentation. Run one of the examples: an example that fails against the provider's own reference is documentation nobody uses.
- Is there a status page with history? Incidents that were posted and resolved are a better sign than an eternal green banner. Look for the destinations affected, start and end times and a plain account of what happened.
- Do the legal pages say something? Terms, a privacy policy that lists what is stored, an acceptable use policy that names prohibited traffic, a refund policy. Pages copied from a template, with no mention of SMS, protect nobody.
- What are the deposit terms? Minimum, setup fees, credit expiry, and whether unused balance can be refunded.
- Does a message arrive? Send ten texts to phones you hold before you send ten thousand. The handset test takes an afternoon.
Red flags
- Award and certification badges with no way to verify them.
- Testimonials with stock photos and no company you can find.
- A sender-ID promise of "100% worldwide": no provider can deliver names in the United States or Brazil.
- Delivery claims of 100%.
- No word anywhere on what may not be sent. A gateway without content rules loses its routes, and your traffic with them.
- Willingness to send as a bank, a carrier or a well-known brand. A provider that accepts impersonation is selling a route that will be closed.
- Delivery reports in which every message is delivered within the same second, including to phones you know are switched off.
- Discounts that require a large deposit before a single test message.
- Claims of long experience that nothing on the site, in the documentation or in the status history supports.
Signs of an honest provider
Good signs are harder to list than red flags, but they exist. An honest provider publishes its limits: the countries where your name will not show, the destinations that confirm only at carrier level, the traffic it refuses. It explains what is billed before you ask. It names the cases where another kind of provider serves you better, such as US marketing under your own brand or domestic traffic in India. Its pages agree with each other, so the price on the rate card matches the price in the API and in the cost preview. And its status history includes bad days. None of this proves a provider is sound, but each sign is expensive to fake and cheap to check.
What a sound provider still asks of you
No documents does not mean no questions. A gateway that protects its routes refuses some content before sending, reviews traffic patterns and may ask about traffic that looks unusual. When you request a sender registration, it needs to know who uses the name and for what, because operators require it. Expect that, and be wary of the opposite: a provider that takes any text to any list without a question is one whose routes, and your messages with them, will not last.
Questions to ask support
A specific question tests knowledge and honesty at once. Pick two or three that matter to your traffic:
- Which sender will recipients in a given country see if I set my brand name?
- Does that country return handset receipts or only carrier acknowledgements?
- Is a message refused before sending billed? Is a failed one?
- How many segments will this exact text use, and why?
- What does your acceptable use policy refuse, and what happens when a message breaks it?
- When a route degrades, where do I find out?
Good answers are short, specific and sometimes "no". An answer that promises everything, or arrives as a sales pitch, tells you more than the question did. Time the reply too: it is the response you will get on the day a campaign goes wrong.
A careful first deposit
Deposit the minimum, on a low-fee network. Send a handful of real messages to your own phones in the countries you care about. Read the delivery report next to the handsets. Ask support one specific question and time the answer. Scale the balance when those four things look right.
Write down what you measured: arrival times, the sender shown, the statuses in the report. It takes five minutes and gives you a baseline if the provider's behaviour changes later.
Keep checking after the first send
Vetting is not a single event; routes change, and a route that was sound in spring can be swapped by autumn. Three habits keep you informed. Read the delivered rate per destination rather than overall, so that one country's decline is not hidden by the others. Check the sender column after each campaign in countries that deliver names. And repeat the handset test after an incident or a sudden change in delivery. If you send through an API, watch failures by reason as well: a sudden rise of one reason on one destination is often the earliest sign of a route problem. Compare providers on the cost per message that actually arrived, not on list price.
Run the checks on us
An email address and a password open an account; there are no documents to send and no phone number to give. The rate card lists all 228 destinations, and the same rates are published as /rates.json and returned by GET /v1/rates. Every account has a test key that validates, prices and answers like live, without sending or billing. Each country page shows the sender rule, the receipt type and the default quiet hours, and the cost preview shows the total per destination before anything is charged. The API reference, the webhook signatures and the OpenAPI file are public, and support answers in the panel seven days a week. The status page keeps every incident since launch on 21 September 2026. The legal pages, among them the acceptable use policy and the privacy policy, carry a summary per clause, and unused balance is refundable. Messages refused before sending are never billed. What we do not publish is a company name and address; the about page explains why, and you should weigh that as you would for anyone else.
Something unclear or out of date? Tell us on the support page; corrections are folded back into the guide and the update date changes.
