Google Pay

Not all gateways support Google Pay. Google Pay is supported on Acquired3DS, Adyen, Airwallex, Authorize.netV2, Braintree, cardstream, Celerispay, CheckoutV2, Easy Pay Direct, Fluid Pay, Fondy, Gala Technology, Merchant Warrior, NMI, NomuPay, Pay.com , Payarc, PaysafeV2, Priority, Revolve3, Solid, SquareV2, StripeV2, Surgeify, Swipen, TotalApps, Truevo, VantivV2, Whitelabel Payments, WorldlineV2, Worldpay.

Google Pay is generally one-time use. Rebills and 1-click upsells are supported on AdyenV2, Airwallex, eMerchantPay, NMI, Stripe, CheckoutV2, and Trust Payments.

Confirm with your gateway and test thoroughly before starting live traffic.

---

Step 1: Login and navigate to the funnel on which to add Google Pay

---

Step 2: Click the gear button on the top left to open the funnel settings

---

Step 3: Open the Payments section

---

Step 4: Add the Google Pay credentials

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

searching for NMI on Google's gateway list

searching for Stripe 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_ and is appended with your account ID.

Enter pk_live_51Rgr0y2MbFpnA82ZcmBIkpi2X88EdzB5qnjL356OdXq0rzvd904DAVWAqqnsDQf0uuxM5ueAHJjQE0i8TLDJvPwG00uDN7asIU/[the accountId from your StripeV2 gateway in Checkout Champ - without the brackets]

It should look something like this when fully entered

pk_live_51Rgr0y2MbFpnA82ZcmBIkpi2X88EdzB5qnjL356OdXq0rzvd904DAVWAqqnsDQf0uuxM5ueAHJjQE0i8TLDJvPwG00uDN7asIU/acct_12345678

Google documents are wrong on Fluid Pay. Gateway must be "gatewayprocessing" (without quotes) and gatewayMerchantId must be the public api key from your Fluid Pay portal.

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.

---

Step 5: Save and Continue

---

Step 6: Edit Checkout page and add Google Pay button

You can choose a white or black Google Pay button. Do not add both to the page. The difference is color only.

Step 6-1: Customize size of button by clicking on the button and dragging the highlighted corners or use Dimensions tab for advanced edits.

Step 6-2: Alternatively Google Pay can be launched from the standard page checkout button with use of a payment radio. Drag a form radio button to the page. Set Name=payment_method, Value=GOOGLEPAY. If the radio is selected on the live checkout page then Google Pay will launch when the page checkout button (or link) is pressed.

---

Step 7: Save the page and exit the page builder.

---

Step 8: On the arrow leaving the checkout page, choose the Google Pay button for navigation.

---

Step 9: Upsell pages

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.

Step 10: Publish the funnel. You’re done and ready to test!

---

Test Mode

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:

1. Set Gateway, Gateway Value, and Gateway Merchant ID using instructions in Step 4

2. Set Merchant ID to “12345678901234567890” (without the double quotes)

3. Set Merchant Name to “Merchant Name” (without the double quotes)

4. Select the Test Mode box

Additional Test Mode Notes:

Inside of the Google Pay Business Console you will locate your "Merchant ID"

After you have joined the Google Group providing access to the test cards and test addresses provided by Google, Google Pay requires the Merchant to create an Integration inside of the Google Pay business console, inside of the "Google Pay API" section.

Select "Web Integration".

The integration configuration will request for a few inputs.

First it will request "Your Website", this will be your domain registered into Checkout Champ(whichever domain the Checkout Page is tied to).

Second, it will ask "Your Google Pay API integration type"- Select "Gateway"

Last request from Google is to supply screenshots of your buyflow/order flow.

"Item Selection"- will be your Product Selection page "Pre-purchase Screen"- will be your Checkout Page (Important: make sure Google Pay button is visible in your screenshot)

"Payment Method Screen"- will be a screenshot of the pop-up of the Google login the consumers will interact with"Google Pay API Payment Screen"- You will need to log into a Google account following selecting the "Google Pay" button on your page, this will show the Test Card Number and Test Address provided by Google, grab this as a screenshot. (Tip: Android won't allow you to take a screenshot of this screen, so take a picture of the screen using another device.)

"Post-Purchase Screen"- this will be a screenshot of a Thank you page, Google requires a Google Pay mark on the thank you page in order to approve integration. Feel free to upload this supplied image if you would like:

---

Style

In the Visualizer settings under Payments → Google Pay, the Button Type setting updates the Google Pay button text according to the selected option. After selecting a button type, save and publish.

Button Type	Dark	Light
book
buy
checkout
donate
order
pay
plain
subscribe

The Google Pay brand name must not be translated. Don't create buttons with your own localized text.

Brand guidelines  |  Google Pay API  |  Google for DevelopersGoogle for Developers