1. Cardless QR Withdrawal
Several major banks now offer cardless ATM withdrawal via QR. The customer:
1. Initiates the withdrawal in the banking app, specifying the amount.
2. Approaches the ATM, which displays a QR.
3. Scans the QR with the banking app — the app authenticates and authorises.
4. Cash is dispensed without a physical card.
This eliminates card skimming at ATMs and allows withdrawals on behalf of others (parents sending children cash) without sharing the card.
2. Mobile Banking App Connection QR
A QR on the ATM screen or the ATM fascia links to the bank's mobile app on the appropriate app store. A QR on an ATM reaches customers at a banking touchpoint with high intent — a significantly better acquisition context than a generic app store listing.
3. QR Fraud Alert Scan
Banks in some markets offer an ATM safety checker: scan a QR to report suspicious ATM devices (card skimmers, pin-hole cameras) directly to the fraud team. The QR is on the ATM fascia and the report includes the ATM ID from the QR, so the fraud team knows exactly which terminal has been flagged.
4. Receipt QR for Instant Support
A QR on the ATM receipt links to: balance check, transaction query, report a problem with this transaction, and the fraud reporting hotline. Converts the paper receipt (low-value traditional channel) into a high-intent customer service touchpoint.
5. ATM Availability QR
A QR on an out-of-service ATM links to the nearest alternative ATMs on a live map and the bank's ATM availability service status. Customers who arrive at a non-functional ATM are guided immediately to an alternative rather than leaving frustrated.
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.
Related tools and guides
- For local payments, the [Pakistan payment QR](/pakistan-payment-qr) page explains the regional flow and what customers see.
- The [regional payment QR](/regional-payment-qr) guide covers payment codes used across different markets.
- Run unfamiliar destinations through the [QR safety checker](/qr-safety-checker) before you share a code widely.
- The [bulk generator](/bulk-generator) builds many codes from a table when one-off generation would take too long.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
- The [UTM builder](/utm-builder) adds campaign parameters so scans show up separately in your analytics.
