Private APN & Enterprise Security: When and Why to Use It

30 Oct 2025

Mobile data isn’t just “internet in your pocket.” For enterprises with roaming staff, payment terminals, or IoT fleets, the path your traffic takes is a security control. A private APN creates a closed data path from SIMs to your network, letting you enforce policy, isolate traffic from the public internet, and integrate cleanly with VPNs or zero-trust tools. This guide explains what private APNs are, when to use them, how they work with VPNs, typical use cases, what they cost, and how to deploy successfully—without jargon.

If your teams travel, the stakes go up: roaming adds new networks, new attack surfaces, and variable policies. A well-designed private APN keeps device traffic predictable and governable across borders. Whether you’re connecting laptops via eSIM, securing field equipment across Esim Western Europe, or building a partner-ready solution via our Partner Hub, the right APN choice determines how easily you can meet audit, compliance, and uptime targets.

Use this as a practical checklist to decide if a private APN fits—and how to keep costs and complexity under control.

What is a Private APN?

A private APN (Access Point Name) is a carrier-side configuration that defines how SIM traffic is handled. Rather than breaking out to the public internet using NAT on a generic, shared APN, a private APN:

Identifies your SIMs into a dedicated routing context
Assigns private/static IP ranges if required
Applies custom firewall, DNS and content policies
Delivers traffic to you over a defined path (e.g., IPsec/GRE to your DC/cloud)

Think of it as “your own lane” inside the mobile core, with enterprise-grade traffic isolation and policy controls.

Key benefits

Traffic isolation: Your devices don’t share a public NAT pool with everyone else.
Predictable addressing: Private or static IPs allow IP allowlisting and system-to-system integrations.
Policy enforcement: Apply DNS filtering, firewall rules, and segmentation per SIM group.
Controlled breakout: Choose where traffic exits—your data centre, cloud VPC, or a regional gateway.

Common variants

Private APN with public breakout: Policy and IP control, but final internet egress is via carrier NAT.
Private APN with private breakout: End-to-end private path to your network over IPsec/GRE/MPLS; no public internet until you decide.
Roaming home routing vs local breakout: Decide whether traffic tunnels back to a home gateway or breaks out regionally for latency/compliance.

When should you use a Private APN?

Choose a private APN when one or more of these apply:

You must IP-allowlist mobile devices to access corporate apps, SCADA, or payment backends.
You need to block open internet access by default, allowing only approved destinations.
You require consistent, auditable logs of device egress and DNS activity.
You deploy IoT/OT fleets where devices are headless and should never be internet-reachable.
You need static or reserved IPs per SIM for device-to-cloud rules or legacy systems.
You’re operating in higher-risk or compliance-heavy sectors (finance, health, critical infrastructure).

Travel scenarios where it shines:

Regional workforces moving between the US, Canada and Mexico using Esim North America
Teams rotating across France, Italy and Spain with Esim France, Esim Italy and Esim Spain
Short-term projects needing fast onboarding in the US via Esim United States

Check your target countries and carriers via Destinations.

Private APN vs VPN vs Zero Trust

These are complementary, not either/or.

Private APN: Carrier-layer isolation and policy. Ensures trusted device identity (SIM/IMSI), private addressing, and controlled gateways.
VPN (IPsec/GRE/SSL): Secure tunnel from APN gateway to your network or cloud VPC. Use to terminate traffic into your security stack.
Zero Trust/SASE: Identity-driven access per user/device/app. Often layered on top (device certificate, posture checks) for user devices.

Recommended patterns

Corporate laptops/phones on the road
Private APN + clientless approach: Route all traffic via your gateway where CASB/SWG runs.
Or Private APN + device VPN: Enforce split tunnel for corporate apps; APN blocks all other internet.
IoT/OT equipment
Private APN with private breakout to your VPC/DC; no public internet access.
Partners/contractors
Private APN with segmented SIM groups and per-segment firewall policies; issue time-bound SIMs.

Pro tips: - Avoid double encryption where unnecessary. If APN-to-cloud IPsec is in place and devices only talk to your internal services, you may not need device-level VPN. - Use device certificates via MDM/EMM for user hardware. The APN identifies the SIM; your MDM identifies the device.

Security controls you actually get

Identity and segmentation
SIM/IMSI-based policies and groups
Optional IMEI binding for device lock
Addressing
Private RFC1918 subnets, with optional static IPs per SIM
CGNAT or 1:1 NAT as needed
Firewalling
Default deny; allow only required FQDNs/IPs/ports
Geo or ASN-based controls for sensitive backends
DNS
Force safe resolvers; block DNS-over-HTTPS egress
Use internal resolver via tunnel for split-horizon domains
Logging and SIEM
Per-SIM flow logs and DNS logs exported to your SIEM
DDoS posture
With private breakout, you decide internet egress; with public breakout, leverage carrier scrubbing

Roaming and travel: what to plan for

