Free BLIK QR Code Generator (Poland)

Host your PDF anywhere, Google Drive (use the "anyone with link" share URL), Dropbox, your own server, S3, etc. Paste the public link here. We encode the URL so the QR works forever and never depends on us. Tip: for Google Drive, replace /view in the share URL with /preview for a cleaner mobile view.

Any downloadable file, installer (.exe / .dmg / .deb / .apk), archive (.zip / .tar.gz), document, dataset. Host it anywhere; we encode the URL. The user's browser handles the download per its own MIME-type rules.

JPEG, PNG, WebP, GIF, or HEIC, host it anywhere. Mobile browsers open the image full-screen; desktop browsers show it inline. Common pattern: print on flyers / business cards / packaging so a scan opens a product photo or gallery.

YouTube and Vimeo URLs open natively in their apps on phones. Direct .mp4 / .webm files open inline in any modern browser. Host self-encoded video on your own server, S3, or Cloudflare R2 and paste the URL.

MP3 / OGG / WAV / FLAC / M4A direct URLs play inline in mobile browsers. Spotify (open.spotify.com/track/…) and SoundCloud (soundcloud.com/…) URLs open in their apps. Apple Music / Bandcamp / Tidal links also work.

This menu is too big to encode, point at a hosted menu URL instead. See /menu-qr-code/ for the recommended approach.

Build the menu inline, every item lives inside the QR code itself. Best for food trucks, pop-ups, and single-product cafes. Larger menus should point at a hosted URL instead.

Paste your form's share link, either the short forms.gle/… or the long docs.google.com/forms/d/e/…/viewform form. We auto-prefer forms.gle when both are available since the shorter URL produces a denser QR. Works for surveys, registrations, RSVPs, lead capture, classroom polls.

Local uploads stay in your browser and only appear on the printed card. The QR data uses the URL above.

Entered in your local timezone. Saved as UTC so anyone who scans the QR sees the right wall-clock time in their own timezone.

Scanning opens the attendee's contact card. Event name and session are recorded in the NOTE field so the attendee remembers where they met.

Tip: right-click any spot on Google Maps and copy the coordinates

Use this if you're sharing a receiving address to accept a payment (BIP-21 bitcoin: URI, Ethereum EIP-681, and equivalents). Do not paste a private key, seed phrase, or extended private key (xprv), those control the wallet, not a single payment. Double-check the receiving address in the generated QR matches what you pasted; chain-agnostic address-swap attacks exist.

A red Swiss flag is automatically overlaid on the QR, required by Swiss banks.

Paste a BOLT11 invoice (lnbc...) or a Lightning address. We prefix with the lightning: URI scheme so any Lightning wallet can scan it.

Use this if you're enrolling a new 2FA account in an authenticator app (Google Authenticator, Authy, 1Password, Bitwarden). Do not screenshot, email, or photograph this QR, the secret inside it is a permanent key to the account.

Compatible with Google Authenticator, Authy, 1Password, Bitwarden, and any standard TOTP app.

Use this if you're provisioning a counter-based hardware token (YubiKey OTP) or a system without a reliable clock. Do not use when TOTP will do, HOTP counters drift, and recovery is harder after a dropped sync.

HOTP (RFC 4226) is the counter-based sibling of TOTP. Use it for hardware tokens like YubiKey OTP or for systems without reliable clocks. Same otpauth:// scheme; counter increments per code instead of advancing on time.

Use this if you're a carrier or MVNO issuing an eSIM activation profile to a customer (iOS 17.4+ / Android 13+). Do not share this QR after it's been scanned, the SM-DP+ activation is usually single-use and the profile belongs to one device.

GSMA SGP.22 activation code per the LPA spec. iOS 17.4+ and Android 13+ scan these directly to provision eSIM profiles. Carriers issue the SM-DP+ address and matching ID; the confirmation code is optional second-factor.

Per RFC 3261, opens a SIP softphone (Linphone, Zoiper, Bria, etc.) and dials the address. sips: forces TLS for signalling. Works with Asterisk, FreeSWITCH, 3CX, and any standards-compliant PBX.

Opens the system MMS composer to send a multimedia message (text + image/audio/video attachment). Distinct from sms: in that the recipient receives an MMS-formatted message. iOS, Android and most carrier apps honour this scheme.

