Crypto Wallet Flow and Amounts
Bead’s crypto payment experience uses a direct wallet to wallet transfer on chain.
Depending on the asset and network, the consumer experience differs:
For many on chain assets and networks, the QR code contains only a destination wallet address. In these cases, the consumer is expected to enter the amount manually in their wallet. This is normal and expected behavior for wallet to wallet transfers.
Some rails, such as Bitcoin Lightning, commonly support a scannable invoice format that can include both the destination and the amount. In those cases, the wallet can populate the amount automatically after scanning.
Hosted payment page ownership
When an integrator routes a consumer into the Bead hosted payment page for crypto, Bead controls that consumer experience end to end. Integrators do not control the hosted page UI, content, or flow.
How the QR code works
What the QR code contains
For many crypto payments, the QR code contains:
a destination wallet address
It typically does not include:
the amount to send
Because the amount is not encoded in the QR code, the consumer will enter the amount in their wallet based on the amount shown on the payment screen.
What the consumer does after scanning
After scanning the QR code, the consumer typically:
opens their wallet
selects the same asset and network they chose on the payment screen
confirms the destination address
enters the amount shown on the payment screen
submits the transfer
The consumer’s wallet is the system of record for the transfer submission. The consumer controls the final send action, including the entered amount.
Why amount entry varies by rail
Bitcoin Lightning example
Bitcoin Lightning commonly uses an invoice style payload that can include:
destination
amount
This can streamline the scan and pay experience because the wallet can populate the amount automatically from the invoice.
On chain transfer example
For many on chain transfers, the common pattern is:
destination address in the QR code
amount manually entered by the consumer in their wallet
This is expected behavior across many wallets and networks.
What integrators should expect
Consumer experience expectations
If your checkout flow includes crypto, set the expectation that:
scanning the QR code routes the consumer to a destination address
for many assets and networks, the consumer will enter the amount shown on the payment screen
the consumer must send using the same asset and network selected on the payment screen
Common mismatch scenarios
Manual entry introduces a risk of mismatch. Common causes include:
amount mistyped
wrong asset selected in the wallet
wrong network selected in the wallet
consumer sends from an exchange flow that introduces delays or uses a different send pattern
Bead’s payment tracking and statuses reflect whether the received transfer matches what was requested.
Ways to reduce miskeys and friction
Integrators can reduce issues by:
setting expectations in their own checkout flow before redirecting to the Bead hosted page, such as a short note that the consumer may need to enter the amount in their wallet
ensuring support teams understand common mismatch scenarios and the likely root causes
linking consumers to troubleshooting guidance when needed
Roadmap note
Because Bead owns the hosted crypto payment page experience end to end, we can evolve the experience over time without requiring changes from integrators.
We are actively exploring improvements to minimize friction and improve consumer success, including:
clearer on screen guidance and coaching for asset, network, and amount entry
UX enhancements that reduce common miskeys
technical enhancements that streamline scan and send behavior where supported by wallets and networks
This page will be updated as capabilities evolve.
Common questions
Will the consumer always enter the amount
Not always. It depends on the coin and network.
For many on chain assets and networks, yes. The consumer enters the amount in their wallet after scanning a destination address. This is expected behavior.
Some rails, such as Bitcoin Lightning, commonly support a scannable format that can include the amount, which can allow the wallet to populate it automatically.
Why does Bead show an amount if the QR code does not include it
Bead shows the intended amount so the consumer knows what to send. The transfer itself is still initiated and confirmed in the consumer’s wallet.
What should I tell a consumer who is confused
Use simple guidance:
Scan the QR code
In your wallet, select the same asset and network
Enter the exact amount shown on screen
Send the transfer
Return to the merchant screen and wait for confirmation
Last updated