Issuer Onboarding Guide for Indian Issuers

This page outlines the issuer onboarding process for GPay India App.

Get Started

To add support for Google Pay device tokens, you will need to onboard through the Issuer Console and complete two legal agreements with Google (a non-disclosure agreement and an issuer agreement), followed by the technical integration with your token service provider (TSP). Reach out to your TSP for more information on the technical work required to integrate with their APIs for device tokenization, and learn more about the onboarding process through Issuer Console by visiting the global Get Started page.

Once you have accepted the NDA and issuer agreement, you are ready to begin integration work with your TSP! Your TSP should be able to guide you through the process of configuring their systems and integrating with their APIs related to device tokenization. The TSP integration section of this site explains Google Pay product behavior, including Google Pay specific requirements for how you configure the settings at your TSP.

Restricting Access

Before launch, regular users shouldn't be able to provision their cards. Work with your TSP to restrict tokenization access to only authorized test and internal user cards until your launch is approved.

Launch Checklist

To ensure a smooth launch of your Google Pay integration please ensure you have:

  • Signed an NDA with Google.
  • Signed the issuer agreement with Google.
  • Completed all functional tests to ensure your tokenization experience is working properly.
  • Confirmed that no known problems exist related to tokenization, in-app transactions, bill payment transactions, BharatQR transactions, or online transactions.
  • Trained your support team to properly handle and route cardholder inquiries.
  • Updated your website to inform cardholders about Google Pay as appropriate, including any relevant user-facing Google Pay support information.
  • Submitted the list of products to launch in English and in your local language to your TSP. This information will be used to update our supported issuers list.
  • Submitted launch checklist documentation with your TSP.
  • Submitted Production Testing Acknowledgement form to your TSP.
  • Received certification from your TSP for launching in production.

Enable Sandbox Mode

During the integration with TSP, you need to use the sandbox mode to test in non-prod env.

Before users can start testing the cards, they need to be allowlisted by Google. Send the email IDs of the testers to this address: gpay-india-issuer-onboarding@google.com. Share all tester email IDs in one go. Write one email ID per line with no commas and periods (no bullet points).

To enable sandbox mode, first ensure that you have downloaded and installed the APK from this shared folder.

To turn sandbox mode on, download the file android_pay_env_override_sandbox using the Android Device's mobile browser. By default, this should download to the /sdcard/Download folder with the file name android_pay_env_override_sandbox. Once you have downloaded the file, reboot the device. After that, the sandbox mode is enabled.

Enable OTP Auto-fill

There are 2 different OTPs for India cards and each one requires a different template. Issuers need to work with their internal teams to ensure the OTP format matches the ones listed below for auto-fill.

Provision OTP

The provisioning OTP is sent when the user tries to add a card. To have the OTP auto-filled, the SMS text should contain any one of the following words or phrases:

  • OTP
  • One Time Password
  • Google Pay

Example: 123456 is your OTP to register your card ending with 6789 on Google Pay.

Transaction OTP

Transaction OTP is sent when the user attempts to make a payment using the card. The OTP is auto-filled if the SMS text contains any one of the following phrases:

  • ... 123456 is the OTP ...
  • ... 123456 is the One Time Password ...
  • ... for Google Pay is 123456 ...
  • ... OTP for your digital wallet is 123456 ...

Example: Hello, 123456 is the OTP for your transaction of Rs 123 with card ending with 6789.

Testing

Issuers should complete the following end-to-end tests for each network and card portfolio you issue to make sure your integration with Google Pay works flawlessly for cardholders.

Add Card

Test case Preconditions Test steps Verification
Add Card option should be visible.
  1. Open Google Pay
  2. Go to Settings > Payment Methods
 Add Card option should be visible.
Verify if OTP is asked while adding Card and auto read. This card has not been added to Google Pay
  1. Open Google Pay.
  2. Go to Payment methods > Add card.
  3. Fill all required details to add card > Accept
  4. OTP should be received to activate card.
  1. OTP should be auto read
  2. Card should get added successfully
Attempt to add a card with incorrect expiry. This card has not been added to Google Pay
  1. Open Google Pay.
  2. Go to Payment methods > Add card.
  3. Try adding expired card
 After entering invalid expiry date, error should be triggered at that field and user should not able to add that card.
User should able to add card from payflow during mobile recharge when bank account is added. User should have already added bank account.
  1. Open Google Pay.
  2. Tap "New Payment".
  3. Tap "Mobile recharge".
  4. Enter valid mobile number and tap the next button.
  5. Choose a recharge plan.
  6. Tap the expander next to the bank account.
  7. Click "Add Card".
  1. Card should get added successfully.
  2. Payment should work from there.
Add card option should not be visible in Payflow screen if no bank account is added. User should not have added bank account.
  1. Open Google Pay.
  2. Tap "New Payment".
  3. Tap "Mobile recharge".
  4. Enter valid mobile number and tap the next button.
  5. Choose a recharge plan.
  6. Tap the expander next to the bank account.
 Only Add Bank Account and Continue buttons should be visible.
Add Card option should not be visible with P2P payment. Use 2 GPay users.
  1. Open Google pay.
  2. Tap "New Payment".
  3. Select the user to transfer money or enter the details using the options under "Transfer Money".
  4. Tap "Pay".
  5. Enter the amount and the reason.
  6. Tap the expander next to the bank account.
 Add card option should not be visible.

