Key Takeaways
A QR code carries no security of its own. Anything a camera can read, a camera can copy, so all protection lives in server-side validation.
Static codes are fine for joining. Anything that credits or spends value should be dynamic, so it can be expired, rotated and revoked.
Prefer staff scanning a member's rotating one-time code over a member scanning a printed code on a wall.
Put a unique code on every placement. The attribution is one of QR's genuine advantages and it costs nothing.
Start with QR because the cost of being wrong is near zero. Add NFC or wallet passes where volume or fraud exposure justifies the hardware.
Printed codes fail silently. Faded, covered and sticker-replaced codes need a periodic physical check and a zero-scan alert.
A QR code is the cheapest credential in loyalty. It costs nothing to print, nothing to distribute, works on every phone made in the last decade, and can be live across two hundred sites by tomorrow morning. That is why it is usually the right way to start a programme.
It is also the least secure credential in loyalty, because anything a camera can read, a camera can copy. A QR programme is only as safe as the validation sitting behind the code, and that is where most implementations are thin.
This guide covers how QR loyalty works, static versus dynamic codes, the four scan patterns, the security model, how QR compares with NFC and wallet passes, how to implement it, and how to measure it.
What a QR code loyalty program is
A QR loyalty programme uses a scannable code as the link between a customer and their membership record. The code may live on a table, a receipt, a product, a poster or the customer's own phone. Scanning it joins, earns, redeems or checks in, depending on what the code points to and who scans it.
Why QR works for loyalty
- No hardware cost: Printing a code costs pennies. NFC needs readers at every till.
- No app requirement: Every modern phone camera reads a QR code natively, so the customer installs nothing.
- Instant estate-wide rollout: A new code can be live everywhere in a day, which matters for multi-site and franchise networks.
- It works where there is no counter: Tables, packaging, events, deliveries, posters. Places a card reader will never be.
- Measurable by placement: A different code per location or campaign tells you exactly where enrolments came from.
2
Code types
static and dynamic
4
Scan patterns
join, earn, redeem, check in
0
Security in the code itself
it all lives server side
Static and dynamic QR codes
| Static | Dynamic | |
|---|---|---|
| What it encodes | A fixed destination, baked into the pattern | A short redirect you control |
| Can be changed after printing | No | Yes, without reprinting |
| Per-scan tracking | Only at the destination | Full, including time, place and device |
| Can be single use | No | Yes |
| Cost | Free to generate | Requires a service to host the redirect |
| Right for | A permanent join link on long-lived signage | Anything involving earning, redemption or security |
The practical rule: static codes are acceptable for joining and for pointing at information. Anything that moves value should be dynamic, because you need the ability to expire it, rotate it, limit it to one use and switch it off when something goes wrong.
The four QR scan patterns
Each pattern carries a different level of risk, which means each needs a different kind of code and a different validation rule. Mixing them behind one code is how QR programmes become unsafe.
Scan to join
A code on a receipt, a poster, a table or packaging that opens enrolment. This is the highest-volume use and the one where QR genuinely outperforms everything else, because you can put a join code physically anywhere a customer encounters the brand, including inside a delivery bag where no counter exists.
Scan to earn
The customer scans a code to credit points or a stamp. The security question lives here, because a code that credits value and can be photographed is a code that can be shared. Earning codes should be dynamic, single use, time limited, and bound to a transaction rather than to a poster.
Scan to redeem
The member displays a code and staff scan it to apply the reward. This direction is far safer than the reverse, because the member's phone shows a one-time code that your system validates and burns. Where it is practical, prefer staff-scans-member over member-scans-poster.
Scan to check in or participate
Events, queues, tastings, service visits. The reward is recognition and recording rather than value, so the security requirement is lower and the operational benefit is high.
Cheap to roll out, controlled where it counts
Dynamic per-placement codes with single-use validation, rotation and velocity limits.
Book a demoTrusted by 5,000+ companies
The security model
The key fact is that a QR code carries no security of its own. It is a visible pattern anybody can photograph. Everything protective has to happen when the scan is validated.
What actually protects a QR loyalty program
- Server-side validation of every scan: The code is a claim, not a credential. Validate the member, the context and the eligibility on each scan.
- Single-use and short-lived codes for earning: A code that can be used once, within a few minutes, cannot be meaningfully shared.
- Rotation on displayed codes: A member's displayed code should change frequently, so a screenshot stops working quickly.
- Binding to a transaction: The strongest earning model credits against a specific till transaction rather than against a scan of a generic code.
- Velocity limits: Caps per member, per device and per location catch sharing and automation before they become expensive.
- Anomaly detection: Scans clustered at impossible rates, from one device, or across distant locations in minutes. Our guide to loyalty program fraud covers the patterns.
- Watch the physical codes: Replacing a printed code with a sticker pointing elsewhere is a real-world attack. Permanent signage needs periodic checking.
QR, NFC and wallet passes compared
| QR code | NFC tap | Wallet pass | |
|---|---|---|---|
| Hardware needed | None | Readers at every point | None, scans or taps |
| Speed at the counter | A second or two, fails in poor light | Under a second | Fast, and nothing to find |
| Copy resistance | Low. A screenshot works | High. Not copyable by camera | Medium to high, depending on configuration |
| Rollout cost | Lowest | Highest | Low once the pass is issued |
| Enrolment friction | Very low | Low | Higher, due to the add-to-wallet step |
| Works without a phone | No, unless printed | No | No |
The sensible pattern for most operators is to start with QR, because the cost of being wrong is almost zero, and add NFC or wallet passes only where volume, counter speed or fraud exposure justifies the hardware and integration. Hybrid is normal: a wallet pass that also carries a scannable code covers both.
How to implement a QR loyalty program
Eight steps, half of which are about control rather than rollout. QR is cheap to deploy and quick to abuse, so the two have to be built together.
1. Decide what each code does
Join, earn, redeem or check in. Mixing them behind one code confuses customers and makes the security model impossible to reason about.
2. Use dynamic codes for anything carrying value
Static codes are fine on a permanent join poster. Anything that credits or spends should be dynamic, so it can be expired, rotated, limited and revoked.
3. Put a unique code on every placement
Per site, per table, per campaign, per pack. The attribution this gives you is one of QR's genuine advantages over every other credential, and it costs nothing.
4. Design the landing experience for a phone in a hurry
One screen, one action, no app install, no long form. A scan that leads to a sign-up page with eight fields converts about as well as no code at all.
5. Prefer staff-scans-member for redemption
A member displaying a rotating one-time code that your system validates and burns is materially safer than a member scanning a code you have printed on a wall.
6. Set velocity limits before launch
Per member, per device, per location, per hour. Retrofitting these after an abuse incident means annoying legitimate members while you tune them.
7. Check the physical estate
Codes get covered, damaged, faded or replaced with stickers pointing somewhere else. Build a periodic check into site routines, and monitor for placements whose scan volume suddenly drops to zero or spikes.
8. Measure by placement from day one
Scans, enrolment conversion and subsequent activity by code. This is what tells you which placements to keep printing and which to stop.
Measuring a QR loyalty program
| Metric | Why it matters |
|---|---|
| Scans per placement | Which locations and materials actually produce scans |
| Scan to enrolment conversion | Whether the landing experience works on a phone in a queue |
| Earn scan success rate | Failed scans point to poor lighting, damaged codes or validation problems |
| Repeat scan rate per member | Whether the mechanic became a habit or was used once |
| Redemption via QR | The end of the loop, and a proxy for whether the value is reachable |
| Anomalous scan rate | Sharing, automation and abuse, which arrive quickly in QR programmes |
| Placements with zero scans | Codes that are damaged, covered or in the wrong place |
Common mistakes
- Using static codes to credit value: They cannot be expired, rotated or revoked, which makes them a permanent liability once shared.
- Treating the code as the security: All of it lives in server-side validation. The pattern protects nothing.
- One code for the whole estate: You lose attribution entirely and cannot isolate a problem to a location.
- Sending scans to a long sign-up form: The conversion loss here is larger than most operators expect.
- Member scans a wall code to earn: Easier to share and harder to control than staff scanning the member.
- No velocity limits: QR abuse is fast, automated and organised, and the first you hear of it is the liability number.
- Never checking the printed codes: Faded, covered and replaced codes fail silently for months.
- Assuming every customer can scan: A share of your base will not, so keep a non-QR route to the same value.
QR loyalty on Loyalife
01 · Codes
Dynamic codes per placement
Unique, expirable, rotatable codes by site, campaign and pack, with attribution built in.
02 · Patterns
Join, earn, redeem and check in
Each scan type configured separately, with the right validation and lifetime for what it does.
03 · Security
Server-side validation
Single-use codes, rotation, transaction binding and velocity limits per member, device and location.
04 · Detection
Anomaly monitoring
Impossible scan rates, single-device clusters and geographically implausible activity surfaced automatically.
05 · Hybrid
QR alongside wallet and card
One member identity behind a code, a wallet pass or a phone number, so customers can use whichever they prefer.
06 · Insight
Placement-level reporting
Scans, conversion and downstream activity by individual code, including placements that have gone silent.
You can also explore loyalty card programs and the Loyalife platform.
QR is the right starting point for almost every programme that needs to be everywhere cheaply. Just do not confuse the code with the control: the pattern on the wall is a claim, and the system behind it is the only thing deciding whether to believe it.
Book your Loyalife demo
Frequently asked questions
A programme that uses a scannable code as the link between a customer and their membership record. The code can live on a receipt, a table, a poster, packaging or the customer's own phone, and scanning it joins, earns, redeems or checks in depending on what the code points to and who is doing the scanning.
A static code encodes a fixed destination baked into the pattern, so it cannot be changed after printing and offers no per-scan control. A dynamic code encodes a redirect you control, so it can be changed without reprinting, tracked per scan, limited to a single use and switched off. Anything carrying value should be dynamic.
The code itself is not secure at all, because anything a camera can read, a camera can copy. Security comes entirely from what happens when a scan is validated: server-side checks on member, context and eligibility, single-use and short-lived earning codes, rotation on displayed codes, binding to a specific transaction, velocity limits and anomaly detection.
QR needs no hardware, works on every phone and can be live across an estate in a day. NFC is faster at the counter and far harder to copy, but needs readers at every point and costs more to roll out. Most operators should start with QR and add NFC or wallet passes only where volume, counter speed or fraud exposure justifies it.
Four. Scan to join, the highest-volume use and where QR genuinely outperforms other credentials because a code can go anywhere. Scan to earn, where the security question concentrates. Scan to redeem, which is safer when staff scan the member rather than the reverse. And scan to check in at events or service visits, where recognition rather than value is the reward.
Make earning codes dynamic, single use and short lived, bind them to a specific till transaction rather than a generic poster, rotate any code displayed on a member's phone, set velocity limits per member, device and location, run anomaly detection on impossible scan rates and geographically implausible activity, and physically check printed codes for sticker replacement.
Yes. A unique code per site, table, campaign and pack costs nothing extra and gives you attribution no other credential provides: you learn exactly which materials and locations produce enrolments and which produce nothing. It also lets you isolate a problem, or an abuse pattern, to a single placement rather than the whole estate.
Scans per placement, scan to enrolment conversion, earn scan success rate, which exposes damaged codes and poor lighting, repeat scan rate per member, redemption via QR, anomalous scan rate as the abuse signal, and placements with zero scans, which usually means a code has been covered, faded or removed.
![Diversity and Inclusion in the Workplace: Why It Drives Success [Activities + Survey Tips]](/Blog-cover-light/inclusion-and-diversity-in-the-workplace.avif?dpl=dpl_8fJikYxuCmYv3RQT1yaE4Git6nzR)
![How to Run an Effective Employee Commitment Survey [+ Sample Questions]](/Blog-cover-light/employee-commitment-survey.avif?dpl=dpl_8fJikYxuCmYv3RQT1yaE4Git6nzR)