Latency vs control
Home routing centralises control but adds RTT from, say, Tokyo to a London gateway.
Regional breakout (e.g., EU vs US gateways) reduces latency for users on Esim Western Europe or Esim North America.
Regulatory constraints
Some countries restrict VPN or enforce local breakout. Match your APN design to the route permitted in the destination. Confirm on Destinations.
IP allowlists and roaming IPs
If you rely on static source IPs, avoid scenarios where roaming uses dynamic CGNAT or changes egress country by country. Private breakout fixes this by presenting consistent IP space.
Device onboarding during travel
eSIM QR provisioning helps. Pre-stage profiles for each region (e.g., Esim France for an EU tour, Esim United States for US trips).

Cost model: what you’ll actually pay

Expect costs in these buckets:

One-off setup
APN configuration, IP ranges, SIM group policies, initial tunnel(s)
Monthly platform fee
Covers APN gateway capacity, monitoring, and management
Per-SIM charge
Often tiered; sometimes includes static IP options
Data usage
Pooled or per-SIM; roaming may have regional rates
Tunnels and hosting
IPsec/GRE tunnel endpoints in your DC/VPC; cloud egress costs may apply
Change management/professional services
Policy updates, incident support, new region gateways

Ways to optimise: - Start with a private APN + public breakout for policy control; add private breakout later for critical apps. - Use regional gateways to avoid transatlantic hairpin data charges for travellers. - Reserve static IPs only for systems that truly need allowlists; use dynamic private IPs elsewhere. - Monitor top talkers; block chatty apps at APN firewall instead of paying for unnecessary data.

Quick decision checklist: do you need a private APN?

Tick “yes” if the statement is true:

We must restrict mobile devices from open internet by default.
We rely on IP allowlists for any critical app or third-party API.
We need device fleet observability (per-SIM traffic and DNS logs).
We operate IoT or unattended devices that should never be publicly reachable.
We have travellers across multiple regions and require consistent egress policies.
We must meet compliance or audit requirements for network segregation.

Three or more “yes” answers usually justify a private APN.

Implementation: step-by-step

1) Define scope and risk - List device types (laptops, phones, IoT), users, and data sensitivity. - Map apps/domains/ports that must be reachable. - Decide “deny-by-default” vs “allow-by-default”.

2) Choose coverage and form factor - Confirm countries and networks via Destinations. - Select regional plans (e.g., Esim North America or Esim Western Europe) and country add-ons (Esim Italy, Esim Spain).

3) Addressing and segmentation - Allocate private subnets per SIM group (e.g., staff vs IoT). - Decide where static IPs are required.

4) Breakout architecture - Start with private APN + public breakout if you only need policy/DNS controls. - For maximum control, deploy private breakout to your DC/cloud via IPsec/GRE. - If latency matters for travellers, request EU and US gateways.

5) Security policy and DNS - Set default deny; allow only business apps/domains. - Enforce DNS to your resolvers; block DoH/DoT egress except approved endpoints. - Add geo/ASN blocks for risky destinations if relevant.

6) Integrate identity and device posture - Bind SIMs to users via MDM/EMM; consider IMEI binding for corporate-owned devices. - For user devices, layer device certificates or ZTNA for application-level control.

7) Build and test tunnels - Establish redundant tunnels; validate failover. - Test roaming from target countries (US/EU) for latency and policy correctness.

8) Logging, monitoring, and alerts - Export flow and DNS logs to SIEM. - Create alerts for policy violations and unusual data volumes.

9) Pilot and scale - Pilot with 10–50 users/devices across two regions. - Iterate rules, then scale to full fleet.

Pro tips: - Test common collaboration apps (Teams/Zoom) for split vs full tunnel to avoid performance complaints. - Document emergency bypass processes for critical field operations.

Common pitfalls (and how to avoid them)

IP allowlists failing during roaming
Use private breakout with consistent source IPs; avoid reliance on roaming CGNAT ranges.
DNS leaks
Force DNS to your resolver; block outbound UDP/TCP 53/853 except to approved IPs; manage DoH with SNI filtering.
Overly broad “allow” rules
Prefer FQDN and minimal port ranges; segment by SIM group.
Latency surprises
Place gateways regionally; verify RTT from your top travel corridors.
Tunnel single points of failure
Always build at least two tunnels to independent endpoints.

Who is this for?

Enterprises securing roaming staff devices with eSIM
Payments, logistics, and field services managing unattended endpoints
MSPs/ISVs embedding connectivity into their solutions via our Partner Hub
Organisations looking for turnkey policies and global eSIM bundles via For Business

FAQ

Q1: What is the main difference between a public and a private APN?
A private APN creates an isolated routing context for your SIMs with custom policies and addressing. Public APNs use shared NAT to the internet with limited control and no dedicated security posture.

Q2: Do I still need a VPN if I use a private APN?
Often yes, but it depends. For IoT or tightly controlled fleets, APN-to-cloud IPsec may be sufficient without device VPN. For user devices, a device VPN or ZTNA provides identity and app-level control on top of the APN.

Q3: Can I get static IPs for my SIMs?
Yes. Private APNs can assign static or reserved private IPs per SIM, which is ideal for IP allowlisting and legacy integrations. Public static IPs are possible but less common; many use private breakout and egress via corporate firewalls.

Q4: Will a private APN work while roaming internationally?
Yes. Design for either home routing (all traffic returns to your gateway) or regional breakout (e.g., EU/US). This affects latency and compliance—verify coverage per country on Destinations.

