QR Code Scams at Airports & Cafés: How to Spot and Avoid Them

Blog

QR Code Scams at Airports & Cafés: How...

QR Code Scams at Airports & Cafés: How to Spot and Avoid Them

30 Oct 2025

Security
QR Code Scams at Airports & Cafés: How to Spot and Avoid Them

Travellers love QR codes because they are fast, contactless and language‑agnostic. Airports, lounges and cafés use them for menus, Wi‑Fi portals, boarding info and payments. Criminals love them for the same reasons. A tampered or fake code can silently redirect you to a malicious site that steals card details, hijacks messaging apps, installs spyware, or tricks you into paying the wrong person. The risk spikes on the road: you are rushed, tired, on public Wi‑Fi and less likely to scrutinise small details. This guide explains exactly how the scams work, what to check before you scan, safer ways to pay and connect, and what to do if you slip up. Whether you are hopping between terminals in the United States, ordering a cortado in Spain, or heading across Western Europe, a few habits will block most attacks. Keep this page handy for your next trip and share it with your travel companions or team.

Why travellers are targeted with QR code scams

  • High turnover environments. Airports and busy cafés see constant footfall; a swapped sticker can harvest hundreds of scans quickly.
  • Trust in signage. Branded posters and table tents create false credibility; a neat sticker overlay looks “official”.
  • Time pressure. Boarding calls, queues and language barriers push you to scan first and think later.
  • BYO devices. Attackers can exploit out‑of‑date phones or permissive browser settings.
  • Payment normalisation. Scan‑to‑pay is normal in many countries, so fake payment QR codes blend in.

If you are planning routes and connectivity, cross‑check local adoption of QR payments and Wi‑Fi portals via our Destinations guides.

How QR code scams work (in plain English)

  • Malicious redirects. A code sends you to a fake version of a brand’s site (Wi‑Fi login, airline check‑in, café menu). The URL looks convincing but collects passwords, card details or passport data.
  • Payment swaps. A code takes you to a genuine payment app but with an attacker’s payee or invoice pre‑filled; you approve and funds go to the wrong account.
  • App sideload prompts. A page urges you to install an “airport app” or “menu viewer” via an APK or profile—common on Android and iOS respectively—opening the door to malware or mobile device management abuse.
  • Messaging takeovers. A landing page requests excessive permissions (SMS, notifications, accessibility) to read 2FA codes or control taps.
  • Dynamic content masking. Short links or URL shorteners hide the destination, making quick checks harder.
  • Sticker overlays. Real posters/menus are fine; the small QR square is replaced with a tampered sticker.

Before you scan: a traveller’s 10‑point checklist

  1. Inspect the QR physically. Is it a sticker on top of another? Misaligned? Bubbling? Smudged print or off‑brand colours are red flags.
  2. Cross‑verify source. Does the code appear on an official screen, laminated menu, or embedded signage—or a loose card left on tables?
  3. Read the URL preview. Most phones show a domain preview. If your phone does not, long‑press the QR or disable auto‑open in your camera settings.
  4. Check the domain, not the title. “airline‑checkin.com.example.ru” is not “example.com”. Watch for misspellings, extra words and unfamiliar TLDs.
  5. Look for HTTPS and a padlock. Not sufficient alone, but the absence is a deal‑breaker. Never enter credentials on non‑HTTPS pages.
  6. Avoid short links when possible. Be wary of bit.ly, t.co, tinyurl unless you can expand them first.
  7. Never install apps from a QR. Go to the official app store manually and search by name.
  8. Don’t grant extra permissions. A menu or Wi‑Fi portal never needs SMS, contacts, accessibility or device admin rights.
  9. Confirm with staff. For payments and Wi‑Fi, ask: “Is this your current QR?” Staff know if codes recently changed.
  10. Use mobile data for sensitive actions. Avoid public Wi‑Fi for logins and payments. An eSIM is safer and faster in busy terminals.

Pro tips: - Make “Show URL preview” and “Ask before downloading” mandatory in your browser settings. - Save official airline and café URLs in bookmarks; open from bookmarks instead of scanning signage.

For regional travel data that lets you bypass risky Wi‑Fi entirely, see Esim North America, Esim Western Europe, or country packs like Esim United States, Esim France, Esim Italy and Esim Spain.

Spotting fakes at airports and cafés

  • Inconsistent branding. Fonts, colours and logos slightly “off” compared with nearby official materials.
  • Suspicious placement. QR on a separate sticker placed over or near the original, or in odd spots (toilet doors, lifts) without context.
  • Too‑good promos. “Free lounge access, scan to claim” or “50% off all coffee now.” Limited‑time bait is a classic trick.
  • Requests for card upfront. A café menu QR that demands card details before showing items is almost certainly fake.
  • Language mismatch. In an official airline zone, the scan page appears in another language with no localisation options.
  • Staff surprise. If staff hesitate or look confused when you ask about a code, don’t scan it.

Safer ways to access menus, Wi‑Fi and boarding info

Menus: - Ask for a printed menu or read items on the physical board. - If the venue insists on digital, type the domain stated on the receipt or napkin ring into your browser manually.

Wi‑Fi: - Ask staff to tell you the network name and portal URL verbally. - Prefer your own mobile data for any account logins, payments or bookings while travelling.

Airline and gate info: - Use your airline’s app and airport’s official app you installed before travel. Open them directly—do not reinstall via QR at the gate.

