White-Label vs API eSIM Platform: Decision Matrix
TL;DR
If you want to sell eSIMs, you have two paths: launch a branded storefront or integrate an eSIM API into your existing platform. Both work. The right choice depends on your budget, technical resources, and how fast you need to launch. This guide compares both models in a decision matrix. For the API product, see Bappy.
The two models
Every eSIM business starts with a choice: do you want a ready-made storefront, or do you want to build the experience yourself? Here is what each model actually looks like.
White-label Storefront
You get a fully built, branded eSIM web store. Custom domain, payment gateway, CRM dashboard included. No coding required.
- Custom domain and branding
- Payment processing included
- QR code delivery automated
- Set up on sign-up; KYC before production
API Integration
You get API endpoints and build the customer-facing experience yourself. Full control over UI/UX. Self-service API keys.
- Complete UI/UX control
- Embed in existing platforms
- REST API with full documentation
- Production keys on sign-up; KYC within 14 days
Both models use the same underlying network: BICS wholesale connectivity (white-label: 200+ countries, 350+ operators; Bappy: 210+ countries). The difference is in how you package and deliver the experience to your customers.
Decision matrix
Here is a side-by-side comparison across the factors that matter most when choosing a platform model.
| Factor | White-label | API |
|---|---|---|
| Budget | €1,000 one-time setup, credited to your wallet | No setup fee (pay per activation) |
| Technical skills | None required | Developer needed |
| Time to market | Store set up on sign-up; KYC before production | Depends on your development time; KYC within 14 days |
| Branding control | Full (your domain, logo) | Full (you build the UI) |
| Margin control | You set retail prices | You set retail prices |
| Maintenance | We host and maintain the store | You maintain your code |
| Scalability | Standard storefront flow | Embedded in your own flows and infrastructure |
| Best for | Travel agencies, tour operators, non-technical teams | Developers, existing platforms, custom UX needs |
When to choose white-label
The white-label storefront is the right choice if most of these apply to you:
- You don't have developers on your team
- You want to launch without a development project
- You want payment processing, CRM, and QR delivery included out of the box
- You're a travel agency, tour operator, or reseller
- You want someone else to handle hosting, updates, and infrastructure
Learn more about the White-label eSIM Platform →
When to choose API
The API model is the right choice if most of these apply to you:
- You have a dev team or technical co-founder
- You want eSIM purchasing embedded in your existing app or website
- You want complete control over the UI and customer experience
- You're building a custom travel platform, super-app, or neobank with travel features
- You want no setup fee and to pay only when customers activate
Learn more about the Bappy eSIM API →
What about Telkor?
Per-MB connectivity platform
Telkor is for a different category entirely. It is a connectivity platform for businesses that ship connected devices or resell connectivity - IoT fleets, eSIM-enabled hardware, mobile rentals, and roaming products. Full programmatic control over every SIM from activation to billing.
It is not a storefront and not a package-based reseller API. It is fleet-scale connectivity infrastructure - designed for operators and device makers who need custom data plans, coverage zones across 278 operators, and real-time device control. Platform credit from €2,000. Zero setup. Monthly fee converts to data credit.
What is per-MB billing?
Most eSIM platforms sell fixed data packages - 1GB, 3GB, 5GB. If a traveler buys 3GB but uses only 1.8GB, they waste 1.2GB. That unused data is called "data breakage."
Per-megabyte (per-MB) billing charges customers only for data they actually consume. A traveler who uses 1.8GB pays for exactly 1.8GB - no rounding, no waste.
Why it matters for resellers
- Lower effective cost per consumed GB - more competitive retail pricing
- Customer pays for actual use - no unused package data
- Real-time usage tracking - accurate billing, no overage surprises
Which OmaxTelecom products support per-MB?
| Product | Billing model |
|---|---|
| Bappy API | Package-based (fixed packages, not per-MB) |
| Telkor Platform | Per-MB billing. Platform credit from €2,000. Zero setup. Monthly fee converts to data credit. |
| White-label Store | Package-based (same as Bappy) |
Per-MB billing suits MVNOs, IoT fleets and high-volume resellers. For most travel businesses, package-based pricing (Bappy/Whitelabel) is simpler and sufficient.
Scalability: when to switch models
Your ideal platform model depends on where you are today - and where you are heading. Here is a volume-based guide.
| Volume | Recommended model | Why |
|---|---|---|
| 0–100/month | White-label Store | No development needed |
| 100–500/month | White-label + consider API | Store handles UX, API for integrations |
| 500–1,000/month | Add Bappy API | Embed eSIM in your existing platform |
| 1,000+/month | White-label + API + consider Telkor | Multi-channel, per-MB for cost optimization |
Migration path
Start with white-label. Add API later.
You don't have to choose one forever. The store and API share the same account, same wholesale rates, same customer data.
- 1 Month 1: Launch the white-label store (€1,000 setup, credited to your wallet)
- 2 Month 3–6: Integrate Bappy API into your existing app/website
- 3 Month 6+: Run both - storefront for direct traffic, API for embedded purchases
- 4 At scale: Add Telkor for per-MB pricing, fleet control, and connectivity infrastructure
Quick recommendation
Not sure where to start?
If you have no developers, start with the white-label store: €1,000 one-time setup, fully credited to your wallet. No monthly platform fee. You can add API access later. If you already run an app or booking platform, start with the API.
Want to compare costs first? See Pricing or talk to our team.
Frequently asked questions
What is the difference between a white-label eSIM platform and an eSIM API?
A white-label platform gives you a fully built, branded storefront with payment processing, CRM, and QR code delivery included. No coding required. An API gives you endpoints to integrate eSIM provisioning into your own app or website - you build the customer-facing experience yourself. In both models you set your own retail price above the wholesale cost.
How much does it cost to start selling eSIMs with each model?
OmaxTelecom white-label platform: €1,000 one-time setup, fully credited to your wallet. No monthly platform fee. The Bappy API has no setup fee - you top up a prepaid wallet (from €10) and pay per activation at wholesale rates. In both models you set your own retail prices.
Can I switch from white-label to API or use both?
Yes. You can start with the white-label storefront, then add API access as they scale or want to embed eSIM purchasing into their own platform. The two models are complementary, not mutually exclusive.
Pricing is based on OmaxTelecom's current offering and may change. White-label: €1,000 one-time setup, fully credited to your wallet. No monthly platform fee. API access has no setup fee, with pay-per-activation pricing. Coverage is provided via BICS wholesale connectivity. All business accounts complete KYC before production access.