Push Provisioning API Access Request

Thank you for contacting Push Provisioning API support. This form will initiate the Push Provisioning API Access process. You may request access for any app package names needed for your development and testing, in addition to your regular production app. Submit this form separately for each app package name with a different SHA256 Fingerprint. For Access usecases you can also use this form to submit your OAuth 2 Client Ids for web provisioning. Submit the form separately for each OAuth client ID that you want to Allowlist.

* Required field

Please enter a valid email address.
You must provide a corporate email address so that we can associate this API access request with a signed contract. Personal email accounts (i.e. gmail, yahoo, msn, etc.) cannot be associated with a contract and therefore will not be given access.
Choose your Google Wallet use case: *
Note: The Access option refers to non-payments use cases such as IDs, badges, and car keys. Please choose the option that is most applicable to your business to reduce turnaround time.
Choose your type of integration: *

For example: XXXXXX-XXXXXXXXXXXXXXX.apps.googleusercontent.com. The value for this field is the same as the client id sent in the authentication request to Google.

Select the option which best describes your company: *
Does the financial company or card issuer have a signed CTA agreement with Google? *
Do you (BIN Sponsor or Program Manager) have a signed CTA agreement with Google and consider this financial company or card issuer a sub-entity? *
Does your company have a signed CTA agreement with Google? *
Does your BIN/Sponsor or Program Manager have a signed CTA agreement with Google? *
App package environment *
Fingerprint should be SHA256, not SHA1
Example: X0:X1:X2:X3:X4:X5:X6:X7:X8:X9:XX:X0:X1:X2:X3:X4:X5:X6:X7:X8: X9:XX:X0:X1:X2:X3:X4:X5:X6:X7:X8:X9
Example: X0:X1:X2:X3:X4:X5:X6:X7:X8:X9:XX:X0:X1:X2:X3:X4:X5:X6:X7:X8: X9:XX:X0:X1:X2:X3:X4:X5:X6:X7:X8:X9
Please select the appropriate network(s) *
You must have a signed CTA Agreement in place with Google Pay for us to process this request. No app packages can be added to the Push Provisioning API without this step complete.
Either the card issuer or the BIN Sponsor or program manager must have a signed CTA Agreement in place with Google Pay for us to process this request. No app packages can be added to the Push Provisioning API without this step complete.
The card issuer must have a signed CTA Agreement in place with Google Pay for us to process this request. Also, we will need a letterhead or email directly from the issuer to ensure they have approved a third party to work on this integration on their behalf. No app packages can be added to the Push Provisioning API without this verification complete.
The card issuer must have a signed CTA Agreement in place with Google Pay for us to process this request. No app packages can be added to the Push Provisioning API without this step complete.
https://myaccount.google.com/privacypolicy?hl=$0
Some account and system information will be sent to Google, and support calls and chats may be recorded. We will use this information to improve support quality and training, to help address technical issues, and to improve our products and services, subject to our Privacy Policy and Terms of Service. Translation services may be used in chats and email.
Additional info
Google apps
Main menu