Navigate to the Issuer Console and sign in with your corporate email address. If your corporate email is not associated with a Google Account, you will need to complete the association process prior to creating your financial institution account.
Input your public business name, business location, and ensure 'Financial Institution' is selected as the business type.
Agree to the Console Terms of Service, and click 'Continue'.
2. Establish a Business Profile
After completing Step 1, proceed to the Business Profile tab within Issuer Console and click 'Get Started'.
Begin by creating a payments profile for your financial institution by providing the name and address of the business in the Business Identity section.
Complete the business profile by filling in the remainder of the Business Information section with the required details. For Merchant Category Code, financial institutions should utilize 'Others (0000)'.
3. Provide Issuer Details
Upon creating a business profile, navigate to the Push Provisioning API menu, accept the Google API Terms of Service, and provide the issuer details by clicking 'Add Information'.
Begin by adding the information of the authorized signatory for your financial institution. The email address provided in this section will first receive the NDA, and once the NDA is signed, the signatory will then be sent the Google Pay Click To Accept Agreement (CTA). Both the NDA and CTA will be sent from the email address dse_na2@docusign.net.
Fill in the remaining information and click the 'Save changes' button. Once complete, the information will be reviewed and Google will proceed with either sending the NDA directly, or reaching out to confirm specific details.
The issuer details section will remain in the status of "In Review" until both the NDA and CTA have been signed.
The signatory will receive a link to both the NDA and CTA from the email alias dse_na2@docusign.net within 2 US business days of submission if all required information is provided initially. If the signatory is having trouble finding the email, have them search for an email from that address and check their spam filter.
Issuers with existing NDA and CTA agreements are not required to sign
new ones. However, both the Business Profile
and Issuer Details sections in the Issuer Console must still be
completed. Upon completion, the NDA and CTA status in the Console will be
pre-populated and updated using the existing agreements.
4. Access Push Provisioning API documentation
Once the NDA is signed, you will have the ability to view all of the Push Provisioning API
documentation. Request documentation access for others by adding their
corporate emails (no personal emails permitted) that have been associated
with a Google Account in the box on the bottom right of the Push Provisioning
status page. Clicking the 'Give Access' button will automatically provision
access to the developer documentation.
5. Google Pay technical implementation
After both the NDA and CTA have been signed, you are ready to begin integration
work with your Token Service Provided (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 integration with TSP section
of this site
explains Google Pay product behavior, including Google Pay specific
requirements for how you configure the settings at your TSP. Once your TSP
integration is complete, you can return to the Issuer Console
to integrate with the
Push Provisioning API. If you
have any issues along the way, our support page
explains where to get help.
BIN Sponsors or Program Managers
If you are a BIN Sponsor or program manager who has already signed the CTA but
would like to launch a new program or sub-entity, you can notify Google by
selecting the option 'BIN Sponsor/Program Manager notification' option within the general inquiry form.
As part of the notification, Google expects that standard testing requirements
have been met for manual tokenization, or the program manager launch process
has been followed for a push provisioning launch.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-07-08 UTC.
[null,null,["Last updated 2025-07-08 UTC."],[[["\u003cp\u003eFinancial institutions can add support for Google Pay device tokens by following a five-step process outlined on this page, starting with onboarding through the Issuer Console.\u003c/p\u003e\n"],["\u003cp\u003eBefore initiating tokenization, the authorized signatory must sign a Non-Disclosure Agreement (NDA) and Click To Accept Agreement (CTA) sent by Google.\u003c/p\u003e\n"],["\u003cp\u003eAccess to the Push Provisioning API and its documentation is granted after signing the NDA and requires adding corporate email addresses associated with Google Accounts.\u003c/p\u003e\n"],["\u003cp\u003eIntegration with your Token Service Provider (TSP) is crucial for device tokenization and must be completed within 6 months of launching Google Pay, as per the CTA.\u003c/p\u003e\n"],["\u003cp\u003eBIN sponsors or program managers launching new programs or sub-entities should notify Google after completing standard testing requirements or the program manager launch process.\u003c/p\u003e\n"]]],["To enable Google Pay device tokens, first, access the Issuer Console and establish a business profile, providing necessary details. Then, provide issuer details, including an authorized signatory, who will receive and sign the NDA and CTA agreements. Once signed, access the Push Provisioning API documentation and grant access to corporate emails. Finally, begin technical integration with your Token Service Provider (TSP) and the Push Provisioning API, adhering to required timelines.\n"],null,["# Get started with Google Pay\n\nTo add support for Google Pay device tokens, you will need to complete the following steps in order:\n\n### 1. Access the [Issuer Console onboarding platform](https://pay.google.com/business/console?business_type=financial_institution)\n\n- Navigate to the [Issuer Console](https://pay.google.com/business/console?business_type=financial_institution) and sign in with your corporate email address. If your corporate email is not associated with a Google Account, you will need to [complete the association process](https://accounts.google.com/signup/v2/webcreateaccount?flowName=GlifWebSignIn&flowEntry=SignUp&nogm=true) prior to creating your financial institution account.\n\n| **Key Point:** A Google Account grants a user access to various Google products using a single username and password. Any email address can be associated with a Google Account. For further assistance with Google Accounts, visit the [help center article](https://support.google.com/accounts/answer/27441).\n\n- Input your public business name, business location, and ensure 'Financial Institution' is selected as the business type.\n\n- Agree to the Console Terms of Service, and click 'Continue'.\n\n### 2. Establish a Business Profile\n\n- After completing Step 1, proceed to the Business Profile tab within Issuer Console and click 'Get Started'.\n\n- Begin by creating a payments profile for your financial institution by providing the name and address of the business in the Business Identity section.\n\n- Complete the business profile by filling in the remainder of the Business Information section with the required details. For Merchant Category Code, financial institutions should utilize 'Others (0000)'.\n\n| **Important:** The business profile will be approved within a few minutes unless there is a discrepancy with the information provided. If the business profile does not reflect 'approved' after one US business day, contact support through the Issuer Console directly.\n\n### 3. Provide Issuer Details\n\n- Upon creating a business profile, navigate to the Push Provisioning API menu, accept the Google API Terms of Service, and provide the issuer details by clicking 'Add Information'.\n\n- Begin by adding the information of the authorized signatory for your financial institution. The email address provided in this section will first receive the NDA, and once the NDA is signed, the signatory will then be sent the Google Pay Click To Accept Agreement (CTA). Both the NDA and CTA will be sent from the email address [dse_na2@docusign.net](mailto:dse_na2@docusign.net).\n\n- Fill in the remaining information and click the 'Save changes' button. Once complete, the information will be reviewed and Google will proceed with either sending the NDA directly, or reaching out to confirm specific details.\n The issuer details section will remain in the status of \"In Review\" until **both the NDA and CTA have been signed.**\n\n- The signatory will receive a link to both the NDA and CTA from the email alias [dse_na2@docusign.net](mailto:dse_na2@docusign.net) within 2 US business days of submission if all required information is provided initially. If the signatory is having trouble finding the email, have them search for an email from that address and check their spam filter.\n\n- **Issuers with existing NDA and CTA agreements** are not required to sign\n new ones. However, both the Business Profile\n and Issuer Details sections in the Issuer Console must still be\n completed. Upon completion, the NDA and CTA status in the Console will be\n pre-populated and updated using the existing agreements.\n\n| **Warning:** Google strictly prohibits issuers from performing **any tokenizations** in the production environment prior to accepting the agreement. The CTA agreement is a standard agreement and is **not customizable**. Once you have accepted the agreement, you will be able to download a PDF version for your records.\n\n### 4. Access Push Provisioning API documentation\n\nOnce the NDA is signed, you will have the ability to view all of the [Push Provisioning API](/pay/issuers/apis/push-provisioning/android)\ndocumentation. Request documentation access for others by adding their\n**corporate emails** (no personal emails permitted) that have been associated\nwith a Google Account in the box on the bottom right of the Push Provisioning\nstatus page. Clicking the 'Give Access' button will automatically provision\naccess to the developer documentation.\n\n### 5. Google Pay technical implementation\n\nAfter both the NDA and CTA have been signed, you are ready to begin integration\nwork with your Token Service Provided (TSP)! Your TSP should be able to guide\nyou through the process of configuring their systems and integrating with their\nAPIs related to device tokenization. The [integration with TSP section](/pay/issuers/tsp-integration/overview)\nof this site\nexplains Google Pay product behavior, including Google Pay specific\nrequirements for how you configure the settings at your TSP. Once your TSP\nintegration is complete, you can return to the [Issuer Console](https://pay.google.com/business/console?business_type=financial_institution)\nto integrate with the\n[Push Provisioning API](/pay/issuers/apis/push-provisioning/android). If you\nhave any issues along the way, our [support page](/pay/issuers/support/overview)\nexplains where to get help.\n| **Key Point:** Integration with the Push Provisioning API is required within 6 months of a Google Pay launch as per the CTA agreement. If you are unable to meet this timeline, [contact the support team](https://developers.google.com/pay/issuers/support/get-help) for assistance.\n\n### BIN Sponsors or Program Managers\n\nIf you are a BIN Sponsor or program manager who has already signed the CTA but\nwould like to launch a new program or sub-entity, you can notify Google by\nselecting the option 'BIN Sponsor/Program Manager notification' option within [the general inquiry form](https://support.google.com/faqs/contact/gp_inquiry).\nAs part of the notification, Google expects that standard [testing requirements](/pay/issuers/tsp-integration/testing#testing_reqs)\nhave been met for manual tokenization, or the [program manager launch process](/pay/issuers/apis/push-provisioning/android/launch-process#launch_process)\nhas been followed for a push provisioning launch."]]
