Free eSIM Activation QR Code Generator
Build standard LPA: activation QR codes that iPhone (iOS 17.4+) and Android (13+) scan to provision an eSIM profile from your SM-DP+ server.
- QR Generator
- 명함 디자이너
- WiFi 카드 인쇄
- 일괄 CSV (500개 코드)
- 40개 템플릿
- 20개 언어
이 바코드 형식은 전경색과 배경색만 사용하여 단색으로 렌더링됩니다. 템플릿, 점/눈 모양, 그라디언트, 프레임, 중앙 로고는 QR 코드에만 적용되며 여기서는 숨겨집니다.
템플릿 30개 더 보기
위의 버튼을 사용하여 스타일을 저장하여 즐겨찾기를 여기에 저장하세요.
또는 내장 아이콘 선택:
108개 아이콘 더 보기
QR 뒤에 낮은 불투명도로 표시됩니다. 사진을 통해서도 스캔되도록 EC=H를 자동 적용합니다.
일괄 생성
CSV를 업로드하여 한 번의 배치로 최대 500개의 QR 코드를 생성하세요. 각 행은 고유한 QR이 되며, 템플릿을 선택하거나 행별로 21가지 속성(색상, 프레임, 도트/아이/아이볼 스타일, 그라디언트, 투명도, 크기, 오류 정정, 형식, 내장 로고 등)을 재정의할 수 있습니다.
21개 열: type, data, filename, frametext, frame, template, fgcolor, bgcolor, size, ec, dotstyle, eyestyle, format, logo, gradient, g2, gtype, gangle, transparent, eyeball, eyecolor. type과 data만 필수입니다. data 내의 필드를 구분하려면 |을 사용하세요(예: ssid|password|WPA).
URL, WiFi, vCard, MeCard, Email, SMS, Event, Location, UPI, SEPA, PayPal, Crypto, Micro QR, rMQR을 포함한 20가지 QR 유형을 모두 지원합니다. 샘플 CSV를 다운로드하여 모든 열, 40개 템플릿, 11개 프레임 스타일, 12개의 내장 로고를 확인해 보세요.
1. 샘플 CSV 다운로드 · 2. Google Sheets, Excel, Numbers 또는 텍스트 에디터에서 편집 · 3. 여기에 업로드
QR 전체 – 유형, 모든 필드 값, 스타일, 프레임, 로고, 명함 디자인 –을 단일 .qr.json 파일로 저장합니다. 나중에 로드하여 한 번의 클릭으로 모든 것을 재현합니다.
QR 코드를 생성하려면 내용을 입력하세요
법정에서도 유효한 전자서명
Abundera Sign은 기본 전자서명을 넘어섭니다. 모든 문서에 암호화 증명, 독립 검증, 변조 방지 증거 패키지가 포함됩니다.
- 자동 생성되는 법원 준비 증거 패키지
- 개인 문서 봉인 — 즉시 변조 감지
- 5개의 독립 시스템에 고정 — 단일 장애 지점 없음
How eSIM Activation QR Codes Work
Every modern eSIM provisioning flow ends in a QR code. The format is defined by the GSMA's SGP.22 Remote SIM Provisioning specification: a payload that begins with LPA: (Local Profile Assistant) and encodes the address of the carrier's SM-DP+ server plus a one-time matching ID. When the device's eUICC scans the QR, it contacts the SM-DP+, downloads the profile, and installs it — no SIM tray, no physical card, no carrier-store visit.
The exact payload format is LPA:1$smdp.example.com$matching-id[$$confirmation-code]. The leading 1 is the activation code version. The optional confirmation code adds a second factor that the user types after scanning. Carriers, MVNOs, and IoT-platform operators all generate activation codes in this format.
Use cases
- Carrier self-service portals — issue an eSIM from a customer dashboard and email/show the QR.
- Travel eSIMs — Airalo, Holafly, GigSky and the rest deliver QR codes by email after purchase.
- IoT fleet provisioning — embed the QR on the device label so installers can onboard with a phone scan.
- BYOD enterprise rollouts — IT generates activation codes per employee.
- Re-provisioning a wiped phone — keep the QR archived; rescan to reinstall after device loss.
Required fields
- SM-DP+ Address — the FQDN of the carrier's Subscription Manager — Data Preparation server (e.g.
rsp.truphone.com). - Activation Code (matching ID) — the one-time token that authorises this specific profile download.
- Confirmation Code — optional second factor; the device prompts the user to type it after scan.
Compatibility
iOS 17.4 and later scan eSIM QRs from any camera. Earlier iOS requires opening the camera in the eSIM setup wizard. Android 13+ supports direct scanning system-wide; Pixel and Samsung have shipped eSIM scanning since Android 11. Most major eUICC vendors (G+D, Thales, Idemia, Kigen, eSIM.me) accept the same LPA format.
26개 언어 지원
완전히 번역된 UI, 원어 스크립트 렌더링, 아랍어 및 우르두어 우→좌 지원.
Frequently Asked Questions
Is the activation code single-use?
Yes — every legitimate matching ID is single-use by design. Once a device redeems the code, the SM-DP+ marks it consumed and any future scan returns 'profile not available'. If your carrier supports re-issuing, request a fresh code rather than reusing the QR.
Will iPhone or Android show the carrier name automatically?
Yes. The SM-DP+ returns metadata (carrier name, plan name, optional icon) before installation, so the user sees a confirmation screen with branding before the profile is installed.
Can I encrypt the activation code so a phone screenshot doesn't expose it?
The matching ID is one-time and tied to a specific SM-DP+, so leakage is bounded — anyone capturing the QR before the legitimate user redeems it can install the profile, but only once. For high-value deployments, add a confirmation code so the QR alone is insufficient.
What if my carrier hasn't given me a QR but only the SM-DP+ and matching ID strings?
Paste them into the form here and we'll build the QR from the standard LPA format. This is exactly what carrier self-service portals do under the hood.
Does this work for dual-SIM phones?
Yes. The eSIM is added as an additional line; the physical SIM remains active. iOS supports up to eight stored eSIM profiles (one active at a time alongside the physical SIM); Android phones vary by manufacturer.
Can I use this for IoT M2M eSIMs?
If your eUICC supports SGP.22 consumer remote provisioning, yes. Many M2M deployments use SGP.32 (the IoT-specific spec) which has a different bootstrap flow but ultimately reads the same LPA format. Consult your eSIM vendor.
Why does my QR say 'invalid activation code'?
Three usual causes: (1) the matching ID has already been redeemed, (2) the SM-DP+ FQDN is wrong (check for trailing slash or http:// prefix — strip both), (3) the carrier scoped the matching ID to a specific eUICC and your device's EID doesn't match. Contact the carrier support line.