1. The Scam
Attackers stick a counterfeit QR code over the legitimate one on a meter or sign. Drivers who scan are sent to a look-alike payment page that captures card details. Use our [QR safety checker](/qr-safety-checker) guidance to identify suspicious codes.
2. Driver Protections
* Check for sticker edges or a raised code—scan with a [QR scanner](/qr-scanner) app that previews URLs.
* Prefer the operator's official app, downloaded from the app store, or the meter's card reader.
* Verify the domain shown before entering payment information.
* Check that the URL matches the legitimate service provider.
3. Operator Protections
* Print codes on tamper-evident labels or engrave them into the meter.
* Inspect sites regularly and record how each code should look—use our [printed QR tester](/printed-qr-tester) methodology.
* Publish the official payment domain on signage and your website.
* Provide a fast channel for reporting fake codes.
* Generate secure payment codes with our [URL QR code generator](/url-qr-code-generator) and track usage with our [UTM builder](/utm-builder).
Use proper sizing with our [QR size calculator](/qr-size-calculator) and follow our [QR placement guide](/qr-placement-guide) for tamper-resistant positioning.
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
