Google Pay for API only
Last updated: July 15, 2026
To accept Google Pay payments, you must:
- Retrieve the Google Pay payment data.
- Tokenize the payment data.
- Request a Google Pay payment.
If your PCI compliance enables you to handle encrypted data directly, you can decrypt the Google Pay token yourself and send it to Checkout.com for processing.
- Follow the integration guides, depending on the platform you are integrating:
- Register your domain and obtain your Google merchant ID through the Google Pay & Wallet Console. For web integrations, you can use the Enroll an entity to the Google Pay Service endpoint instead.
Note
Android integrations do not support domain registration through the Enroll an entity to the Google Pay Service endpoint.
When you submit a payment data request to the Google Pay API, you must configure your PaymentDataRequest Google pay object setting the following parameters:
gatewayset tocheckoutltdgatewayMerchantIdset to your public keyallowedCardNetworksset to the card schemes you want to accept
For more information about Google Pay API PaymentDataRequest object, see the Google Developer documentation for Android
The tokenizationData.token property returned in the PaymentMethodData object contains the payment data.
When you receive the payment data from Google, call the Request a token endpoint to tokenize the encrypted payment data.
Note
To process Google Pay transactions, you must authenticate your request using the same public key you provided to the Google Pay API in the gatewayMerchantId parameter.
Information
Your base URL's {prefix} value is unique to your account and environment. To learn how to retrieve your base URLs for the sandbox and production environments, see API endpoints.
post
https://{prefix}.api.checkout.com/tokens
Use the token value from the token field in your payment request.
Call the Request a payment endpoint, setting the following fields, depending on the token format you want to use:
Information
Your base URL's {prefix} value is unique to your account and environment. To learn how to retrieve your base URLs for the sandbox and production environments, see API endpoints.
post
https://{prefix}.api.checkout.com/payments
To request a payment using the Checkout.com token, set the following fields:
source.typeset totokentokenset to the value of thetokenfield in you got in the tokenize the Google Pay payment data response.
If the approved field is true, your authorization was successful. A failed authorization can indicate the payment used an invalid or expired card, or a card with an insufficient available balance.
A successful response includes a payment_account_reference value, which is a unique reference to the underlying card for network tokens. If the card scheme provides an eci value, the response includes it. The value indicates the security level that the card scheme decided to request the payment with.
To test Google Pay payments, first create a test Checkout.com account.
Use Google's built-in test card suite to add mock test cards to your wallet and simulate different payment flows.
You can disable the test card suite to test with your real cards. In this case, Google mocks the response using a generic test card.
If you perform a payment with a real card in Google's sandbox environment, Google Pay provides a test card in the encrypted payment data. This ensures that no actual transaction takes place. This automatic payment data encryption for testing is unique to Google Pay. Do not perform tests for any other payment method using real card numbers or card details in your sandbox environment.
Note
Google validates your Google merchant ID in the Production environment, but not in the Sandbox environment. Register with the Google Pay & Wallet Console and obtain a valid merchant ID before moving to Production. For web integrations, you can optionally register your domain and merchant ID through the Enroll an entity to the Google Pay Service endpoint instead.