Paste the QR URL from your Alipay Receive Money page (Settings → My QR Code → Save). We pass it through verbatim. The Alipay app, AliPayHK, and any device with the Alipay+ scanner will recognise the URL or QR.

Personal receive codes start with wxp://f2f. Merchant codes are https://payapp.weixin.qq.com/... URLs from the Weixin Pay merchant portal. Paste either; we encode verbatim. The WeChat app and any Weixin-Pay-enabled scanner will resolve it.

Swish is Sweden's national P2P / merchant mobile-payment service. Payee can be a private mobile number (Swish-number) or a 1234-style merchant alias. The Swish app on iOS and Android scans the standard swish://payment?data=... URI.

Vipps is Norway's dominant mobile-payment app (now Vipps MobilePay across the Nordics). Send to phone emits a vipps://send?... deeplink for P2P; Merchant short-link wraps a https://qr.vipps.no/... URL.

Paste the link from your Mercado Pago Cobrar page (the https://mpago.la/..., https://link.mercadopago.com.br/..., or full mercadopago.com short-link). Works across MP apps in Argentina, Brazil, Mexico, Chile, Colombia, Uruguay and Peru.

Use this if you need pharma / medical / direct-part-marking symbology or you're encoding for industrial imagers. Do not use for consumer-facing signage, Apple iPhone cameras do not decode Data Matrix natively.

Data Matrix is a square 2D matrix barcode (ISO/IEC 16022) used in healthcare, electronics, manufacturing, and direct-part marking. Holds up to ~2,335 alphanumeric characters in a single tag. Note: this is not a QR code, QR-only styling (eyes, dots, gradients, frames, logos) is disabled and the basic monochrome render is used.

Use this if you're generating boarding passes, transit tickets, or electronic-ID payloads for dedicated scanners. Do not use for public marketing print, most phone cameras won't decode Aztec reliably.

Aztec Code (ISO/IEC 24778) is the 2D barcode used by airline boarding passes, train tickets, and electronic ID. Designed to scan well on phone screens and at low contrast. Holds up to ~3,067 alphanumeric characters. Not a QR; QR-only styling is disabled.

Use this if you're printing an IATA-compliant boarding pass (Aztec, QR, or PDF417) for gate scanners at any of the 200+ airlines that implement BCBP / Resolution 792. Do not use this to board a real flight you didn't check in for, the format carries no cryptographic signature; airline gate systems validate against their own DCS, not against the QR itself.

IATA Resolution 792 / BCBP Implementation Guide v7. Encode as Aztec for mobile boarding passes, PDF417 for printed Type-A stock, or QR for modern gates. We build the mandatory M1 header + a single leg; paste the full BCBP in Advanced for multi-leg itineraries.

Use this if you need stacked-linear barcode for driver's-licence parsing, boarding passes, airbills, or AAMVA workflows. Do not use for normal consumer phone-camera signage, coverage is uneven across readers.

PDF417 (ISO/IEC 15438) is a stacked linear barcode used on US driver's licences, passports, FedEx airbills, and AAMVA-encoded ID cards. Holds up to ~1,800 ASCII characters. Not a QR; QR-only styling is disabled.

Use for legitimate purposes only: AAMVA parser testing, kiosk & age-gate development, accessibility tools, and demoing AAMVA workflows. Producing a counterfeit government ID is identity fraud and is prosecuted as a felony in every US state. Use real data only when you own the source license, or use synthetic data clearly marked as such.

Renders as a PDF417 barcode following the AAMVA Card Design Standard. Scan it back with this site's scanner to see the structured License Preview parser in action.

Code 128 (ISO/IEC 15417). Variable-length, high-density, encodes the full ASCII set. Used in shipping labels (UPS, FedEx, DHL all use it for their internal tracking), supply chain, and industrial labelling.

Code 39 (ISO/IEC 16388). The original alphanumeric barcode, supported by every scanner ever made. Used in healthcare patient bands, DOD military logistics (LOGMARS), and inventory tagging.

Code 93, Symbol Technologies' more compact successor to Code 39. Mandatory two checksum characters (C and K) make it more reliable on scuffed labels.

Codabar (NW-7), used by US blood banks, FedEx airbills (legacy), libraries (US/CA/EU), and photo finishing. Self-checking; does not require a check digit.

EAN-13 / GTIN-13, global retail product identifier. Used outside North America (which uses UPC-A) on every retail consumer product. Use the 12-digit GS1 number; the 13th check digit is computed for you.

EAN-8 / GTIN-8, compact retail product identifier for small packages where EAN-13 won't fit (chewing gum, batteries, etc.).

UPC-A / GTIN-12, North American retail product identifier. Use the 11-digit GS1 number.

UPC-E, compact 8-digit zero-suppressed variant of UPC-A for small packages.

ITF-14 (Interleaved 2 of 5), GS1's standard for shipping cartons / outer cases. Identifies the product inside (GTIN-14). Used by every major retailer and 3PL warehouse.

Vehicle Identification Number per ISO 3779. Encoded as a Code 39 barcode for compatibility with state DMV scanners, automotive registries, and insurance/title workflows. The 9th character is a check digit (auto-validated, not auto-computed, input invalid VINs are still encoded for testing).

Paste the link from your Payconiq merchant portal, typically https://payconiq.com/t/1/... for transactions or https://payconiq.com/l/1/... for static merchant QRs. Scanned by Payconiq, Bancontact, KBC Mobile, Belfius, ING, BNP Paribas Fortis, and most Benelux banking apps.

EPC QR Code (EPC069-12 / Girocode), the European standard for SEPA Credit Transfer initiation via QR. Supported by most European banking apps including Sparkasse, ING, KBC, BNP Paribas, Rabobank, and all EPC-compliant banks.

Paste the URL to your .pkpass file or Apple Wallet deep link. Scanning opens the pass directly in Apple Wallet on iOS devices.

Paste the Google Wallet save link from the Google Pay API or your pass issuer. Scanning opens the pass directly in Google Wallet on Android devices.

Use this if you want to move a public SSH key (id_ed25519.pub, id_rsa.pub) to another machine by QR. Do not paste a private key (anything labeled PRIVATE KEY, id_ed25519 without the .pub suffix). A QR is not an encrypted channel; if you photograph the scanned screen, the key is on that photo.

Encodes the entire authorized_keys line. Scan to copy/paste the key onto a new machine.

Use this if you're sharing an OpenPGP public key block (-----BEGIN PGP PUBLIC KEY BLOCK-----). Do not paste a private key block (PGP PRIVATE KEY BLOCK). Anyone who scans the code reads the payload; only public material belongs here.

For very long keys, use rMQR landscape or split into multiple QRs. Standard QR caps around ~2KB.

Use this if you're provisioning a WireGuard peer and need to move a .conf to a phone or tablet. The config contains the peer's PrivateKey, treat the QR like the private key itself. Do not screenshot, email, or photograph it; delete the rendered QR from shared screens as soon as the device has imported it. Rotate the key if the QR is ever captured by a camera that isn't the target device.

The official WireGuard mobile apps scan these directly. Never include your private key in a printed QR, only digital sharing.

Use this if your WebAuthn server issued a FIDO:/ URI for cross-device passkey sign-in, or if you want a QR that opens your passkey-management page. Do not use this to "create" a passkey, the URI is issued by your relying party; we only wrap it as a QR.

Use this if your healthcare provider, state health department, or health-wallet app gave you a shc:/ URI (vaccination record, lab result, discharge summary, prescription) and you want to share it as a QR code. Do not use this to "create" a health card, the cryptographic signature is issued by the health authority; we only wrap the URI as a QR.

The URI starts with shc:/ followed by digits. If your card is chunked (shc:/1/2/..., shc:/2/2/...), paste one chunk at a time and generate one QR per chunk, SHC verifiers scan them in sequence. Single-chunk payloads fit in a V22 QR (~1,191 digits).

Use this if you're a brand owner preparing for the GS1 Sunrise 2027 cutover or you need a single code that carries product identity + batch/expiry/serial. Do not use as a standalone marketing QR, retailers' POS systems will treat it as inventory data first, URL second.

GS1 Digital Link, the Sunrise 2027 successor to EAN-13. Resolver domain defaults to id.gs1.org. GTIN check digit is validated live.

Use this if you're a manufacturer or importer preparing for the EU Digital Product Passport (DPP) mandate, operational 19 July 2026 under ESPR Regulation (EU) 2024/1781. Each individual product instance sold in the EU needs a scannable QR or Data Matrix resolving to its DPP record. Do not use this as a marketing QR, the URL should resolve to structured DPP data (JSON-LD), not a landing page.

The QR encodes a GS1 Digital Link URL pointing to your DPP record, the same URI syntax as GS1 Digital Link (Article 10 mandate explicitly references it). Your resolver must return structured DPP data (GS1 Digital Link resolver or custom JSON-LD endpoint) and the unique identifier must comply with ISO/IEC 15459:2015.

Paste the share link from the Spotify app, or just the ID. We build the open.spotify.com URL automatically.

Format depends on platform, for Mastodon use @user@instance, for Bluesky use handle.bsky.social, for Nostr paste the npub key.

Geo URI (RFC 5870) opens directly in any maps app on the device (Google Maps, Apple Maps, OsmAnd, etc.) without picking a vendor.

Standard BitTorrent magnet link. Scanned by any BitTorrent client that supports URI scheme handlers.

Entered in your local timezone. Saved as UTC so anyone who scans the QR sees the right wall-clock time in their own timezone.

Scanning the QR opens the native calendar app with a Subscribe prompt. Standard webcal:// URI scheme.

Your entire bio page is encoded into the QR's URL hash, no backend, no account, no tracking. The /bio/ page decodes and renders it client-side.

Paste the 11-character video ID, a youtu.be URL, or a youtube.com/watch URL. We normalize to youtu.be/{id}.

Opens the Apple Music app (or the web player) directly to the song, album, playlist, or artist. Storefront controls which country's catalog is used.

Find your Place ID at https://developers.google.com/maps/documentation/places/web-service/place-id. Scanning opens the Google Review dialog for your business.

The slug in your Yelp URL after /biz/. Scanning opens the Yelp Write A Review page.

The d + numeric ID from your TripAdvisor listing URL. Scanning opens the Write Review page.

Routes happy customers to your public review page and unhappy ones to a private channel. The branching happens in the user's browser via a hash splash at /review/, with no backend and no tracking. Important: Google's review-gating policies prohibit hiding negative reviews. Use this only to collect private feedback in addition to allowing all customers to leave a public review if they choose.

Tries the deep link first; if the app isn't installed, shows the right store button (App Store on iOS, Play Store on Android). On desktop, opens the web fallback. OS detection happens at /app/, no backend. The deep link must be an https universal link or Android app link; custom schemes such as myapp:// are ignored.

Paste any meeting invite link. For Zoom, Google Meet, and Teams we extract the canonical join URL automatically.

If a URL is provided, the QR opens the page with your promo code appended as ?code=YOURCODE. Without a URL, the QR encodes the plain promo code text.

Requires the Venmo mobile app. Desktop browsers will redirect to venmo.com instead.

Opens the Cash App with your $cashtag pre-filled.

Creator-support platforms. We build the canonical profile URL automatically.

TWINT is Switzerland's most popular mobile payment app, supported by every Swiss bank.

Bizum is the dominant P2P payment service in Spain, operated by the consortium of Spanish banks.

Accepted by every Singapore bank app. Uses the EMVCo Merchant-Presented Mode QR standard.

Japanese JPQR unified QR payment standard. Accepted by PayPay, LINE Pay, Rakuten Pay, and 20+ Japanese payment apps.

Hong Kong Faster Payment System. Works with every Hong Kong retail bank and HKICL's FPS service.

DuitNow by PayNet, Malaysia's national real-time payment network. Works with all Malaysian retail banks and e-wallets.

MoMo e-wallet URI, Vietnam's most-used mobile payment app with 30+ million users.

M-PESA by Safaricom, Kenya's dominant mobile money network. EMVCo MPM QR, readable by the M-PESA app and Safaricom-compatible scanners.

BLIK, Poland's dominant mobile payment system used by all major Polish banks. The 6-digit code is time-limited and confirms the transaction in the payer's banking app.

Interac e-Transfer, Canada's national real-time money transfer service, supported by all major Canadian banks and credit unions.

MB WAY, Portugal's leading mobile payment app linked to SIBS/Multibanco. The phone number identifies the recipient in the MB WAY network.

GCash, the Philippines' largest mobile wallet with 80+ million users. EMVCo MPM QR format, scannable by the GCash app.

Maya (formerly PayMaya), major Philippine e-wallet and digital bank. EMVCo MPM QR format, scannable by the Maya app.

Kakao Pay, South Korea's leading mobile payment platform from KakaoTalk (50+ million users). Paste a merchant code or a full https://qr.kakaopay.com/ link from your Kakao Pay for Business dashboard.

Naver Pay, major South Korean e-wallet operated by Naver, integrated with the Naver shopping and content ecosystem. Paste a merchant ID or a full https://npay.naver.com/payments/ link.

LINE Pay, mobile wallet from LINE Corporation, widely used in Japan, Taiwan, and Thailand. Paste a merchant ID or a full https://line.me/pay/ link from your LINE Pay merchant dashboard.

iDEAL, the Netherlands' national bank transfer payment scheme, used by 70%+ of Dutch online shoppers. Paste the full iDEAL payment URL issued by your payment processor (Mollie, Stripe, Adyen, etc.).

Boleto Bancário, Brazil's ubiquitous printed-invoice payment method, accepted by every Brazilian bank. Paste the 44-digit linha digitável (bank slip) or the 48-digit concessionária code. Banking apps recognize the digit pattern and auto-fill the payment.

QRIS, Bank Indonesia's unified QR (EMVCo MPM, live cross-border to Thailand, Malaysia, Singapore, Vietnam via ASEAN RPC). Accepted by every Indonesian bank and e-wallet (GoPay, OVO, DANA, ShopeePay, LinkAja). The QR encodes the NMID + merchant name + optional fixed amount.

VietQR, Vietnam's national unified QR built on NAPAS + the ASEAN Regional Payment Connectivity standard. Every Vietnamese retail bank app scans it. Bank BIN examples: 970436 (Vietcombank), 970418 (BIDV), 970422 (MB Bank), 970415 (VietinBank).

QR Ph, the Philippines' national unified QR standard from Bangko Sentral ng Pilipinas (BSP), sitting above the individual e-wallets (GCash, Maya) and all major retail banks. Interoperable EMVCo-MPM format.

KHQR, National Bank of Cambodia unified QR. Live cross-border to Thailand (PromptPay), Laos (Lao QR), Vietnam (VietQR). Supports both USD and KHR since Cambodia is dual-currency.

Lao QR, Bank of the Lao PDR unified QR. Accepted by BCEL, LDB, JDB, and every Lao retail bank app. Cross-border live with Thailand (PromptPay), Cambodia (KHQR), Vietnam (VietQR).

PayShap, BankservAfrica's real-time rapid payment rail, live across every major South African bank (Absa, FNB, Nedbank, Standard Bank, Capitec, Discovery, Investec, TymeBank). Send in <10 seconds by mobile number or ShapID.

Use this if you want to share your Zelle-registered email or US phone number as a scannable contact card. Note: Zelle has no universal QR URI scheme, scanners open your chosen contact method; the payer still initiates the transfer from their own banking app. This QR is a convenience, not a direct-pay link.

Zelle is built into every major US bank app (Chase, Bank of America, Wells Fargo, Capital One, Citi, and ~2,000 others). This QR encodes a mailto: or tel: that opens the recipient's contact card. The payer then opens their banking app, taps Zelle, and pastes the email / phone, the actual transfer happens bank-to-bank, never through us.

Satispay, Italy's licensed payment-institution mobile wallet. Accepted by 300,000+ Italian merchants. Customers scan the QR from the Satispay app; no card data, no typing PIN.

Use this if you're piloting Drex (Brazil's wholesale/retail CBDC, launched 2026 by Banco Central do Brasil on a Hyperledger Besu DLT). Drex settles via the existing Pix infrastructure; most merchant integrations accept the same Pix EMVCo-style QR with a Drex flag.

