Skip to content
Help Center Guide · NFC & Contactless
3 min readVerified 2026-11-16

Google Smart Tap

Requirements for Google Smart Tap contactless redemption: Collector ID, public/private key pairing, and scanner NFC_SMART_TAP settings.

In This Guide

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.

SYSTEM ARCHITECTURE FLOW
INTERACTIVE ARCHITECTURE
GOOGLE SMART TAP NDEF & ECDH P-256 NEGOTIATION
STAGE 01 PHASE 1: ISSUER, COLLECTOR ID & CLASS KEY BINDING
1
Configure smartTapMerchantId & 8-digit hex/int collectorId via POST/api/v1/google-wallet/setup
2
Register ECDH P-256 Public Key + Key Version in Google Wallet Issuer Account
3
Enable Smart Tap on Class (enableSmartTap: true, redemptionIssuers: [...])
4
Populate smartTapRedemptionValue on each Pass Object (LoyaltyObject, etc.)
STAGE 02 PHASE 2: CONTACTLESS NDEF SERVICE NEGOTIATION (NFC_SMART_TAP)
1
Reader selects Smart Tap AID (A000000476D0000111) over ISO-DEP
2
Negotiates NDEF session (Negotiate SmartTap Request + Reader Ephemeral Key)
3
Android device matches collectorId, signs & encrypts smartTapRedemptionValue using ECDH P-256 shared secret + AES-128-CTR / HMAC-SHA256
4
Reader decrypts payloadDispatches to Passinstance Validation Engine (readerType: "NFC_SMART_TAP"POST/api/v1/reader/redeem or /scans)

Prerequisites & Configuration Parameters

Prerequisites: To use Google Smart Tap (NFC_SMART_TAP) at physical locations, your Google Wallet Class must declare your authorized redemptionIssuers (issuerId), your terminal must broadcast the matching 32-bit collectorId, and your Passinstance Validation Configuration must enable NFC_SMART_TAP reader mode.

  1. 1
    Google Pay & Wallet Business Console Collector ID (collectorId): Configure a unique numeric Collector ID (and smartTapMerchantId) 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. 2
    Class & Object Smart Tap Hydration: When nfcEnabled: true is active on a Passinstance template, Passinstance automatically sets enableSmartTap: true and redemptionIssuers: ["<issuerId>"] on the Google Wallet Class, and writes the pass's serialNumber (or custom NFC message) into smartTapRedemptionValue on every issued Google Wallet Object.
  3. 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. 4
    Passinstance Reader Settings (NFC_SMART_TAP): Configure the device reader mode to NFC_SMART_TAP (or AUTO dual-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:

JSON
{
  "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

MethodEndpoint PathDescription
POST/api/v1/google-wallet/setupConfigures your Google Wallet issuer account and provisions your Smart Tap collectorId & smartTapMerchantData.
GET/api/v1/google-wallet/statusReturns { isConfigured, collectorId } for your workspace Google Wallet & Smart Tap setup.
PUT/api/v1/reader/validateConfigures Smart Tap / VAS hardware reader collector keys and NFC defaults on your workspace integration.
POST/api/v1/reader/redeemProcesses a reader-decrypted tap redemption payload (X-Reader-Secret, request payload).

Example: Checking Provisioned Smart Tap Collector ID

BASH
GET /api/v1/google-wallet/status
X-API-Key: <API_KEY>

Response (200 OK):

JSON
{
  "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.

Ready to launch your first pass program?

Create your workspace, configure your pass template, and test a real pass in Apple Wallet and Google Wallet before you scale.