White‑Label eSIM Platform: What You Get (Website, iOS/Android, Portals)

Launching an eSIM brand should be fast, predictable, and traveller‑friendly. Simology's white label eSIM platform gives you a complete stack: a branded website, native iOS and Android apps, and the operational portals your team needs to run day‑to‑day. You get the product catalogue, provisioning, payments, fraud tools, analytics, and support workflows out of the box—so you can focus on growth, not plumbing. Typical partners go live in weeks, not months.

This overview breaks down every module you receive, who does what during implementation, and the exact steps to launch. We also show how the traveller experience stays front‑and‑centre—from finding the right plan to one‑tap installation and instant connectivity. Where visuals help, you'll find annotated screenshots in the Simology Partner Hub. If you're comparing build vs buy, use the checklists and timelines below as a benchmark for scope, effort, and ownership.

What's included in the white label eSIM platform

1) Branded web storefront

A conversion‑ready site that sells global and regional eSIMs with best‑practice UX for travellers:

• Mobile‑first product pages, plan comparison, and checkout
• Region and country collections
• Device compatibility checks and guidance
• Currency, tax display, and multi‑language localisation
• Payment orchestration (cards, Apple Pay, Google Pay, local methods)
• Account area for order history, re‑downloads, invoices
• SEO structure and landing pages aligned to destinations

Content, branding, and domain are tailored to you. You manage pages and promotions from the Partner Admin Portal (details below).

2) Native iOS and Android apps

App‑store ready, with all traveller essentials:

• In‑app eSIM install using system frameworks (no QR code required on supported devices)
• Auto‑detect compatible devices; QR fallback for older models
• Real‑time status: installed/activated, data balance, expiry
• Data counters and top‑up flows
• Push notifications for install reminders, low data, and expiry
• Support entry points: chat, guided troubleshooting, help articles
• Secure account, biometric sign‑in, and purchase history

We ship you branded builds; you publish under your own Apple/Google developer accounts to retain your customer relationship and store analytics.

3) Operational portals (with screenshots in the Partner Hub)

Partner Admin Portal

• Catalogue: enable/disable countries and regions, set retail and promo pricing
• Merchandising: bundles, upsells, vouchers/coupons
• Content and localisation: copy blocks, FAQs, help articles
• Theming: logos, colours, typography
• Integrations: payment, analytics, SSO, webhook endpoints

Support Portal

• Search by email/order/ICCID; view eSIM state and history
• One‑click reissue, reshare activation details, or refund
• Network tools: APN, roaming status, attach/detach logs
• Customer notes, macros, and SLA timers

Finance & Reporting

• Revenue, margin, and cohort dashboards
• Tax breakdowns, invoicing exports, settlement files
• Chargeback tracking and fraud signals

Reseller/Agent Portal (optional)

• Sub‑accounts with role‑based access
• Commission structures and wallet balance
• Bulk codes and activation batches

4) Provisioning, APIs, and webhooks

• Order to eSIM fulfilment: allocate eUICCs, assign plans, deliver LPA links/activation codes
• Multi‑IMSI routing and network redundancy
• REST APIs for order creation, status, and refunds
• Webhooks for order paid, eSIM issued, installed, activated, data thresholds, and expiry
• SDKs for in‑app purchase and install flows

Traveller experience: designed to minimise friction

Your customers should be online in minutes, not hours. The default flow:

1. Discover a plan via search or region page; device check runs automatically
2. Pay with a familiar method; receive activation in‑app or via email
3. Install directly within the app (or scan a QR code); mobile data toggles are guided step‑by‑step
4. Land and connect. If needed, the app confirms roaming/APN settings with one tap
5. Manage usage, top up, and extend validity inside the app or website

For travellers hopping multiple countries, the app keeps the plan active and shows local tips and APN guidance.

Integration at a glance

You can launch with Simology defaults on day one, then extend. Typical touchpoints:

• Payments: Stripe/Adyen out of the box; add local methods as needed
• Identity: Email + OTP by default; optional SSO (OAuth/SAML)
• Analytics: GA4 and server‑side events; optional Segment, BigQuery exports
• Support: Native portal included; optional Zendesk/Freshdesk connectors
• Messaging: Email templates included; optional SendGrid/postmark; optional SMS for OTPs
• Tax: Display and calculations by region; export summaries for your accountant
• Webhooks: Plug into your ERP, BI, or marketing automation

Pro tip: Start with the vanilla stack to ship faster; integrate your preferred tools in sprint two.

Timelines and responsibilities

Most partners launch in 4–6 weeks. Here's a proven plan.

Week 0: Readiness checklist