Pro tips: - Bookmark your airline, airport, hotel and favourite coffee chain URLs pre‑trip. - Enable “Private DNS”/“Encrypted DNS” and use a reputable browser with anti‑phishing protections.

Payment safety tips on the road

  • Verify the payee. If a QR opens your payment app, check the recipient name and amount before approving.
  • Use contactless cards or wallet. Tap‑to‑pay on terminal beats scan‑to‑pay from a random poster.
  • Don’t save cards on pop‑up portals. Use guest checkout or wallets that tokenise your card.
  • Turn on payment notifications. Real‑time alerts let you catch and report fraud quickly.
  • Separate cards. Keep a low‑limit card for travel micro‑payments; reserve your main card for larger, trusted spends.
  • Reconcile daily. Review transactions each evening while details are fresh.

If you manage company travellers, centralise guidance and reimbursement via For Business. Travel partners can access co‑branded safety kits in our Partner Hub.

Protect your phone before you fly

  • Update OS and apps, especially browser and wallet apps.
  • Disable “Install unknown apps” (Android) and ignore profile install prompts (iOS).
  • Turn off “Open links in installed app” for unknown domains to reduce automatic handoffs.
  • Use a password manager; it won’t auto‑fill on fake domains.
  • Enable two‑factor authentication using an authenticator app rather than SMS when possible.
  • Set your camera to ask before opening QR links automatically.

What to do if you already scanned a bad QR

Act quickly. You can often limit damage within minutes.

  1. Disconnect. Turn on flight mode and disable Wi‑Fi/Bluetooth.
  2. Close the page. Do not tap any further prompts. Force‑quit the browser.
  3. Clear browsing data. Remove recent cookies/history for the last hour.
  4. Change passwords. For any accounts you entered after scanning, change passwords from a clean device and sign out of all sessions.
  5. Cancel suspect payments. Contact your bank via the number on the card. Explain you may have paid a fraudulent recipient.
  6. Remove profiles/apps. Uninstall any app you installed from the QR and remove any unfamiliar device profiles.
  7. Run a security scan. Use your phone’s built‑in scanner or a reputable mobile security app.
  8. Monitor accounts. Enable alerts and watch for new charges or login attempts over the next week.
  9. Report locally. Tell the venue/airport so they can pull the fake code and warn others.

If you’re mid‑trip without safe Wi‑Fi, switch to mobile data—an eSIM pack like Esim Western Europe or Esim North America lets you secure accounts without touching public networks.

Regional note: using eSIM to avoid risky Wi‑Fi

Most QR cons strike when you’re offline and hunting for Wi‑Fi. With travel eSIMs you can: - Skip captive portals entirely. - Use your banking and airline apps on mobile data. - Hotspot a companion device securely.

Pick a regional plan like Esim Western Europe for multi‑country trips or a local bundle such as Esim United States, Esim France, Esim Italy or Esim Spain.

FAQ

Q: Are QR code scams really common for travellers? A: Yes. High‑traffic, low‑attention areas like gates, lounges and café tables are ideal for attackers. Even a simple sticker swap can net hundreds of scans daily.

Q: How do I tell a safe URL from a fake one quickly? A: Focus on the registered domain (the part before the last dot and TLD). “example.com” is safe if expected; “example‑support.com‑secure.info” is not. Avoid taking page titles or logos at face value.

Q: Is scanning a QR automatically dangerous? A: Scanning itself is not harmful. Risk begins when you open the link, install something, or enter data. Use URL preview, verify domains, and never install apps from a QR.

Q: What about QR menus that ask for my card before showing items? A: Treat that as a red flag. A menu should not require payment details up front. Ask for a printed menu or pay at the counter.

Q: Should I use airport Wi‑Fi to download airline apps? A: Prefer mobile data. Install official apps before travel or search the app store directly. Avoid QR prompts on posters or tray tables.

Q: Does a padlock (HTTPS) mean the site is safe? A: It means the connection is encrypted, not that the site is trustworthy. Combine HTTPS with domain checks, context and staff verification.

The bottom line

QR codes are handy, but trust the source not the square. Verify before you scan, avoid installing anything via QR, pay only through confirmed channels, and keep your phone locked down. With basic checks and reliable mobile data, you can sidestep nearly every qr code scam travel threat on your itinerary.

Next step: Plan secure connectivity for your route with our regional and country eSIMs on Destinations.

Read more blogs

Andes Highlights (3 Weeks): Peru–Bolivia–Chile–Argentina Connectivity

Andes Highlights (3 Weeks): Peru–Bolivia–Chile–Argentina Connectivity

