Check a Receive Address After Scanning Its QR Code

A QR image is a convenient way to carry text. It is not evidence that the destination belongs to the intended person, accepts the asset or is on the network you expect.

Read what the scanner actually decoded

After scanning, inspect the destination shown by the receiving application before confirming any further action. If the scanner opens a web link or displays a payment request, inspect that destination and every included field separately. Do not follow a QR image into a recovery-phrase form. A code that looks like one you used previously can still contain different text.

Know the scope of this interface’s address QR

The inspected RunixCoin receive code passes a public address to its QR renderer. That address alone does not encode the complete transfer agreement: network, token identity and amount still need separate checks. Changing a network view does not make an address-only image proof of the selected chain. This describes the inspected code path, not a successful camera scan or completed transfer test.

Use an independent comparison

Compare the entire decoded public address with the intended recipient’s address obtained through a trusted channel. Do not rely solely on the image’s caption or the first and last characters. Confirm the network by name and chain ID where available, then confirm the asset on that network. For tokens, distinguish the token contract used to identify the asset from the recipient account that would receive it. Those two addresses serve different purposes.

Resolve a changed value before proceeding

If the scanned result differs from the expected address, stop rather than editing an unfamiliar result by guesswork. Reopen the trusted receive screen and establish which account it represents. If a scanner cannot show the full result, use a method that permits review. Saving or sharing a receive image also associates an address with its context; consider that privacy cost. You can perform these comparisons without approving a token or signing a message, and this guide does not instruct you to send funds.

References and verification

Reviewed 10 November 2026. Product details reflect inspected interface code; camera scanning, browser behavior and mainnet execution were not verified.