如需配置新的多户钥匙,用户必须在其设备上完成身份验证和关联流程。这会将外部用户账号与 Google 钱包账号相关联。
本文档将概要介绍不同平台上的该流程。
从 Android 应用添加到 Google 钱包
在本部分中,我们将介绍从服务提供商的 Android 应用将卡片保存到 Google 钱包的流程。
用户流
以下图示从 Google 钱包的角度展示了用于配置多家庭密钥的用户流程。
图 1:用户开始预配卡片并接受《服务条款》。
在配置网络连接和初始服务时,系统会向用户显示旋转的连接动画。
完成此操作后,用户接受《服务条款》并继续执行流程。
图 2:用户配置完成。
当后台服务在设备上预配账号时,系统会向用户显示旋转的保存动画。
服务完成后,系统会显示一个成功界面。
如果用户设备上尚未安装 Google 钱包应用,系统可能会在后续界面中提示用户下载该应用。
要点
如果卡已保存到所选 Google 账号,系统会向用户显示一个链接,用于在 Google 钱包应用中打开该卡,以便用户查看卡详情。
如果卡已保存到用户登录的 Google 账号以外的其他 Google 账号,用户会收到一条消息,指出其他 Google 账号已保存该卡。
如果用户尝试添加卡片,但没有 Google 账号,系统会提示用户创建账号。创建 Google 账号后,流程会照常继续。
支持多家庭密钥流程的应用需要与 Google Play 服务 API 集成。不过,服务提供商应用对 Google Play 服务的这些方法调用在公开分发的 Google Play 服务版本中不可用。服务提供商应用开发者必须添加并获取对自定义模块的访问权限,才能调用某些方法。如需了解详情,请咨询您的服务提供商。
支持多家庭密钥流程的应用需要与 Google Play 服务 API 集成。不过,服务提供商应用对 Google Play 服务的这些方法调用在公开分发的 Google Play 服务版本中不可用。服务提供商应用开发者必须添加并获取对自定义模块的访问权限,才能调用某些方法。如需了解详情,请咨询您的服务提供商。
通过网站添加到 Google 钱包
本部分介绍如何通过发卡机构的网站将卡保存到 Google 钱包。
第 1 步:登录网站
此流程的第一步是登录发卡机构的网站,然后选择“添加到 Google 钱包”按钮。
图 3:用户登录网站并前往“添加到 Google 钱包”按钮。
第 2 步:使用 Google 账号登录
用户完成“使用 Google 账号登录”流程,然后在发卡机构的网站上看到加载屏幕,之后在下一步中被重定向到 Google 钱包。
[null,null,["最后更新时间 (UTC):2025-07-11。"],[],[],null,["# Provision a new card\n\nTo provision a new Multi-family Key, the user must complete an authentication\nand association flow on their device. This links their external\nuser account to a Google Wallet account.\nThis document describes that process at a high level across different surfaces.\n\nAdd to Google Wallet from an Android app\n----------------------------------------\n\nIn this section, we describe the flow to save a card to\nGoogle Wallet from a Service Provider's Android app.\n\n### User flow\n\nThese figures illustrate the user flow to provision a Multi-family Key from a\nGoogle Wallet perspective.\n| **Note:** Before this flow begins, the user must authenticate within the Service Provider's app. Next, they must select the [Add to Google Wallet](/wallet/access/multi-family-key/get-started/brand-guidelines#add-to-google-wallet-button) button. If the user doesn't have a Google Account, they complete a flow to create one and then continue the flow to provision their card.\n**Figure 1**: A user begins to provision their card and accepts the Terms of Service.\n\n\n- A spinning connection animation is shown to the user while network connectivity and initial services configure.\n- After this completes, the user accepts the Terms of Service and continues with the flow.\n\n\u003cbr /\u003e\n\n**Figure 2**: User provisioning completes.\n\n\n- A spinning save animation is shown to the user while background services provision the account on the device.\n- After the services complete, a success screen appears.\n- The user might be prompted in subsequent screens to download the Google Wallet app, if it doesn't already exist on their device.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n### Key points\n\n- If the card is already saved to the selected Google Account, the user is instead shown a link to open the card in the Google Wallet app, where they can view card details.\n- If the card is saved to a Google Account other than the one the user is logged into, the user receives a message that indicates another Google Account has already saved that card.\n- If the user attempts to add a card and doesn't have a Google Account, a prompt to create an account appears. After creation of the Google Account, the flow continues normally.\n- Apps that support Multi-family Keys flows need to integrate with Google Play services APIs. However, the method calls from the Service Provider app to Google Play services aren't available in the publicly distributed version of [Google Play services](https://developers.google.com/android/guides/overview). The Service Provider app developer must add and get access to custom modules to call certain methods. Check with your Service Provider for more information.\n\nAdd to Google Wallet on a Wearable from an Android app\n------------------------------------------------------\n\nUsers can provision to their Wearables by initiating the provisioning flow on\ntheir phone and selecting a single Wearable, as seen in this figure:\n**Figure 1**: Wearable provisioning flow.\n\n### Key points\n\n- Provisioning to a Wearable requires a phone capable of provisioning a card.\n- Users can provision to their phone and Wearable in a single flow, or they can restart the flow to add it to a Wearable after the first provisioning to their phone is complete.\n- Users should be limited by the Service Provider to provisioning only a single Wearable.\n- Inquire with your Service Provider about the availability of Wearable provisioning.\n- Apps that support Multi-family Keys flows need to integrate with Google Play services APIs. However, the method calls from the Service Provider app to Google Play services aren't available in the publicly distributed version of [Google Play services](https://developers.google.com/android/guides/overview). The Service Provider app developer must add and get access to custom modules to call certain methods. Check with your Service Provider for more information.\n\nAdd to Google Wallet from a Website\n-----------------------------------\n\nThis section describes the flow to save a card to Google Wallet from\nan issuer's website.\n\n### Step 1: Sign in to Website\n\nThe first step in the flow is to sign in to the issuer's website and select\nthe Add to Google Wallet button.\n**Figure 3**: A user logs into a website and navigates to the Add to Google Wallet button. **Important:** Google requires that your website authenticates users before you show the Add to Google Wallet button. Sending the user an email with a \"secret\" link is not sufficient authentication.\n\n### Step 2: Sign in with Google\n\nThe user completes Sign in with Google and then sees a loading screen\non the issuer's website before being redirected to Google Wallet in the next\nstep.\n**Figure 3**: A user chooses a Google Account to link to their Multi-family Key. **Note:** You can download this [loading gif](/static/wallet/access/images/web-provisioning-loading.gif) for use on your website's loading page if you would like to match the Google Wallet loading screen.\n\n### Step 3: Complete Provisioning\n\nThe user completes the provisioning flow within Google Wallet.\n**Figure 3**: A user continues with provisioning, accepts terms of service, and completes the flow."]]