You want to sell eSIMs. Good call. The market is growing faster than anyone predicted, every new phone supports eSIM, and travellers are tired of hunting for SIM kiosks in airports.
But now you have a choice to make: WhiteLabel or API?
If you can install WordPress, you can launch WhiteLabel. If you can read JSON, you can use the API. And if you’re feeling ambitious, you can run both from the same account.
Let’s break it down.
The Quick Comparison
| Factor | WhiteLabel | API |
|---|---|---|
| Setup cost | €500 (matched to €1,000 credit) | €0 |
| Monthly fee | €0 | €0 |
| Time to launch | 48 hours | ~7 days (depends on your dev) |
| Technical skill | None | Developer required |
| Branding | Your logo, colours, domain | 100% your own UI |
| Checkout | Hosted (we handle payments) | You build it |
| Best for | Speed, no-code, testing market | Custom UX, existing app/platform |
| Countries | 210+ | 210+ |
| Packages | 2,968 | 2,968 |
Same inventory. Same Tier-1 carrier backbone. Same 344 operator connections. The difference is how you sell it.
WhiteLabel: The 48-Hour Store
WhiteLabel is a fully hosted eSIM storefront with your branding on it. Your logo. Your colours. Your domain. Your pricing. Behind the scenes, it’s powered by Bappy’s infrastructure, but your customers never know that. They see your brand, buy from your brand, and trust your brand.
How It Works
- You sign up. €500 deposit gets matched to €1,000 in wholesale credit.
- You configure. Upload logo, set brand colours, choose your domain (or subdomain).
- You set prices. We give you wholesale rates. You decide your retail markup.
- You launch. Share the link. Customers browse countries, pick packages, pay, and get their eSIM QR code instantly.
That’s it. No code. No servers. No payment gateway integration. No eSIM provisioning logic. You focus on selling. We handle everything else.
WhiteLabel Is Perfect When:
- You don’t have a developer (and don’t want to hire one)
- You want to test the eSIM market before building a custom solution
- You’re a travel agency, tour operator, or content creator who wants to add eSIM as a product
- You need to launch this week, not this quarter
- You want revenue from day one with minimal effort
Real example: A tour operator in Croatia added a WhiteLabel eSIM store to their booking confirmation emails. Tourists land, scan the QR code, buy data. The tour operator earns margin on every sale. Setup took one afternoon.
API: The Developer’s Playground
The Bappy API gives you programmatic access to everything: list plans, create Links (activate eSIMs or physical SIMs), fetch top-up plans, send SMS to a Link, check live network status, pull transaction analytics. Full REST API with JSON responses and OAuth 2.0 Client Credentials auth via OmaxTelecom ID.
How It Works
- You sign up. No setup fee. Get API keys immediately.
- You integrate. REST endpoints for packages, orders, activations. Full docs at developer.omaxtelecom.com.
- You build. Your checkout, your UI, your user experience. The API handles the eSIM magic.
- You scale. Provision eSIM or physical SIM via a single POST /v1/links call.
API Is Perfect When:
- You have a developer (or are one)
- You’re building eSIM into an existing app, platform, or booking system
- You need custom checkout flows, localised pricing, or dynamic packaging
- You want full control over the customer experience
- You’re building a travel app, fintech product, or IoT platform
Real example: A travel app integrated Bappy’s API into their booking flow. When a user books a flight to Japan, the app automatically suggests a Japan data plan. User taps “Add eSIM” and it’s included in the checkout. eSIM is delivered via the app before the traveller boards the plane.
The Hybrid Option: Both
Here’s the part most platforms don’t offer: you can use both WhiteLabel and API from the same Bappy account. Same inventory, same wholesale rates, same dashboard.
Why would you do this?
- Launch fast with WhiteLabel while your dev team builds the API integration
- Use WhiteLabel for direct sales (your website, email campaigns) and API for integrated sales (your app, partner platforms)
- Test pricing and demand with WhiteLabel, then build a custom experience based on real data
- Serve different customer segments through different channels, all from one account
One account. Two channels. Zero extra fees.
The Decision Framework
Still not sure? Answer these three questions.
1. Do You Have a Developer?
No? Go WhiteLabel. You’ll be selling eSIMs by Thursday.
Yes? Consider API if you want a custom experience. Or start with WhiteLabel and let the dev build the API integration in parallel.
2. Do You Have an Existing Platform?
No? WhiteLabel gives you a complete storefront. No need to build one from scratch.
Yes? API lets you embed eSIM into your existing product. Your users never leave your app.
3. How Fast Do You Need to Launch?
This week? WhiteLabel. 48 hours, remember?
This month? Either works. API gives you more control but takes more time.
This quarter? API with a fully custom experience. Use that time to build something special.
Cost Comparison Over 12 Months
Let’s make this concrete. Assume you sell 500 eSIMs per month with an average margin of €5 per sale.
| Factor | WhiteLabel | API |
|---|---|---|
| Setup cost | €500 | €0 |
| Dev cost (12 months) | €0 | ~€2,000-5,000 (integration) |
| Monthly platform fee | €0 | €0 |
| Revenue (500/mo × €5 × 12) | €30,000 | €30,000 |
| Net profit (year 1) | €29,500 | €25,000-28,000 |
WhiteLabel wins on first-year ROI because of lower upfront cost and zero development time. API catches up in year 2 when there’s no dev cost to amortise. Both generate the same gross revenue.
The real question isn’t which costs less. It’s which gets you to revenue faster and serves your customers better.
Common Questions
“Can I switch from WhiteLabel to API later?”
Yes. Same account. Your wholesale balance carries over. Your customers won’t know the difference.
“Does WhiteLabel look generic?”
No. Your domain. Your logo. Your brand colours. Customers see your brand, not ours. We’re infrastructure, not competition.
“Is the API hard to integrate?”
If your developer can work with a REST API and read JSON, they’ll be fine. Full docs, sandbox environment, and we’re available on email if something’s unclear.
“What if I need help deciding?”
Email nikola@omaxtelecom.com. I’ll tell you what I’d do in your situation. No sales pitch, just a straight answer.
The Bottom Line
WhiteLabel is for speed. You want to sell eSIMs without writing code, managing infrastructure, or waiting for a dev sprint to finish. €500 setup, €0/month, live in 48 hours.
API is for control. You want to build eSIM into your product with a custom experience. €0 setup, €0/month, your timeline depends on your team.
Both is for the ambitious. Launch with WhiteLabel today. Build with API this month. Run them in parallel forever.
All three options give you 210+ countries, 2,968 packages, 344 operator connections, and a bird who thinks this is a perfectly reasonable way to run a telecom business.