Drex, Brazil's tokenised central bank digital currency, Phase-1 live 2026. Settles through existing Pix QR infrastructure during the transition. For pure-Pix transfers, use Pix.

Use this if you're testing Digital Euro pilot rails (ECB preparation phase, 2023–present; live retail issuance decision expected late 2026). Format follows EPC / SCT-Inst QR patterns with a CBDC flag. Not yet a production payment method, pilot participants only.

Digital Euro, the ECB's proposed retail CBDC. Preparation phase runs through Oct 2026; live issuance pending Governing Council decision. For standard euro bank transfers, use SEPA or EPC Girocode.

Digital Ruble, Bank of Russia CBDC. Pilot banks began retail rollout September 2026; mandatory distribution via commercial banks scheduled phase-in through 2027. Each wallet address is issued by a participating bank.

e₹ / Digital Rupee, the RBI's retail CBDC, live via pilot banks since December 2022. QRs share UPI-style VPAs with an @{bank}digital suffix (e.g. @icicidigital, @hdfcdigital). Interoperable with the existing UPI QR landscape since October 2023.

Use this if you want a reusable Lightning receive QR. BOLT12 offers (lno1...) don't expire and can be scanned repeatedly, unlike BOLT11 invoices. Not all Lightning wallets support BOLT12 yet (Phoenix, Core Lightning, LNDk, Zeus partial); check your wallet before handing out printed QRs.

