A crypto payment QR code encodes instructions that compatible wallet software can read. It reduces copying work, but it does not prove that the merchant is trustworthy or that a payment has arrived. The wallet holder must still inspect and approve the actual transaction.
Understand what the code can carry
Depending on the network and wallet format, a payment URI can include an address, asset or contract, network identifier and amount. Wallets differ in how much of that information they understand. Always retain readable payment instructions as a fallback.
For example, Coinvay’s EVM token instructions can identify the token contract and chain as well as the destination and integer quantity. A wallet that recognizes only an address may still require the customer to select the network or enter the amount correctly. Scanning does not justify skipping that review.
Check the final wallet screen
Compare the proposed asset, network, recipient and amount with the current checkout before signing. A substituted QR code, stale screenshot or wrong-network wallet can produce an unintended transfer. The on-screen code should come from the live payment request rather than an old image saved in a conversation.
For native-coin payments, leave enough balance for network fees. For token payments, ensure the wallet has the required native fee asset or another explicit fee-paying arrangement. QR convenience does not remove those requirements or guarantee compatibility with an exchange withdrawal interface.
Keep scanning separate from settlement
Opening a wallet link or scanning an image does not mark the invoice paid. Coinvay still verifies the transfer on the selected blockchain, including the correct amount, recipient and confirmation state. The merchant should fulfill only after that authoritative check.
In the sandbox preview, a visual QR placeholder is deliberately not a payment request. Real Base Sepolia test checkout generates actual test payment instructions. This distinction helps staff demonstrate the interface without accidentally presenting a live receiving instruction during a training session.
Practical checklist
- Scan from the current trusted checkout, not a saved screenshot.
- Review the final wallet transaction before approval.
- Use verified invoice status rather than a scan event as proof of payment.
Common questions
Can a QR code contain a private key?+
QR is only an encoding format and can carry many types of data. A normal receiving-payment QR should contain payment instructions, not ask a customer to disclose recovery material.
Why does my wallet show only an address after scanning?+
Wallet URI support varies. Use the readable checkout instructions to select the correct asset and network and enter the exact quoted amount before sending.
Sources and further reading
Primary references and Coinvay product documentation. Check the linked pages for current details.
AI-assisted drafting, published by Coinvay. Examples are illustrative. Read our editorial approach.