Loyalty platforms offering QR and NFC wallet pass options let brands support both scan-based and tap-based loyalty workflows through Apple Wallet and Google Wallet. Platforms use “QR support” and “NFC support” differently. Some only use QR codes or NFC tags for enrollment, while others support member identification and pass validation at checkout.
This guide compares QR codes and barcodes displayed on loyalty passes, NFC wallet-pass validation, Apple VAS, Google Smart Tap, and the hardware and POS requirements behind each setup.
It also explains the difference between a complete loyalty platform and wallet pass infrastructure connected to an existing CRM, POS or loyalty engine. Customers can store a digital loyalty card in Apple Wallet or Google Wallet without downloading a separate brand loyalty app, but enrollment, identification, reward calculations and pass updates still depend on the platform and integration.
Loyalty Platforms Offering Both QR and NFC Wallet Pass Support
The platforms below support loyalty passes in Apple Wallet and Google Wallet with QR or barcode scanning and NFC wallet-pass validation. The main differences are where the loyalty rules run, how each platform connects to existing systems, and what hardware and credentials are required.
| Platform | Wallet Coverage | QR or Barcode Support | NFC Wallet Support | Loyalty Role | Validation Requirements |
|---|---|---|---|---|---|
| PassKit | Apple Wallet and Google Wallet | QR codes and supported barcode formats displayed on the pass | Apple VAS and Google Smart Tap | Wallet-pass infrastructure connected to an existing or custom POS, CRM, database, or loyalty engine | Compatible scanner or staff app for barcodes. Apple VAS or Google Smart Tap reader, certificates, and credentials for NFC. |
| Passcreator | Apple Wallet and Google Wallet | QR codes and barcodes displayed on the pass, with mobile scanning available through Smart Scan | Apple VAS and Google Smart Tap | Pass creation, management, and validation tools | Compatible scanner or staff app for barcodes. Supported VAS or Smart Tap reader and the required wallet configuration for NFC. |
| Stell | Apple Wallet and Google Wallet | QR codes and barcodes available for scanning and fallback validation | Apple VAS and Google Smart Tap | Wallet-pass platform with loyalty tools and connections to POS and CRM systems | Supported NFC terminal or reader for tap-based identification. QR or barcode scanning can remain available where NFC is not supported. |
| PassNinja | Apple Wallet and Google Wallet | QR, Aztec, PDF417, and Code 128 formats | Apple VAS and Google Smart Tap | API-led wallet-pass infrastructure for custom loyalty and identification systems | Compatible barcode scanner or certified NFC terminal, with approved Apple or Google credentials for NFC validation. |
These platforms support scannable wallet-pass data and NFC validation, but they differ in where loyalty rules run and which hardware, credentials, and integrations are required.
For a deeper breakdown of the differences, read our NFC vs QR code comparison
What Counts as QR and NFC Wallet Pass Support?
QR and NFC support can refer to different stages of a contactless loyalty workflow. A platform may use a QR code only for enrollment, place a scannable barcode on an Apple Wallet pass or Google Wallet pass, or connect that code to member identification and reward redemption at checkout.
NFC wallet passes require more than an NFC tag. The pass must carry the correct NFC payload, work with Apple VAS or Google Smart Tap, and communicate with compatible validation hardware. The terminal must then send the member identity to the POS, CRM, or loyalty system. A platform should qualify only when the wallet pass, reader, and backend complete that flow together.
QR Code Enrollment vs Wallet Pass Validation
Scanning a QR code can start the loyalty signup flow, but it does not confirm that the platform can validate the saved wallet pass at checkout. A code on in-store signage, a website, or a receipt may open a sign-up page where the customer adds a digital loyalty card to Apple Wallet or Google Wallet. The saved pass may then display a separate QR code or barcode linked to the member record. The same pass can also be distributed through email, SMS, an app, or a direct web link.
When the customer presents the pass at checkout, a staff app, scanner, or POS reads the identifier and sends it to the connected loyalty system. That system identifies the member and decides whether to add points, apply a reward, or process a redemption. Some platforms also support dynamic or rotating barcodes. QR enrollment and wallet pass validation are separate capabilities, so buyers should confirm support for both.
NFC Tags vs NFC Wallet Pass Validation
Near field communication, or NFC, supports two distinct interactions in this loyalty workflow: opening an enrollment link through an NFC tag and validating a saved wallet pass. Tapping an NFC tag may open a website, signup form, or pass-enrollment link on the customer’s phone. It starts the enrollment flow but does not validate the loyalty pass stored in Apple Wallet or Google Wallet.
An NFC wallet pass carries data that a compatible reader or payment terminal can retrieve through Apple VAS or Google Smart Tap. The reader sends the member identifier to the connected POS, CRM, or loyalty system, which then applies the relevant points, reward, or redemption rules.
A platform should only be described as supporting NFC wallet-pass validation when the saved pass can communicate with compatible hardware and complete that backend workflow. NFC tag distribution alone does not meet that standard.
Apple VAS vs Google Smart Tap for NFC Wallet Passes
Apple VAS and Google Smart Tap both let a loyalty pass communicate with compatible NFC hardware, but they are separate protocols with different setup paths. Apple Wallet contactless passes require VAS-certified readers or payment terminals, compatible POS software, and an approved NFC certificate. Depending on the checkout design, the pass can be read separately, before payment, or alongside an Apple Pay transaction.
Google Wallet uses Smart Tap. The pass must be configured for Smart Tap and connected to a merchant setup that includes a Redemption Issuer ID, Collector ID, configured pass class, authentication keys, and Smart Tap-capable hardware. The terminal sends the pass value to the POS or loyalty system, which processes the member action. The connected backend then sends any updated loyalty data to the pass.
A platform offering NFC wallet passes should prove support for each wallet separately. Standard contactless payment support is not enough, and support for Apple Pay or Google Pay does not confirm loyalty-pass validation. Confirm the protocol, hardware, credentials, POS configuration, and backend flow for both Apple Wallet and Google Wallet before deployment.
Can One Loyalty Pass Support Both QR and NFC?
Yes. A single mobile wallet pass can display a QR code or barcode and carry an NFC payload, provided the platform, wallet, and checkout hardware support both methods. This allows the same pass to work across stores with different payment terminals, scanners, and POS integrations.
- QR supports enrollment. Customers can scan a code on a website, receipt, or in-store signage to add the loyalty pass to Apple Wallet or Google Wallet.
- QR provides a fallback. Staff can scan the code on the saved pass when NFC readers are unavailable, unsupported, or not installed at every location.
- NFC can be introduced gradually. Multi-location brands can enable tap-based identification at selected stores without replacing existing digital passes or changing the loyalty experience elsewhere.
This lets brands add NFC where the hardware supports it without losing QR coverage at other locations.
Hardware and Approval Requirements for QR and NFC Wallet Passes
QR and NFC wallet passes depend on compatible checkout hardware, wallet credentials, terminal configuration, and backend processing. Before rollout, the business, wallet platform, POS provider, and hardware vendor should confirm their respective responsibilities and test the complete workflow on both Apple Wallet and Google Wallet.
QR and Barcode Validation Requirements
A wallet pass can display a QR code or barcode linked to the customer’s member record. The format must be supported by the wallet pass, checkout scanner, and connected POS or validation system.
At checkout, a scanner, staff app, or POS reads the barcode value and sends it to the system responsible for the loyalty rules. That system identifies the member and applies the relevant action, such as adding stamps, updating the points balance, applying a reward, or recording a redemption.
Static, dynamic, and rotating barcodes may require different backend logic. Existing scanners may be suitable, but compatibility should be tested with the actual pass, hardware, and POS integration before rollout.
NFC Reader and Payment Terminal Requirements
NFC wallet passes require readers or payment terminals that support Apple VAS, Google Smart Tap, or both. A terminal that accepts Apple Pay, Google Pay, or another contactless payment method may still be unable to read loyalty-pass data.
The reader must retrieve the member identifier and send it to the correct POS, CRM, or loyalty system. Terminal firmware, reader software, and backend configuration may need changes before the workflow can operate reliably.
The wallet platform, terminal vendor, and POS provider should confirm protocol support, hardware compatibility, software configuration, and how member data reaches the backend.
NFC Certificates and Smart Tap Credentials
Apple Wallet and Google Wallet use separate credentials for NFC loyalty passes. Support for one wallet does not confirm that the other is ready for deployment.
- Apple Wallet: NFC-enabled passes require an approved NFC certificate, Apple VAS-compatible hardware, and POS software that supports the required VAS transaction flow.
- Google Wallet: Smart Tap requires a Redemption Issuer ID, Collector ID, authentication keys, a configured pass class, and compatible terminal hardware.
Confirm who owns and manages each certificate, credential, and key before deployment. The wallet platform may support the setup, but the business, POS provider, and hardware vendor can also have responsibilities.
Test each wallet separately under real checkout conditions. An Apple Wallet pass and a Google Wallet pass may require different credentials, terminal settings, and validation steps.
POS, CRM, and Loyalty System Integration
The scanner or NFC terminal reads the member identifier. The connected POS, CRM, database, or loyalty engine then matches it to the correct customer record and applies the loyalty program rules.
Depending on the setup, that system may add stamps, award points, apply a reward, record a redemption, or update tier status. The backend or integration layer then sends the updated fields to the wallet platform, which changes what appears on the pass.
APIs, webhooks, or middleware may connect these systems. Real-time pass updates depend on that integration rather than on the QR scan or NFC tap alone.
For the wider system architecture, read our guide to loyalty program integration. For systems that need redemption activity reflected on passes in real time, see our guide to mobile wallet loyalty platforms with real-time redemption tracking.
Loyalty Engine or Wallet Pass Infrastructure For NFC & QR?
A wallet pass platform manages pass creation, delivery to Apple Wallet and Google Wallet, QR and NFC data, and pass updates. A loyalty engine manages member profiles, points, tiers, rewards, and earning rules.
Brands with an existing POS, CRM, or loyalty system can keep it as the source of truth and use the wallet layer to display member IDs, points balances, and tier status. Without that backend, an all-in-one loyalty platform may be needed to run the loyalty rules and manage the customer-facing pass.
The choice determines which integrations, APIs, and internal resources the business needs. Our guide to loyalty platform providers explains the wider differences between these platform types.
What a Loyalty Pass Should Display After QR or NFC Validation
After QR or NFC validation identifies the loyalty member, the mobile wallet pass should show their current program status. The pass acts as the customer-facing record in Apple Wallet or Google Wallet, while the connected POS, CRM, database, or loyalty engine remains responsible for the underlying data.
A useful pass may display:
- Member details, including a name, account number, or customer ID
- Program progress, such as a points balance, stamp count, or tier status
- Available rewards, including expiry dates and redemption conditions
- Program information, such as store locations, terms, contact details, or account links
After a purchase or redemption, the backend sends the updated fields to the wallet platform. The pass then reflects the new balance, reward, or membership status. How quickly that happens depends on the POS integration and whether the source system supplies real-time data.
On supported wallets and devices, a pass update may trigger a push notification on the lock screen when a balance, reward, or tier changes. Wallets can also surface a nearby-pass reminder when the customer approaches a participating location, subject to their settings and permissions. These notification features remain separate from QR-based and NFC wallet-pass validation.
QR and NFC determine how the member is identified. The connected backend determines what appears on the pass afterward.
10 Checks Before Choosing a Loyalty Platform With QR and NFC Wallet Pass Support
A platform should be judged on whether the complete loyalty workflow works, not whether QR, NFC, Apple Wallet, or Google Wallet appear on its feature list.
- Confirm wallet coverage
Check that the platform supports Apple Wallet and Google Wallet passes with the capabilities required on each wallet. - Test the enrollment flow
Make sure customers can receive the pass through QR codes, direct links, email, or text messages. Test the process on both an iPhone and an Android phone, including any required customer details, permissions, or consent steps. - Check the saved pass
Confirm that the loyalty card appears correctly in the wallet app and displays a QR code or barcode supported by your checkout equipment. - Verify QR validation
The code should identify the correct member so the connected loyalty system can apply the rules used to earn points or redeem rewards. - Verify NFC wallet-pass validation
Confirm that NFC applies to the saved pass. An NFC tag that only opens a signup page does not meet this requirement. - Check both NFC protocols
Verify Apple VAS and Google Smart Tap separately. Support for one does not prove support for the other. - Confirm hardware compatibility
Ask which scanners, NFC readers, and payment terminals have been tested with the proposed setup. - Assign credential ownership
Establish who obtains and manages certificates, Collector IDs, authentication keys, and other wallet credentials. - Confirm cross-channel member matching
Decide which system stores the member record and verify that QR scans and NFC taps resolve to the same customer profile without creating duplicates. That system should also apply earning and redemption rules and supply the data shown on the pass. - Test the complete workflow
Run enrollment, QR scanning, NFC tapping, backend processing, pass updates, and QR fallback under real checkout conditions.
The customer interaction, validation hardware, loyalty logic, and pass update must operate as one connected flow. Do not commit to terminal hardware or development work until the provider has demonstrated that workflow on both wallets.