BOLT12 "offers" are the reusable successor to BOLT11 Lightning invoices, no per-payment re-issuance, no 1-hour expiry. Generated server-side by Core Lightning (lightning-cli offer), LNDk, or Strike. Our QR is a passthrough.

Use this if you're sharing a Monero receiving address or subaddress to accept a payment (monero:<address>?tx_amount= format). Do not paste a seed phrase, view key, or spend key, those control the wallet, not a single payment. If privacy matters for the amount, use a subaddress: regenerate it per recipient so on-chain observers can't link payments.

Monero (XMR) is the largest privacy-by-default cryptocurrency. QR emits a monero: URI per the community-standard scheme; GUI and CLI wallets, Cake, MyMonero, Feather, and Monerujo all parse it.

Solana Pay emits a solana: transfer-request URI per the Solana Pay spec. Scanning with Phantom, Solflare, or any Solana Pay-compatible wallet prefills the recipient, amount, and token, then hands off to the wallet for a one-tap confirm.

LNURL (LUD-01) is a bech32-encoded Lightning URL; a Lightning address (LUD-16) looks like an email address and resolves to a LNURL-pay endpoint. Both scan straight into any Lightning wallet, Wallet of Satoshi, Phoenix, Muun, Zeus, Alby.

Emits an xrpl: payment URI. Most custodial exchanges route deposits through a single hot wallet and identify each customer by destination tag, if your recipient gave you one, include it or the exchange can't credit the right account.