• Brand assets (logo, colours, app icons)
• Company and support details (legal name, address, emails)
• Domain and DNS access
• Apple and Google developer accounts
• Payment PSP account (or use Simology's PSP to start)
• Initial catalogue selection (countries/regions and pricing)
• Privacy, terms, refund policy copy (templates provided)

Week 1–2: Brand, content, and catalogue

• Simology: Stand up staging storefront; load initial plans; enable destinations taxonomy
• Partner: Provide copy and translations; confirm pricing and promotions
• Joint: Review product pages for key markets

Week 2–3: Payments, analytics, and domain

• Simology: Configure PSP, GA4, and webhooks; set up tax display; connect support portal
• Partner: Verify PSP; connect domain and SSL; configure consent and cookie banners

Week 3–4: Apps build and QA

• Simology: Produce branded iOS/Android builds; run device install tests; pass test artefacts
• Partner: Publish to stores; validate purchase and install across target devices; localise store listings

Week 4–5: Launch and optimise

• Go live; monitor conversion and install success
• Introduce vouchers or welcome discounts
• Enable additional regions based on demand

Who does what

Simology

• Platform hosting, provisioning, updates, and monitoring
• Default integrations (payments, analytics, messaging)
• Portals, APIs, and dashboards
• Compliance templates and security controls

Partner

• Brand, domain, app store ownership
• Pricing strategy and promotions
• Customer service staffing and tone of voice
• Local tax registration and accounting

Joint

• QA, go‑live readiness, and post‑launch optimisation
• Roadmap: loyalty, resellers, and enterprise features

Operational controls and reliability

Inventory and routing

• eUICC pools with automatic allocation
• Multi‑IMSI and network failover where supported

Fraud and abuse

• Velocity checks, BIN and geolocation risk scores
• Device fingerprinting and disposable email filters

Compliance and privacy

• GDPR‑aligned data handling; role‑based access controls
• Data retention and export tools

Finance

• Settlements, tax summaries, and reconciliation exports
• Dispute workflows with evidence packs

Pro tip: Use webhooks for "installed" and "activated" events to trigger welcome emails with APN tips—this cuts support tickets by ~20%.

Merchandising the catalogue

Start focused; expand with data.

• Lead with your top 10 routes by audience
• Offer regional passes for multi‑country trips
• Create bundles (e.g. 15‑day pass with top‑up credit) to increase average order value
• Use the destinations structure for SEO and easy browsing
• Test price points and promotions; the portal shows conversion and refund impact

Pro tip: Add a pre‑trip email series (T‑7, T‑2, landing) with install reminders and local network tips; it boosts first‑try success and reduces roaming confusion.

Launch checklist (copy/paste)

• Domain connected and SSL green
• PSP payments live; test Apple Pay and Google Pay
• Top 20 destination pages reviewed (copy, images, FAQs)
• iOS/Android app published; install flow verified on two devices per OS
• Support macros written for install, APN, and top‑up
• Refund policy and help centre pages live
• Webhooks connected to your CRM/marketing tool
• Dashboard alerts set for conversion drop, failed installs, and chargebacks

Frequently asked questions

How long does it take to launch?

Most partners launch in 4–6 weeks. If you use Simology's default PSP and templates, a soft launch can happen in 2–3 weeks while apps are in review.

Can we customise everything to our brand?

Yes. You control logo, colours, typography, voice/tone, domain, and app store presence. Product names, pricing, and promotions are also fully configurable.

What devices are supported?

Any eSIM‑capable iPhone, iPad, and recent Android flagships. The storefront and apps auto‑detect compatibility and guide QR vs in‑app install accordingly.

Do we need our own payment processor?

You can go live on Simology's PSP setup initially, or connect your own Stripe/Adyen account for direct settlement. Apple Pay and Google Pay are supported.

How do we handle support?

Use the built‑in Support Portal with search, reissue, and refund tools. You can also connect to your helpdesk. Macros and guides are preloaded for common issues.

What about taxes and invoices?

The Finance portal provides tax breakdowns and exports. You remain the merchant of record and handle filings in your jurisdictions; templates are provided to streamline.

Pro tips from successful partners

• Keep the homepage simple: three featured regions, one traveller proof point, one CTA
• Default to in‑app install messaging; QR codes are your fallback, not the hero
• Add low‑data alerts at 80% usage; enable one‑tap top‑ups to protect NPS
• Localise help articles per top destination (APN names, roaming toggles, common devices)
• Use vouchers for first‑time buyers rather than site‑wide discounts to protect margin
• Review "install failed" logs weekly; small tweaks to copy or timing can lift completion rates

Integration summary

• Mandatory to launch: Brand assets, domain, PSP (or Simology PSP), app store accounts
• Strongly recommended: GA4, webhooks to your CRM, email sender
• Optional: SSO, BI exports, Zendesk/Freshdesk connectors, reseller portal

Next step: Explore features, see portal screenshots, and request access in the Partner Hub. If you're assessing suitability for your organisation, start with For Business and map the catalogue via destinations.