Google Pay (Checkout Champ)
Last updated
Last updated
Not all gateways support Google Pay. Google Pay is supported on Acquired3DS, Adyen, Airwallex, Authorize.netV2, Braintree, cardstream, Celerispay, CheckoutV2, Easy Pay Direct, Fondy, Gala Technology, Merchant Warrior, MerchantConnect, MerchantConnectV2, NMI, NomuPay, Pay.com , PaysafeV2, PaysafeV2, Priority, Revolve3, SquareV2, Stripe, StripeV2, Surgeify, Swipen, TotalApps, Truevo, VantivV2, Whitelabel Payments, WorldlineV2, Worldpay.
Select the Gateway that you want your Google Pay transactions to run to. Ensure the gateway is in the supported list at the top of this document.
Please review the tooltips in the app for a detailed explanation of each credential.
Gateway Value can be found here https://developers.google.com/pay/api/web/reference/request-objects#gateway
Example searching for NMI on Google's gateway list
Gateway Merchant ID is the Merchant Id provided by your gateway (you may need to reach out to the gateway or merchant provider for this value). It is the same value found on your VAR sheet and should be the same value as entered here on your gateway configuration:
Stripe requires entry of a Publishable Key instead of Gateway Merchant Id. This is a long value that starts with pk_. If using Stripe Connect, append a forward slash and the connected account ID to the public key and enter the entire value as Publishable Key. It will look similar to this pk_12345/acct_54321.
Merchant ID is retrieved from your business console https://pay.google.com/business/console/
Place your page in Test Mode to enable testing with Google. Do be sure to uncheck when testing is complete. Click here for more details on testing.
You can choose a white or black Google Pay button. Do not add both to the page. The difference is color only.
There are 3 options for upsell pages. Communicate with your gateway about the appropriate workflow.
Option 1:
Your gateway supports a 1-click upsell on Google Pay using a payment token returned from the gateway at checkout
Place one or more standard buttons on each upsell page. Follow standard instructions for those buttons to submit the upsell. Add class cc-one-click-btn to each button. There is no need to have a Google Pay button on each page. The buttons will submit using the original payment token.
Option 2:
Your gateway does not support Option 1. You prefer to have a generic button on the upsell page instead of a Google button.
Place one or more standard buttons on each upsell page. Follow standard instructions for those buttons to submit the upsell. The buttons will automatically support Google Pay or non-Google Pay based on the checkout. Google Pay will redirect the consumer to Google to complete the upsell. No additional work is needed.
Option 3:
Your gateway does not support Option 1. You prefer to have a Google button on the upsell page.
Place one or more standard buttons AND one or more Google Pay buttons on each upsell page. Choose all the buttons on the arrow(s) leaving the page. When the live page loads the standard buttons are removed if the checkout was with Google Pay. Pressing the Google Pay buttons will redirect the consumer to Google to complete the upsell. When the live page loads the Google Pay buttons are removed if the checkout was not Google Pay. The standard buttons will submit the upsell.
This section is used for Google to approve your implementation. You must uncheck the Test Mode box and enter your live Merchant ID and Merchant Name once approved.
In Test Mode a transaction will not go to the gateway for approval. The transaction will automatically approve.
Full testing details can be found here
You may need to enable test cards on your Google Pay account. See here.
Follow these steps to test Google Pay on CheckoutChamp:
Set Gateway, Gateway Value, and Gateway Merchant ID using instructions in Step 4
Set Merchant ID to “12345678901234567890” (without the double quotes)
Set Merchant Name to “Merchant Name” (without the double quotes)
Select the Test Mode box
