公司徽章概览
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
公司工牌是闭环卡片，用于识别
并授予建筑物访问权限
用户可以将自己的公司工牌添加到
使用 Android 手机安全地访问工作场所
建筑物。
企业徽章还能让用户
对个人信息的访问权限（如用户详细信息和
重要工作场所电话号码
用户必须满足的前提条件
用户需要满足以下条件才能在 Google 钱包中使用公司工牌：
- 从 Google Play 下载其服务提供商应用的最新版本
- 为了尽可能提供更流畅的用户体验，不妨考虑创建 Play 免安装应用。本指南中介绍的通过 Android 应用创建公司徽章的所有功能均与 Play 免安装应用兼容。有关免安装应用的详情，请参阅
Google Play 免安装体验概览。
- 搭载 Android 9.0 或更高版本且已开启 NFC 功能的手机
- 最新版本的 Google 钱包应用（推荐）
如需详细了解用户支持信息，请参阅
报道
将公司工牌保存到 Google 钱包。
适用于工作场所的前提条件
工作场所需要满足以下条件才能支持通过 Google 钱包使用公司工牌：
- 支持 NFC 的读卡器，能够通过服务提供商支持的协议从 Google 钱包接收用户账号凭据。
品牌推广指南
品牌推广指南包含与“添加到 Google 钱包”相关的信息按钮指南和企业徽章素材资源
要求。您还可以使用字段映射模板
企业徽章上的每个字段。
卡配置和用户体验
服务提供商应用将用户账号与
通过“添加到 Google 钱包”流程登录 Google 账号。如需详细了解此集成的步骤，请参阅预配新卡片。
术语
下表介绍了本文档中使用的术语及其
含义。
| 组件图对象定义 |
| 访问读取者 |
支持 NFC 的工作场所读卡器。 |
| 账号 |
通常由使用服务提供商管理系统的工作场所管理。
|
| 账号中心 |
账号中心可以访问管理访问卡生命周期所需的信息，以及通过访问读卡器进行身份验证所需的身份验证密钥。账号中心还会执行安全和风险活动，以提高系统的整体安全性。
|
| Google Play 服务 |
Google Play 服务应用及其设备服务，用于启用所有企业徽章功能。此组件还涵盖 Google 钱包应用。如需了解详情，请参阅 Google 钱包结构页面。
|
| Google 服务器 |
实现多个闭环 API 的 Google 后端服务器
支持企业徽章。
|
| 服务提供商 |
工作场所管理系统的技术提供商。
|
| Workspace 应用 |
由 Workplace（或服务提供商）创建的 Android 应用，供用户管理其账号。
也称为服务提供商应用。
|
| 发卡机构 |
发卡的 Workplace。
|
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-25。
[null,null,["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003eCorporate Badges are NFC-enabled digital cards stored in Google Wallet for secure building access and workplace information.\u003c/p\u003e\n"],["\u003cp\u003eEmployees need an Android phone running Android 9.0 or higher, NFC enabled, and the latest versions of the Service Provider and Google Wallet apps.\u003c/p\u003e\n"],["\u003cp\u003eWorkplaces need NFC-enabled readers compatible with Google Wallet and the Service Provider's protocol to support Corporate Badges.\u003c/p\u003e\n"],["\u003cp\u003eService Providers link user accounts to Google Accounts for card provisioning, streamlining building access management.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Wallet provides fast access to user details and workplace information, improving employee experience.\u003c/p\u003e\n"]]],["Corporate Badges identify users and grant building access via Android phones. Users add badges to Google Wallet through their Service Provider's app, requiring Android 9.0+, NFC, and the latest Wallet app. Badges provide user details and workplace numbers. Workplaces need NFC-enabled readers. Service Provider apps link user accounts to Google Accounts, and the documentation includes brand guidelines, provisioning steps, and terminology, including \"Account Hub,\" \"Service Provider,\" and \"Workplace app.\"\n"],null,["# Corporate Badge Overview\n\nCorporate Badges are closed-loop cards used to identify\nusers and grant building access.\n\nUsers can add their Corporate Badge to their\nAndroid-powered phone to securely access workplace\nbuildings.\n\nCorporate Badges also give users fast\naccess to information such as user details and\nimportant workplace phone numbers.\n\nUser prerequisites\n------------------\n\nFor a user to use Corporate Badges with Google Wallet, they need the following:\n\n- The latest version of their Service Provider's app from Google Play\n - For a possibly more streamlined user experience, consider creating a Play Instant App. All functionality in this guide for creating Corporate Badges from Android apps is compatible with Play Instant Apps. For more information about Instant Apps, see the [Overview of Google Play Instant](https://developer.android.com/topic/google-play-instant/overview).\n- A phone that runs Android 9.0 or higher, with NFC turned on\n- The latest version of the Google Wallet app (recommended)\n\nFor more user support information, see the support\narticle\n[Save your corporate badge to Google Wallet](https://support.google.com/wallet/answer/14085932).\n\nWorkplace prerequisites\n-----------------------\n\nFor a workplace to support Corporate Badges with Google Wallet, they need the following:\n\n- NFC-enabled readers capable of receiving a user account credential from Google Wallet through the Service Provider's supported protocol.\n\nBrand guidelines\n----------------\n\nThe [brand guidelines](/wallet/access/corporate-badge/get-started/brand-guidelines) contain information on \"Add to Google Wallet\" button guidelines and Corporate Badge asset\nrequirements. A field mapping template is also available to show how data maps\nto each field on a Corporate Badge.\n\nCard provisioning and user experience\n-------------------------------------\n\nThe Service Provider app links the user account to a\nGoogle Account through the Add to Google Wallet flow. For details on the\nsteps of this integration, see\n[Provision a new card](/wallet/access/corporate-badge/get-started/provision).\n\nTerminology\n-----------\n\nThe following table describes terms used in this documentation and their\nmeaning.\n\n| Component Diagram Object Definitions ||\n| Access Reader | NFC-enabled workplace readers. |\n| Account | Typically managed by workplaces that use a Service Provider's management system. |\n| Account Hub | Account Hubs have access to the information necessary to manage the lifecycle of access cards and the required auth keys to authenticate with access readers. The Account Hub also performs security and risk activities in order to improve overall security of the system. |\n| Google Play Services | The Google Play Services application and its device services, which enable all Corporate Badge functionality. This component also encompasses the Google Wallet app. For more information, see the [Google Wallet structure](/wallet/access/corporate-badge/guides/google-wallet-structure) page. |\n| Google Servers | Google backend servers that implement several closed-loop APIs supporting Corporate Badge. |\n| Service Provider | Technology providers of workplace management systems. |\n| Workplace app | An Android application created by a Workplace (or Service Provider) for user to manage their account(s). \u003cbr /\u003e Also referred to as Service Provider app. |\n| Card Issuers | The Workplace that issues the cards. |\n|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"]]
