Google Pay for Payment Pages

Google_Pay_Logo__2020_.svg.png

 

Google Pay™ is a digital wallet platform and online payment system developed by Google to power in-app, online, and in-person contactless purchases on mobile devices, enabling users to make payments with Android phones, tablets, or watches.

 

Features

  • Protect Plus is supported, but checks cannot be run over the card details, as these are not made available to Trust Payments for Google Pay transactions.
  • Payments scheduled through our Subscription engine are supported. You must have a merchant number that supports the processing of recurring payments. Click here to learn more.
  • Payments may be subject to chargebacks, depending on your acquiring bank.

  The security code setting on your security policy is not applicable for Google Pay transactions, and therefore, they cannot be suspended based on the security code. However, AVS checks are still performed, and transactions can still be suspended due to your security policy configuration.

  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

  Your acquiring bank must support Google Pay with Trust Payments. Contact our Support Team for further information.

 

How it works

  1. The customer clicks the Google Pay button displayed on your checkout. If they are not already signed into their Google Pay account, the customer is prompted to sign in.

    choice.jpg

  2. A pop-up is displayed, in which the customer is displayed the final transaction amount and asked to choose their preferred payment method.

    click-button.jpg

  3. The customer clicks "Pay" to confirm their intent to purchase, before being redirected back to the Trust Payments hosted response page. (You can optionally enable a redirect that takes the customer back to your own website - click here to learn more)

    response.jpg

 

Configuration

Enabling Google Pay

To enable Google Pay on your test site reference, please contact our Support Team. Once enabled, the Google Pay button will be displayed on the payment choice and payment details pages (providing the browser supports the service) and you can test your solution.

 

Set up your Google account for testing

To begin testing Google Pay when targeting a test environment, you will need a Google account and you will need to join a group Google provides that allows you to use a set of API test cards for testing your Google Pay solution.

  1. Once you have registered a Google account, sign in to the account in your browser, navigate to the following page:
    https://groups.google.com/g/googlepay-test-mode-stub-data
  2. Then click "Join group".

    googlepay-gettingstarted-0411-01-en.png


  3. Once you have set your preferences, click "Join group".

    googlepay-gettingstarted-0411-02-en.png


  4. You will be presented with a page that confirms you have been granted access to the Google test suite:

    googlepay-gettingstarted-0411-03-en.png


  5. To ensure this is working, Google provide a demo page where you can click a Google Pay button to view the payment form.
        Click here to open this in a new tab.

    If everything is working as expected, you should be able to select any of the example payment methods and click "CONTINUE". This will process a test payment.

    googlepay-gettingstarted-0411-04-en.png

 

Modify your POST to Trust Payments

You can optionally modify your POST submitted to Trust Payments to determine the billing and delivery address to be used for the payment authorisation. By submitting the following fields with value 1, this will ensure that the billing and delivery information are retrieved from the customer’s wallet. This expedites the payment process, providing a more seamless checkout experience for the customer.

  Field name Format Description
table-optional.png billingcontactdetailsoverride Numeric (1)
  • "0" – Uses billing details submitted in the POST.
  • "1" – Uses billing details from the customer’s wallet.
table-optional.png customercontactdetailsoverride Numeric (1)
  • "0" – Uses delivery details submitted in the POST.
  • "1" – Uses delivery details from the customer’s wallet.
<form method="POST" action="<DOMAIN>/process/payments/choice">
...
<input type="hidden" name="billingcontactdetailsoverride" value="1">
<input type="hidden" name="customercontactdetailsoverride" value="1">
...
<input type="submit" value="Pay">
</form>

Replace <DOMAIN> with a supported domain. Click here for a full list.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request