Phone numbers, eSIMs and email aliases.
PikaSIM
Anonymous eSIM. 190+ countries. BTC/XMR. No account, no identity.
pikasim.com
- Zero KYC
- US
- Evidence and facts →
Anonymous eSIM. 190+ countries. BTC/XMR. No account, no identity.
Evidence and facts
Evidence and facts
Why evidence is 94/100Formula 3.1
- Source coverageMaterial claims checked against current sources
- +70
- Review ageOldest recorded check is 63 days old
- +24
Specs
Review analysis, source material, related services, and history
About
Travel eSIM service with no account or email required, paid via BTCPay on infrastructure hosted in Finland.
Analysis
PikaSIM sells travel eSIMs across 190 or more countries with no account, email or identity required, paid through BTCPay-processed Bitcoin, Lightning or Monero on infrastructure the description locates in Finland.
The operators are unidentified and the service is unvetted with no disclosed funding, so the crypto-only checkout is the private path while card or Stripe payment would attach email and payment metadata.
Travel data users prioritizing a crypto-only, no-account purchase flow who accept an unidentified, unvetted operator.
Corporate identity
Registry-sourced, not audited. The facts below come from cited web research rather than a direct registry query. Each claim links its own source.
- LEGAL ENTITY
- CodeBru, Incsource ↗
- REGISTERED ADDRESS
- 1100 E 16TH Ave Unit 4, Denver, CO 80218-1566, United Statessource ↗
Frequently Asked Questions
Is identity verification required?
No identity verification is recorded for typical use. Official terms state a strict no-KYC policy: no identity documents, no account registration, no phone number and no required email for crypto purchases.
Which payment methods are accepted?
Please check the provider site for accepted payment methods.
Where is it available?
Recorded availability: GLOBAL.
Is the operator based in a Five Eyes country?
Yes. The recorded jurisdiction is US, a Five Eyes country (US, UK, CA, AU, NZ). This is jurisdiction context and does not by itself establish that a service is safer or less safe.
How are identity, operator, and evidence fields reported?
Identity exposure is level 0 of 4. A hosted operator is recorded. Jurisdiction is shown as context, not a safety verdict. Evidence confidence is 94/100 and recorded risk is standard.
Sources and history
Terms and privacy policy
No changes to the documents we watch since we started checking on 9 Aug 2026. Last checked 9 Aug 2026.
Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.