How Can QSRs Add App-Free Customer Recognition at the Payment Terminal?

QSRs can add app-free customer recognition by running loyalty software on the payment terminals they already use: the terminal recognises a returning card from an approved, non-payment reference, a first-time guest can join by entering a phone number on the terminal, and rewards are applied during the payment without a phone, an app or a QR code. For a fast food loyalty programme, terminal-based customer recognition works best alongside an ordering app rather than instead of it, because apps still do the job of ordering, delivery and collection.

Key takeaways

• Speed decides what works at payment. Contactless accounted for 75% of UK debit card transactions in March 2026, so any loyalty step that adds time competes with a tap.
• Recognise the card, then invite the guest. Returning cards can earn automatically; first-time guests can join once on the terminal with a phone number.
• Keep the app for what apps do well. Ordering, delivery and collection still suit an app, so terminal recognition covers the guests who never open it.
• Treat the card reference and phone number as personal data. Plan notices, the lawful basis and PECR-compliant messages before the pilot.
• Confirm every device. Supported models vary, so check each counter, kiosk and drive-through terminal before rollout.

How we put this guide together

This guide draws on UK Finance payment statistics, published loyalty research from Antavo, guidance from the Information Commissioner's Office (ICO) and the PCI Security Standards Council, technical documentation from EMVCo and Adyen, and Zeal's own product and developer documentation, all checked on 10 October 2026. Zeal sells value-added services for payment terminals, so we have a commercial interest in this topic. We do not quote recognition rates, uplift figures or customer results.

Why app-less loyalty for fast food fits a quick payment

App-less loyalty for fast food starts from how guests pay. UK Finance reports that contactless methods accounted for 39% of all UK payments in 2025 and that 58% of UK adults now use mobile contactless regularly. Its card spending update shows contactless made up 75% of debit card and 66% of credit card transactions in March 2026. A QSR guest who taps and goes does not want to find a phone, open an app and scan a code first.

Consumers also seem to be cooling on apps as the way into loyalty. Antavo's Global Customer Loyalty Report 2026 found that logging in to a mobile app as the favourite way to interact with a loyalty programme fell to 44.1%, from 59.0% in 2025. Recognition on the payment terminal removes that step for the guests who never open the app.

Figure 1. Loyalty sign-up without the queue, from Zeal's introduction to Loyalty Link.

How terminal-based customer recognition works in a QSR

1. The guest pays as normal with a card or phone wallet on the payment terminal.
2. The payment application reads the card and produces an approved card reference. In Zeal's developer documentation, the payment application generates this card fingerprint itself, and the card number is never sent to Zeal.
3. Zeal checks the reference against the restaurant's programme and returns a short response, such as a stamp earned or a reward ready.
4. A first-time guest can join on the terminal. With Loyalty Link, an unregistered customer can enter a phone number on the terminal, receive an SMS enrolment link and be recognised on later eligible visits.
5. The payment completes under the control of the approved payment application, and the visit appears in the Merchant Dashboard.
6. Refunds and reversals undo the reward linked to the original sale.

The payment application keeps control of the payment throughout, and our guide to smart payment terminal capabilities covers how a terminal should behave offline or when a service fails.

Figure 2. How Loyalty Link signs up and recognises customers, from Zeal's introduction to Loyalty Link.

Choosing a payment terminal SDK for loyalty

A payment terminal SDK for loyalty lives inside the busiest part of a QSR: the payment. Zeal's ISV page describes its SDK as held to a strict processing budget, and its developer documentation shows hooks at fixed points in the transaction: after the card is read and before it is verified (for discounts), after the receipt (for surveys, phone-number capture or enrolment), and on refunds and reversals. Whatever you choose, ask the questions in Table 1.

Table 1. Questions to ask about a payment terminal SDK for loyalty

Card-linked loyalty programmes for QSR, alongside the app

Card-linked loyalty programmes for QSR and ordering apps do different jobs. An app is the right place for ordering ahead, delivery and collection; terminal recognition covers the guest at payment who never opens it. We build both: in September 2024 we launched a white-label app for Dara's Ice Cream with delivery, pickup and pay in-store, and Zeal's retail and QSR page describes connecting an existing loyalty engine to supported terminal journeys.

Wallets need their own test. EMVCo explains that a payment token is constrained in how it can be used, for example to a specific merchant, device or payment scenario, and Adyen's identifier guide states that "For NFC wallet transactions, a PAN is not available and thus there is no card alias". A guest who sometimes taps a card and sometimes a phone can therefore look like two guests unless the programme links them.

First-party data capture at payment terminal checkouts

First-party data capture at payment terminal checkouts gives a QSR two kinds of data: a card reference that links visits, and, if the guest joins, a phone number.