Q5: How much does a private APN cost?
Expect a setup fee, a monthly APN platform charge, per-SIM pricing (optionally for static IPs), data usage, and tunnel/cloud costs. You can start small with policy-only public breakout, then add private breakout and regional gateways as needs grow.

Q6: Does this support eSIM and multi-region bundles?
Yes. Private APN policies apply to both physical SIMs and eSIMs. For travellers, pair your APN with regional plans like Esim Western Europe or Esim North America and country-specific options such as Esim France or Esim United States.

Next step

Design the right private APN for your fleet and travel patterns. Speak to our enterprise team via For Business to scope coverage, security policies, and rollout.

Read more blogs

EU Long Stays: Fair‑Use for Nomads & Students (90/180‑Day Rule)

Planning a long stretch around Europe? Here’s the traveller‑first guide to EU fair use on long stays. Confusion often comes from mixing two different systems: immigration rules (the Schengen 90/180‑day stay limit) and telecom rules (EU roaming fair use). They are not the same. Immigration limits how long you can stay. Telecom fair use limits how long you can roam on an EU plan before surcharges kick in. If you’re a student with local residency, you’re treated differently to a roaming nomad bouncing between countries. And regional eSIMs add a third option that avoids most “home vs abroad” checks altogether. This guide cuts through the jargon with plain‑English explanations, examples you can copy, and practical checklists to keep your connectivity clean and cost‑predictable. If you just want a solution: country eSIMs are best when you settle in one place; regional EU eSIMs shine for multi‑country hops. Keep reading for the details and how to choose.The quick version: Fair‑use vs 90/18090/180 rule: Immigration. Most visa‑exempt visitors can stay in the Schengen Area up to 90 days in any 180‑day period. Nothing to do with mobile plans.EU roaming fair use: Telecom. EU/EEA operators let their customers “roam like at home” across the EU. To stop permanent roaming, they can apply fair‑use checks over a four‑month window and, if triggered, add regulated surcharges after warning you.Regional travel eSIMs: These are made for roaming. They don’t rely on EU “roam like at home” privileges, so the home‑vs‑abroad test usually doesn’t apply. Instead, your limit is the plan’s validity and data allowance.For country coverage quirks (e.g., Switzerland, UK post‑Brexit), see Destinations.What the EU fair‑use policy actually says (for travellers)EU “Roam Like at Home” (RLAH) protects EU/EEA subscribers using their home mobile plan around the bloc. It applies primarily if you hold an EU plan with an EU operator.The home‑presence and usage test (4‑month window)Your EU operator can watch usage over at least four months. If both are true, they may flag permanent roaming:1) You’ve been more time “abroad” than “at home,” and2) You used more data while roaming than you did at home.If they detect this, they must warn you and give at least 14 days to change your pattern (e.g., use the line domestically or reduce roaming). If nothing changes, they can add small, regulated surcharges on roaming usage. Your service isn’t cut off, but costs rise.Data caps on “unlimited” plans while roamingIf your domestic plan is unlimited or very cheap per GB, your operator can set a specific fair‑use roaming data allowance, calculated from your plan price and EU wholesale caps. The allowance and any out‑of‑bundle surcharge must be clearly communicated. Always read the roaming section of your tariff.Residency or “stable links”Operators can ask for proof of residency or stable links (study, work) when you buy or keep a domestic plan. This isn’t immigration control; it’s to ensure domestic plans aren’t used as permanent roaming products.Warnings and surchargesYou’ll receive a warning before any fair‑use surcharge applies.Surcharges are capped by EU rules and reviewed periodically.Paying a surcharge doesn’t fix the root cause. If your lifestyle is long‑term roaming, reconsider your setup (see below).Note: RLAH covers EU/EEA. It does not automatically include Switzerland or the UK. Check Destinations before you go.Residency vs roaming: which bucket are you in?Students with a local contract (resident or stable link)If you study in, say, France and sign up for a French mobile plan using local documentation, France becomes your “home” for that line. Your everyday use in France typically outweighs your time abroad, so your weekend trips to Spain or a fortnight in Italy sit comfortably within fair use. For deeper country fit, see Esim France, Esim Spain and Esim Italy.Digital nomads and long‑stay visitors (non‑resident)If you don’t have EU residency and you rely on a single EU domestic SIM while rarely returning to its home country, you’re likely to trip the fair‑use test after a few months. Two cleaner options:Use country eSIMs in each country you stay in for a month or two; orUse a regional travel eSIM designed for roaming around Europe.How regional eSIMs fit into long staysRegional travel eSIMs are built for cross‑border use. Instead of offering a domestic plan with RLAH, they provide roaming access in multiple countries from day one. This sidesteps the “domestic vs roaming” test entirely.Multi‑country coverage: A single profile that works across much of the EU. See Esim Western Europe for a practical one‑SIM solve when you’re rotating through EU hubs.Validity and data: Plans come with defined validity (e.g., 15–90 days) and data buckets. If you run out, top up or add another plan—no residency checks.Outside the EU: Heading to or from North America? Pair your Europe plan with Esim North America or set up before you fly with Esim United States.When you’re staying a whole term in one country, a local eSIM can be cheaper for heavy data. For multi‑country months, regional usually wins on simplicity.When to choose a country eSIM vs a regional EU eSIMChoose a country eSIM when:You’ll spend 30+ days in one country and use lots of data.You need local rates for domestic calls or long‑term top‑ups.Example pages: Esim France, Esim Italy, Esim Spain.Choose a regional EU eSIM when:You’ll cross borders frequently (e.g., 3–6 countries over 2–4 months).You prefer one number/data plan to manage across the trip.See: Esim Western Europe.Use dual‑SIM: keep your primary line for authentication calls/SMS, and set the travel eSIM as your data line.Step‑by‑step: Students (semester or year abroad)1) Get a local plan in your host country- Sign up with local ID/student proof. Your host country becomes “home” for that plan.2) Read the roaming section of your tariff- Note any roaming data caps and the four‑month fair‑use window.3) Use your host‑country SIM domestically most of the time- Weekend trips are fine. Long multi‑month trips outside your host country might trigger warnings.4) Add a regional eSIM for holiday stretches- If you’ll travel for several weeks, switch your data line to Esim Western Europe to avoid breaching your domestic plan’s fair‑use pattern.5) Keep alerts on- Don’t ignore SMS warnings. You usually get at least 14 days to adjust your usage before surcharges apply.6) Check non‑EU neighbours- UK/Switzerland often sit outside inclusive roaming. Verify on Destinations before you go.Step‑by‑step: Digital nomads (90–180 days across EU)1) Decide your pattern- Many short stays in multiple countries? Start with a regional plan. One or two long stops? Mix in country eSIMs for each stop.2) Set up before you move- Install the eSIM profile while you have reliable Wi‑Fi. Test with a small top‑up.3) Use dual‑SIM smartly- Keep your home SIM active for 2FA/texts. Set the travel eSIM as the default for data.4) Rotate plans, not penalties- Regional eSIMs like Esim Western Europe are priced for roaming and won’t run into EU “permanent roaming” tests. When staying put, switch to the local country plan (e.g., Esim Spain).5) Avoid long‑term reliance on a single EU domestic plan- If you don’t live there, the four‑month fair‑use pattern will likely catch up and add surcharges.6) Leaving or arriving via the US/Canada?- Bridge the gap with Esim North America or sort stateside coverage with Esim United States.Worked examplesStudent in France, 9 months, frequent tripsYou take a French plan as your main line. You spend most days in France, with occasional weekends in Spain/Italy. You remain well within fair use. For a four‑week summer rail trip, you add Esim Western Europe for data and keep the French SIM for calls/SMS.Nomad, 5 months, 5 countriesMonth in Portugal, then Spain, France, Belgium, Netherlands. You use a regional plan for months 1–3. For months 4–5, because you’re stationary and need more data, you add Esim Spain and Esim France during those longer stays. No EU domestic fair‑use checks apply to your regional eSIM; the country eSIMs are priced for local use when you’re settled.US visitor, 2 months in Italy with side tripsYou keep your US number active for banking but avoid pricey long‑term roaming on your domestic US plan. You install Esim Italy for the base month and add a short regional top‑up for a two‑week loop through neighbouring countries.Pro tips to stay compliant and connectedTrack days and data: set a calendar reminder every time you cross a border and use your phone’s data counter per SIM.Respect SMS warnings: they are your early‑warning system before surcharges.Prefer Wi‑Fi calling and messaging apps for cross‑border calls.Use hotspot sparingly if your plan restricts tethering.Check country exceptions on Destinations before visiting microstates or non‑EU neighbours.Business travellers: corporate pools can smooth roaming costs—see For Business or partner with us via the Partner Hub.FAQQ1: Does the Schengen 90/180‑day rule limit my mobile usage?A: No. 90/180 is immigration. EU telecom fair use is separate. You could be within your visa limit yet still trigger a roaming fair‑use surcharge—or vice versa.Q2: How long can I roam on an EU domestic plan before fair‑use kicks in?A: Operators check at least a four‑month window. If, in that period, you spend more time and use more data abroad than at home, they can warn you and later add regulated surcharges.Q3: I have an “unlimited” EU plan. Is roaming unlimited too?A: Not necessarily. Operators can set a specific fair‑use roaming data cap for unlimited/low‑cost plans and must tell you the allowance and any surcharge once you hit it.Q4: Do regional travel eSIMs have fair‑use limits?A: They’re built for roaming, so the EU “home vs abroad” test doesn’t apply. You’re bound by the plan’s validity and data bucket, plus any reasonable‑use terms (e.g., hotspot limits). For multi‑country trips, see Esim Western Europe.Q5: If I buy a French SIM, can I spend the summer in Italy on it?A: Yes, but extended, heavier use outside France could trigger the four‑month fair‑use test. For a long Italy stay, switch to Esim Italy or add a regional eSIM for the travel leg.Q6: I’m a US traveller. Should I rely on my US plan’s roaming?A: For short trips, maybe. For long stays, many US plans throttle or cap roaming after a few weeks. It’s usually better value to keep your US number for SMS and run EU data on a regional or country eSIM. Start here: Esim United States and Esim Western Europe.Next stepPlan your route, pick your coverage: explore country and regional options on Esim Western Europe, then check country specifics via Destinations.