Emits a web+stellar:pay URI per SEP-0007. Scanning with Lobstr, Freighter, or any SEP-7-aware wallet opens a prefilled payment screen. Leave the asset code blank to request native XLM; a memo is often required by exchanges to credit the right sub-account.

Emits an algorand:// payment URI. Leave the asset ID blank to send native ALGO; set it to an Algorand Standard Asset ID (like USDC's 31566704) to request a token transfer instead. Pera Wallet and Defly both parse this scheme.

Emits a web+cardano: URI per CIP-13. Yoroi, Eternl, and Daedalus all parse this scheme to prefill a send screen with the recipient and amount.

Encodes the SS58 address verbatim, no URI scheme. Polkadot.js, Nova Wallet, SubWallet, and Talisman all recognise a bare SS58 address in a QR and offer to send to it.

BIP-353 lets a Bitcoin address hide behind a human-readable user@domain handle, resolved via a DNSSEC-signed TXT record instead of a payment processor. The QR carries the ₿-prefixed handle; a compatible wallet resolves it to a fresh address at scan time.

Safety note: a Cashu token is a bearer instrument, whoever holds the token can redeem it, like cash. Don't post this QR publicly or leave it on a screen anyone can photograph.

Cashu is a Chaumian ecash protocol built on Bitcoin/Lightning. A token (cashuA... / cashuB...) is redeemed by whoever scans it, there's no on-chain settlement until it's swapped at the mint. Nutstash, Cashu.me, and eNuts all read this QR.

