One square, two uses
QR codes appear everywhere in payments: on shop counters, bills, event passes and parcels. They look the same, but their jobs differ. A merchant’s code is a way for you to pay them. A code on your own screen is a way for others to pay you. The risk lies in the moment a stranger asks you to scan a code in order to receive something.
When you scan a code in a payment app, you are in the pay-out direction. The app reads the code, shows a name and an amount and asks you to authorise. There is no scan that brings money in.
Where the confusion is used
Fraud with codes follows a few familiar stories. A buyer for an item you are selling says you must scan their code to receive the payment. A caller says a refund will arrive after you scan. A leaflet or sticker placed over a genuine shop code redirects payments elsewhere.
In all of these the instruction to scan to receive should end the conversation. Money is not delivered by scanning.
Read the screen after the scan
Once the code is read, the payment app shows a confirmation screen. This is the checkpoint. Read:
- The name of the recipient. Does it match the shop or person you expect?
- The amount, if it is filled in. Does it equal what you owe?
- The button label and the app’s wording about paying.
If the name is a person’s when you expected a business, or an unrelated business, stop and cancel. The phone has told you something before any money moved.
Counters, stickers and printed codes
At a shop, glance at the code before you scan. Is it a sticker attached over something else? Is the surface scratched or uneven? Compare the name that appears after the scan with the name on the shop’s board. A small business that you visit often will not mind you asking whether the name shown is theirs.
When you run a shop, check your own counter code regularly and keep it where customers can see it but where it cannot be covered easily. Matching the settled credits each evening against your sales also reveals a swapped code quickly.
Codes for your own receiving
Showing a QR code to be paid is fine. The code carries only the details the payer needs. If you share it publicly, such as on a social post, understand that anyone can read the name attached to it. Consider using a code that carries only a business name where possible, and avoid posting it with your full personal details.
Tracking helps you notice
A transaction list is a good place to catch mistakes. A payment to an unfamiliar name on a date you were in a shop is a flag that the code may have been swapped. If you record the merchant you meant to pay, any difference between that and the name on the statement becomes visible when you review.
If the payment went astray, note the time and the exact name shown, and contact your bank using an official number. Provide the date, the amount and the name in the first call.
Practising with the family
Run a short exercise at home. Show everyone a payment app’s confirmation screen and ask them to say aloud, in order, what they check before approving: name, amount, direction. After a few repetitions it becomes a reflex. That reflex is far more powerful than a long list of warnings that nobody remembers on a busy day.
Tickets, parking and event codes
Codes printed on posters, parking meters and event flyers deserve the same care as those on a shop counter, perhaps more, because nobody is standing nearby to notice a tampered sticker. Where the code leads to a payment, check the name on the confirmation. Where it leads to a website, read the address as you would any link. If the context feels odd, such as a code on a lamp post offering a discount, skip it and use the organiser’s official app instead.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


