> ## Documentation Index > Fetch the complete documentation index at: https://docs.passentry.com/llms.txt > Use this file to discover all available pages before exploring further. # Using NFC with Apple Wallet and Google Wallet passes > Set up NFC passes for Google Wallet and learn about Apple Wallet approval, suitable use cases and support from PassEntry. An NFC-enabled pass can be tapped against a reader instead of scanned. Both wallets read the same NFC value from the pass, but each has its own prerequisites before that value reaches a reader. Google Wallet needs no approval. Apple Wallet needs an entitlement from Apple, granted per use case, which takes weeks to obtain. > [!NOTE] > > Each wallet uses its own protocol to carry the NFC value to the reader. Apple uses [Apple Pay Value Added Services](https://developer.apple.com/wallet/loyalty-passes/#implementation) and Google uses [Smart Tap](https://developers.google.com/wallet/smart-tap). Both work with the same PassEntry readers. ## Google Wallet and Apple Wallet compared | | Google Wallet | Apple Wallet | | - | - | - | | Approval required | None | Apple NFC entitlement | | Application route | Not applicable | Contact PassEntry first; the route depends on your region and use case | | Typical lead time | None | Allow 4 to 10 weeks per use case; timing is not guaranteed | | Scope of approval | Not applicable | Use case and territory | | Barcode and QR passes | No approval needed | No approval needed | Until Apple grants the entitlement, the same pass taps on Android but offers no tap option on iPhone. This is expected and not an error. ## Choosing between NFC and barcode Barcodes work on every device with no approval, no reader hardware and no lead time. Most integrations are better off launching on barcode and adding NFC once the use case is proven and any Apple entitlement has been granted. NFC suits loyalty redemption, membership identification, hotel check-in and event entry. The holder holds their phone to the reader instead of finding the pass and presenting a code, and the NFC value is never displayed, so a pass that carries only NFC can't be shared as a screenshot. Check that your use case is [suitable](#suitable-use-cases) before choosing your reader hardware. A pass can carry both. On Apple the barcode appears in the pass details, and on Google it appears behind a "Show code" button. ## While Apple approval is pending You do not have to wait for Apple before building. Without the Apple entitlement you can still: * Issue passes to both wallets (without NFC on Apple Wallet). * Tap Android devices against a reader using Google NFC. * Run your full API integration, including pass creation, updates, notifications and webhooks. * Validate passes on iPhone using a barcode or QR code. The only thing the entitlement blocks is NFC on the Apple pass itself. ## Choose your certificate before you issue passes Apple passes are signed with a Pass Type Identifier certificate. PassEntry can issue passes on its own certificate, but if you later move to your own certificate, you will need to reissue those passes. If you plan to add Apple NFC, contact us before going live so we can advise on the certificate setup for your application route. **With your own certificate from the start**, adding NFC later is an update. Once Apple grants the entitlement, you update the certificate and the barcode passes you have already issued can be updated to carry NFC. Holders keep the pass they already have. **If you move from a PassEntry certificate to your own**, existing passes cannot move across. You have to deactivate them and reissue every pass to every holder on your new certificate. Adding your own certificate needs no NFC approval. If your application route requires your own certificate, set it up before you go live. See [Adding an Apple Pass Certificate](https://docs.passentry.com/documentation/adding-an-apple-pass-certificate.md). ## Setting up Google NFC **1. Enable NFC on your pass template** Open the template in the PassEntry dashboard, find the **Scanning** section and turn on **Enable NFC**. **2. Set the NFC value** The NFC value is what the reader receives when the pass is tapped. Under **Source**, choose **UUID**, **Ext ID** or **Custom**, in the same way you choose a barcode value. See [Pass Identifiers](https://docs.passentry.com/documentation/passes/identifiers/guide.md) for when to use each. Loyalty templates have a separate **Enable Google NFC** toggle that must also be on. When it is on and the template has a barcode value but no NFC value, the pass presents the barcode value over NFC. See [the FAQ](https://docs.passentry.com/faq/guide.md#why-do-i-have-to-choose-to-enable-google-nfc-when-creating-a-loyalty-pass) for how the two fields interact. **3. Set up a reader** Use the [PassEntry Reader app](https://docs.passentry.com/documentation/guides/passentry-reader-app/guide.md) on a supported handheld device, a [VTAP reader](https://docs.passentry.com/documentation/guides/vtap-reader/guide.md), or your own hardware. Apple use cases require a VAS-approved reader. To send each tap to your own system rather than validating it in PassEntry, see [Third-Party Validation](https://docs.passentry.com/documentation/guides/validation-options/guide.md). **4. Test the tap** Add the pass to Google Wallet on an Android device and hold the phone against the reader. The reader receives the NFC value, applies whichever validation you have configured, and logs the scan in PassEntry. ## Applying for the Apple NFC entitlement Start by sending your use case to PassEntry. We review your requirements, region and expected pass volumes, then advise on the application route. Depending on that review, we may submit the request to Apple on your behalf or advise you to apply directly. Contacting us does not guarantee a submission or approval. Apple's process varies by region. Approval covers the agreed use case and territory only. Contact us before expanding your use case or launching in another country. ### Suitable use cases Use cases to discuss with PassEntry include: * Membership identification. * Hotel check-in. * Loyalty programmes. * Gift vouchers. * Event ticketing. These examples still require approval. Door and building access, including hotel room keys, and financial services such as credit cards and payments are outside the scope of this NFC pass service. Hotel check-in does not include unlocking a room. If you are unsure whether your use case fits, contact us before starting an application. ### Application steps **1. Send your use case to PassEntry** Email [support@passentry.com](mailto:support@passentry.com) with: * Your use case and the countries where it will operate. * Your expected pass volumes and rollout plans. * The pass type and reader hardware you plan to use. * The legal entity responsible for the service. * Any existing Apple entitlement application or response from Apple. **2. Confirm your application route and requirements** We review your submission and ask for any missing information. We then confirm whether we can submit it to Apple on your behalf or whether you need to apply directly. We will explain what your route requires, including any Apple Developer account and certificate. See [Adding an Apple Pass Certificate](https://docs.passentry.com/documentation/adding-an-apple-pass-certificate.md) for enrolment and certificate setup. If you cannot meet a requirement, such as having an Apple Developer account, tell us so we can advise on your options. **3. Supply the information Apple requests** Apple may ask follow-up questions about the business case and technical setup. Supply these through the application route agreed with PassEntry. **4. Confirm permission before testing** Allow 4 to 10 weeks for the application process. Timing and approval are not guaranteed. > [!WARNING] > > Do not issue Apple NFC passes without approval for your use case. If you receive permission to test, keep within the agreed scope and limits. Test permission does not authorise a production launch. **5. Configure your certificate** Follow PassEntry's guidance on the certificate required for your approved application route. See [Choose your certificate before you issue passes](#choose-your-certificate-before-you-issue-passes) for what this means for passes you have already issued. **6. Complete the go-live requirements** Confirm the launch requirements with PassEntry before rolling out. You may need to provide evidence of the working integration, staff training and customer-facing materials promoting Apple Wallet NFC. Supply the evidence requested for your use case and wait for confirmation that you can go live. ### How PassEntry can help You can contact PassEntry for an initial eligibility enquiry whether or not you are a signed live client. Include your use case, region and expected pass volumes, and tell us if you have trouble meeting any requirements. For signed live clients, we also provide detailed application support: reviewing your application before submission, sharing guidance from previous applications, and supplying technical details about how passes are issued and validated. Apple decides whether to approve your application; PassEntry cannot guarantee approval or a faster response. Contact [support@passentry.com](mailto:support@passentry.com) to get started. ## Related topics - [PassEntry FAQs: API keys, NFC, templates, and limits](https://docs.passentry.com/faq/guide.md) - [Downloading Passes](https://docs.passentry.com/documentation/passes/downloading-passes/guide.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.