Configuring Google Pay™ on Payment Pages
This article takes you through the set up process of Google Pay™ on a Hosted Checkout Payment (HCO) page.
Google Pay allows cardholders to use the payment method stored in their Google wallet to perform online payments.
Cardholders can use any browser to pay with Google Pay via a HCO Payment Page, they will see Google’s payment sheet where they can authorize the payment using their fingerprint, or device password.
Note: Google Pay is only available for merchants using Chase Paymentech as their processor.
Enabling Google Pay™ on a Payment Page
NOTE: Chase or Exact has to enable the flag for Google Pay before the following steps can be performed.
An RPM (Real-time Payment Manager) user with the Merchant Administrator role has the option to enable Google Pay in the Payment Types section of the Payment Page Settings. By default, the feature is disabled. The “Google Pay Terms and Conditions” must be reviewed for the feature to be enabled (Note: it is necessary to click on the hyperlink and read the document to activate this feature).
The following screenshot from the Payment Page Settings shows the hyperlink and check mark that a Merchant Admin has to click, and select in order to use Google Pay:
Once Google Pay is enabled on the Payment Page Settings, the Google Pay icon will become visible on the payment page preview page)
Cardholder payment processing flow via an HCO Payment Page
Once Google Pay is enabled for the HCO Payment Page, the Google Pay button will appear on the payment page.
During the checkout phase, when the Google Pay button is selected by a cardholder the Google Pay window will appear. If the cardholder has a card in their wallet it will present a window showing their Google account name/email and the last four digits of their default payment card. They have the option of using the dropdowns if they would prefer to pay with another stored card, or a different Google account:
The image below shows the screen where a cardholder can add a card if this is the first time they are using the Google Pay wallet; the cardholder will also be prompted to add a billing address.
Adding a new card and billing address:
The cardholder then clicks “PAY” to complete the transaction.
If the transaction is canceled, the cardholder will return to the HCO payment page. If the cardholder authorizes the transaction, it will be processed and the rest of the screen/receipt flow will be the same as it is for regular credit card transactions (i.e. it will be defined by the merchant integration options on the HCO Payment Page Settings; for more information, please refer to the Hosted Checkout Payment Pages Integration Manual).
Real-time Payment Manager (RPM) Transaction Details
In the RPM transaction details, the “Wallet Provider” field can be used to determine if the transaction was processed using a digital wallet.
Notes on Google Pay™
The Google Pay wallet 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). One consequence of this is that the last four digits of the DPAN used in an Google Pay transaction in the RPM transaction list do not correspond to the actual last four digits of the cardholder’s credit card.
Was this article helpful?
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
We appreciate your effort and will try to fix the article