Skip to content

Google Pay

Offer Google Pay to your merchants: what you set up, how it runs over the card processor, and how to test it.

Google Pay runs over the card processor of the project: a Google Pay payment is a card payment, with a device token and cryptogram, or with the card stored in the customer's Google account. You don't need a separate processor contract. The merchant's customers pay on the hosted payment page, or in the merchant's own checkout.

How it works

  1. The customer chooses Google Pay and approves the payment.
  2. Google returns an encrypted payment token to Ginger. Ginger decrypts it and sends the payment to the card processor of the project.
  3. The processor authorises the payment like a card payment. A payment with a cryptogram doesn't need 3-D Secure; a payment with a card from the Google account can need it.

Google Pay works with every card processor: Silverflow, Elavon, Rapyd, Shift4 and IPG.

Set it up

Allow the payment method

Give the merchant and the project permission for Google Pay, as for any payment method. See Merchant hierarchy.

Check the card contract

The project needs a working card contract, with the card brands the merchant accepts. One-click and recurring Google Pay payments follow the merchant's card settings. See Processor contracts.

Set the Google merchant ID, if the merchant has one

Add the google-pay contract with google_merchant_id: the merchant ID from the Google Pay business console. Without it, Ginger uses the Google merchant ID of your platform. Ask your Ginger contact whether a merchant that integrates Google Pay host to host needs its own. See the google-pay fields of Update a project contract in the API reference.

Test

A project in active-testing sends its Google Pay payments to the test environment of the processor. Google Pay returns test card data in its test environment.

For your merchants

The integration is in the payment acceptance docs: Google Pay in your own checkout and Google Pay recurring payments.

Next steps