A branded checkout on your website or in your app. eSIM Copilot runs payment, eSIM delivery, reporting, and support behind the scenes; start hosted, build deeper with the API when you want.
Atlas Trips
atlas.trips/japan
Hosted checkout
Japan mobile plan
Customer: Mia Chen
10 GB / 30 days
Install link delivered after payment.
EUR8.50
Payment
eSIM
Receipt
Partner console
Order recorded. Usage and support visible.
One script
Add an entry point without building carrier logic.
Your checkout
Plans, payment, receipt, install link, and top-up.
Your console
Orders, usage, reports, support context, and events.
How you launch
Generate a hosted checkout, embed it in your website or mobile app — or integrate the API directly and build your own experience.
Quick start · no code
Start selling without building checkout or carrier logic:
> <script src="esimcopilot.js" />
> data-esimcopilot-open
Full control · API
Make every screen your own while we run the mobile layer underneath:
> POST /v1/orders
> webhook: esim.issued
Most partners launch with the quick-start tools and add the API where it matters. Same account, nothing to migrate.
What it runs
The embed gives customers a simple buying flow. Behind it, your team gets the controls required to sell, support, and report on mobile plans.
Your colours, your labels, your plan set. Pin one destination or open the full catalogue.
Card, wallet, receipt, tax, and payment state handled by the hosted checkout.
Provision the eSIM, deliver the install link, and keep the activation state visible.
Track orders, top-ups, countries, data usage, and revenue from the management console.
Common install questions can be handled by AI, with humans ready when an account needs judgement.
Signed webhooks let your CRM, support desk, or warehouse stay in sync later.
How it embeds
Hosted checkout keeps the first integration small. You can still move deeper with REST endpoints and webhooks later, without changing the underlying mobile platform.
Use your existing CTA, destination card, account screen, or landing page module.
Let customers compare bundles before the checkout opens.
Add the script as a Custom HTML tag and fire it on the product, destination, or checkout pages you choose.
Open checkout from a chat reply, account event, or logged-in product flow.
<script async src="https://js.esimcopilot.com/v1/esimcopilot.js"></script>Paste the script directly into your site or add it as a Google Tag Manager Custom HTML tag. Production settings live in your account and the embed docs.
Management console
Overview
1,248
Orders
195
Countries
600+
Networks
Order paid
Atlas Trips
EUR8.50
eSIM issued
Northline Bank
$18.00
Top-up added
Nomad Desk
EUR4.00
Behind the embed
Your team gets brand control, plan configuration, order history, usage visibility, reports, and support context from one account.
Choose the plans and destinations your customers should see.
Review orders, payments, usage, and support events.
Export reports or stream events through signed webhooks.
Where it fits
The checkout can be narrow and contextual, or broad enough to expose the full catalogue. It appears where the need already exists.
Travel product
A customer already planning a trip can add mobile connectivity in the same flow, with the plan filtered to the country they are reading about.
Fintech or membership
A bank, insurer, loyalty programme, or member app can offer connectivity without becoming a carrier or building fulfilment logic.
Device or SaaS onboarding
Use hosted checkout first, then move to API and webhooks when mobile becomes core to the workflow.
Platform fit
Hosted checkout is the fastest way to test demand, not a dead end. The same account can later use REST, webhooks, reports, and Claude.
Hosted checkout
One entry point, branded checkout, managed fulfilment.
Learn more
REST API
Plans, orders, eSIMs, usage, and signed webhook events.
Learn more
Claude MCP
Search plans, inspect usage, create orders, and guide support.
Learn more
Ready when you are
Tell us where the embed will live. We will help you shape the plan catalogue, brand treatment, management view, and support path before it goes live.
FAQ
A first branded checkout can be live quickly once the account, plan filters, and brand settings are configured. API and webhook work can be added later when the product needs deeper control.
Yes. The hosted checkout is loaded from a JavaScript embed and can be opened from your own button or product flow. It is designed for plain HTML, React, Vue, Svelte, Webflow, WordPress, and similar environments.
They receive the eSIM install link and confirmation in the branded flow. Your account records the order, payment state, eSIM state, and support context.
Yes. You can scope the checkout to a single plan, destination, category, or a broader catalogue depending on the use case.
That depends on the setup. The checkout can run as a fully branded experience, or you can keep eSIM Copilot visible as a trust signal where it helps.
Yes. The REST API returns plans, orders, eSIM state, and the LPA activation code, so you can build your own screens and a native install flow. Most teams launch with the hosted checkout first and move to the API where mobile becomes core.