Google Wallet

Overview

Google Wallet now supports adding government-issued digital IDs in select regions, enabling users to present an official ID from their phone for identity verification in a secure and convenient way

• ID: google-wallet
• Type: eID (app)
• Verification Type: Presentation
• Regions: North America, United States
• Countries: AS, BR, GU, MP, SG, TW, US, VI
• Subdivisions: US-AR, US-AZ, US-CA, US-CO, US-GA, US-IA, US-MD, US-MT, US-ND, US-NM, US-PR
• Adoption: 500,000
• URL: https://developers.google.com/wallet/identity

Integration with Trinsic

• Permission required: Yes, this method requires an entitlement from Google in order to start performing verifications from the wallet.
• Cost: Contact the Trinsic team

User Flow

To see an example: watch this video.

The Google Wallet verification flow works on mobile and desktop. On desktop, users are presented a QR code which they scan in order to open the Google Wallet application. On mobile, the user clicks a button which deep-links them to their Google Wallet application. In both cases, the user is taken to their mobile app where they complete a biometric authentication and consent to share the requested data.

Obtaining a Test Credential

In order to complete a Google Wallet verification in test mode, you must first obtain a test credential. Currently, it is not possible to obtain a test mDL credential; however, a test ID Pass credential is available.

ID Passes are fully compliant with 18013-5 and function the same as mDLs. Google Wallet can store both mDLs and ID Passes; Trinsic supports both document types with a single integration.

Google Wallet only accepts credentials issued by trusted authorities.  Creating a test ID pass lets you develop against the API without a real government‑issued ID and without real ID data.

Prerequisites

To create a test ID pass you will need two Android devices: a Holder and an Issuer.

Step 1: Prepare Holder Device

In order to hold and share test credentials, you must configure the Holder Device to use Google Wallet’s Sandbox Environment.

Request Access

The Google account to which your Holder Device is signed in (and which must end in @gmail.com) must first be allowlisted by Google in order to access the Google Wallet Sandbox.

Fill out Google’s Google Pay Sandbox Access Request form to request access.

Note: You will not receive an email or other notification when you have been approved. To know if you have been allowlisted, check if the ability to swap to the sandbox environment (see below) is present on your Holder Device.

Enable the Sandbox Environment

Once approved, you must configure the Holder Device to use the sandbox environment.

Follow Google’s documentation to do this.

To verify that your device is in sandbox mode, open Google Wallet, tap your profile picture → Wallet settings, and look for a SANDBOX message at the bottom.

Step 2: Prepare Issuer Device

On the Issuer Device, download the Utopia ePassport Simulator app, and create a new test credential within it.

Once you’ve created the credential, you’re ready to issue it into the Holder Device.

Step 3: Issue credential to Holder Device

Google’s official documentation for this process is found at this link. You can also follow the following instructions:

1. On the Holder Device, open Google Wallet and tap Add to Wallet.
2. Choose ID → ID pass.
3. When Google Wallet prompts for MRZ scan, do the following with the Issuer Device:
   • From the Utopia app, tap the entry for the new simulated passport you created.
   • Place Issuer Device (with the MRZ screen open) on the back of Holder Device during the NFC scan.
   • Provide any additional biometric or selfie verification required by Google Wallet.
4. After completion, the ID Pass appears in your Google Wallet.

Step 4: Launch Google Wallet Test mode from Trinsic Dashboard

1. Within the Trinsic dashboard, switch to the Test Environment.
2. Navigate to the Verification Profiles page.
3. Click on one of your test mode Verification profiles, or create a new Verification Profile
4. Add Google Wallet to the Verification Profile if not already added
5. Make sure Google Wallet is enabled.
   1. Click the 3-dot icon on the Google Wallet provider in the Verification Profile Providers list, then click Enable.
   2. 
6. Launch a Google Wallet verification
   1. Click the 3-dot icon on the Google Wallet provider in the Verification Profile Providers list, then click Launch Verification
7. Complete the flow using the Holder Device.

Going live

After you’ve tested your integration with a test ID pass, you must request production access for each relying party using the service (usually this means you’ll need a separate approval per Live Verification Profile). As a duly authorized aggregator of Google Wallet, Trinsic will facilitate the approval process for you. Reach out to your representative for next steps.

Direct API Requirements

📘

Direct API is not a requirement.

You can integrate with this provider using the Hosted UI instead, with no additional integration requirements on your end.

What your integration must support in order to use this provider with the Direct Provider Sessions API.

• Supports Direct Provider Sessions: ✅
• Launch Method: PerformNativeChallenge — A native API must be invoked on the user's device with a challenge object, returning a response which must be passed back to Trinsic.
• Collection Method: SubmitNativeChallengeResponse — Submit the device's native challenge response back to Trinsic via the Submit Native Challenge Response API.

Outputs

ℹ️

Normalized Attributes

These attributes form part of our normalized model, a standardized set used across providers. Trinsic normalizes this for you and lets you know when a property is available for each provider.