Google Pay via Checkout.com
This feature is currently a Private Beta release. Contact Chargebee Support to enable Google Pay via Checkout.com for your live and test sites.
Google Pay enables customers to make secure payments using cards saved to their Google Account on supported devices. With the Checkout.com integration, customers can securely complete payments using any supported credit or debit card linked to their Google Account.
This integration supports both 3D Secure and non-3D Secure payment flows.
Note
Google Pay via Checkout.com is available only for NAS platform users.
For more information about Google Pay support in Checkout.com, see the Checkout.com documentation.
Prerequisites
Before configuring Google Pay via Checkout.com in Chargebee, ensure the following requirements are met:
- Checkout.com is configured as a payment gateway in your Chargebee site.
- Google Pay is enabled in your Checkout.com account.
- The required Google Pay setup has been completed in Checkout.com before configuring it in Chargebee.
- For production usage, Google Pay must be enabled in Checkout.com Live mode, not only in Test mode.
- Confirm with Checkout.com Support that the integration is approved and active for live payments, if required.
- Google Pay cloud-stored cards linked to a Google Account are supported for this integration.
- You can use both live cards and Checkout.com test cards to validate the integration. Google ensures that live cards used in the Google test environment do not create actual transactions.
Configure Google Pay via Checkout.com
Before enabling Google Pay, Configure the Checkout.com payment gateway in Chargebee. If the gateway is already configured, proceed with the following steps:
- Log in to your Chargebee Billing site.
- Go to Settings > Configure Chargebee > Payment Gateway > Checkout.com.
- Enable Google Pay.

- If required, enter the Google Merchant ID.
This field is optional. You can find the Google Merchant ID in the top-right corner of your Google Pay & Wallet Console account.

- Click Save to complete the configuration.

Checkout Flow
The following workflow occurs when a customer selects Google Pay during checkout:
- The customer clicks Proceed to Checkout from the Your Order page.
- In the Add your payment details window, the customer selects the Google Pay tab.
- The customer clicks GPay.
- The Google Pay pop-up appears and prompts the customer to sign in to their Google Account.
- The customer selects an existing card or adds a new card to complete the payment.
- After the payment is completed, the customer is redirected back to Chargebee.
Once checkout is completed:
- The payment method is linked to the customer record.
- Future recurring payments are processed using the selected Google Pay card.
Integration Options
Chargebee supports the following checkout integration methods for Google Pay via Checkout.com:
| Integration method | Description | Supported |
|---|---|---|
| Chargebee Hosted Pages (In-App Checkout) | Customers complete checkout using Chargebee's in-app hosted checkout and pay using Google Pay via Checkout.com. | Yes |
| Chargebee Hosted Pages (Full-Page Checkout) | Customers complete checkout using Chargebee's full-page hosted checkout and pay using Google Pay via Checkout.com. | Yes |
| Chargebee JS (Payment Components) | Use Chargebee Payment Components to present Google Pay via Checkout.com in your checkout flow. | Yes |
| Own form fields with Chargebee JS / APIs | Use your own checkout flow with Chargebee JS or APIs to process Google Pay via Checkout.com. | Yes |
Payment Features
The following features are supported for Google Pay via Checkout.com.
| Feature | Description | Supported | Default state | Configuration / behavior |
|---|---|---|---|---|
| Integration sync mode | Defines how payment requests and statuses are processed between Chargebee and Checkout.com. | Yes (Asynchronous only) | Asynchronous | Checkout.com processes Google Pay payments asynchronously. Chargebee receives the final payment status through webhooks. Webhooks are mandatory, and status updates may be delayed. |
| Capture settings | Determines when authorized funds are captured. | Yes | Auto Capture | Auto capture is the only supported capture setting for Checkout.com. No additional configuration is required. |
| Verification modes | Defines how payment methods are verified before processing. | Yes | Enabled | Checkout.com verifies Google Pay tokens during payment processing. No additional configuration is required. |
| Regulatory requirements support | Supports gateway-specific regulatory requirements during checkout and payment collection. | No | NA | No separate Google Pay-specific regulatory configuration is required in Chargebee. |
| Statement descriptor | Displays the business name on customer bank or card statements. | Yes | Disabled | Configure this under Settings > Configure Chargebee > Transaction Descriptor. If not configured in Chargebee, Checkout.com can use a static statement descriptor configured for the processing channel. Learn more about this. |
| Chargeback management | Handles chargeback events and applies configured actions on invoices and subscriptions. | Yes | Disabled | Enable Chargeback Management under Settings > Configure Chargebee > Billing LogIQ > Chargeback Management. Configure the required dispute webhooks in Checkout.com. |
| Fraud management | Uses gateway fraud signals to identify high-risk transactions. | Yes | NA | For improved fraud screening, send the recommended additional fields supported by Checkout.com. |
| Transaction initiation type | Identifies whether a transaction is customer-initiated (CIT) or merchant-initiated (MIT). | Yes | Supported | Google Pay via Checkout.com supports recurring billing after customer authorization. During CIT, Checkout.com sets merchant_initiated: true. |
| Error intelligence | Provides standardized categorization of payment failures. | Yes | Enabled | Supported for Checkout.com. No configuration required. |
| Gateway transaction details | Displays raw gateway transaction responses. | Yes | Enabled | Available under Error details on the transaction page. |
| Addition of payment methods in Chargebee dashboard | Allows payment methods to be added directly through the Chargebee dashboard. | No | NA | Google Pay requires customer authorization and cannot be manually added through the Chargebee dashboard. |
Supported Token Formats
The following token formats are supported for Google Pay via Checkout.com.
| Token type | Description | Supported | Token field | Token format |
|---|---|---|---|---|
| Chargebee Payment Intent | Recommended token format for custom checkout implementations using Chargebee JS. | Yes | payment_intent[id] | payment_intent_id |
| Chargebee token | Legacy token format for selected gateways and payment methods. Not recommended for new implementations. | No | token_id | NA |
| Gateway permanent token | Permanent gateway reference used for recurring payments or migrations from another PSP to Twikey. | Yes | payment_method[reference_id] | customer_id/payment_source_id |
| Gateway temporary token | Short-lived token that can be converted to a permanent token. | No | NA | NA |
Testing the Integration
Test the integration on your Chargebee test site before enabling it in production.
After validating the setup and checkout flow in the test environment, configure and enable the integration in your live environment.
You can use the Checkout.com test cards to test Google Pay via Checkout.com in your Chargebee test site.
Was this article helpful?