For the complete documentation index, see llms.txt. This page is also available as Markdown.

Use GooglePay™

GooglePayTM has over 150 million users across 42 global markets using the app each month. The wallet is used on nearly 800.000 websites as a secure payment gateway. Roughly 20% of all mobile purchases are made using this digital payment gateway.

Availability

To check in which countries or regions you can use Google Pay, read more on availability and geographical coverage here. If you need more information on Google Pay, you can also refer to these Google resources:

Supported features

Since Google Pay is not a classical payment method, but a digital wallet, the supported features depend on the payment means that are used.

Furthermore, the merchant can only accept payment methods that are activated on the specified terminal ID.

The payment means within the wallet are then processed via the normal processors.

For example, if a cardholder selects his Visa card, the card is then processed as such, through Google Pay as the wallet.

Only Visa, Mastercard, and American Express are supported through Google Pay at this point.

Supported Google Pay Features

Within Google Pay itself, 2Checkout Supports the following feature set:

Feature
Via Payment Page
Via Server-To-Server

Pay with Cryptogram

Pay with PAN only

3-D Secure

(Cryptogram/PAN only)

The Difference between PAN only and Cryptogram lies in the way authentication/3D Secure is handled:

PAN Only: 3DS/Authentication is handled through 2Checkout.

Cryptogram: Authentication is handled by the device, e.g. by using the devices fingerprint sensor. This is limited to Android devices, using the Google Chrome browser! All other devices and browsers will always chose PAN Only!

Supported currencies

GooglePayTM supports EUR, USD, GBP, CHF, DKK, NOK and SEK transactions.

Workflow

  1. Follow the Google Pay Web documentation (https://developers.google.com/pay/api/web/overview) to add a Google Pay button to your web page.

  2. Use 2Checkout's Google merchant ID when building the merchantInfo object.

  3. Set gateway to verifone and gatewayMerchantId to your 2Checkout's gateway ID found below when building the tokenizationSpecification object.

GooglePay supports two authorization methods:

- PAN_ONLY: physical card stored in Google Pay™

- 3DS required: yes (managed by 2Checkout)

- CRYPTOGRAM_3DS: device-tokenized card

- 3DS required: no (authenticated by Google Pay™)

  1. After the shopper authorizes the payment, pass the token from the Google response to Verifone to process the payment. To do this, encode the token to base64 and add it to the placeOrder call payload in the PaymentToken property.

  2. When the customer completes the Google Pay payment sheet, Google returns a PaymentData response object. Extract the encrypted token from:

Encode the token value to Base64, then pass it to the placeOrder API call in the PaymentToken field:

  1. Go-live

Request parameters

Parameter
Type/Description

sessionID

Required (string) Session identifier, the output of the Login method. Include sessionID into all your requests. 2Checkout throws an exception if the values are incorrect. The sessionID expires in 10 minutes.

Required (object) Object designed to collect all data necessary for an order, including billing, product/subscription plan and payment details. See code sample for more details.

Request sample

Response parameters

Parameter
Type / Description

Object Object containing order information.

Response sample

Last updated

Was this helpful?