Frequently Asked Questions
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.
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.