What Is Google Smart Tap?
Google Smart Tap (NFC_SMART_TAP) is Google Wallet's encrypted contactless NFC presentation protocol based on NFC Forum Type 4 Tag / ISO-DEP NDEF service negotiation. It enables Android smartphones to transmit a Loyalty, Offer, Gift Card, Event Ticket, or Generic pass credential over 13.56 MHz NFC directly to compatible POS or access terminals without requiring the user to locate and open a barcode on screen.
Prerequisites & Configuration Parameters
Prerequisites: To use Google Smart Tap (
NFC_SMART_TAP) at physical locations, your Google Wallet Class must declare your authorizedredemptionIssuers(issuerId), your terminal must broadcast the matching 32-bitcollectorId, and your Passinstance Validation Configuration must enableNFC_SMART_TAPreader mode.
-
1
Google Pay & Wallet Business Console Collector ID (
collectorId): Configure a unique numeric Collector ID (andsmartTapMerchantId) in your Google Wallet Issuer profile and upload your compressed ECDH P-256 (prime256v1) public key with a key version integer (e.g.,1). -
2
Class & Object Smart Tap Hydration: When
nfcEnabled: trueis active on a Passinstance template, Passinstance automatically setsenableSmartTap: trueandredemptionIssuers: ["<issuerId>"]on the Google Wallet Class, and writes the pass'sserialNumber(or custom NFC message) intosmartTapRedemptionValueon every issued Google Wallet Object. -
3
Reader Terminal Pairing: Load the matching
collectorId, key version, and ECDH P-256 private key into your POS or certified NFC reader profile. -
4
Passinstance Reader Settings (
NFC_SMART_TAP): Configure the device reader mode toNFC_SMART_TAP(orAUTOdual-protocol VAS + Smart Tap) under Validation Configuration -> NFC Settings alongside your Validation Place so contactless taps execute the exact same 14-rule validation and mechanic engine as optical barcode scans.
Google Wallet Class & Object Smart Tap Schema
When Passinstance synchronizes a Smart Tap-enabled template and pass to Google's walletobjects/v1 API, it includes the following protocol properties:
{
"loyaltyClass": {
"id": "3388000000022194812.cls_7b9e4c12",
"issuerName": "Phenix Roasters",
"programName": "VIP Coffee Club",
"enableSmartTap": true,
"redemptionIssuers": [
"3388000000022194812"
]
},
"loyaltyObject": {
"id": "3388000000022194812.pass_c41a8d20",
"classId": "3388000000022194812.cls_7b9e4c12",
"state": "ACTIVE",
"smartTapRedemptionValue": "PI-8849-2026-X9",
"barcode": {
"type": "QR_CODE",
"value": "PI-8849-2026-X9"
}
}
}
Smart Tap Setup & Validation API Reference
| Method | Endpoint Path | Description |
|---|---|---|
| POST | /api/v1/google-wallet/setup | Configures your Google Wallet issuer account and provisions your Smart Tap collectorId & smartTapMerchantData. |
| GET | /api/v1/google-wallet/status | Returns { isConfigured, collectorId } for your workspace Google Wallet & Smart Tap setup. |
| PUT | /api/v1/reader/validate | Configures Smart Tap / VAS hardware reader collector keys and NFC defaults on your workspace integration. |
| POST | /api/v1/reader/redeem | Processes a reader-decrypted tap redemption payload (X-Reader-Secret, request payload). |
Example: Checking Provisioned Smart Tap Collector ID
GET /api/v1/google-wallet/status
X-API-Key: <API_KEY>
Response (200 OK):
{
"isConfigured": true,
"collectorId": "50992104"
}
Configure the matching collectorId and ECDH key slots on your hardware reader via Settings -> Wallet -> NFC (/settings/workspace/wallet/nfc) or download a NFC config.txt bundle via GET /api/v1/reader/devices/:id/config-file.
Always Keep Optical Barcode Fallback
Even with NFC_SMART_TAP active across your checkout lanes, keep a standard 2D QR or Aztec barcode enabled on the pass layout (nfcNoBarcode: false) so customers with older Android phones or disabled NFC settings can still scan optically.
Explore NFC Pass Configuration, Apple VAS, and Compatible NFC Readers.
