Google Pay

Google Pay^TM is enabled on the Payment Gateway and so merchants are not required to register directly with Google.

The Payment Gateway handles the complexity of the Google Pay payment experience including the Google Pay button rendering, authentication, security, compliance, and payment processing. Google Pay offers greater security for customers since no card or wallet data is exposed to the merchant environment.

How It Works

1. The merchant creates a payment session using the Payment Gateway and the customer is redirected to HPP.
2. The customer selects the Google Pay button as the payment method.
3. Customer selects their card from the Google Payment sheet and authenticates the transaction.
4. Google Pay encrypts the customer's payment details and the customer is redirected back to the merchant site.
5. The merchant receives the final payment result from HPP.

Prerequisites

The following is required in order to be able to accept Google Pay payments on HPP:

• Have an active merchant account on the Payment Gateway.
• Use the HPP integration.
• Google Pay availability depends on device and browser compatibility. A list of supported browsers can be found on the documentation from Google. HPP will first check whether the customer's device or browser supports Google Pay before rendering the Google Pay button.

If all the prerequisites are met, contact our Product Support team to enable Google Pay on your merchant account.

Authentication with Google Pay

When a customer chooses to pay with Google Pay on HPP, a request is sent to Google to authenticate the customer. Google Pay supports the following two authentication methods which are handled by HPP:

1. If the customer has an Android device with a valid card added to their Google Wallet, then the customer can proceed with device authentication. Google will return a device token to HPP and no further customer authentication is required.
2. If a customer is using an Android device but does not have a Google Wallet OR is not using an Android device, but is using a supported browser or device (listed above), is signed into their Google account and has a valid card added to their wallet, then Google will return a Primary Account Number (PAN) in the encrypted payload. HPP will then proceed to a step-up 3D Secure authentication in order to perform customer authentication.

Testing

Testing Google Pay can be done in our Sandbox environment before enabling Google Pay in production.

Test Cards

The test cards that follow can be used to simulate different transaction outcomes.

📘

Test cards must be added to a Google Pay wallet signed in with a Google test account and used only in the Sandbox environment.