Integrate Google Pay

Here's how to integrate Google Pay into your Cards solution.

Introduction

To add Google Pay to your Cards solution, you will need to complete these 3 steps:

1. Signing of the commercial agreement

The first step to offer tokenization is to agree and sign the commercial conditions with us. If you haven't done so yet, contact our sales team.

2. BIN configuration

If you contracted our BIN Sponsorship solution, we will need you to complete this form indicating your app package name and the action that will initiate the flow so that we can configure your BIN in Mastercard Connect or Visa Online. Here is a breakdown of each:

👉🏼 Package name

It is a unique and unambiguous value that identifies your application. With this value, Google can enable your application to use the Push Provisioning flow.

You can find it in the URL of your application in the Google Play Store listing. For example, the URL of an application can be play.google.com/store/apps/details?id=com.example.app123 where the package name is com.example.app123.

👉🏼 Action

This value is what will indicate both to your application and Google what to do when your customer presses the "Add to Google Wallet" button. We recommend that the action be OPEN.

You will need to provide an example of this action so that we can make the corresponding configurations. It could be: com.example.app123.OPEN.

3. Register with Google

To add tokenization with Google Pay to your Cards solution, follow these steps:

Add your company to the contract we have signed with Google by completing this form.

• If you contracted BIN Sponsorship, select the option BIN Sponsor or program manager notifying Google of a sub-entity launch.
• If you are a principal or affiliate member, select the option New Issuer in live Google Pay country.
• Contact our Integrations team or request support from our team using the “Need help?” option on the Dashboard, selecting the contact reason Cards > Wallets/Tokenization > Updates > Update contract.

4. Push Provisioning

Here are the preliminary steps you will need to follow in order to launch Push Provisioning to all your customers.

• The user experience of your application must be consistent with the API guidelines and the Google Pay branding guidelines.
• You have implemented the API functions correctly.
• Your application is stable and ready for release.

To meet these requirements, you will need to complete these steps:

👉🏼 UX / UI Branding Review

Google will assess the designs on how push provisioning will be used in your application and ensure that the proposed follows the brand guidelines.

To enable Google to assess your designs, you will need to complete this form by attaching a presentation (.pptx) or a PDF file (.pdf).

👉🏼Access to Push Provisioning API

To use the Push Provisioning functionality, your application must be enabled for this purpose. To do this, you will need to complete this form.

• Select the Google Wallet use case that applies to your business. We recommend selecting Payments Card.
• Select your company's description. We recommend choosing Financial company or card issuer operations under a BIN Sponsor or Program Manager.
• Indicate that you do NOT have a signed CTA (click-to-accept agreement) with Google, but that Pomelo does. To do this, contact our Integrations team or request support from our team using the “Need help?” option on the Dashboard, with the contact reason being Cards > Wallets/Tokenization > Updates > Update contract.
• Indicate the app package name of your application. Google will use this data to enable Push Provisioning in your app.
  • Indicate that it is for use in a production environment.
• Select the date you wish to go live.
• Select the brand of your cards (Mastercard or VISA).

Configure your application following this guide. Additionally, we provide you with the branding guidelines and best practices for implementing the solution to provide the best experience.

👉🏼 App Review

At this stage, you will need to provide Google with a video for each test case.

Once you have made the videos, you will need to send them to Google using one of these two options:

• Google Drive: upload the videos to your own Google Drive folder and share them with [email protected] in an email.

• Your own file-sharing tool: provide instructions using the general support form for the Google Pay team to access your videos.

  👉🏼 Field Testing

The purpose of this step is to verify that your application and tokens work well in production before publicly launching the feature. To complete this step, you must meet these requirements:

1. You will need to generate at least 25 tokens with a success rate of over 90%.
2. You will need to generate at least 3 transactions with the tokens generated in the previous step with a transaction success rate of over 90%.

3. Field tests cover the following use cases:

   • The user is the primary account holder of the card.
   • The user has one or more cards from the same issuer.
   • The user is a co-owner of a card (if applicable).
   • The user is an authorized user of the card (if applicable).

   Once you have met these requirements, you will need to complete this form requesting Google's final approval.

Important:

• Currently, you can only use one card design per BIN.
• For the Manual Provisioning flow, you should not make any adjustments to your technical integration.
• Since we loaded the configuration in the brand network, you should wait at least 10 business days for the changes to take effect.
• You will need to share between 5 and 20 card-id with us so that we can enable those cards for testing the flows.
  • These card-id must correspond to productive cards.
  • Once you have successfully validated that everything works as expected, contact us so that we can enable your entire BIN for Google Pay. This process needs to be coordinated with the brand network.
• You will need to have your customers' email address and cell phone number registered with area code without symbol in order to send them the identity validation verification code. Example: 541123456777
  • If your customers do not have up-to-date information, you can update it using this endpoint.