Web Push Provisioning for Google Wallet
Before you start, make sure tokenization is live on your Bank Identification Number (BIN) and you've confirmed a build path with your Customer Success Manager.
Part 1: Requirements
To add cards to Google Wallet from your website, your program needs its own profile in the Google Issuer Console, Google's portal for card issuers. Visa connects your program to Google on your behalf, so you complete Google's onboarding up to the key exchange. Unit handles the remaining steps.
Step 1: Create a Google Issuer Console Profile
Create your profile by following Google's Get Started page. When the profile setup asks for your Visa BID (Business ID, Visa's identifier for the bank that issues your cards), enter the BID for your bank partner:
| Bank partner | Visa BID |
|---|---|
| Thread Bank | 10034854 |
| i3 Bank | 10006981 |
If you're not sure which bank partner issues your cards, ask your Customer Success Manager.
Step 2: Add Unit as a Technical Contact
Add cardops@unit.co as a technical contact on your profile so Unit can submit your user flows and launch request to Google on your behalf.
Step 3: Complete Onboarding Through the Key Exchange
In the Google Issuer Console, complete onboarding steps 1–4, which include signing Google's Non-Disclosure Agreement (NDA) and Click to Accept (CTA) agreement. Stop when you reach the key exchange step. This completes your work in the Issuer Console.
Step 4: Share Your Web Origins
Send your Customer Success Manager each web origin, the website address where the Add to Google Wallet button will appear (for example, www.banking.com). Unit allowlists your origins with Visa and Google on your behalf.
Requirements Complete
Once you've completed onboarding and shared your web origins, Unit configures your program with Visa and Google. Your Customer Success Manager will let you know when your configuration is complete and your developers can start the integration.
Part 2: Integration
Your developers start once Unit confirms that your configuration is complete. Add one of Unit's components to your website. Each one needs the card ID and a customer token for the end customer. Either one covers both Apple Wallet and Google Wallet, so if you've already added a component for one wallet, it covers the other as well.
- Card component: The full card interface, with Add to Wallet built in. Follow the web steps in the Card component guide.
- Add to Wallet component: Only the Add to Wallet buttons, for your own card interface. Follow the Add to Wallet component guide.
You can build the Add to Wallet button and flow from scratch instead of using a Unit component. Expect significantly more engineering time and more extensive approvals. Talk to your Customer Success Manager before you start.
Part 3: Test and Launch
Test Your Integration
Contact your Customer Success Manager for guidance on testing. To run the Add to Google Wallet flow end to end, you need:
- Google Account: To sign in and start the flow from your website.
- Android device that supports Google Wallet: The flow starts in a browser, but the card is activated in the Google Wallet app on the device, so you need one to confirm the card arrives.
Google's Launch Approval
Unit handles the remaining steps with Visa and Google on your behalf. Unit configures your program with Visa, finalizes the required steps in your Google Issuer Console profile, and submits your launch request to Google.
Google's approval typically takes about a month and can take longer.
Unit's Launch Approval
Once Google approves and you've tested your integration, Unit enables web push provisioning for your program, and the Add to Google Wallet button goes live for your end customers on your website.
When a card is added to Google Wallet from the web, Google creates a device token, the Device Primary Account Number (DPAN), that stands in for the card during in-store and in-app payments. Google also saves the underlying card number, the Funding Primary Account Number (FPAN), to the end customer's Google account, so they can spend online and on devices that can't create a device token. Unit configures your program with Visa to support this DPAN and FPAN model.