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

30 Oct 2025

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 scale

Tax 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 partners

Identify tax nexus by region

EU/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 invoice

Seller 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 rules

Define 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 trust

Display vs settlement currency

Display 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 sources

Use 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 checkout

Detect 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‑ups

Common scenarios and calculations

Mid‑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 friction

Refund policy matrix

Technical 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 refund

Verify 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 playbook

Prevention
Strong 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 representment
Order 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.
Triage
Low‑value/high‑cost disputes: consider concession.
High‑value/clear evidence: proceed to representment with focused docs.
Post‑mortem
Update 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 wholesale

Practical timeline and comms

Day 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 logic

Credit 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 watch

EU/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 audits

Daily reconciliation checklist

Match 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 storage

Provide 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.

FAQ

Q1: 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.

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

eSIM Not Working? The 15 Most Common Fixes (iOS & Android)

When you land and your eSIM won’t connect, it’s rarely a dead end. In most cases it’s a quick setting, a network registration delay, or a simple reinstall. This guide walks you through a traveller-first triage and the 15 most reliable fixes for when an eSIM is not working on iOS or Android. You’ll check line activation, roaming, APN, network selection, and dual-SIM priorities step by step. We’ll also flag what to collect before contacting support and how to avoid issues next time.If you’re choosing a plan for your trip, start with our regional and country packs (for example Esim United States, Esim France, Esim Italy, Esim Spain or Esim Western Europe and Esim North America). For destination-by-destination coverage and set-up notes, head to Destinations.Quick triage: is it your eSIM, your device, or the network?Run this 60‑second checklist to pinpoint the issue: - Airplane Mode off? Mobile Data on? Wi‑Fi off (for testing)? Restart done?- Is the eSIM line installed, turned on, and set as the Mobile Data line? - Is Data Roaming enabled for the eSIM line? - Does manual network selection show local networks? Can you latch onto any? - Any usage limits hit (data cap/exhausted), plan expired, or activation pending?Pro tip: Give new eSIMs 2–5 minutes after landing to register. If you installed mid‑flight, reboot after arrival.The 15 most common fixes (iOS & Android)Use these in order. After each fix, test by toggling Mobile Data off/on and loading a plain web page.1) Confirm your phone is eSIM‑compatible and unlockediOS: iPhone XR/XS or newer typically support eSIM.Android: Many recent models do; check your device settings.Settings path:iOS: Settings > Mobile Data > Add eSIM (or “eSIMs”)Android: Settings > Network & Internet > SIMs (or Mobile network)Ensure the phone is carrier‑unlocked. If it’s locked to a home network, roaming eSIMs may not register.2) Reboot and toggle radiosToggle Airplane Mode on for 10 seconds, then off.Restart the device.Turn Wi‑Fi off briefly to force a cellular test.3) Make sure the eSIM is installed and activeiOS: Settings > Mobile DataCheck the eSIM is listed and “On”.Set Mobile Data: eSIM lineAndroid: Settings > Network & Internet > SIMsTurn on the eSIM.Set Preferred SIM for Mobile data: eSIMIf you don’t see the eSIM, re‑scan the QR or use the activation code provided by your eSIM vendor.4) Enable Data Roaming for the eSIM lineRoaming must be enabled for travel eSIMs. - iOS: Settings > Mobile Data > eSIM line > Data Roaming = On- Android: Settings > Network & Internet > SIMs > eSIM > Roaming = On5) Check plan status, allowance and validityConfirm the plan is activated (some start on installation; others on first network attach).Ensure you have remaining data. If you’ve hit the cap, speeds may drop or data may stop.If your trip spans borders, confirm your plan covers those countries (e.g., use Esim Western Europe for multi‑country EU travel or Esim North America across USA/Canada/Mexico).Pro tip: If you installed long before travel, check the expiry window hasn’t elapsed.6) Set network to 4G/5G Auto (avoid 2G/3G only)iOS: Settings > Mobile Data > eSIM line > Voice & Data = 5G Auto or 4G/LTEAndroid: Settings > Network & Internet > SIMs > eSIM > Preferred network type = 5G/4G (Auto)Some networks have retired 3G; forcing 3G can block data.7) Manually select a local network, then revert to AutomaticiOS: Settings > Mobile Data > Network Selection > turn Automatic off > choose a listed local carrier. After a successful attach, you can return to Automatic.Android: Settings > Network & Internet > SIMs > eSIM > Network > choose a carrier, then try switching back to Automatic.Pro tip: If one network fails, try others in the list. Regional eSIMs often have multiple partners.8) Check and (if required) set the APNMost eSIMs push APN automatically, but some require manual entry. - iOS: Settings > Mobile Data > eSIM line > Mobile Data Network- Android: Settings > Network & Internet > SIMs > eSIM > Access Point NamesIf your provider specifies an APN, enter exactly as given (case sensitive). Save and select it.9) Update carrier settings and OSiOS: Settings > General > About. If a “Carrier Settings Update” prompt appears, accept. Also update iOS to the latest version.Android: Settings > System > System update. Install pending updates. Some devices also offer a “Carrier Services” or “Operator configuration” update in the Play Store.10) Turn off VPN, Private Relay and firewall apps (temporarily)VPNs, DNS filters and Private Relay can interrupt first network registration or captive portals.- Disable these, reboot, attach to the network, then re‑enable if needed.11) Reset network settings (safe but clears saved networks)If the above steps fail: - iOS: Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings- Android: Settings > System > Reset options > Reset Wi‑Fi, mobile & BluetoothYou’ll lose saved Wi‑Fi and Bluetooth pairings. Your eSIMs remain, but you may need to re‑select defaults.12) Prioritise the eSIM if you use two linesDual‑SIM phones can get confused about data routing.- Set the eSIM as the default data line.- Disable the physical SIM temporarily, or turn off “Allow Mobile Data Switching” (iOS) to keep data on the eSIM.13) Reinstall or reissue the eSIM (only if allowed)Delete the eSIM profile, then add it again using the original QR/code.Some QR codes are single‑use. If re‑adding fails, request a reissue from your provider before deleting.Always be connected to Wi‑Fi while installing an eSIM.14) Toggle VoLTE/5G options if calls aren’t neededData‑only eSIMs don’t require voice features. If attach fails:- Try disabling 5G temporarily (set to 4G/LTE).- Toggle VoLTE off/on (some networks need it one way or the other). Test each change.15) Give it time, move, or try a different bandNew registration can take a few minutes. Buildings and basements block signals.- Wait 2–5 minutes after changes, then restart.- Move outdoors or closer to a window.- If available in your device, try locking to LTE only (then re‑enable Auto) to stabilise initial attach.Before you fly: a 5‑minute pre‑travel checklistInstall the eSIM on Wi‑Fi before departure (but don’t exhaust the validity window).Save your QR/code and account login offline.Verify your device is unlocked and supports the destination bands.Know whether your plan is country‑specific (e.g., Esim United States, Esim France, Esim Italy, Esim Spain) or regional (e.g., Esim Western Europe).Turn on Data Roaming for the eSIM line, and set it as your Mobile Data line.Keep your physical SIM off or ready to toggle if you won’t use home roaming.When to contact support (and what to send)If you’ve worked through the fixes and still can’t connect, share these details with support to speed resolution: - Your device make/model and OS version- eSIM ICCID or EID (found in SIM/Network settings)- Country and city you’re in, and which networks appear in manual selection- Screenshots of: eSIM status, Data Roaming toggle, APN screen, network type (4G/5G)- Whether you’ve tried network reset, reinstall, and different network selectionsPro tip: Try a local SIM test with a friend’s device, if available, to rule out a local outage.For teams and frequent travellersIf you manage multiple travellers, centralised eSIM management saves hours. Explore pooled data, shared dashboards and deployment via QR or SM‑DP+ with For Business. Partners and resellers can automate provisioning and track redemptions via the Partner Hub.FAQsWhy is my eSIM not working after landing? Often it’s one of three things: Data Roaming is off, the eSIM isn’t set as the Mobile Data line, or the phone needs a reboot to register on the local network. Start with toggling Airplane Mode, enabling Data Roaming, and selecting a local network manually.Do I need to change APN settings for an eSIM? Usually no—APNs auto‑provision. If data won’t start, check the APN screen. If your provider lists a specific APN, enter it exactly and select it.Will a VPN stop my eSIM from working? VPNs and Private Relay can interfere with initial registration and captive portals. Turn them off, get connected, then re‑enable.Can I keep my physical SIM active while roaming on an eSIM? Yes, but set the eSIM as the default data line. If data keeps switching to the physical SIM, disable “mobile data switching” (iOS) or temporarily turn off the physical SIM.My eSIM shows bars but no internet. What now? This points to APN, data routing, or plan allowance. Confirm the eSIM is the data line, verify APN, and check you haven’t hit a data cap. Toggling 5G to 4G/LTE can also stabilise data.Which eSIM should I choose for multi‑country trips? Pick a regional plan: for the EU/Schengen area use Esim Western Europe; for cross‑border North American travel use Esim North America. For single‑country travel, browse by country via Destinations.Next step: Ready to pick a plan that works where you’re going? Start with Destinations to find the right eSIM and setup notes for your trip.

