QR Wallet

• Name: QR Wallet
• URL: https://qr.xyz/
• Category: smart-account wallet-and-payments company / paymaster-and-merchant-integration operator / mobile wallet distribution shell
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: QR Wallet belongs in companies/ because the useful question is not only how do smart accounts, sponsored transactions, or QR payments work? but who decides network coverage, paymaster policy, partner admission, Discovery listing, token integration, and merchant API access around that stack? The accessible docs do not clearly surface a separate legal-entity name, but they do show a branded operator boundary that reviews partnership requests, issues API keys, curates a built-in DApp catalog, controls sponsored-transaction coverage, and packages merchant QR flows, stablecoin checkout, and wallet UX into one company-run shell.
• What it does:
  • Operates a non-custodial multi-chain mobile wallet with unified balances, multiple wallets, and smart-account-based gas abstraction
  • Sponsors user transactions through a paymaster flow on supported networks and defines when users fall back to USDC/USDT gas payments or native-token gas
  • Packages QR Wallet Pay, Gaian Pay integration, and Thai PromptPay-compatible QR parsing into one merchant-payments experience
  • Runs a partner-facing integration surface for businesses that want QR payments, stablecoin checkout, API access, webhooks, and DApp discovery placement
  • Curates the in-wallet Discovery catalog, including listing requirements, featured positioning, and strategic-partner placement
  • Uses Alchemy for RPC, bundler, and paymaster infrastructure, which makes vendor composition part of the effective operator surface rather than leaving the wallet as a fully neutral standalone stack
• Key claims:
  • The About page says QR Wallet covers network fees through a sponsored-transactions system, supports 12 blockchains, and uses Alchemy for RPC, bundler, and paymaster infrastructure, which is the clearest high-level reason the operator shell matters
  • The Sponsored Transactions docs say QR Wallet decides daily sponsored-transaction availability, which networks are covered, and when users instead pay gas in stablecoins or native tokens
  • The Integration Overview says businesses can integrate QR payments in minutes via API, accept USDC and USDT across 12 blockchains, and receive webhooks for automated processing, showing a real partner-facing operating surface rather than only a consumer wallet app
  • The Partnership Request flow says teams submit applications by email or in-app, QR Wallet reviews them in 1–3 business days, and then provides API keys and documentation, which makes partner admission and credential issuance explicit operator powers
  • The DApp Listing docs say QR Wallet runs the Discovery catalog, sets listing requirements, offers featured placement for strategic partners, and routes listing through the same partnership-review funnel, which means app distribution and traffic-shaping live with the operator too
  • The accessible docs repeatedly use the QR Wallet brand as the responsible operating shell but do not clearly name a separate legal entity, so the right current read is branded operator boundary with incomplete public legal labeling, not neutral protocol
• Whitepaper: No separate company whitepaper is the point here. The strongest current primary materials are QR Wallet’s live docs corpus, especially the About, Sponsored Transactions, QR Payments, Integration Overview, DApp Listing, and Partnership Request pages.
• Sources:
  • https://qr.xyz/
  • https://docs.qr.xyz/welcome/readme.md
  • https://docs.qr.xyz/core-concepts/sponsored-transactions.md
  • https://docs.qr.xyz/features/qr-payments.md
  • https://docs.qr.xyz/for-partners/integration-overview.md
  • https://docs.qr.xyz/for-partners/dapp-listing.md
  • https://docs.qr.xyz/for-partners/partnership-request.md
  • https://docs.qr.xyz/features/wallet-and-balances.md

Internal linkages

• Product-layer note: qr-wallet.
• Useful operator-boundary comparisons for wallet-plus-payments packaging: crossmint, halliday, and passkeys-foundation.
• Useful infrastructure dependency comparison: alchemy for a case where hosted wallet UX inherits a named middleware stack rather than standing alone.

Protocol / company boundary

• Keep qr-wallet focused on the product surface: smart-account UX, unified multi-chain balances, same-address EVM behavior, sponsored transactions, and QR payment parsing.
• Keep this note focused on the named operator shell that decides partner admission, API-key issuance, Discovery inclusion, supported-network and sponsorship coverage, and the broader merchant-integration workflow.
• That split matters because how does QR Wallet work? and who controls which integrations, listings, sponsored routes, and merchant workflows are allowed to feel native inside QR Wallet? are related but not identical questions.
• The accessible docs do not yet justify a sharper legal-entity map than QR Wallet itself, so keep this note at the branded company/operator layer until stronger primary legal materials surface.

Control surface

• Practical leverage sits in paymaster policy, supported-network coverage, smart-account deployment defaults, merchant QR and checkout workflow, API-key issuance, webhook-backed integration flow, Discovery listing policy, token and partnership review, and the surrounding mobile-wallet distribution shell.

• A second-order dependency sits in infrastructure composition: QR Wallet’s docs openly name Alchemy for RPC, bundler, and paymaster roles, which means users and partners are not only inheriting QR’s product decisions but also QR’s chosen upstream middleware stack.

• Even with non-custodial positioning, QR Wallet still controls what counts as the default path for gasless use, merchant acceptance, app discovery, and payments partner access.

• Read QR Wallet as a company-run wallet-and-payments control plane, not as a neutral account-abstraction primitive.

• Last reviewed: 2026-08-11 UTC