To provision a new card, the user must complete an authentication and association flow on the user's device to link their external student account to a Google Wallet account. This article describes that process at a high level.
Add to Google Wallet from an Android app
In the following section, we describe the flow to save an account to Google Wallet from an account provider's Android app.
These figures illustrate the user flow to provision a card from a Google Wallet perspective.
- A spinner is shown to the user while network connectivity and initial services complete.
- After the services complete, the user accepts the terms of service and continues with the flow.
- A spinner is shown to the user while background services complete.
- 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.
Google only supports an account linking from Android applications. If you need to support other use cases, check with your Google contact.
If the card is already saved to the selected Google Account, the user is shown a link to open up 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 as normal.
Apps that support Campus ID flows need to integrate with Google Play Services APIs.
However, the method calls from the provider app to Google Play Services aren't available in the publicly distributed version of Google Play Services. Rather, the provider app developer must add and get access to custom modules to call certain methods.
Check with your provider for more information.