Skip to main content
Google Pay lets customers pay using cards stored in their Google account. When a customer clicks the Google Pay button on your checkout page, they select a stored card from their Google account, authenticate if required, and the payment is processed without the customer manually entering card details. Through PCI Booking’s Payments Library, Google Pay is offered alongside card payments, Apple Pay, PayPal, and other methods on the same checkout page.

​
How Google Pay Works with PCI Booking

When a customer selects Google Pay at checkout, the Payments Library displays the native Google Pay payment sheet. The customer chooses a payment method from their Google account and authorizes the transaction. PCI Booking receives encrypted payment data from Google and processes it securely. No card data passes through your servers. Google Pay supports all operations: CHARGE, TOKENIZE, CHARGE_AND_TOKENIZE, PREAUTH_AND_TOKENIZE, and GATEWAY_TOKENIZE. 3D Secure is handled natively by Google Pay. Browser support: Chrome on Android and desktop Chrome with a linked Google account.

​
Prerequisites

​
1. Create a Business Profile

  1. Go to the Google Pay & Wallet Console.
  2. Sign in with your Google account.
  3. Complete the business profile setup, including your business name, address, and website.

​
2. Register Your Website

  1. Add your website URL in the console.
  2. Select Direct as the integration type. PCI Booking decrypts the Google Pay payment data for you; do not select a gateway integration.
  3. Under Google Pay API > Encryption keys, add the PCI Booking public encryption key. Request it from support@pcibooking.net.
  4. Upload the PCI Booking Attestation of Compliance (AOC) as your PCI document, also obtained from support. Google requires the full AOC, not the one-page certificate.
  5. Submit the domain, public key and AOC together for approval. Google reviews your website and integration before granting production access.
Google may require the PCI document for a Direct integration to be an AOC in your own company name, and may not accept PCI Booking’s AOC instead. If you hold your own AOC, upload it. If you do not, contact support@pcibooking.net before you submit.

​
3. Get Your Merchant ID

After Google approves your integration, you receive a Merchant ID. This is required for production.
You can test without a Merchant ID using Google’s test environment. The Merchant ID is only required for production.

​
4. Store in PCI Booking

Create an eWallet account in PCI Booking with: Google Pay accounts take no key. Do not send a private key or certificate for a Google Pay account. You can store credentials through the PCI Booking portal or programmatically via the Store Credentials API.

​
Testing

You can test Google Pay without a production Merchant ID. In test mode, the Google Pay payment sheet shows test cards that do not process real payments. Once your integration is approved and you have a Merchant ID, switch to production mode to accept real payments.
Google Pay buttons only appear when the Payments Library detects a compatible browser and a Google account with saved payment methods. Use checkAvailability() in the Payments Library to verify support before rendering the button.

​
Next Steps

Payments Library Credentials

Overview of all payment method credentials

Payments Library Overview

Integrate the library in your checkout page