A prepaid, server-to-server REST API over the 4,090 plans SimWay sells across 190 destinations. You buy at a discount off the public price, you set your own retail price, and your customer never sees us.
Four decisions define it, and they are all settled. Reading them first will save you reading the rest if one of them is a dealbreaker.
Decision
What it means for you
Prepaid balance
You deposit, every purchase debits the balance, and it can never go below zero. There is no credit line, no invoice at month end and no way to be surprised by a bill. The refusal when funds run out is a 402 with the two numbers in it.
Published volume tiers
Four rungs from 8% to 20%, recomputed nightly from your trailing 30-day spend. The rate is on a public page rather than behind a sales call. Staff can set a per-account rate that supersedes the ladder entirely.
API and nothing else
There is no white-label storefront, no hosted checkout and no reseller portal you point customers at. You own the front end and the customer relationship; we deliver profiles.
Sandbox first
Sandbox keys run against the same base URL, the same routes and the same request and response shapes as live — only the credential differs. A live key is minted by an owner in the cabinet once the account is approved, and depositing is live-mode only: a sandbox key opening an invoice would be sending real cryptocurrency to test a code path.
Who it is for
Anyone whose customer is already about to travel, and who can run a server-side integration. That second half is a real constraint, not boilerplate: the partner surface emits no CORS headers at all, so a key cannot be used from browser JavaScript and there is no client-side SDK to drop in.
Travel sellers
Agencies, OTAs and tour operators attaching connectivity to a booking that is already paid for. The order carries your own reference, so a profile ties back to a booking without a second system.
Telcos and MVNOs
Selling roaming to your own subscribers without building supplier relationships in 190 destinations, and without a roaming agreement per market.
Device retailers
Attaching a data plan at the point a phone or tablet is sold. The install payload includes a scannable QR and a one-tap Apple universal link.
Corporate travel platforms
Provisioning a profile per trip against a prepaid float, with a statement that reconciles by construction — every row carries the balance it produced.
What integrating actually involves
Three calls to sell something. The examples below are generated from the same endpoint records the reference pages render, so they cannot drift from the parameter tables, and they use a sandbox key — pasting one costs you nothing.
Price it. A dry run that deducts nothing and tells you whether the balance would clear. Calling it before every order is what stops you spending an idempotency key on a refusal.
Order it. The money moves synchronously; the profiles do not. You get 202 with the order id, the price you were charged and your new balance.
Poll it. Sleep poll_after_ms, read the order, repeat while it is not null. When it is null the order is terminal and esims[] holds what was delivered.
One order can carry up to 50profiles, provisioned individually, and partial delivery is a first-class outcome: delivered profiles stay sold and the undelivered units’ money is back on your balance in the same transaction that writes the status.
Four things that are true, and checkable
We have no partners yet, so there is nothing here about scale. These are the claims that can be verified without taking our word for anything.
We name the carrier, per destination
The catalogue holds which mobile operator each plan roams onto and at which generation, for 187 of 190 destinations and 150 distinct operators. It comes back on every plan as networks. Nobody else in this market publishes it — and it is the question a traveller asks that a price list cannot answer. Check it on any destination page.
The discount cap is a measurement, not a posture
20% is the deepest rate anyone gets, because at 20% every active plan still clears the hard price floor and at 25%, 819 of them do not. A supplier who will quote you a deeper rate on the whole catalogue is either buying better than us or is about to reprice you. The arithmetic is on the pricing page.
The sandbox is an environment, not a demo
Same base URL, same routes, same shapes, a $1,000 float, and four fixture plans that force the outcomes you otherwise cannot rehearse: a 402 that binds its key, a supplier failure with an automatic refund, a run that outlives your HTTP client, and a partial delivery. Profiles come back with Luhn-valid ICCIDs and real scannable QR codes. What it does and does not do.
The numbers are published, including the awkward ones
Rate limits per tier, the retry ladder, how long a doomed order takes to report failure, how stale usage counters can be (30 minutes), and every error code with its cause. An integration fails on the cases nobody documented, so those are the ones written down.
Where this programme is today
It is new. There are no partner logos on this page because there are no partners, and a page that pretended otherwise would be the first thing a competent buyer caught. Here is the state of it, so nothing is a surprise after you have written code.
Built and running
The full catalogue, priced per account, with incremental sync.
Ordering, with idempotency, partial delivery and automatic refunds.
Profiles with the complete install payload, and usage counters.
The prepaid ledger, which reconciles by construction.
Live and sandbox modes, per-key rate limits, IP allowlists.
Not built — do not plan around it
Webhooks. None, of any kind. Polling is the delivery mechanism.
Self-serve signup. A partner account is opened by a person, and so is being added to one. Everything after that — keys, deposits, the statement — is yours in the cabinet.
Card deposits. Cryptocurrency or bank transfer. A chargeback arrives months after the float is spent.
Order cancellation. No endpoint. An order runs to a terminal state.
A live usage read. Counters are up to 30 minutes old.
Questions
What do I actually get?
A server-to-server REST API over the same catalogue simway.pro sells — 4,090 active plans across 190 destinations — at a discount off the public price, plus a prepaid balance that every purchase debits. You build the storefront; we do not host one for you and there is no white-label shop.
How is it priced?
A published volume ladder from 8% to 20% off list, recomputed nightly from your trailing 30-day spend, with no commitment and no monthly fee. Staff can set a per-account rate that supersedes the ladder. Nothing is deeper than 20%, because a hard price floor protects the margin under it.
Do I have to commit to a volume?
No. There is no minimum, no monthly fee and no contract term. The tier is a function of what you actually bought in the last 30 days, so it moves both ways on its own.
How do I pay?
You deposit and the balance is debited on each purchase; it can never go below zero. POST /partner/v1/deposits mints a cryptocurrency invoice for a whole number of dollars between $100 and $10,000 and answers a link to pay it; the float moves when that payment settles, not when you call the endpoint. Bank transfer is the rail for anything larger. Cards are not a rail here — a chargeback lands months after the float has been spent.
How fast is provisioning?
About 5 seconds end to end in the normal case, with a hard ceiling of 92 seconds on one run. Ordering answers 202 immediately and you poll, because a client that waits will time out and retry, and a retry on a purchase is a double charge.
Are there webhooks?
No. Polling is the only delivery mechanism, and the order object tells you when to stop polling. We would rather say that plainly than imply a webhook is coming.
Can I try it before talking to anyone?
Yes. A sandbox key runs against the same base URL and the same routes with a $1,000 float, four fixture plans that force the failures you cannot otherwise rehearse, and synthetic profiles with Luhn-valid ICCIDs and real scannable QR codes. Only the credential differs between sandbox and live.
How to start
Email [email protected]. There is no signup form, and that is not coyness: opening an account is a decision a person makes, and putting a form in front of it would only hide the wait. Tell us what you sell and roughly what volume you expect.
What comes back is an account with your own login on it. From then on the cabinet is yours: mint and revoke your own keys, read your balance and statement, open a deposit, and see every order and profile. The sandbox float is already on the account and costs nothing to spend.
Live traffic still needs approval from a person, and depositing is live-mode only. Everything you write against sandbox works unchanged against live — the base URL and the routes are identical and only the credential changes.
The cheapest thing in the catalogue is $1.49 at list, which is $1.20 at the deepest published rate. Prices are in USD and there is no way to be billed in anything else.