Planning a south america itinerary 3 weeks through the high Andes? This route stitches together Peru’s Sacred Valley, Bolivia’s La Paz and Salar de Uyuni, Chile’s Atacama Desert, and northern Argentina’s quebradas or Mendoza wine country—often by long-distance bus and a couple of short flights. Connectivity is different at altitude: coverage is strong in cities but drops in high passes and salt flats; bus Wi‑Fi is patchy; border towns can be blackspots. The smart move is an eSIM with multi‑country coverage, backed by offline maps, offline translations, and a simple routine for crossing borders by bus without losing service. Below you’ll find a practical, connectivity-first itinerary; checklists to prep your phone, apps and documents; and on-the-ground tips for staying online where it matters: booking transport, hailing taxis, backing up photos, and navigating when the signal disappears.If you’re transiting via Europe or North America, you can also add a layover eSIM to stay connected door-to-door. Start with our country list on Destinations, then follow the steps, and you won’t waste time chasing SIM shops at 3,500 metres.The 3‑week Andes route at a glanceWeek 1: Peru (Cusco, Sacred Valley, Machu Picchu) - Fly into Cusco (or Lima then connect). - Base in Cusco; day trips to Pisac/Chinchero/Maras–Moray. - Train to Aguas Calientes; Machu Picchu visit; return to Cusco or continue to Puno/Lake Titicaca.Week 2: Bolivia and Chile (La Paz, Uyuni, San Pedro de Atacama) - Bus/collectivo via Copacabana to La Paz. - Fly or overnight bus to Uyuni. - 3‑day Uyuni–altiplano tour ending in San Pedro de Atacama (Chile).Week 3: Chile and Argentina (Atacama to Salta or Mendoza/Buenos Aires) - Choose: - North: San Pedro to Salta/Jujuy by bus; fly to Buenos Aires. - Or South: San Pedro–Calama flight to Santiago; bus or flight to Mendoza; onward to Buenos Aires.Connectivity notes (quick): - Cities: generally strong 4G/4G+; 5G in major hubs (Santiago, Buenos Aires). - Altitude/rural: expect long no‑signal stretches (Uyuni, altiplano passes, Paso Jama). - Bus Wi‑Fi: often advertised, rarely reliable. Plan to be offline onboard. - Border regions: networks switch; a multi‑country eSIM avoids sudden loss.eSIM vs local SIMs for a 4‑country tripFor a route with multiple borders and remote legs, eSIM wins on time and reliability.What a multi‑country eSIM gets you: - One plan across Peru, Bolivia, Chile, Argentina (check coverage per country on Destinations). - No passport/SIM registration queues at kiosks. - Keep your home number active on the physical SIM for calls/SMS codes. - Instant top‑ups if you burn data on photos or navigation.When a local SIM still helps: - Long stay in one country with heavy data use (e.g., a month in Buenos Aires). - Dead zones where a different local network performs better (rarely worth the hassle on a 3‑week pace).Practical approach: - Use an eSIM as your primary data line across all four countries. - If you find a specific local network far better in one region, add a cheap local SIM and keep the eSIM as backup.Device readiness checklist (before you fly)1) Check eSIM compatibility and SIM‑lock status on your phone.2) Buy and install your eSIM while on home Wi‑Fi. Keep a PDF/printed copy of the QR code.3) Label lines clearly (e.g., “eSIM Andes Data”, “Home SIM”).4) Turn on data roaming for the eSIM; leave roaming off for your home SIM to avoid charges.5) Set up dual‑SIM rules: data on eSIM; calls/SMS default to home SIM if needed.6) Download offline: Google Maps/Organic Maps for all target regions; language packs (Spanish at minimum); bus/air tickets; hotel confirmations.7) Cloud backups: set to upload on Wi‑Fi only; pre‑create shared albums for travel companions.8) Test tethering/hotspot with your laptop/tablet.If you’re transiting popular hubs, consider a short layover eSIM: - USA connections: add an Esim United States or a broader Esim North America.- Europe connections: Madrid/Barcelona? Use an Esim Spain. Paris or Rome? See Esim France and Esim Italy. Multi‑country layovers? Try Esim Western Europe.City‑by‑city connectivity notesCusco & the Sacred Valley (Peru)Coverage: Good in Cusco city; variable in high villages (Maras/Moray) and along Inca Trail approaches.Tips: Download Sacred Valley maps offline; pin viewpoints and ruins. most taxis use WhatsApp—save your accommodation’s number.Machu Picchu/Aguas Calientes: Patchy to none at the citadel. Upload your photos later; don’t rely on live ticket retrieval.Lake Titicaca: Puno and CopacabanaPuno: Reasonable 4G; bus terminals crowded—screenshot QR tickets.Crossing to Copacabana: Expect a signal drop around the border; have directions saved offline.La Paz (Bolivia)Good urban 4G; the cable car network has decent signal but tunnels do not.Yungas/“Death Road” tours: Mountain valleys cause dead zones—share your emergency contacts with the operator, carry a charged power bank, and don’t plan remote calls.Uyuni and the Altiplano (Bolivia to Chile)Uyuni town: OK 4G; ATMs finicky—use Wi‑Fi for banking apps.Salt flats/lagunas: Assume offline for most of the 3‑day tour. Guides often carry satellite phones; agree a pickup time/place in San Pedro and preload your map route.San Pedro de Atacama (Chile)Town: Solid 4G; accommodations often have Wi‑Fi but speeds vary.Geysers, Valle de la Luna: Offline navigation essential; sunrise trips start before mobile networks wake up in some areas.Salta/Jujuy or Mendoza/Buenos Aires (Argentina)Salta/Jujuy: Good city coverage; quebradas have long no‑signal sections.Mendoza: City 4G/5G; vineyards outside town can be patchy.Buenos Aires: Strong 4G/5G; ideal for cloud backups and large downloads before you fly home.Border crossings by bus: step‑by‑stepThe big ones on this route: Peru–Bolivia (Puno/Copacabana), Bolivia–Chile (Uyuni–San Pedro via Hito Cajón), Chile–Argentina (Paso Jama to Salta or Los Libertadores to Mendoza).How to keep service and sanity:1) The day before:- Top up your eSIM data.- Confirm your plan includes both countries you’re entering/leaving.- Download offline maps for both sides of the border and your town of arrival.- Save bus company WhatsApp and terminal address offline.2) On departure morning:- Keep a paper copy or offline PDF of tickets, insurance, and accommodation proof.- Charge phone and power bank; pack a short cable in your daypack.3) On the bus:- Don’t count on bus Wi‑Fi. Keep your eSIM as primary, but expect drops near mountain passes.- If your phone supports it, enable “Wi‑Fi calling” for later when you reach accommodation Wi‑Fi.4) At the border posts:- Data may be unavailable. Keep QR codes and booking numbers offline.- After exiting one country and entering the next, toggle Airplane Mode off/on to re‑register on the new network.- If the eSIM doesn’t attach, manually select a network in Mobile Settings.5) Arrival:- Send your accommodation a quick WhatsApp when you’re back online.- Recheck your eSIM’s data roaming is on; confirm you’re on an in‑country network, not a weak roaming partner.Pro tips: - Dual profiles: If your eSIM allows, keep a secondary profile for a different network in the same country—helpful in border towns.- Cash buffer: Some border terminals don’t accept cards; download a currency converter for offline use.Offline survival kit (5‑minute setup)Maps: Download regions for Cusco, Sacred Valley, Puno, La Paz, Uyuni, San Pedro, Salta/Jujuy or Mendoza, and Buenos Aires.Translations: Download Spanish for offline use; add phrasebook favourites (bus tickets, directions, dietary needs).Documents: Save PDFs of passports, tickets, hotel addresses; star them for quick access.Rides: Screenshots of pickup points; pin bus terminals and hotel doors.Entertainment: Podcasts and playlists for long bus legs, set to download on Wi‑Fi only.Altitude and your tech: what changesCoverage gaps lengthen: Fewer towers at high altitude; valleys can block signal. Assume offline on remote excursions.Batteries drain faster in cold: Keep your phone warm and carry a power bank (10,000–20,000 mAh).Hotel Wi‑Fi may be congested: Schedule big uploads (photo backups, app updates) for big-city stays like Santiago or Buenos Aires.GPS still works offline: Your blue dot shows on offline maps without data—preload everything.Data budgeting for 3 weeksTypical traveller usage across this route: - Messaging/Maps/Bookings: 0.2–0.5 GB/day- Social and photo sharing: 0.3–0.7 GB/day- Occasional video calls/streaming: 0.5–1.0 GB/dayFor a mixed-use trip, plan 15–25 GB for 3 weeks. Heavy creators should double it and upload over hotel Wi‑Fi when possible. If you work remotely, consider a higher‑capacity plan and a backup eSIM; see our guidance on For Business.Practical route with transport and connectivity cuesDays 1–4 Cusco base: Strong city signal; day trips may be spotty—go offline-ready.Days 5–6 Machu Picchu: Expect no service at the ruins; sync tickets ahead.Days 7–8 Puno to La Paz via Copacabana: Border signal drop; re‑register networks after crossing.Days 9–11 Uyuni tour to San Pedro: Treat as offline; charge nightly; carry spare cables.Days 12–14 San Pedro: Stable in town; tours offline; top up data before Paso Jama.Days 15–17 Salta/Jujuy or Mendoza: Good urban 4G; rural patches are offline.Days 18–21 Buenos Aires: Strongest connectivity of the trip; clear your uploads and map downloads for the flight home.Partnering and stopover extrasHospitality and tour operators in the Andes: help your guests stay connected—explore co‑branded solutions via our Partner Hub.Transatlantic flyers: test your eSIM setup on a layover with an Esim United States or Esim Western Europe before hitting high-altitude blackspots.FAQs1) Do I need a local SIM in each country?No. A multi‑country eSIM covering Peru, Bolivia, Chile and Argentina is simpler and works well for a 3‑week pace. Consider a local SIM only if you’ll spend longer in one country and want the absolute best regional coverage.2) Will my WhatsApp number change with an eSIM?No. WhatsApp is tied to your registered number, not your data line. Keep your home SIM active for voice/SMS (roaming off if you wish), and use the eSIM for data—WhatsApp continues as normal.3) Can I hotspot to my laptop or camera?Yes. Enable tethering on your eSIM. Mind your data: cloud backups and OS updates can burn gigabytes—set them to Wi‑Fi only or schedule in big cities.4) What if there’s no signal on the Uyuni/Atacama legs?That’s expected. GPS still works offline. Pre-download maps and translations, carry a power bank, and sync plans with your tour operator before departure.5) Will I get roaming charges at borders?If you’re using a multi‑country eSIM with coverage in both countries, you won’t incur extra roaming fees from your home carrier. Keep roaming off on your home SIM to avoid accidental use.6) I’m connecting via Europe or the US—worth getting a layover eSIM?Yes. It’s an easy way to test your setup and stay reachable. Try Esim North America or country options like Esim Spain, Esim France, or Esim Italy for common hubs.Next step: Browse South America coverage options and build your plan on Destinations.

