Stay organized with collections
Save and categorize content based on your preferences.
To provision a new Hotel Key, the user must complete an authentication
and association flow on their device. This links their external
user account to a Google Wallet account.
This document describes that process at a high level across different surfaces.
Add to Google Wallet from an Android app
In this section, we describe the flow to save a card to
Google Wallet from a Service Provider's Android app.
User flow
These figures illustrate the user flow to provision a Hotel Key from a
Google Wallet perspective.
Figure 1: A user begins to provision their card and accepts the
Terms of Service.
A spinning connection animation is shown to the user while network
connectivity and initial services configure.
After this completes, the user accepts the Terms of Service and
continues with the flow.
Figure 2: User provisioning completes.
A spinning save animation is shown to the user while background services
provision the account on the device.
After the services complete, a success screen appears.
The user might be prompted in subsequent screens to download the
Google Wallet app, if it doesn't already exist on their
device.
Key points
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.
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.
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.
Apps that support Hotel Key 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.
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.
Add to Google Wallet on a Wearable from an Android app
Users can provision to their Wearables by initiating the provisioning flow on
their phone and selecting a single Wearable, as seen in this figure:
Figure 1: Wearable provisioning flow.
Key points
Provisioning to a Wearable requires a phone capable of provisioning a
card.
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.
Users should be limited by the Service Provider to provisioning only a
single Wearable.
Inquire with your Service Provider about the availability of Wearable
provisioning.
Apps that support Hotel Key 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.
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.
Add to Google Wallet from a Website
This section describes the flow to save a card to Google Wallet from
an issuer's website.
Step 1: Sign in to Website
The first step in the flow is to sign in to the issuer's website and select
the Add to Google Wallet button.
Figure 3: A user logs into a website and navigates to the
Add to Google Wallet button.
Step 2: Sign in with Google
The user completes Sign in with Google and then sees a loading screen
on the issuer's website before being redirected to Google Wallet in the next
step.
Figure 3: A user chooses a Google Account to link to their
Hotel Key.
Step 3: Complete Provisioning
The user completes the provisioning flow within Google Wallet.
Figure 3: A user continues with provisioning, accepts terms of
service, and completes the flow.
[null,null,["Last updated 2025-07-11 UTC."],[[["\u003cp\u003eHotel Key provisioning requires users to authenticate and link their external account to Google Wallet.\u003c/p\u003e\n"],["\u003cp\u003eUsers can add Hotel Keys to Google Wallet from Android apps, Wearables (initiated from a phone), and websites.\u003c/p\u003e\n"],["\u003cp\u003eThe provisioning process involves accepting terms of service and may require creating a Google Account if one doesn't exist.\u003c/p\u003e\n"],["\u003cp\u003eService providers may need to integrate with custom Google Play services modules for certain functionalities.\u003c/p\u003e\n"],["\u003cp\u003eWearable provisioning is subject to service provider availability and limitations, such as single Wearable provisioning.\u003c/p\u003e\n"]]],["Users provision a Hotel Key by authenticating and associating their account with Google Wallet. From an Android app, users select \"Add to Google Wallet,\" accept terms, and complete provisioning. Wearable provisioning is initiated from the phone. On a website, users sign in, select \"Add to Google Wallet,\" then sign in with Google and complete provisioning. If a card already exists, users are shown a link to it. A Google account is required; if they dont have one they must create it.\n"],null,["# Provision a new card\n\nTo provision a new Hotel 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 Hotel 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/hotel-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 Hotel Key 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 Hotel Key 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 Hotel 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."]]