Safety note: a Fedimint note is a bearer instrument, whoever holds it can redeem it, like cash. Don't post this QR publicly or leave it on a screen anyone can photograph.

Fedimint issues Chaumian ecash notes backed by a federation of guardians rather than a single custodian. A note (fed1...) redeems on whichever federated mint issued it, scan it into a Fedimint-compatible wallet before the federation goes offline.

Payjoin (BIP-78/BIP-77) is a BIP-21 URI with a pj= endpoint appended. If the sending wallet supports it, both parties contribute inputs to the transaction, breaking the common-input-ownership heuristic chain analysis relies on. BTCPay Server, Wasabi, and JoinMarket all support the receiving side.

Use this if you want a reusable Bitcoin payment address that doesn't leak a fresh address every time, a PayNym stays constant across payments while each actual transaction still uses a unique derived address on-chain.

A PayNym (BIP-47) is a reusable payment code, unlike a normal Bitcoin address, sharing it publicly doesn't burn address privacy: the two wallets derive a fresh one-time address per payment behind the scenes. Samourai Wallet, Sparrow, and paynym.is all support it.

Use this if you want one reusable Bitcoin address that doesn't link your payments together on-chain. Every payment sent to a silent payment address lands at a different on-chain output, but you can post the same address everywhere.

Silent Payments (BIP-352) let you publish one static address that never appears on-chain, each payment derives a fresh one-time output via ECDH between sender and receiver keys. No address reuse, no on-chain link between payments, no notification transaction needed. Live in Cake Wallet, Sparrow, and Bitcoin Core (indexing only).