31 Oct 2025
Best eSIM for Europe (2025): Plans, Coverage, Fair-Use

Best eSIM for Europe (2025): Plans, Coverage, Fair-Use

Choosing the best eSIM for Europe in 2025 comes down to what you actually do on the road: how many countries you’ll cross, how much data you burn, whether you need 5G, and if hotspot tethering matters. Pricing is competitive, but not all “Europe” eSIMs are equal—some throttle after small “unlimited” buckets, some exclude popular destinations, and others won’t let you tether at all. This guide compares Europe-ready eSIMs by price per GB, 5G access, hotspot policy, and fair-use rules, so you don’t discover limits at the worst time (like mid-ride-share across borders).For most travellers, Simology’s regional plan is a standout: consistent 4G/5G coverage across key countries, transparent allowances, hotspot enabled, and simple top-ups. If you’re mainly in one country, a local eSIM (e.g., France, Italy, Spain) can push price per GB down even further. Flying via the US or Canada? Pair a Europe eSIM with a North America plan to stay connected gate-to-gate. Below is how to choose, what to expect, and the fastest way to avoid fair-use surprises.Quick verdict: the best eSIM for Europe in 2025Best overall for multi-country trips: Simology Esim Western Europe — multi-country coverage, hotspot allowed, fair-use clearly stated, easy top-up.Best value if staying in one country: Simology country eSIMs such as Esim France, Esim Italy and Esim Spain — usually the lowest price per GB.Best for transatlantic travellers: Pair Esim United States or Esim North America with a Europe plan for seamless coverage on both sides.Best for teams and frequent flyers: Managed accounts via For Business — pooled visibility, cost control, consolidated billing.If you’re unsure which countries are covered, start with the full list on Destinations.How we compared Europe eSIMsPrice per GB: Divide plan price by included GB. Ignore “unlimited” claims unless a clear daily/total high-speed cap is disclosed.Coverage footprint: Number of countries, inclusion of the big four (France, Italy, Spain, Germany) plus the UK, Nordics, Benelux, Portugal, Switzerland and popular Balkans.Network quality: Access to top local operators and 5G in major cities; no permanent throttling.Hotspot/tethering: Explicitly allowed by default.Fair-use policy (FUP): Transparent thresholds, reasonable roaming terms, and no punitive restrictions for normal travel use.Ease of use: Instant delivery, QR installation, quick top-ups, responsive support.Simology’s regional and country eSIMs score well on the above, particularly on price-per-GB transparency and hotspot inclusion.The best Simology picks for EuropeEsim Western Europe — top pick for most travellersWho it’s for: - City-hoppers doing 3–12 countries in one trip - Families or remote workers who rely on hotspot - Travellers wanting simple top-ups and a single eSIM across bordersWhat you get: - Broad multi-country coverage across Western Europe with 4G/5G where available - Hotspot/tethering enabled - Clear, upfront data allowances with straightforward price-per-GB - Friendly fair-use terms intended for travel (not permanent roaming)Why it’s hard to beat: - You avoid the SIM shuffle at borders and keep one APN and one data monitor - 5G in major hubs for quick downloads and video calls - Competitive price-per-GB compared with typical regional packsConsider if: - You’re mostly staying in one country (a local eSIM may be cheaper per GB) - You need calling minutes (data-only eSIMs use VoIP apps; pair with your primary SIM for voice/SMS)Check availability and covered nations on Esim Western Europe and confirm your route against Destinations.Country eSIMs — the best price per GB when you stay putIf your itinerary centres on a single country, local plans often win on value and sometimes on peak speeds.France: See Esim France for dense 5G in Paris, Lyon, Marseille and strong rail-corridor coverage. Excellent for city weekends and Riviera road trips.Italy: Esim Italy offers solid 5G in major cities and coastal belts; good for hotspots on trains and ferries.Spain: With Esim Spain, coverage is wide across cities and islands; great for digital nomads needing steady tethering.Choose a country eSIM when: - You won’t cross borders or only do a quick day trip - You want the lowest cost per GB and plan to stream or hotspot frequentlyTransatlantic and multi-region itinerariesConnecting through North America? Avoid airport Wi‑Fi hunting by pairing your Europe eSIM with a North America plan:USA only: Esim United StatesUS/Canada/Mexico: Esim North AmericaInstall both profiles before you fly, then toggle data lines per region. If you’re organising trips for teams or events, centralise management with For Business. Travel brands and creators can explore partnerships via the Partner Hub.Fair-use policies in Europe explained (and how they affect you)Fair-use policies exist to prevent abuse of roaming and unlimited plans. Here’s what matters in practice:Roaming vs “local”: Most Europe eSIMs are regional roaming bundles. That’s fine for travel, but networks may apply FUP while roaming, such as deprioritisation or caps during congestion.“Unlimited” usually isn’t: High-speed data often has a daily or total cap (e.g., 1–5 GB/day at full speed, then throttled). If a plan says unlimited, look for the high-speed allowance first.Hotspot limits: Some providers block tethering or throttle hotspot specifically. Simology plans allow hotspot by default unless stated otherwise.Country exclusions: Not every “Europe” plan includes Switzerland, the Balkans or microstates. Confirm the exact list on Destinations.Usage window: Plans run for a set validity period from first activation; unused data may not roll over.Practical takeaways: - Pick a plan with a clear high-speed allowance if you work on the go. - Expect speed variation at busy times or on rural routes; try different network selections if your device allows. - For long trips, buy a sensible base allowance and top up rather than chasing “unlimited”.Step-by-step: how to choose the right Europe eSIM1) Map your route - List every country and the number of days in each. - If 3+ countries, lean towards Esim Western Europe; otherwise a country eSIM may be cheaper.2) Estimate your data need - Light (maps, messages, occasional rides): 3–5 GB/week - Moderate (social, short video, hotspot for email): 6–10 GB/week - Heavy (HD video, frequent hotspot/video calls): 12–20 GB+/week3) Decide on 5G vs 4G - If you upload media, join video calls, or plan to tether often, choose 5G access where available.4) Confirm hotspot - Ensure your plan explicitly allows tethering if you’ll share data to a laptop or tablet.5) Plan your dual-SIM setup - Keep your home SIM active for calls/SMS, but set the eSIM as your data line and switch data roaming off on your primary SIM to avoid bill shock.6) Check device compatibility - Most recent iPhone, Samsung Galaxy, Google Pixel and other flagships support eSIM. If unsure, consult your device specs.7) Buy and install early - Purchase from Simology, scan the QR code, and add the eSIM before departure while on good Wi‑Fi.8) Test and label - Toggle mobile data to the eSIM briefly at home to confirm activation. Name it “Europe Data” (or country) to avoid confusion.Activation and on‑trip checklistBefore you fly: - Install your eSIM profile over Wi‑Fi. - Set the eSIM as “Mobile Data” line; turn data roaming off on your primary SIM. - Download offline maps; update apps while on Wi‑Fi.On arrival: - Toggle the eSIM data line on. - Ensure Data Roaming is enabled for the eSIM line. - If speeds seem slow, briefly toggle Airplane Mode or select a different partner network in Settings.During your trip: - Monitor data usage in your phone settings. - Hotspot when needed; disable when idle to save battery and data. - Top up through your Simology account if you’re running low.Pro tips to save data and avoid surprisesUse Low Data Mode/ Data Saver on your phone.Disable auto-play for video in social apps.Cache music and podcasts on Wi‑Fi.Prefer Wi‑Fi for big backups; pause cloud photo sync while roaming.Use Wi‑Fi calling for voice; WhatsApp/FaceTime use your existing number even on a data-only eSIM.For road trips, keep offline maps for every country you’ll cross.If you’ll be in the US before/after Europe, install Esim United States or Esim North America in advance.FAQ: Europe eSIMs1) Will my phone work with a Europe eSIM? - Most recent iPhone (XR/XS and newer), Google Pixel (3 and newer), and flagship Samsung devices support eSIM. Region-specific models vary. If in doubt, check your device settings for “Add eSIM” or consult the manufacturer’s specs.2) Can I use hotspot/tethering with Simology eSIMs? - Yes, Simology plans allow hotspot unless stated otherwise on the specific product page. Tethering performance depends on local network conditions.3) How fast is 5G in Europe? - In major cities, typical real-world 5G ranges from 150–500 Mbps, with higher peaks possible. Speeds vary by network, location, and time of day, and can be managed during congestion.4) I’m visiting 8–10 countries in two weeks. What’s best? - A regional plan like Esim Western Europe keeps things simple across borders. If you’ll spend 5+ days in a single country with heavy usage, add a local eSIM (e.g., Esim France or Esim Italy) for cheaper per‑GB data during that block.5) Do I need to show ID to buy an eSIM in Europe? - Most data-only eSIMs in Europe do not require ID, but requirements vary by country. If verification is required, Simology will prompt you during checkout.6) Can I keep my WhatsApp number and receive texts from my bank? - Yes. Your WhatsApp stays linked to your number. Keep your physical SIM active for SMS; set the eSIM as data-only and turn off data roaming on the primary SIM to avoid charges.The bottom lineThe best eSIM for Europe is the one that matches your route, data habits, and need for 5G and hotspot. For most travellers crossing multiple borders, Simology’s Esim Western Europe combines solid coverage, transparent allowances, and tethering without hoops. If you’ll camp in one country, local eSIMs like Esim France, Esim Italy or Esim Spain usually deliver the lowest price per GB. Flying via the US or Canada? Add Esim United States or Esim North America for smooth connectivity end to end.Next step: Compare coverage and pick your plan on Esim Western Europe.