• Both are personal data. The ICO's pseudonymisation guidance says pseudonymised data is personal data in the hands of someone who holds the additional information, so a card reference that links visits needs a lawful basis and a clear notice.
• Separate service messages from marketing. The ICO's PECR guidance says unsolicited marketing texts and emails normally need consent, with a soft opt-in for similar products where the details came directly from the customer, and every marketing message must offer an opt-out.
• Document the balance. If you rely on legitimate interests, record a legitimate interests assessment, and remember that an objection to direct marketing is absolute.
• Keep card data in the payment application. PCI SSC FAQ 1301 says approved terminals do not by themselves guarantee PCI DSS compliance or reduce scope, so confirm scope with your acquirer.

How to pilot a fast food loyalty programme on the payment terminal

Frictionless loyalty enrolment at checkout still needs testing in a real kitchen. Zeal's retail and QSR page recommends deciding whether optional phone-number capture suits the programme, agreeing the customer prompts and staff guidance, and testing the checkout in your own operating environment.

1. Confirm the devices. Check every terminal model and acquirer route in the pilot sites against the supported list.
2. Choose one journey. Start with automatic stamps or points on payment before adding discounts that change the amount.
3. Write the guest notice. Explain the card reference, the sign-up text message and how to opt out.
4. Brief the team. Staff should know what the terminal will show and what to say if a guest asks.
5. Measure the right things. Track sign-up completion, wallet and card coverage, refunds, complaints and any change in payment time.
6. Scale through the payment provider. PSPs deploy the SDK through their terminal management system, one cohort at a time.

What we have learned about loyalty on payment terminals since 2019

I co-founded Zeal with Belal Mohamed in 2019. Since 2019 I have spent seven years building loyalty that lives on the payment terminal, and we built the core technology in 2020 and 2021. In 2022 and 2023 we spent two years in real-world testing, and merchant feedback from those pilots guided key improvements.

In my experience, loyalty in a busy queue succeeds when nobody has to explain it. That is why we work in three steps:

• We confirm the terminal first. In my experience, supported models vary, so the exact payment terminal is checked before anything is switched on.
• We deploy through our partners' TMS. The payment provider releases the software, so restaurant teams install nothing.
• We agree data requirements up front. Integration and customer-data requirements are agreed before deployment, and Zeal works alongside the existing EPOS and payment processing.

More than 30,000 merchants are activated on Zeal across payment providers. We are live in the UK with Adyen, DNA Payments, Elavon, Lloyds Cardnet, NMI, Viva Wallet and Worldpay, our partners' signed activation pipeline covers 4 million payment terminals, we have raised $14 million in total, and the team won Team of the Year at the UK FinTech Awards 2026. Figures 1 and 2 are Zeal's own explanatory graphics, first published on the Zeal blog.

Frequently asked questions

Can a fast food restaurant recognise repeat customers without an app?

Yes, where its payment terminals are supported. A returning card is recognised from an approved reference during payment, and a first-time guest can join by entering a phone number on the terminal. Guests who pay in cash or with a new card need another way to identify themselves.

How does frictionless loyalty enrolment at checkout work?

A returning guest taps as usual and earns automatically, and a first-time guest is invited on the terminal to enter a phone number once and receive an SMS sign-up link to complete later. Nothing has to be downloaded at payment, and later visits need no extra step.

Does terminal recognition slow down the queue?

It should not add steps for a returning guest, who simply taps as usual. Sign-up adds one step for a first-time guest, so test payment times during the pilot and keep any discount that changes the amount until the basic journey is proven.

What happens when a guest pays with Apple Pay instead of a card?

A phone wallet presents a token that differs from the physical card, so the same guest can appear as two cards. Test wallets separately and give guests a way to link both to one profile.

Do QSRs need consent to text a guest the sign-up link?

The guest asks for the sign-up link by entering a phone number, but any later marketing text normally needs consent or a valid soft opt-in under PECR. Keep the sign-up message and marketing messages separate, and offer an opt-out in every marketing message.

Sources

• UK Finance, UK Payment Markets 2026 (summary), 19 August 2026, and Card Spending Update for March 2026, 16 June 2026.
• Antavo, Global Customer Loyalty Report 2026, 12 March 2026.
• EMVCo, EMV Payment Tokenisation; Adyen Docs, Card and shopper identifiers for loyalty use cases.
• Information Commissioner's Office, Pseudonymisation, PECR electronic mail marketing rules and Legitimate interests (updated 23 March 2026).
• PCI Security Standards Council, FAQ 1301, August 2023.
• Zeal, Loyalty Link, ISV page, developer documentation, retail and QSR page and Dara's Ice Cream app launch, checked 10 October 2026.

About the author

Omar Ebeid is Co-founder and CEO of Zeal, which he founded with Belal Mohamed in 2019. He holds an MSc in Entrepreneurship from the University of Bath and won the Vice-Chancellor's Award at the University of Surrey. Under his leadership Zeal won Team of the Year at the UK FinTech Awards 2026 and Platinum at the Juniper Research Future Digital Awards 2023, and has raised $14 million in total, including a $10 million pre-Series A round announced on 9 September 2026. Connect with Omar on LinkedIn.