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.
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.
- Can you test without paying? A sandbox or test key that validates requests and returns real prices lets you build before money moves.
- 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.
- Is there a status page with history? Incidents that were posted and resolved are a better sign than an eternal green banner.
- 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.
- 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.
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.
Run the checks on us
The rate card lists all 228 destinations. Every account has a test key. The API reference, webhook signatures and OpenAPI file are public. The status page keeps six months of incidents. The legal pages carry a summary per clause, and unused balance is refundable. 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? Write to [email protected]; corrections are folded back into the guide and the update date changes.