30 Oct 2025

Compliance 101: eKYC, Data Privacy (GDPR), and Logs Retention for Partners

Modern travel demands instant connectivity, and eSIM makes it happen. For partners reselling or embedding Simology connectivity, the job is bigger than coverage and price. You’re handling identity checks, personal data, and operational logs across borders. This guide brings together the essentials of eSIM compliance eKYC GDPR in plain English so you can build trust with travellers while staying audit‑ready. We outline what data is genuinely needed, how to minimise risk, and how long to keep records without over‑retaining. You’ll also find checklists and pro tips for privacy‑by‑design and practical data retention schedules. If you serve travellers headed to multiple regions — from Esim United States to Esim Western Europe — your compliance posture must flex with local rules while giving a consistent, friction‑light experience. Use this as a blueprint to align your teams and vendors, and to make privacy a feature travellers can feel.Why eKYC matters for eSIM travellers and partnersElectronic Know Your Customer (eKYC) verifies a traveller’s identity before activating service in markets where it’s required by telecom, anti‑fraud, or security regulations.Typical triggers: - Prepaid SIM rules (many EU and APAC markets). - Roaming controls and fraud prevention. - Payment risk or chargeback mitigation for high‑value plans.What eKYC usually collects: - Identity document data (passport, national ID, sometimes driving licence). - Face verification (selfie with liveness) to match the document. - Minimal device data to bind activation (e.g., EID/IMEI), and IP/location signals for risk scoring.Country differences matter. For instance, some EU countries require SIM registration before first use, while the United States is generally lighter on mandatory SIM registration but robust on privacy and law enforcement requests. If your travellers are buying across Esim France, Esim Italy, or Esim Spain, your workflow should adapt to each market’s rules without making the user repeat steps. Direct travellers to options on Destinations, and ensure your backend enables compliant activation journeys per country.GDPR and global privacy principles, distilledGDPR sets the global benchmark for personal data protection. Even when you sell outside the EU, adopting its core principles will simplify operations and reduce risk.Key principles to build into your eSIM flows: - Lawful basis: Most eSIM processing rests on contract (to provide service), legal obligation (where eKYC is mandated), and legitimate interests (fraud prevention). Use consent only for optional features like marketing. - Purpose limitation and minimisation: Collect only what the regulation or the service genuinely requires. Don’t repurpose identity images for unrelated analytics. - Storage limitation: Keep data only for the period needed to meet legal, tax, or dispute requirements — then delete or irreversibly anonymise. - Security and confidentiality: Encrypt at rest and in transit. Limit access by role. Maintain separation between KYC images and operational logs. - Transparency and control: Clear notices at point of capture, easy access to rights (access, rectification, deletion), and visible retention timelines.Cross‑border transfers: - If EU/UK data leaves the EEA/UK, safeguard with adequacy decisions, Standard Contractual Clauses (SCCs) or UK IDTA as appropriate, plus transfer risk assessments and technical controls (encryption, key management).Practical tip: Keep your Data Processing Agreement (DPA) stack tidy. You should have a DPA in place with Simology and any sub‑processors, aligned to the data you actually collect in each workflow.Data retention and logs: what to keep, and for how longTelecom operations generate a lot of data. You need enough to support travellers, fulfil lawful obligations, and investigate fraud — but not so much that you create unnecessary risk.Common data categories - eKYC data: document images, extracted fields, liveness artefacts, verification outcome, and audit trail. - Activation and provisioning: EID/IMEI, ICCID, activation timestamps, plan details, order/payment references. - Network session metadata: session start/stop, cell/location approximations, volume counters (no content). - Support and compliance: consent logs, policy versions, ticket history, refunds/disputes, law enforcement requests (where applicable). - Security: access logs, API logs, fraud signals, device fingerprints.Typical retention ranges (select minimum necessary) - eKYC images and liveness artefacts: 90 days to 24 months, depending on local mandate and dispute window. Prefer deleting images once the verification decision is final and only retaining a hashed template or verification token where admissible. - Extracted KYC data (e.g., name, document number): retain only as long as needed to meet telecom registration requirements; commonly 6–24 months, varying per country. - Activation/provisioning records: 12–24 months to support customer care, chargebacks, and lawful requests. - Network session metadata (no content): 6–12 months is typical in many markets; local law may require longer or shorter. - Billing/tax records: often 6–7 years in many jurisdictions. Store these separately and avoid bundling with KYC images. - Security and access logs: 6–18 months to support incident response and forensics.Do not keep - Raw biometric templates or full‑resolution video beyond the shortest regulatory and operational need. - Duplicate copies of KYC images in analytics sandboxes or support tools. - Content of communications (not part of eSIM data plans) unless explicitly regulated and lawful.Step‑by‑step: Build your retention schedule1) Map your data: - List every field captured in eKYC, activation, usage, billing, and support.2) Assign lawful purpose and system of record: - For each field, define why you need it and where it lives.3) Set retention per category: - Use the shortest timeline that satisfies the strictest regulatory need for that market.4) Automate deletion: - Implement lifecycle rules (e.g., S3 object lifecycle, database TTLs) and keep evidence of deletion in audit logs.5) Separate storage: - Store KYC images separately from billing/usage. Restrict access via least privilege.6) Document it: - Maintain a one‑page retention matrix per market. Keep it updated when laws change.Pro tips - Use tokenisation: replace document numbers with irreversible tokens in everyday systems; keep the mapping in a segregated vault. - Prefer summary over detail: retain aggregate usage counters over per‑packet detail. - Time‑box support access: temporary just‑in‑time access for agents, with session recording.Privacy‑by‑design for eSIM: a practical checklistMinimise from the start: collect only the document type required for that country. If a national ID suffices, don’t ask for a passport.Make it legible to travellers: show exactly why data is needed, where it’s stored, and for how long.Default to the strictest market: design flows that can downgrade requirements for lighter regimes, not the other way around.Secure everywhere: TLS 1.2+, encryption at rest (AES‑256 or better), HSM‑protected keys, rotating secrets.Strong vendor governance: DPAs, sub‑processor lists, breach SLAs, penetration tests, and SOC 2/ISO 27001 where available.Data Protection Impact Assessment (DPIA): run a DPIA for identity verification and cross‑border transfers.Consent hygiene: separate toggles for marketing vs service updates; keep timestamped consent logs.Traveller self‑service: portal to access/delete data where allowed, and to download invoices for expenses.eKYC implementation options and risk controlRight‑size your eKYC to the market and plan type:Document scan + liveness: standard for countries with SIM registration rules. Store verification outcome; avoid long‑term storage of the raw selfie/video.Database checks: where lawful, validate against government or telco registries to avoid storing images.Risk‑based flows: lighter checks for low‑risk, low‑value plans; step‑up verification if fraud signals trigger.Offline fallback: for travellers with poor connectivity, enable deferred document upload with limited temporary access.Re‑use safely: if a traveller verified last month for Esim North America, you may re‑use a tokenised verification to buy Esim United States without re‑capturing images, subject to local rules.Pro tips - Hash and forget images: retain a cryptographic hash of the document image for deduplication/fraud detection, not the image itself. - Separate decisioning: store “pass/fail + reason code” in operational systems; keep raw artefacts in a secure verification vault with short retention.Cross‑border operations: aligning US, EU, and beyondEU/UK: expect SIM registration in several markets, strong GDPR rights, and tight storage limitation. Host EU resident data in the EEA/UK where possible, with SCCs for any exports.United States: generally fewer mandatory KYC rules for prepaid; focus on CPNI, state privacy laws, and law enforcement response processes. Regional nuances apply.APAC/MENA: several markets require passport/ID capture for SIM activation; watch for data localisation (country‑resident storage) requirements.Keep it simple for travellers. Someone buying Esim Western Europe wants one purchase to cover France, Italy, and Spain. Behind the scenes, your systems should meet each market’s registration rules without extra friction. Offer clear guidance on Destinations and provide country‑specific help within the checkout.What travellers expect (and notice)Speed: a sub‑2 minute identity check that works on mobile.Clarity: simple explanations for why an ID is needed in France versus not in the US.Control: the ability to delete their account or remove a stored document when rules allow.Security cues: trusted logos, clear privacy links, and no surprise re‑verification for add‑on plans.Helpful coverage info: straightforward product pages like Esim France, Esim Italy, and Esim Spain that set expectations before checkout.Partner integration with SimologyIf you’re building on Simology via wholesale or bundling connectivity into your product:Define roles early: who is controller vs processor for eKYC, activation, and support data.Use standard endpoints: integrate identity verification and consent capture through approved APIs; don’t invent parallel data stores.Align retention with us: mirror Simology’s recommended timelines and ensure automated deletion on your side.Centralise help content: point travellers to the right local guidance and plan pages on Destinations.Governance cadence: quarterly reviews of sub‑processors, transfers, DPIAs, and incident drills.Explore options on For Business and get documentation, samples, and support via the Partner Hub.Quick compliance checklistseKYC readiness - Markets mapped: which plans require ID? - Verification vendor vetted and under DPA. - Short‑term storage of images with auto‑delete. - Decision tokens available for re‑use. - Clear traveller messaging per market.GDPR and privacy - Lawful bases documented per data category. - Transparent notices and consent logs. - Data subject request workflow tested end‑to‑end. - Cross‑border safeguards (SCCs/IDTA) in place.Logs and retention - Separate stores for KYC, usage, billing, and support. - Automated retention rules and deletion evidence. - Least‑privilege access with time‑boxed elevation. - Regular log integrity and access reviews.Security - Encryption everywhere, key rotation, HSM/KMS. - MFA and SSO for all admin access. - Pen tests and vulnerability management. - Incident response runbooks and contacts maintained.FAQQ1: What is eKYC in the context of eSIM? A1: eKYC is a digital identity check used before activating service in markets that require SIM registration or where you need stronger fraud protection. It typically includes scanning a government ID and a quick liveness check to confirm the document belongs to the traveller.Q2: Do all countries require eKYC for eSIM? A2: No. Requirements vary by country and plan type. Several EU and APAC markets require registration; others, such as parts of the United States, typically do not. Check plan pages like Esim United States and regional bundles such as Esim Western Europe for local notes.Q3: How long should we keep KYC images? A3: Keep them only as long as needed to satisfy local rules and operational needs. Many partners aim for 90 days to 12 months, deleting images once verification is final and retaining only a decision token or hash. Always separate image retention from billing/tax record retention.Q4: What network data is retained about travellers? A4: Operational metadata such as activation timestamps, session start/stop times, and aggregated data volumes. Content of communications is not retained. Typical retention ranges from 6 to 12 months, subject to local law and support requirements.Q5: How is GDPR handled when serving multi‑region travellers? A5: Apply GDPR principles by default: minimisation, clear purposes, storage limitation, strong security, and proper transfer safeguards (e.g., SCCs). Host EU data in the EEA/UK when possible, and use contractual and technical measures for any transfers.Q6: Can previous eKYC be reused for repeat purchases? A6: Often, yes. If regulations allow, store a tokenised verification result and reuse it for future activations (e.g., moving from Esim North America to Esim United States), avoiding another document capture. Respect market‑specific rules and set an expiry for reuse.Next step: Access implementation guides, sample DPAs, and integration support via the Simology Partner Hub.

30 Oct 2025