Bead Developers
  • Introduction
  • Quick Start
  • Authentication
  • Payments
    • Create Payment
    • Payment Statuses
    • Payment Webhooks
    • Test Transactions - Crypto
    • Changelog
  • Entity Management
    • Onboarding
    • Merchant Management
      • Get Merchant
      • Changelog
    • Location Management
      • Create Location
      • Get Location
      • List Locations
      • Update Location
      • Delete Location
      • Changelog
    • Terminal Management
      • Terminal Lifecycle (Concepts)
      • Create Terminal
      • Get Terminal
      • List Terminals
      • Update Terminal
      • Delete Terminal
      • Webhook Management
      • Changelog
  • Settlement
    • Batches
    • Settlement Details
  • Reporting
    • Payment History Concepts
      • Pagination and Sorting
    • Partner Payments
    • Merchant Payments
    • Terminal Payments
    • Changelog
  • Reference Guide
    • Core Concepts
      • Environments & Base URLs
      • Authentication
      • Error Codes
    • Enumerations & Schemas
      • Tender Types
        • Crypto
        • Alternative Payments
      • Settlement Currencies
      • Common Field Types
    • Endpoint Index
      • Table View (All APIs)
      • Download OpenAPI / Postman
    • Payment Scenarios
      • Under- and Over-Payment Handling
      • Reclaiming Unconverted Crypto
    • Operational Guides
      • Compatible Crypto Wallets
      • Webhook Event Reference
    • Support & Contacts
      • Integration Support
      • Escalation Contacts
    • Changelog
  • FAQs & Troubleshooting
    • Authentication FAQs
    • Payments FAQs
      • Resolving “403 Forbidden” When Creating Payments
    • Environment & Testing
      • How to Test Klarna Payments
      • How to Prepare for USDC Testing
      • How to Test Klarna Payments
    • Webhooks & Error Codes
Powered by GitBook
On this page
  1. Reference Guide
  2. Operational Guides

Compatible Crypto Wallets

Bead is wallet-agnostic: any wallet that can

  1. scan the QR code we provide, and

  2. broadcast the exact asset on the correct network to the destination address

will complete the payment successfully.

Asset / network
Example wallets (mobile & desktop)
Notes

Bitcoin (on-chain)bitcoin tender

BlueWallet, Sparrow, Electrum, Ledger Live

Use Testnet in Sandbox.

Bitcoin Lightningbitcoin_Lightning tender

Phoenix, Muun, CashApp, Zeus

Wallet must support BOLT-11 or LNURL QR codes.

Ethereum (Sepolia → Mainnet)ethereum tender

MetaMask, Coinbase Wallet, Trust Wallet, Ledger Live

Switch to Sepolia in Sandbox.

USDC EthereumusdC_Ethereum tender

MetaMask, Rainbow, Ledger Live

Token auto-fills from QR; enable Sepolia token list in Sandbox.

USDC PolygonusdC_Polygon tender

MetaMask, Coinbase Wallet, Trust Wallet

Switch to Polygon Amoy in Sandbox; Polygon Mainnet in Production.

Minimum wallet capabilities

Capability
Why it matters

QR scanning

Bead encodes the payment address (and invoice for Lightning) in QR form.

Exact-amount send

Customer must match the requested crypto amount to avoid underpaid / overpaid states.

Network switch

Sandbox uses testnets (Sepolia, Amoy, Lightning Testnet); the wallet must let the user change networks.

Timely broadcast

Payment windows range from 2 – 10 minutes; wallets that delay broadcasts can trigger expired status.

Unsupported or caution-flagged wallets

Category
Reason

Wallets without testnet support

Cannot be used in Sandbox QA flows.

Custodial “layer-3” solutions that only support internal transfers

Unable to broadcast on-chain transactions to Bead’s address.

As new assets and networks are added, this page will be updated. Treat unknown tender types or networks as unsupported until documented here.

PreviousOperational GuidesNextWebhook Event Reference

Last updated 10 days ago