Brand and catalogue.
Your colours, your labels, your plan set. Pin one destination or open the full catalogue.
Hosted checkout
Sell mobile phone plans inside your product.
Add a branded checkout for customer mobile plans. eSIM Copilot runs payment, eSIM delivery, reporting, and support behind the scenes, while the experience stays in your brand.
A
LiveAtlas 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.
What it runs
The checkout is only the visible part.
The embed gives customers a simple buying flow. Behind it, your team gets the controls required to sell, support, and report on mobile plans.
Checkout and payment.
Card, wallet, receipt, tax, and payment state handled by the hosted checkout.
eSIM delivery.
Provision the eSIM, deliver the install link, and keep the activation state visible.
Reports and usage.
Track orders, top-ups, countries, data usage, and revenue from the management console.
AI and human support.
Common install questions can be handled by AI, with humans ready when an account needs judgement.
Events when you need them.
Signed webhooks let your CRM, support desk, or warehouse stay in sync later.
How it embeds
Start with one entry point. Expand when the product proves it.
Hosted checkout keeps the first integration small. You can still move deeper with REST endpoints and webhooks later, without changing the underlying mobile platform.
Open from your button.
Use your existing CTA, destination card, account screen, or landing page module.
Show a plan picker.
Let customers compare bundles before the checkout opens.
Install through Google Tag Manager.
Add the script as a Custom HTML tag and fire it on the product, destination, or checkout pages you choose.
Trigger it in code.
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
Mobile plans, under control.
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
A customer checkout, plus the operating layer behind it.
You are not adding a checkout button and hoping for the best. 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
Mobile plans designed around your customers needs.
The checkout can be narrow and contextual, or broad enough to expose the full catalogue. The point is that it appears where the need already exists.
Travel product
Offer a phone plan beside flights, hotels, or destination guides.
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
Bundle mobile plans into a travel card, account perk, or paid tier.
A bank, insurer, loyalty programme, or member app can offer connectivity without becoming a carrier or building fulfilment logic.
Device or SaaS onboarding
Add mobile connectivity when a customer activates a device or team.
Use hosted checkout for the first product surface, then move to API and webhooks when mobile becomes core to the workflow.
Platform fit
Start with the embed. Keep the rest of the platform available.
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
Launch the first product surface.
One entry point, branded checkout, managed fulfilment.
Learn more
REST API
Build your own screens later.
Plans, orders, eSIMs, usage, and signed webhook events.
Learn more
Claude MCP
Let Claude operate the mobile layer.
Search plans, inspect usage, create orders, and guide support.
Learn more
Ready when you are
Put mobile plans in your product.
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
Common questions about embedded connectivity.
How long does the embed take to launch?
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.
Does it work in our existing app or CMS?
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.
What does the customer see after payment?
They receive the eSIM install link and confirmation in the branded flow. Your account records the order, payment state, eSIM state, and support context.
Can we control which plans appear?
Yes. You can scope the checkout to a single plan, destination, category, or a broader catalogue depending on the use case.
Is eSIM Copilot visible to customers?
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.
Related
Keep exploring the embedded mobile stack.
Useful next stops for embedding checkout, building deeper with APIs, connecting admin workflows, and pricing the rollout.