This page provides general information and FAQ about Google Pay API.
About Google Pay API
Google Pay enables effortless checkouts for your app and website. With the Google Pay API, your customers can use the cards saved to their Google Accounts for seamless checkout within your apps and sites.
How to get support
Register with the Google Pay and Wallet Console and select Contact support. We can help you troubleshoot your integrations. Additionally, reference our Android troubleshooting guide and Web troubleshooting guide to self-debug your integration.
The Google Pay API has several supported features.
Supported forms of payment
The Google Pay API may return cards or network tokens.
Recurring billing and subscriptions
Support for recurring billing is tied to the payment method returned in the Google Pay API response. Both tokenized cards and cards on file can be used for recurring billing. To process recurring billing, the merchant doesn't have to call our API at a cadence. Rather, the payment credential is stored on the merchant side for recurring payments. The merchant uses their payment gateway APIs to manage recurring billing.
Google Pay supports recurring payments if the following statements are true:
- Merchants comply with network rules, such as merchant-initiated transactions.
- Terms of payment are disclosed and accepted by the user within the merchant’s buyflow.
We also support recurring billing with variable amounts. For example, monthly phone bills for mobile carriers are supported. To get more information, merchants must contact their payment gateway representative.
Auto-reload or "top-up"
To process an auto-reload charge for the same cost, the merchant doesn't have to call our API each time. The payment credential is stored on the merchant side and reused. To get more information, merchants must contact their payment gateway representative.
Merchants can handle transaction reversals for cancellations, reimbursements, or disputes in the manner that they currently handle chargebacks for other forms of payment. To get more information, merchants must contact their processors representative.
Approved nonprofit organizations (NPOs) can integrate the Google Pay API to collect donations, if, and only if, they provide documentation to prove, certify, and validate their nonprofit status. For example, US NPOs must provide valid 501(c)3 status proof from the IRS in order to qualify.
Terms and Policies
Google Pay API Terms of Service
All merchants must agree to and adhere to the Google Pay API Terms of Service.
Google Pay API Acceptable Use Policy
All merchants must agree to and adhere to the Google Pay API Acceptable Use Policy.
Our policy on Gambling is defined in our Google Pay API Acceptable Use Policy.
Our policy on gambling may change from time to time. All submissions are subject to review and approval.
We currently accept gambling integrations from companies based in the following countries: Australia, Canada, France, Germany, Ireland, Italy, Japan, the Netherlands, Spain, Sweden, and the United Kingdom. We might choose at a later date to expand support beyond the current level.
Gaining production access to the Google Pay API for gambling integrations requires completing a series of prerequisites:
- If you have an Android-only gambling integration based in one of the above countries, you must adhere to Google Play's gambling policy and onboard with Google Play's vetting process first. We can then evaluate your Android-only integration for production access to the Google Pay API. If you have a Web-only gambling integration based in one of the above countries, you must submit an authorized license to prove your eligibility to provide gambling services in-country during your onboarding process with the Google Pay API. We can then evaluate your Web-only integration for production access to the Google Pay API.
- If you have an Android and Web gambling integration in one of the above countries, you must adhere to Google Play's gambling policy and onboard with Google Play's vetting process first. We can then evaluate your Android and Web integrations for production access to the Google Pay API.
If you expand the Google Pay API into a country that you were not previously approved for, contact us to gain approval for the expansion. Please note that you will need to provide an authorized gambling license for each country in which you plan to offer gambling-related services. We do not allow the Google Pay API to be used for gambling services where they are aimed / addressed to individuals who are underage or are otherwise forbidden from gambling according to local laws.
Our policy on Healthcare is defined in the Google Pay API Acceptable Use Policy.
Be prepared to share a relevant license when onboarding to validate your Healthcare use case. All submissions are subject to review and approval.
Financial Services Policy
Our policy on Financial Services is defined in the Google Pay API Acceptable Use Policy.
Be prepared to share a relevant license when onboarding to validate your Financial Services use case. All submissions are subject to review and approval.
The following FAQ apply to merchants.
The Google Pay API returns payment methods in a signed and encrypted payload. The returned payment methods consist of either PAN or tokenized cards made of device PAN (DPAN) and cryptograms.
Tokenized card payloads are processed without additional step-up or challenge.
Card payloads that consist of PAN require 3D Secure through an in-house or a PSP-provided solution.
If your PSP manages all the risk and SCA logic, make sure that your Google Pay API integration includes the following properties:
merchantInfo.merchantName(Android, Web): The merchant name is rendered in the payment sheet.
transactionInfo.countryCode(Android, Web): This indicates where the transaction processes. You must specify the acquirer bank country.
transactionInfo.totalPrice(Android, Web): The total monetary value of the transaction with an optional decimal precision of two decimal places.
(CRYPTOGRAM_3DS). Both supported and unsupported cards are listed.