What do you need to understand first?
A code can be replaced on a notice or copied into an otherwise convincing message. It may lead to a phishing page or prepare a payment to the wrong address. The visual pattern is not an identity check; the useful evidence is what it asks your device to open or approve.
What might this look like?
A payment notice has a sticker over the original code. The scan opens a wallet request, but the destination differs from the recipient details you confirm separately. You cancel the request instead of assuming the printed notice makes it safe.
Where is the safety checkpoint?
How can you work through it?
Identify the result of the scan
Read the preview before opening it. Distinguish a web address from a payment request. Decline unexpected downloads or prompts.
Confirm the intended source
Use a route you already know to check the recipient or notice. A sticker, logo or familiar surrounding page is not enough.
Review payment details in full
Check the asset, network, destination, amount and fee in the wallet. Use the trusted signing display if available.
Leave a secret-collection page
A code for receiving or paying does not justify entering recovery words. If you disclosed information or paid, preserve evidence and use the response guide.
When should you pause?
Pause until you can check each point below without sharing spending secrets.
- You know what the code opened.
- The destination was confirmed outside the code.
- The wallet request matches the intended action.