A crypto QR code payment can make an in-person checkout fast, but only when the code, wallet, network, amount, and confirmation process are designed together. This guide provides a reusable setup checklist for merchants accepting Bitcoin, USDC, or other supported crypto assets without directing customers to the wrong address or chain.
Overview
A QR code is only the handoff between a merchant’s payment instructions and a customer’s wallet. It does not, by itself, prove that funds arrived or that the customer paid the correct amount. A reliable crypto QR code payment workflow must answer five questions:
- Where should the payment go? Identify the receiving address or the payment gateway account.
- Which network should the customer use? A token such as USDC may exist on multiple networks, and a wallet transfer on the wrong network can create recovery problems.
- What asset and amount are due? Display the currency clearly and avoid relying on a ticker symbol alone.
- How long is the request valid? Invoice-specific codes should have an expiration or status rule.
- How will the merchant verify payment? The order should not be marked complete solely because a customer shows a wallet screen.
For a small operation, a wallet app and a carefully labeled QR code may be enough for limited transactions. A busier point of sale usually benefits from an NFT payment gateway, stablecoin payment gateway, or crypto payment API that creates a unique invoice, monitors the blockchain, and reports status to the merchant system. The appropriate choice depends on transaction volume, supported chains, settlement needs, and the level of wallet integration required.
For broader checkout planning, use the NFT checkout integration checklist alongside this guide. It covers the surrounding checkout and transaction-cost decisions that a QR code alone cannot solve.
Checklist by scenario
Scenario 1: A fixed wallet address for a simple in-person payment
A static QR code points to the same address every time. It is easy to print and can work for donations, low-volume sales, or a clearly separated business wallet. Before using one, confirm the following:
- Generate the code from the correct receiving address, not a copied address from an untrusted message.
- Label the accepted asset and network beside the code, such as “USDC on [specified network]” rather than simply “USDC.”
- State whether the customer must enter the amount manually.
- Use a dedicated merchant wallet rather than a personal wallet that holds unrelated assets or valuable NFTs.
- Test scanning with each wallet app your customers are likely to use.
- Provide a readable text address as a fallback, while warning staff not to read or retype it casually.
Static codes create an operational limitation: the merchant must match an incoming transaction to a customer or order using the amount, timestamp, reference, or another internal process. They are less suitable when several customers may pay the same amount at once.
Scenario 2: An invoice-specific QR code for a defined order
An invoice-specific QR code is generated for one order and can encode the destination, asset, network, amount, and expiration. This is generally easier to reconcile because each payment request has its own identifier. A typical wallet QR code checkout should follow this sequence:
- Create the order in the point-of-sale or checkout system.
- Generate a payment request using only the asset and chain combinations your system supports.
- Render the QR code together with the amount, currency, network, order reference, and expiration time.
- Ask the customer to scan from the wallet’s payment or send function, not from an unfamiliar browser prompt.
- Show a clear “payment detected,” “confirming,” or “paid” status based on your verification rules.
- Release the product or NFT only after the required status is reached.
- Store the transaction hash, order ID, wallet address when available, asset, network, amount, and timestamps for reconciliation.
For a developer-built flow, a crypto payment API or Web3 payments provider may expose webhooks for detected and confirmed transactions. Design the integration so duplicate notifications do not create duplicate orders, and so a delayed or failed webhook can be reconciled from the chain or provider dashboard.
Scenario 3: Bitcoin and USDC at the same point of sale
Do not present one generic “crypto” QR code when Bitcoin and USDC follow different payment formats or network rules. Give customers a clear asset choice first, then generate the corresponding request. For USDC, display the exact network and verify that the receiving wallet or payment provider supports that combination. For Bitcoin, confirm whether the workflow uses an on-chain address, a supported payment protocol, or a provider-managed invoice.
Use separate test cases for each asset. A successful Bitcoin test does not validate a USDC flow, and a USDC transfer on one network does not validate another network. Keep the supported combinations in a written matrix that staff can consult at the register.
What to double-check
QR code and wallet behavior
- Scan the printed and on-screen versions under normal lighting and from typical customer distances.
- Check that the QR payload uses the payment URI format expected by the wallets you support.
- Confirm that scanning opens the wallet’s send or payment screen with the intended fields populated.
- Test both newer and older supported wallet versions if your customer base uses a mixture of devices.
- Inspect the code after resizing, laminating, or placing it behind a counter; low contrast and glare can prevent scanning.
Payment verification
Use this verification template for every transaction:
Order: [order ID]
Asset: [asset name and contract or currency identifier]
Network: [exact chain]
Expected amount: [amount and precision]
Destination: [merchant address or provider account]
Expiration: [time and timezone]
Status rule: [detected, confirmed, or provider-defined status]
Transaction reference: [hash or provider ID]
Do not treat a customer’s screenshot, a wallet animation, or a “sent” message as final verification. Check the receiving address, asset, network, and amount in the merchant wallet, block explorer, or payment provider. The required confirmation policy should be defined before launch and applied consistently, especially when delivering an NFT or another irreversible digital product.
Monitor the workflow after launch. The crypto payment monitoring guide can help organize alerts and operational checks, while the Web3 payment webhook guide covers confirmation and retry handling.
Common mistakes
- Using a QR code without naming the network: A familiar token name does not identify a unique chain.
- Reusing one address for every order: This complicates reconciliation and may expose more transaction history than intended.
- Accepting unsupported tokens: A wallet may allow a customer to send an asset that the merchant system cannot credit or redeem.
- Skipping small-value tests: Test the full flow, including scanning, detection, confirmation, refund handling, and receipt generation.
- Trusting a pasted address: Verify the final destination through a controlled source and use wallet security controls where available.
- Releasing an NFT on detection alone: A detected transaction may still be pending, replaced, underpaid, or sent on the wrong chain.
- Failing to plan exceptions: Staff need instructions for overpayments, underpayments, expired invoices, duplicate payments, wrong-network transfers, and network outages.
For a deeper wallet review, consult the crypto wallet security audit checklist. Keep payment records in line with your internal accounting process using the payment recordkeeping guide.
When to revisit
Review the crypto QR code payment setup before seasonal planning cycles, when adding a store or event location, when supporting another token or network, and whenever the wallet, QR library, point-of-sale system, or payment provider changes. Reprint or replace static codes if the receiving address changes, and verify every displayed code after a website, app, or hardware update.
At least annually, run a complete test from invoice creation to reconciliation. Confirm supported wallet behavior, URI formatting, asset and network combinations, expiration rules, confirmation thresholds, staff instructions, and fraud controls. Also review whether a static code still fits the business. If payment volume or order complexity has grown, an invoice-specific QR flow with a crypto payment API may reduce manual matching and improve auditability.
Before going live, have one person scan the code and another independently verify the destination, asset, network, amount, and transaction status. Record the result, retain the current QR source, and schedule the next review date. That simple control turns a convenient QR display into a maintainable piece of NFT payments infrastructure.