[null,null,["最后更新时间 (UTC):2025-08-29。"],[[["\u003cp\u003eThe Smart Tap protocol uses Redemption Issuer ID, Collector ID, and Pass class ID to facilitate communication between Google Wallet and terminals, enabling merchants to redeem passes from various developers.\u003c/p\u003e\n"],["\u003cp\u003eRedemption Issuer ID typically represents a single merchant and is used for Smart Tap and other features like geo-based notifications.\u003c/p\u003e\n"],["\u003cp\u003eCollector ID is a unique numeric ID assigned to a Redemption Issuer, enabling terminals to identify themselves and request a specific merchant's pass when a user taps their device.\u003c/p\u003e\n"],["\u003cp\u003ePass class ID identifies a specific type of pass and is linked to an Issuer account, allowing a pass object referencing this ID to be saved to a user's Google Wallet.\u003c/p\u003e\n"]]],["The Smart Tap protocol uses three identifiers for communication between Google Wallet and terminals: Redemption Issuer ID, Collector ID, and Pass Class ID. The Redemption Issuer ID represents a merchant, while the Collector ID uniquely identifies a terminal requesting a merchant's pass. A Pass Class ID, formatted as `issuerId.classSuffix`, identifies a specific pass tier. These IDs facilitate the exchange of information, enabling merchants using different pass developers to redeem passes. An Issuer account can have only one Collector ID.\n"],null,["# Collection identifiers overview\n\nThis page describes the identifiers used by the Smart Tap protocol.\n\nOverview\n--------\n\nThe Smart Tap protocol communicates information about a pass saved to a user's\nGoogle Wallet app and the terminal application. The following graphic summarizes\nthe communication flow between the terminal and Google Wallet:\n\nBecause merchants may use multiple businesses or contractors to develop their\npasses, Google uses three identifiers to facilitate sending information between\nGoogle Wallet and terminals. This allows merchants who use a particular terminal\nprovider to redeem passes from different developers. The following IDs are the\nthree \"collection identifiers\" used in the Smart Tap protocol.\n\n- [Redemption Issuer ID](#redemption_issuer_id)\n- [Collector ID](#collector_id)\n- [Pass class ID](#pass_class_id)\n\n| **Note:** Along with these identifiers, pass developers are responsible for defining what data is mapped and communicated between Google Wallet and terminals. Additional configuration is also required so that the terminal can recognize the mapped fields.\n\nRedemption Issuer ID\n--------------------\n\nA Redemption Issuer ID is a specific type of Issuer ID. A Redemption Issuer ID\ntypically represents a single merchant. In contrast, an Issuer ID for a\npass developer might represent a platform that stores pass classes for many\ndifferent merchants. A platform that stores pass classes for multiple merchants\nis also referred to as an Aggregator.\n\nRedemption Issuers are used for more than just Smart Tap. For example,\nRedemption Issuers are also used to render geo-based notification reminders\nbased on the Redemption Issuer's locations. So, an Issuer ID that's listed as a\nRedemption Issuer on a pass might not be configured for Smart Tap.\n\n### Redemption Issuer ID vs. Issuer ID\n\nAn Issuer ID is a unique identifier of a Google Wallet Issuer account. The\nIssuer ID can be found the\n[Google Pay \\& Wallet Console](https://pay.google.com/business/console/home).\n\nAn Issuer can represent a merchant (such as a restaurant), an offer provider, or\na terminal manufacturer, and more. When pass classes and objects are developed,\nthey are linked to a specific Issuer ID. The Issuer ID is included in both pass\nclass IDs and object IDs.\n\n| ID | Format | Notes |\n|-----------|-------------------------|--------------------------------------------------------------------------------------------------------|\n| Class ID | `issuerId.classSuffix` | The `classSuffix` is a unique, developer-defined value for a specific pass class (e.g. a loyalty tier) |\n| Object ID | `issuerId.objectSuffix` | The `objectSuffix` is a unique, developer-defined value for a specific pass object (such as a user ID) |\n\nAn Issuer can create as many classes as they need.\n\nCollector ID\n------------\n\nIf a merchant supports Smart Tap at their terminals, their Redemption Issuer\nwill have a Collector ID. The Collector ID is a numeric ID (8 digits) that\nterminals use to identify themselves. Since a Redemption Issuer may support\nmultiple merchants, the Collector ID is used to request a specific merchant's\npass.\n\nWhen a user taps their device to a Smart Tap capable terminal, the terminal\nsends the Collector ID to the user's device. The device then authenticates with\nthe terminal using the public key for that Collector ID. See\n[Communication flow](/wallet/smart-tap/introduction/communication-flow) to learn more.\n\nImportant notes:\n\n- Only one Collector ID is assigned to an Issuer ID\n- A Collector ID is unique across all Issuer IDs\n\nTo obtain a Collector ID for your Issuer ID, see\n[Merchant configuration](/wallet/smart-tap/introduction/merchant-configuration).\n| **Note:** An Issuer account can only have one Collector ID.\n\nPass class ID\n-------------\n\nA class ID identifies a particular tier or type of pass. A class ID follows the\nformat below: \n\n issuerId.classSuffix\n\nThe class suffix is a developer-defined value unique to this pass class. A pass\nobject referencing this class ID is saved to a user's Google Wallet app.\n| **Note:** A pass class ID is owned by a single Issuer account, but can be linked to multiple Redemption Issuer IDs."]]