Wraps either a standard ethereum: payment/contract-call URI (EIP-681) or a raw EIP-712 typed-data JSON blob for a wallet to sign. MetaMask, Rainbow, and any WalletConnect-paired wallet parses the URI form directly; typed-data JSON is meant for developer or hardware-wallet tooling that accepts a pasted signing payload.

Encodes a W3C Decentralized Identifier (did:key, did:web, did:ion, did:pkh, did:ethr, and others) as a bare URI. Any DID-aware wallet or resolver looks up the associated DID document from the method and identifier.

Wraps a Nostr identifier (NIP-19 bech32): npub1... for a public key, nprofile1... for a profile with relay hints, nevent1... for a specific note. Damus, Amethyst, Primal, and any NIP-19-aware client resolve it directly. Never paste an nsec1 (private key), that's not what this field is for.

Encodes the plaintext Sign-In with Ethereum message verbatim (EIP-4361). A compatible wallet or dApp signs it to authenticate, the QR itself carries no signature, it's the message to be signed.

Encodes an RFC 2397 data: URI verbatim, useful for handing over a small text snippet or inline image without hosting it anywhere. Capped at 4KB, large payloads won't fit reliably in a scannable code.

Encodes a bluetooth: pairing URI. Support varies by OS and app, check that your target device's Bluetooth stack recognizes this scheme before relying on it for unattended pairing.