30 Oct 2025
Simology API & SDK: Quick Start for Catalog, Checkout & Activation Webhooks

Simology API & SDK: Quick Start for Catalog, Checkout & Activation Webhooks

Integrating Simology’s eSIM into your app or site should be quick, safe and predictable. This guide shows you how to stand up a working flow end‑to‑end: pull a live catalogue, create a checkout, and handle activation webhooks to deliver eSIM credentials. You’ll get example endpoints, headers, sample payloads, sandbox tips, and robust error and retry strategies so you can go live with confidence.We assume you’re building for travellers and want a clean, reliable purchase and activation journey. The same patterns apply whether you’re selling a single-country plan like Esim United States or regional bundles such as Esim Western Europe and Esim North America. If you’re still shaping your plan range, explore available markets on Destinations and see what resonates with your audience. When you’re ready to partner, head to the Partner Hub or our For Business page to get access.What you’ll buildA minimal, production‑ready integration includes:Catalog: Fetch plans (SKU, coverage, allowance, validity, price) and display them.Checkout: Create an order/checkout session and direct the user to pay.Webhooks: Receive order status and eSIM activation credentials securely.Activation: Present LPA QR or SM‑DP+ + activation code in your UI.Post‑purchase: Poll or subscribe to status updates; offer top‑ups if supported.PrerequisitesA Simology partner account with API credentials: request access via the Partner Hub.Sandbox environment enabled (for test cards and simulated activations).Public HTTPS webhook endpoint (TLS 1.2+, supports POST, returns 2xx on success).Server ability to store secrets and verify signatures.Optional: SDK installed (Node.js or Python) or curl for initial testing.Tip: While you prototype, use live product copy from Destinations. For regional content and FAQs, see Esim France, Esim Italy and Esim Spain.Environments and authenticationTypical environment split:Sandbox base URL (example): https://sandbox-api.simology.ioProduction base URL (example): https://api.simology.ioAuthentication:Use the HTTP header: Authorization: Bearer YOUR_API_KEYSend JSON: Content-Type: application/jsonUse idempotency for POSTs: Idempotency-Key: a-unique-uuid-per-intentPro tips: - Rotate keys regularly; keep them server-side only. - Scope keys to least privilege; separate sandbox and production keys. - Log the response header request_id (if provided) for faster support.Step 1: Fetch the eSIM catalogueEndpoint (example): - GET /v1/catalog?country=US - GET /v1/catalog?region=western-europeExample request:GET /v1/catalog?country=US HTTP/1.1 Host: sandbox-api.simology.io Authorization: Bearer sk_sandbox_123 Accept: application/json Example response:{  "items": [    {      "sku": "US-5GB-30D",      "name": "United States 5 GB / 30 days",      "region": "US",      "coverage": ["US"],      "data_allowance_mb": 5120,      "validity_days": 30,      "price": { "amount": 14.99, "currency": "USD" },      "activation_method": "lpa",      "esim_type": "data",      "terms_url": "https://simology.io/esim-united-states",      "available": true    }  ],  "updated_at": "2025-01-10T09:12:44Z" } Implementation notes: - Cache catalogue responses for several minutes; invalidate on webhook or daily refresh. - Use query params to filter by country/region to reduce payloads. - Map regional SKUs to your UX—e.g., “Western Europe” → Esim Western Europe.Pro tips: - Localise currencies client-side only if your payment provider requires it; keep SKU and currency from the API authoritative. - Surface coverage and validity clearly; travellers value transparency.Step 2: Create a checkout session (order)Endpoint (example): - POST /v1/checkout/sessionsExample request:{  "customer": {    "email": "alex@example.com",    "country": "GB"  },  "items": [    { "sku": "US-5GB-30D", "quantity": 1 }  ],  "success_url": "https://yourapp.example/checkout/success?session_id={SESSION_ID}",  "cancel_url": "https://yourapp.example/checkout/cancel",  "metadata": {    "user_id": "u_789",    "source": "ios-app"  } } Example response:{  "id": "cs_abc123",  "payment_url": "https://pay.sandbox.simology.io/cs_abc123",  "status": "pending",  "expires_at": "2025-01-10T09:27:44Z" } Redirect the user to payment_url.On success, Simology will send a webhook (see next step) such as checkout.completed or order.paid.Error example:{  "error": {    "code": "sku_unavailable",    "message": "Requested SKU is not available in the selected region.",    "request_id": "req_9x8y7z"  } } Pro tips: - Always include a unique Idempotency-Key on POSTs to prevent duplicate orders. - Do not fulfil on the browser redirect alone; wait for the signed webhook.Step 3: Webhooks for checkout and activationExpose a POST endpoint, e.g., https://yourapp.example/webhooks/simologyExpected events (names may vary by integration): - checkout.completed — customer returned from payment - order.paid — funds confirmed; fulfilment can begin - activation.ready — eSIM credentials ready for delivery - order.failed or payment.failed — handle gracefullySecurity: - Simology signs webhook payloads. Expect a header like: - Simology-Signature: t=1736500000,v1=hex-hmac-sha256 - Verify HMAC using your webhook secret and the raw request body + timestamp t. - Reject if signature invalid or timestamp skew > 5 minutes.Example webhook: order.paid{  "type": "order.paid",  "id": "evt_123",  "created": "2025-01-10T09:20:02Z",  "data": {    "order_id": "ord_456",    "session_id": "cs_abc123",    "items": [      { "sku": "US-5GB-30D", "quantity": 1, "unit_price": 14.99, "currency": "USD" }    ],    "customer": { "email": "alex@example.com" }  } } Example webhook: activation.ready{  "type": "activation.ready",  "id": "evt_789",  "created": "2025-01-10T09:21:10Z",  "data": {    "order_id": "ord_456",    "line": {      "iccid": "8988307000001234567",      "smdp_plus": "LPA:1$sm-dp-plus.simology.net$ACT-CODE-1234",      "qr_url": "https://sandbox-api.simology.io/v1/qr/ord_456.png",      "valid_from": "2025-01-10T09:21:10Z",      "expires_at": "2025-02-09T23:59:59Z"    }  } } Retries: - Respond 2xx on success within 5 seconds. - Non-2xx triggers automatic retries with exponential backoff (e.g., 1m, 5m, 30m, hourly up to 48h). - Webhooks are idempotent; use the event id to deduplicate.Pro tips: - Store the full webhook event before processing; reprocess safely if needed. - Use a separate signing secret per environment; rotate on a schedule.Step 4: Deliver and activate the eSIMOnce you receive activation.ready: - If you display QR in-app: render qr_url or generate your own QR from the LPA string (smdp_plus). Confirm the screen brightness/instructions for scanning. - If you deliver manually: present the SM‑DP+ address and activation code clearly.UI checklist: - Show coverage and validity (mirror your catalogue details, e.g., Esim North America). - Provide concise device instructions (Settings > Mobile Data > Add eSIM). - Remind users to keep primary SIM for calls/SMS if needed, using data on eSIM. - Offer a link back to plan details (e.g., Esim United States) for FAQs.Step 5: Post‑activation status and top‑upsCommon endpoints (examples): - GET /v1/orders/{order_id} — check latest status. - GET /v1/lines/{iccid} — inspect data used/remaining. - POST /v1/topups — add data to an existing line.Example line status:{  "iccid": "8988307000001234567",  "status": "active",  "data": {    "used_mb": 1200,    "remaining_mb": 3920  },  "valid_until": "2025-02-09T23:59:59Z" } Pro tips: - Cache status for 30–60 seconds to avoid rate limits. - If you surface data usage, include a timestamp and note that roaming networks can report with slight delay.Errors, rate limits and observabilityHTTP status patterns: - 400 validation_error — your request is malformed (missing field, invalid SKU). - 401/403 auth_error — bad or expired credentials, wrong environment key. - 404 not_found — order/line ID not recognised. - 409 conflict — duplicate idempotency key with different payload. - 429 rate_limited — back off using Retry-After header. - 5xx server_error — transient; retry with backoff and jitter.Canonical error body:{  "error": {    "code": "rate_limited",    "message": "Too many requests. Try again later.",    "request_id": "req_123",    "retry_after": 30  } } Best practices: - Always log request_id and error.code. - Implement circuit breakers for persistent 5xx. - Respect Retry-After on 429; apply exponential backoff with jitter. - Use unique Idempotency-Key per action (e.g., “create checkout for cart 123”). - Monitor webhook delivery success rate and age of last processed event.SDK quick startWhile you can integrate with raw HTTP, SDKs speed up auth, idempotency and webhook verification. The shapes below reflect the examples above; adapt to your language and tooling.Node.js (example):import { Simology } from "@simology/sdk"; const sim = new Simology({ apiKey: process.env.SIMOLOGY_API_KEY, baseUrl: "https://sandbox-api.simology.io" }); const catalog = await sim.catalog.list({ country: "US" }); const session = await sim.checkout.create({  customer: { email: "alex@example.com", country: "GB" },  items: [{ sku: "US-5GB-30D", quantity: 1 }],  success_url: "https://yourapp.example/success?session_id={SESSION_ID}",  cancel_url: "https://yourapp.example/cancel" }); Webhook verification (pseudo):app.post("/webhooks/simology", express.raw({ type: "application/json" }), (req, res) => {  const signature = req.header("Simology-Signature");  const event = sim.webhooks.verify(req.body, signature, process.env.SIMOLOGY_WEBHOOK_SECRET);  // process event.type ...  res.sendStatus(200); }); Python (example):from simology import Simology sim = Simology(api_key=os.getenv("SIMOLOGY_API_KEY"), base_url="https://sandbox-api.simology.io") catalog = sim.catalog.list(country="US") Tip: Keep the webhook route using raw body to preserve signature integrity.Security and privacy essentialsStore only what you need (e.g., order_id, sku, iccid). Avoid storing full QR images if the LPA string is sufficient.Encrypt secrets at rest; restrict access via IAM.Validate webhook payload against expected schema before acting.Do not render raw error messages to end users; translate to helpful guidance.Go‑live checklistSandbox to production switch with environment flags.API key rotation plan and secret storage verified.Idempotency implemented on all POST operations.Webhook endpoint verified with signature checks and 2xx acks.Observability: logs capture request_id, event.id, order_id, iccid.Rate limit handling and backoff tested.Happy path and failure path user messaging in place.Regional catalogue mapped to your content (e.g., Esim France, Esim Italy).FAQHow do sandbox and production differ? Sandbox uses test payment and simulated activation events. Payload shapes mirror production, but no real provisioning occurs. Use separate API keys and webhook secrets per environment.Can I test activation without scanning a QR? Yes. Use the LPA string (SM‑DP+ and activation code) from activation.ready to test your UI. In sandbox, you can display it without provisioning a real profile.What happens if my webhook endpoint is down? Simology retries with exponential backoff for a defined window (for example, up to 48 hours). Keep processing idempotent and return 2xx only after you have safely stored/handled the event.How should I handle plan regions in my UX? Keep your SKUs aligned with clear coverage descriptions (country vs region). Link to destination pages like Esim United States or Esim Western Europe for clarity, and aggregate them under Destinations.Can I issue refunds or cancellations via API? Many setups support POST /v1/refunds or cancelling unpaid checkouts. Always wait for webhook confirmation (refund.processed) before altering customer entitlements.Do you support top‑ups and usage queries? Yes in most cases—use the lines and topups endpoints as shown. Cache usage responses briefly and inform travellers about reporting delays when roaming.Next step: Ready to get credentials and sandbox access? Visit the Partner Hub to kick off your integration.

30 Oct 2025