In-app Payments - Merchant Transactions

You can test a transaction on any of the following merchants. Myntra is shown as an example here as you can cancel the order immediately afterwards.

  • Myntra
  • Yatra
  • Dunzo
  • Magicpin
  • Confirmtkt
  • EaseMyTrip
  • Limeroad
  • Zoomin
  • Coolwinks
Test case Preconditions Test steps Verification
User should be able to make a successful payment using a sample in-app merchant app for cards, OTP is asked, and the OTP is auto-read.
The user should be navigated back to the sample in-app merchant after completion of the transaction.
  1. User should have cards and accounts added in Google Pay.
  2. Sample in-app Merchant app should be installed.
  1. Launch Sample in-app Merchant app
  2. Fill all required details.
  3. Tap on Pay with GPay button.
  4. Complete a payment using GPay.
  1. Verify if user is able to complete the transaction by invoking GPay.
  2. Verify if OTP is asked while making the payment.
  3. Verify if OTP is auto read.
  4. Verify if the chat head is created under the business section after successful transaction.
  5. Verify if the user is successfully navigated back to the sample in-app merchant application.
Verify user is able to switch to Card as payment option after initiating payment with Bank account.
  1. User should have cards and accounts added in Google Pay.
  2. Sample in-app Merchant app should be installed.
  1. Initiate merchant payment who accepts both Card and bank account.
  2. With Bank account as payment option, click Proceed to pay.
  3. Tap device back button on MPIN screen.
  1. Verify that user is navigated back to payflow screen.
  2. Verify that user is able to switch to Card as payment option and complete payment

In-app Payments - Bills/postpaid/prepaid payments

Bill payments and prepaid recharge are supported and need to be tested. The following options can be used for testing for card tokenization:

  • Postpaid Mobile bill payment
  • Prepaid Mobile / DTH Recharge
  • Utilities bill payment - Electricity / Water / Gas / Broadband
Test case Preconditions Test steps Verification
User should able to add Card from payment flow and make successful payment. User should not have added Card as payment method.
  1. Tap New Payments.
  2. Tap Mobile recharge or Bill Payment.
  3. Select the relevant service and initiate the recharge process.
  4. On the page for option to pay, tap the expander to open the payment options.
  5. Tap the Add card option and proceed with the process.
  6. Payflow page should load again with any previous data.
  7. Select added card as payment method > click Proceed to pay.
  1. Verify that user is able to add card from the payflow page.
  2. Verify that payflow page is displayed after the card gets added successfully.
  3. Verify that payment is done successfully.
User should be able to successfully recharge using card payment. User should have already added Card as payment method.
  1. Tap New Payments.
  2. Tap Mobile recharge or Bill Payment.
  3. Select the relevant service and initiate the recharge process.
  4. On the page for option to pay, tap the expander and select the card.
  5. Complete the rest of the payment process.
  1. Verify if OTP is asked while making the payment.
  2. Verify if OTP is auto read.
  3. Verify that the OTP screen is displayed with a timer.
  4. Verify that card option is available as payment method.
  5. Verify that re-send SMS option is displayed after the timer ends (reach zero)
  6. Verify that payment is done successfully.
Verify card payment for recharge with invalid OTP. User should have already added Card as payment method.
  1. Tap New Payments.
  2. Tap Mobile recharge or Bill Payment.
  3. Select the relevant service and initiate the recharge process.
  4. On the page for option to pay, tap the expander and select the card.
  5. Proceed to pay.
  6. Enter an invalid OTP.
  1. Verify that payment is failed.
  2. Verify that re-send SMS option is available.

Bharat QR Payments

List of supported merchants:

  • TataSky online recharge
  • Domino's
  • Baskin Robbins

Several other merchants also support BharatQR and should be fine to test with.

Test case Preconditions Test steps Verification
User should able to make a successful payment to Bharat QR using cards. User should have already added Card as payment method.
  1. Tap New Payments.
  2. Tap "UPI ID or QR".
  3. Tap "Open Code Scanner".
  4. Scan the QR code.
  5. Enter the amount and complete the payment using card.
  1. Verify if OTP is asked while making the payment.
  2. Verify if OTP is auto read.
  3. Verify if the user is able to complete the transaction.
Transaction should not succeed if incorrect OTP is entered during high value payment. User should have already added Card as payment method.
  1. Tap New Payments.
  2. Tap "UPI ID or QR".
  3. Tap "Open Code Scanner".
  4. Scan the QR code.
  5. Initiate a high value card payment and proceed with the payment.
  6. Enter incorrect OTP.
  1. Verify if relevant error message is seen for incorrect OTP.
  2. Verify that transactions do not succeed.

You need to use a Google Account associated with your corporate email address rather than a personal account.

If Google Workspace hosts your corporate account, you already have a Google account. Otherwise you need to follow these steps to link your corporate email address to Google.

  1. Open the Create your Google Account page to associate your corporate account to a Google account.

    Requesting access

  2. Type in the requested information on the Create your Google Account screen; you must use your corporate email address.

    Enter your corp email address