Passes through an Apple HomeKit setup code (X-HM://...), the same code printed on the accessory or its box. Anyone who scans it can add the accessory to their Home app, treat the printed code, and this QR, the way you'd treat a physical key.

Encodes a LoRa Alliance TR-005 onboarding string (LW:D0:<JoinEUI>:<DevEUI>:...), the same format printed on LoRaWAN device labels. Network servers and provisioning apps that support TR-005 scan it to register the device without hand-typing 16-digit hex identifiers.

Encodes a Wi-Fi Easy Connect (DPP) bootstrap URI, the same format printed on a router or IoT device's Wi-Fi Easy Connect label. A DPP-capable phone scans it to provision the device onto the network without ever typing or exposing the Wi-Fi password.

Encodes a Thread border-router pairing credential. Thread is the low-power mesh radio behind many Matter smart-home devices; scanning this QR with a Thread-aware app or hub joins a device to the mesh.

Encodes a DIDComm v2 out-of-band invitation, either a didcomm:// URI or an https link carrying an _oob= parameter. A DIDComm-capable agent (wallet or app) scans it to establish an encrypted messaging channel with the inviter.

Encodes an OpenID4VCI credential offer URI (openid-credential-offer:// or haip://). A compatible digital-wallet app scans it to pull down a verifiable credential from the issuer named in the offer.

Safety note: an mDL device engagement is a one-time or live-session value. A saved image can stop working within seconds, generate it fresh at the moment of the scan rather than printing or storing it.

Encodes an ISO/IEC 18013-5 mobile driver's license device-engagement string (mdoc:...). This is the live handshake a verifier's reader uses to request specific attributes from a phone-based ID, issued fresh per session, not a static credential.

Safety note: a SIOPv2 request carries a live sign-in session. A saved image can stop working within seconds, generate it fresh at scan time instead of printing or reusing it.

Encodes a Self-Issued OpenID Provider v2 (SIOPv2) sign-in request. A compatible identity wallet scans it, then self-issues an ID token back to the relying party to complete sign-in without a separate password.

Safety note: a EUDI wallet request carries a live verification session. A saved image can stop working within seconds, generate it fresh at the moment someone needs to scan it.

Encodes an EU Digital Identity Wallet request, an OpenID4VP presentation request, OpenID4VCI credential offer, or mdoc engagement string, depending on what the relying party asked for. Scan with an EUDI-compliant wallet app.

Safety note: a cross-device sign-in URL is minted for one sign-in attempt. A saved image can stop working within seconds, generate it fresh at the moment you actually need to scan it.

Encodes a vendor cross-device sign-in URL, the kind Google, Apple, or Microsoft show on a desktop sign-in screen for you to scan with your phone. Each URL is minted for one sign-in attempt.

Use this if you're printing the onboarding QR for a Matter-certified smart-home device (light bulb, sensor, lock, thermostat). The code admits the device into any Matter ecosystem, Apple Home, Google Home, SmartThings, Alexa, Home Assistant. Do not share once the device is paired, anyone with the code can commission it into a fresh fabric.

Matter QR payload (Connectivity Standards Alliance spec). Format is MT: + base38-encoded CBOR. Manual pairing code (11 digits) is the fallback for devices without a QR. Every Matter-certified product is shipped with one from the manufacturer.

WalletConnect v2 (now called Reown) URI. Generated by the dApp when a user clicks "Connect Wallet". Scanning with MetaMask, Trust, Coinbase Wallet, Phantom, Rainbow, Zerion, and 300+ other wallets completes the pairing. Session-specific, URIs are single-use.

NFT claim / mint URLs from thirdweb, Reown, Zora, Manifold, or any chain-aware frontend. Scanning opens the claim page in the user's browser; WalletConnect or injected provider handles the on-chain mint. Works across Ethereum, Base, Polygon, Optimism, Arbitrum, Zora, Solana (scheme-dependent).

Tailscale auth-key URL (ephemeral or reusable) from the admin console. Scanning on a new device triggers the auth flow. Works for Tailscale, Headscale (self-hosted), and compatible forks. Don't publish reusable keys in public QRs, anyone can join your tailnet.

Works for any ActivityPub-compatible server (Mastodon, Pleroma, GoToSocial, Akkoma). Profile URL for sharing; OAuth authorize link for signing into a third-party app.

Use this if you're printing a pet tag, key-chain sticker, laptop label, water-bottle decal, or anything else you want returned if lost. Scanner sees an "if found" contact prompt; owner is never exposed until they choose to respond.

No account, no tracking, no service that can paywall your tag. The QR goes straight to your chosen contact method with a pre-filled "I found this" subject line. Works for pet tags, luggage, bike locks, cameras, anything with a visible printable surface.

Australian New Payments Platform PayID. Works with Osko-enabled bank apps.

Saudi Arabia's ZATCA FATOORA e-invoice QR. Legally required on every commercial invoice in KSA since 2023. Emit Phase 1 (5 TLV tags) with just the basic fields above, or Phase 2 (9 tags, mandatory since 2024) by filling the cryptographic fields.

Unified QR, modern Bitcoin wallets pick the Lightning route for small/fast payments and fall back to on-chain. Recommended format for Bitcoin receivers.

Local uploads stay in your browser and only appear on the printed card. MeCard QR data has no photo field.

MeCard is a simpler alternative to vCard, preferred by some Android devices

Micro QR capacity: 35 digits, 21 uppercase alphanumeric, or ~15 bytes (lowercase/URLs). Best for short codes, serial numbers, and IDs. For URLs, use standard QR instead.

Rectangular Micro QR, a narrow, wide format ideal for test tubes, wristbands, and ticket strips. Up to 361 characters.