23 Dec 2025

Dual SIM with eSIM: Two Numbers on One Phone (Calls, OTPs, Data)

Staying reachable without burning money on roaming is the modern traveller’s headache. Dual SIM with eSIM solves it: keep your main number active for calls and OTPs, and add a low-cost local or regional data plan on the same phone. No SIM swapping. No missed texts from your bank. In this guide, we explain how dual SIM with eSIM works, how calls/SMS/data behave, and how to set it up on iPhone and Android. We also cover common use cases like work/personal separation and travel/local pairing, plus how WhatsApp and other apps handle two numbers. If you’re planning a trip, browse country and regional options via Destinations or pick ready-made bundles such as Esim Western Europe or Esim North America. For the US or single-country trips, see Esim United States, Esim France, Esim Italy and Esim Spain.What is dual SIM with eSIM?Dual SIM means your phone can maintain two mobile lines at once. One or both can be eSIMs (digital SIM profiles). Typical setups: - Physical SIM + eSIM active together. - Two eSIMs active (on many newer devices). - Multiple eSIM profiles stored, with up to two active at a time (device-dependent).On dual SIM dual standby (DSDS) phones, both lines are “on” for calls and texts when idle. You set a default line for data, calls and messages, and you can switch defaults at any time.Device support varies. Recent iPhones and most mid/high-end Android phones support dual SIM with eSIM, but some models allow only one eSIM active at a time or restrict 5G/VoLTE on the secondary line. Check your device’s specs before you travel.Why use dual SIM eSIM? Practical use casesWork and personal separationKeep your personal number private while making and receiving work calls on a second line.Set the default for outgoing calls to your work line during office hours and flip it back to personal later.Mute one line at set times to reduce interruptions without missing urgent personal calls.Travel: keep your home number for OTPs, add local dataKeep your home SIM active for banking OTPs, two-factor codes and critical calls.Add a local or regional eSIM for affordable 4G/5G data and local rates.Disable data roaming on your home line to avoid bill shock; use the travel eSIM for all data.Pick country plans like Esim United States, Esim France, Esim Italy or Esim Spain, or choose a multi-country pass such as Esim Western Europe or Esim North America. Explore more via Destinations.Coverage and cost optimisationUse the line with stronger coverage for data in fringe areas.Keep a cheap voice/SMS plan on one line and a high-data plan on the other.Switch defaults on the fly when you cross borders or move between networks.Teams, events and short-term projectsProvision temporary eSIM lines for contractors, events or field staff without shipping plastic SIMs.Centrally manage usage and budgets; see For Business.Partners and resellers can streamline deployments via the Partner Hub.How calls, SMS, data, OTPs and apps behaveUnderstanding how two lines interact avoids surprises.Calls in standby: Both lines can receive calls when idle. When you place or receive a call on one line, the other may go to voicemail or show as unreachable unless your device/network supports features like call waiting across lines or Wi‑Fi Calling. Behaviour varies by carrier and phone.Default for voice/SMS: You choose a default line for outgoing calls and texts, but you can select the other line per contact or per call.Mobile data: Only one line provides mobile data at a time. You set this in settings. Some phones support “allow mobile data switching”, automatically using the other line if the selected data line has weak signal.SMS-based OTPs: OTP texts arrive on the line tied to that number as long as that line is enabled and has signal. Data does not need to be enabled on that line. If you’re abroad, receiving OTPs may incur roaming SMS charges on your home line—turn off data roaming but keep SMS/calls enabled to control costs.iMessage/FaceTime (iPhone): You can enable iMessage/FaceTime for one or both numbers and choose which to use by default.WhatsApp and similar apps:The standard WhatsApp app supports one number per device. Data can come from either line.To run two WhatsApp accounts on one phone, use WhatsApp + WhatsApp Business (iOS/Android) or OEM dual-app features (on some Android devices).Your WhatsApp number does not change just because your data comes from your travel eSIM.Set-up: dual SIM with eSIMiPhone step-by-stepObtain your eSIM details: QR code or activation code from your provider.On iPhone, go to Settings > Mobile Data > Add eSIM (or “Add Data Plan”).Scan the QR code or enter details. Wait for activation.Label your lines (e.g., “Personal” and “Travel”). Clear labels prevent mistakes.Choose defaults: - Default Line for Calls and SMS. - iMessage & FaceTime line. - Mobile Data line (set to your travel/local eSIM when abroad).Toggle “Data Roaming”: - Turn off for your home line while travelling. - Turn on for your travel eSIM, if required.Optional: Enable “Allow Mobile Data Switching” if you want automatic fallback.Test: Place a call from each line, send yourself an SMS from another phone, and load a webpage to confirm the data line.Pro tips for iPhone: - You can store multiple eSIMs and swap which are active. Many newer iPhones support two active eSIMs. - Backups don’t include eSIMs. Keep your activation details safe; some carriers limit re-downloads. - For Wi‑Fi Calling, enable it separately per line (Settings > Phone > Wi‑Fi Calling).Android step-by-step (Pixel/Samsung and similar)Get your eSIM QR/activation details from your provider.Open Settings > Network & Internet (or Connections) > SIMs > Add eSIM.Scan the QR code or enter details. Wait for activation.Name each SIM (e.g., “Work” and “Data”).Set preferences: - Preferred SIM for Calls. - Preferred SIM for SMS. - Preferred SIM for Mobile Data (set to the travel/local eSIM).Roaming: - Disable data roaming on your home line. - Enable on your travel eSIM if needed.Optional: Enable “Switch data automatically” or similar to allow fallback.Test calls, SMS, and data on both lines.Pro tips for Android: - Some phones let you duplicate apps (Dual Messenger/App Twin) to run two WhatsApp accounts. Alternatively, use WhatsApp + WhatsApp Business. - Not all Android models support two eSIMs active simultaneously. If yours doesn’t, use one physical SIM + one eSIM, or swap active eSIM profiles as needed. - VoLTE/5G availability can differ per SIM slot/line; check your device and carriers.Travel checklist: avoid bill shock and stay reachableBefore you fly: - Install and activate your travel eSIM over Wi‑Fi at home. - Label lines clearly and set the travel eSIM as the Mobile Data line. - Turn off Data Roaming on your home line; leave Calls and SMS on if you need OTPs. - Enable Wi‑Fi Calling for your home line if supported, to improve reachability without roaming data. - Check voicemail and call forwarding settings for both lines. - Tell your bank you’re travelling; ensure OTPs can arrive via SMS or app. - Save carrier support contacts and your eSIM activation details offline.On arrival: - Confirm the travel eSIM connects and data works. - Place a brief test call from each line and send a test SMS. - Keep an eye on status bar icons to ensure you’re not accidentally using data on the home line.Pro tips and common gotchasKeep eSIM credentials safe: Many providers allow limited re-installs. Don’t delete an active eSIM while abroad unless you’re certain you can re-download it.One data line at a time: Even with two active lines, only one provides mobile data. Choose carefully for maps, ride-hailing and tethering.Call collisions: During a call on one line, the other may be unreachable on some networks. If that’s critical, enable Wi‑Fi Calling and test how your phone behaves.Battery impact: Two active lines can use more battery. Mitigate by disabling 5G on the non-data line, reducing background activity, and using Wi‑Fi where possible.Apps tied to a number: Services like WhatsApp, Signal and Telegram can be re-registered to another number, but you may lose message history or access. Decide which number you want long-term before switching.Region-savvy plans: Multi-country eSIMs like Esim Western Europe simplify border crossings; US/Canada/Mexico travellers can look at Esim North America. Compare options by country on Destinations.Regional picks for travellersCity breaks or rail trips across multiple EU countries: Choose Esim Western Europe to avoid juggling separate plans.US road trip or conferences: Use Esim United States for nationwide coverage; combine with your home line for OTPs.Canada/US/Mexico multi-stop: Try Esim North America for cross-border continuity.Single-country travel: See Esim France, Esim Italy and Esim Spain for local choices, or browse the full list via Destinations.Business travel at scale: Central provisioning, spend control and support via For Business; partners can onboard faster with the Partner Hub.FAQsCan I use both numbers at the same time?Yes, both lines are on standby for calls and texts. Only one line provides mobile data at a time. If you’re on a call on one line, the other may be temporarily unreachable depending on device/network features.Will OTP texts arrive while my data is on the other eSIM?Yes. OTPs arrive on the line associated with that number as long as that line is enabled and has signal. Data does not need to be on for SMS. Roaming SMS fees may apply if you’re abroad on your home line.Can I use WhatsApp with two numbers on one phone?The standard app supports one number. To run two accounts, use WhatsApp + WhatsApp Business (works on iOS and Android) or an OEM dual-app feature on some Android phones. Your data can come from either line regardless of the WhatsApp number.How do I avoid roaming charges on my home SIM?Turn off Data Roaming for the home line. Keep Calls and SMS on if you need to receive OTPs or critical calls. Set your travel eSIM as the Mobile Data line. Consider Wi‑Fi Calling to improve reachability without data roaming.Does dual SIM affect battery life?Slightly, because the phone maintains two network registrations. Reduce impact by disabling 5G on the non-data line, using Wi‑Fi, and turning off the secondary line when not needed.What if my phone supports only one eSIM active at a time?Use one physical SIM plus one eSIM, or store multiple eSIM profiles and switch which is active as required. Check your device manual for limits on active lines and 5G support.Next step: Plan your trip and pick the right travel eSIM by browsing Destinations.

