Cards & Wallets · Digital Wallets · Google Pay

Getting started with Google Pay

When using Your Payment Page

Follow these simple steps to use Google Pay with Your Payment Page.

Step 1 — Integrate to the Google Pay API

To be able to use Your Payment Page you will also need to integrate directly to the Google Pay API to get the payment method data. There are two different options for integrating with Google:

When using either of these options you will need to specify a gateway of pay360 and the gatewayMerchantId will be the unique merchant identifier that is assigned to you when you are boarded.

Both integrations will return a payment method data response containing an encrypted payment data token as well as some other metadata about the payment method which can be forwarded on directly to our payments API.

Step 2 — Integrate to Your Payment Page

Google Pay transactions are submitted to our main payments API. See the When using Your Payment Page section of the following pages for full details and example requests:

Step 3 — Test the integration

See Testing Google Pay.

When using the PaySuite Payment Page

Our hosted solution has an integration to the Google Pay JavaScript (Web) API so you will not need to integrate directly with Google yourself.

Follow these simple steps to use Google Pay with the PaySuite Payment Page:

Step 1 — Register with Google

You’ll need to register as a Google Pay merchant using the Google Pay Business Console. You will be given a Google merchant identifier which you will need to provide to us when you are boarded.

Step 2 — Integrate with the PaySuite Payment Page

Our hosted Google Pay pages are initialised in the same way as the hosted pages for all of our other supported payment methods, you’ll just need to have Google Pay enabled on your account. See the When using the PaySuite Payment Page section of the following pages for more details:

Step 3 — Test the integration

See Testing Google Pay.

Terms of service

All merchants must adhere to the Google Pay APIs Acceptable Use Policy and accept the terms defined in the Google Pay API Terms of Service.

Google Pay authorisation methods

The Google Pay API can return payment methods with two different types of authorisation method. The authorisation method of a payment method is determined by the way it was added to the Google Pay wallet. The two authorisation methods are:

  • Non-tokenised cards where no Strong Customer Authentication (SCA) has been performed on the payment method. These are referred to by Google as PAN_ONLY. These transactions will need to go through 3-D Secure in our payment platform. Your merchant account will need to be configured for 3-D Secure to be able to process payment methods of this type. A payment method of this type will resolve to an FPAN (Funding PAN) which is the actual PAN as physically printed on a card.
  • Android device tokens that have been authenticated with a 3-D Secure cryptogram. These are referred to as CRYPTOGRAM_3DS by Google. These transactions will not need to go through 3-D Secure in our payment platform. A payment method of this type will resolve to a DPAN (Device PAN), a tokenized PAN different from the FPAN and unique to the device used, which we will forward on to the acquirer; our system will never know or be aware of the actual FPAN of the payment method.

Each of these types are processed differently by our platform and displayed differently in our merchant Portal. The non-tokenized card payment methods will be presented as a regular card transaction in that the payment product will be that of the card scheme whereas the Android device token payment methods will be presented with a payment product of ‘Google Pay’. Both types will have a payment method source of ‘Google Pay’ so you will be able to easily identify all payment methods that have come from a Google Pay wallet.

At the time of making a request to our payments API it is unknown what payment method type has been selected, so you must be able to handle the response flow for each type. Google Pay Payments shows the request and the response for each of them.

Supported transaction types

As well as payments and payouts the following transaction types are also supported with Google Pay:

  • Authorisation
  • Capture
  • Cancel
  • Repeat

These all work in the same way as card payments — see Transaction types for what each one does, and the Cards API endpoints reference for their requests and responses. The only difference is that the payment method is sent in paymentMethod.googlepay, as shown on Google Pay Payments.

Supported card schemes

Google Pay payment methods with the following card schemes are supported:

  • AMEX
  • DISCOVER
  • JCB
  • MASTERCARD
  • VISA

Available acquiring routes

We support Google Pay on the below acquirers with more being continuously added.

  • Vantiv
  • Barclays
  • Elavon
  • Worldpay
  • American Express
  • First Data (Fiserv) (WIP)
  • Credorax (WIP)
  • HSBC (WIP)