Google Pay on Payment Pages

Google Pay™ allows cardholders to securely perform online payments using the credit cards stored in their Google Wallet.

Unlike Apple Pay, cardholders can use any browser (Chrome, Safari, Firefox, etc.) to pay with Google Pay via a Hosted Checkout (HCO) Payment Page. When the user clicks the Google Pay button, they will be presented with Google’s native payment sheet where they can authorize the transaction using their fingerprint, device password, or Google account login.

🚧

Processor Limitation

Google Pay is currently only available for merchants using Chase Paymentech as their payment processor.

📘

Compliance Requirements

Before using this feature, you must review Google’s Terms of Service and Acceptable Use Policy.

1. Enabling Google Pay in the RPM

By default, Google Pay is disabled on your Hosted Checkout Payment Pages. An RPM user with the Merchant Administrator role must enable it manually.

Note: Chase or E-xact must first enable the background flag for Google Pay on your merchant account before you can perform the following steps.

1. Log in to the Realtime Payment Manager (RPM).
2. Navigate to your Payment Page Settings.
3. Under the Payment Types section, locate the Google Pay settings.
4. You must click the hyperlink to review the “Google Pay Terms and Conditions”. (The system requires you to click the link and read the document to activate this feature).
5. Check the box to enable Google Pay and save your changes.

Once enabled and saved, the Google Pay icon will become visible on your payment page preview and the live checkout page.

2. Cardholder Payment Experience

When a customer arrives at your Hosted Checkout page, the Google Pay button will be prominently displayed alongside standard credit card entry fields.

Checkout Flow:

1. Selecting the Wallet: The cardholder clicks the Google Pay button.
2. Reviewing Stored Cards: The Google Pay window will appear, displaying their Google account name/email and the last four digits of their default payment card.
3. Switching Methods: The user can click a dropdown menu to select a different stored card or sign in with a different Google account.
4. Adding a New Card: If the customer is using Google Pay for the first time or has no stored cards, they will be prompted to enter a new card and billing address directly within the Google interface.
5. Authorization: The customer clicks "PAY" to complete the transaction.

If the transaction is canceled by the user, they will be seamlessly returned to your standard HCO payment page. If the transaction is authorized, your normal screen and receipt flow will execute exactly as it would for a standard credit card transaction.

3. Transaction Details & Tokenization

Similar to other digital wallets, Google Pay uses a tokenized version of the cardholder’s credit card to perform payments.

This token is a 16-digit number called the DPAN (Device Primary Account Number). Because the actual credit card number is never passed to the gateway, the last four digits displayed on the receipt and in your RPM transaction list will correspond to the tokenized DPAN, not the physical credit card.

Identifying Google Pay Transactions in the RPM

You can easily track which transactions were processed via Google Pay within your dashboard.

• Open the Transaction Details for a specific payment in the RPM.
• Look for the Alternative Payment Method row.
• The Wallet Provider field will indicate that a digital wallet was used, and it will specifically identify Google Pay as the source.