30 Oct 2025

Billing & Finance Ops: VAT Invoices, Multi‑Currency, and Refund Flows

Getting eSIM billing right isn’t just about taking payments—it’s about trust, compliance, and clarity for travellers and partners at scale. This guide covers the practical building blocks of esim vat invoicing multi currency operations: how to handle VAT/Sales Tax by region, present FX cleanly, calculate pro‑rations fairly, and run refund, chargeback, and dunning flows that reduce friction. Whether you’re a marketplace, reseller, MNO/MVNO, or travel brand, the goal is the same: ship fast, stay compliant, and keep customer effort low. We’ll walk through usable checklists and decision points, and point to where Simology supports your commerce stack—across destinations like Esim Western Europe, Esim North America, and single‑country packs such as Esim United States, Esim France, Esim Italy, and Esim Spain. For partnership options and operational tooling, see For Business and our Partner Hub.Why billing precision matters for eSIM at scaleTax compliance varies by region and buyer type. Poor handling risks fines or blocked payouts.Travellers expect local currency clarity and transparent FX—especially when buying on the move.Pro‑rations and top‑ups must feel fair; opaque maths is a refund magnet.A clear refund and chargeback playbook minimises losses and disputes.Strong dunning keeps B2B/wholesale cashflow healthy without harming relationships.VAT invoicing essentials for eSIM providers and partnersIdentify tax nexus by regionEU/UK: B2C digital services are typically VATable where the customer is located; B2B may use reverse charge if a valid VAT number is provided.US/Canada: Sales tax/GST/HST/PST rules vary by state/province and product classification; marketplace vs. seller of record impacts liability.APAC/ROW: Several countries operate VAT/GST on digital services to local consumers. Thresholds and registration rules differ.Note: Always validate assumptions with your finance team and align seller‑of‑record responsibilities in partner contracts.Data you must capture on a VAT‑compliant invoiceSeller legal name, address, and tax registration (e.g., VAT ID).Buyer details; collect VAT number for B2B where applicable.Unique invoice number, issue date, supply date (if different).Line items: product name (e.g., “eSIM 5 GB – France”), quantity, unit price, discounts.Tax rate and amount per line, and total tax.Currency of account and any FX conversion basis.Notes: reverse charge wording (when applicable), credit note references for refunds.Step‑by‑step: Configure VAT and invoice rulesDefine seller‑of‑record per market and channel (direct vs. reseller).Configure tax determination: by billing address, IP/geo, payment BIN, or combined evidence.Set B2B logic: VAT number capture, real‑time validation, and reverse charge handling.Attach tax codes to catalogue SKUs by region (e.g., EU digital service vs. US telecom).Generate VAT invoices on payment capture; issue credit notes on refunds.Store signed PDFs plus machine‑readable data (e.g., CSV/JSON) for audit.Provide travellers with self‑serve invoice downloads via order history.Pro tip: When selling cross‑border packs like Esim Western Europe, ensure your SKU structure supports per‑buyer tax determination even if the product spans multiple countries.Multi‑currency pricing and FX display that customers trustDisplay vs settlement currencyDisplay currency: what the shopper sees at checkout (e.g., EUR, GBP, USD, CAD).Settlement currency: what your gateway pays out in (often USD or EUR).Show the display currency by user location or browser currency, but disclose when settlement occurs in a different currency.Pro tip: Present a single total in the shopper’s local currency with tax included for B2C. For B2B, show net, tax, and gross with the buyer’s VAT status clearly flagged.Rounding, fees, and rate sourcesUse a consistent FX source (e.g., daily mid‑market rate plus a disclosed margin).Round prices to local conventions (e.g., .99, or 0.05 increments where applicable).Clearly disclose any FX mark‑up and that the card issuer may apply additional conversion fees.Step‑by‑step: Implement multi‑currency in your checkoutDetect preferred currency from locale and BIN, allow manual override.Convert base prices using your rate source and cache rates for the day.Compute taxes in the display currency; track base currency equivalents for accounting.Apply rounding rules per currency; store pre‑ and post‑round values.Show a plain‑English FX note (e.g., “Billed in USD; amounts shown in EUR for your reference” where relevant).Reconcile settlements: map PSP payouts in the settlement currency back to order‑level FX snapshots.Pro tip: Keep the FX snapshot (rate ID, timestamp, margin) on each order to simplify refunds and audits.Pro‑rations, expiries, and top‑upsCommon scenarios and calculationsMid‑cycle upgrade to a larger data pack: charge a pro‑rated difference based on remaining days or unused data value.Early cancellation (goodwill): offer a pro‑rated credit note based on unused data/validity.Auto‑renewal cancellations before renewal date: no proration; ensure clean cancellation messaging.Top‑ups: treat as separate SKUs with their own tax rules; avoid recalculating tax on the original order.Two pro‑ration models - Time‑based: Value remaining = price × (days remaining ÷ total days). - Usage‑based: Value remaining = price × (unused data ÷ total data).Pro tip: Pick one model per product family and document it in the checkout and invoice notes to avoid disputes.Refund and chargeback flows that reduce frictionRefund policy matrixTechnical failure (e.g., profile never delivered/activated): full refund.Partial usage but network issues verified: partial refund or goodwill credit.Buyer error (wrong device/region) with no usage: one‑time goodwill refund to reduce chargeback risk.Fraud or card testing: block and no refund; share device/usage fingerprints with your PSP.Always issue a credit note matching the original tax treatment and currency.Step‑by‑step: Process a refundVerify eligibility: review activation logs, usage, and support notes.Select type: full, partial (amount or percentage), or voucher credit.Calculate tax reversal: mirror original tax rate and FX snapshot.Create credit note linked to the original invoice; include reason code.Execute refund via PSP in the original payment method and settlement currency.Notify the customer with clear timelines (e.g., “3–10 business days depending on bank”).Pro tip: For travellers buying local packs like Esim France or Esim United States, add geo‑tips in the confirmation email (device compatibility, APN steps). Fewer setup issues mean fewer refund requests.Chargeback playbookPreventionStrong descriptor: include “Simology eSIM” and support URL.3‑D Secure where available; AVS/CVV checks and velocity rules.Pre‑delivery device checks (e.g., eSIM capability).Evidence for representmentOrder details, IP/device fingerprint, and BIN country match.Delivery proof: eSIM QR/profile delivered timestamp.Usage logs (data session started), and T&Cs acceptance.Customer communications and refund policy shown at checkout.TriageLow‑value/high‑cost disputes: consider concession.High‑value/clear evidence: proceed to representment with focused docs.Post‑mortemUpdate fraud rules (e.g., block risky BIN ranges, disposable emails).Feed learnings into support macros and checkout copy.Pro tip: Create reason‑code playbooks (e.g., “product not received” vs. “fraudulent”). Standardise the evidence pack to submit within 48 hours.Dunning and collections for B2B and wholesalePractical timeline and commsDay 0: Invoice issued with net terms (e.g., Net 14/30). Include payment link, bank details, currency, and tax breakdown.Day 3 before due: Friendly reminder with statement of account.Day 0 due: Notice with next steps and escalation path.Day 7 overdue: Second reminder; offer card-on-file as a fallback.Day 14–21 overdue: Account manager call; agree a payment plan.Day 30+: Suspend non‑critical benefits (marketing funds, new activations) while preserving active travellers where possible.Pro tip: For resellers sourcing regional packs like Esim North America or Esim Western Europe, suspend new order creation before disabling existing lines to avoid traveller impact.Risk controls and suspension logicCredit limits per partner; auto‑adjust based on payment history.Collateral or prepayment for new partners until two clean cycles.Grace windows for active travellers; offer top‑up vouchers funded from security deposit if needed.Automated dunning across email + portal banners; keep comms factual and friendly.Regional nuances to watchEU/UK: Display VAT‑inclusive prices for consumers. If a B2B buyer enters a valid VAT number, apply reverse charge and show required wording on the invoice.US: Product taxability differs by state; telecom vs. digital service classification can change rates. Marketplace facilitator laws may shift liability.Canada: GST/HST/PST mix varies by province; register thresholds apply.Travellers often buy in one country for use in another (e.g., purchase from the UK for Esim Spain). Determine tax based on customer location rules, not the visited country, unless local laws require otherwise.Multi‑country bundles: Use consistent SKUs tied to the buyer’s location for tax, not each covered country.Pro tip: Keep your plan catalogue aligned with geo coverage on Destinations so tax and pricing logic stays in sync with what travellers actually buy.Reporting, reconciliation, and auditsDaily reconciliation checklistMatch orders to payments: amount, currency, fees, settlement date.Verify tax amounts by jurisdiction and product SKU.Confirm invoice and credit note sequences are gap‑free.Review refunds vs. payouts; reconcile FX differences to a gain/loss account.Surface anomalies: negative margin orders, duplicate refunds, or out‑of‑policy credits.Export formats and storageProvide CSV/JSON exports per day/week with:Order ID, SKU, region, buyer type (B2B/B2C), FX rate used.Net, tax, gross, currency, settlement currency, fees.Invoice/credit note numbers and links.Retain PDFs and raw data per statutory timelines; ensure timezone consistency across logs.Pro tip: Store an immutable “tax calc snapshot” per order so later tax engine changes don’t alter historical documents.Quick setup checklist (save this)Define seller‑of‑record per channel/region.Map tax codes per SKU and integrate VAT number validation.Implement display currency with clear FX notes; keep settlement currency stable.Choose a single pro‑ration model and document it.Automate credit notes for refunds; mirror original tax and FX.Build a reason‑coded chargeback pack and a 30‑day dunning cadence.Reconcile daily; export audit‑ready tax and payout data.FAQQ1: How should I handle VAT for B2B eSIM sales in the EU/UK? A: Collect and validate the buyer’s VAT number at checkout. If valid, apply reverse charge and include the correct wording on the invoice. If not, charge VAT as for B2C. Keep the validation result with the order.Q2: Can I show prices in multiple currencies but settle in USD or EUR? A: Yes. Use a stable settlement currency operationally, show shopper‑friendly display currencies, and disclose the settlement currency and any FX margin. Keep the FX snapshot per order for refunds and audits.Q3: What’s the fairest way to calculate partial refunds on data packs? A: Pick one method and be consistent. Time‑based works well for validity‑driven plans; usage‑based suits metered data. Mirror the original tax and FX when issuing the credit note.Q4: How do I reduce “product not received” chargebacks? A: Send a post‑purchase email with device compatibility checks, clear activation steps, and support links. Keep delivery logs of the eSIM profile and show your refund policy at checkout. For country packs like Esim Italy, add country‑specific APN tips.Q5: What should a VAT invoice include for eSIM? A: Seller and buyer details (including VAT IDs), unique invoice number, dates, line‑item prices, tax rates and amounts, totals, currency, and any reverse charge text. Issue credit notes for any refunds.Q6: How should dunning work for wholesale partners? A: Use a clear cadence (reminders before and after due), offer multiple payment methods, set credit limits, and suspend new activations before impacting existing travellers. Manage it via your partner portal—see our Partner Hub.Next step: Build a compliant, traveller‑friendly billing stack with Simology—start here: For Business.

30 Oct 2025