Google Pay

Why don't my consumers see Google Pay as an option on the MyCheckout hosted payment pages?

The MyCheckout hosted payment pages use the isReadytoPay method of Google. If the answer we get back is true, we will show Google Pay as a payment product your consumer can pay with. This will only be the case if you have provided the merchantName (a human readable name that contains your company's name and that is suitable for display in the payment sheet) and merchantOrigin (the URL on which you host your webshop where the checkout is initiated), two properties that are mandatory for Google Pay to be send in.

You can provide the merchantName and the merchantOrigin in the configuration center or you can provide it in the CreateHostedCheckoutRequest.

Since both these properties are mandatory to pay with Google Pay, we can only show Google Pay as a payment option for your consumers, once these two properties are provided.

Why do I sometimes see a card payment product ID for a Google Pay transaction?

In case your consumer paid with a card which is stored in their Google account, we process this Google Pay transaction as a regular card transaction and will apply if relevant fraud validation and 3-D Secure. You can simply send in paymentProductId 320 in your request, but except in this case in the response of your API request a payment product ID of a card:

Visa: paymentProductId 1
American Express: paymentProductID 2
Mastercard: paymentProductId 3
Discover: paymentProductId 12

Can you process both the tokenized cards (CRYPTGRAM_3DS) for Google Pay as well as the cards stored in the Google account (PAN_ONLY)?

Yes, we process both the tokenized cards (CRYPTGRAM_3DS) for Google Pay as well as the cards stored in the Google account (PAN_ONLY), irrespective of the integration type you use (so creating the checkout page yourself, using our JavaScript SDK, using our MyCheckout hosted payment pages or offering it in-app using our Android SDK).

What is the difference between consumers paying with a card on file (PAN_ONLY) and a tokenized card (CRYPTOGRAM_3DS) if they pay using Google Pay?

Consumers who want to pay with Google Pay, will use cards that are either:

Stored in their Google account

These cards must be processed as regular credit cards, which means that for example 3-D Secure validations or fraud validations must be done.
Since these cards must be processed as regular credit cards, we adjust the payment product ID internally to the one of the card scheme of the card of the consumer and process it further as a regular card
These transactions are referred to as PAN_ONLY transactions in the Google documentation
These type of cards can be used for online and in-app payments

Stored in their Google Pay app on their device

These cards are tokenized (using scheme tokens) and will be processed as such
These transactions will be processed as Google Pay transactions and the relevant data, like the 3-D Secure cryptogram, is sent to the acquirer to process this Google Pay transaction
These transactions are referred to as CRYPTOGRAM_3DS transactions in the Google documentation
These type of cards can be used for online, in-app and in-store payments

How can I see Google Payments in Insight or in the WebCollect Payment Console (WPC)?

You will see Google Pay transactions either under the payment product Google Pay or under the payment product Visa, Mastercard, Discover or American Express.

In case your consumer paid with a card stored in the Google Pay app, you will see these transactions as Google Pay transactions. Please note that for further processing you will be able to see the card scheme associated to the Google Pay transaction and its associated payment product ID as well, which can be a different one than the payment product ID 320 which is used as the generic one. For Google Pay MasterCard you will see payment product ID 321, while payment product ID 320 is used for Google Pay Visa.

In case your consumer paid with a card on file (PAN_ONLY), you will see these transactions under the card payment product used by your consumer.

Why does Google Pay appear a split second later on the payment product selection page of the MyCheckout hosted payment pages?

Prior to showing the Google Pay button on the payment product selection page of the MyCheckout hosted payment pages, we validate whether the consumer can make a payment with Google Pay. Due to this validation, it takes a split second before your consumers can see Google Pay as an option to pay with.

Why do I not see Google Pay separately on my invoice?

Since Google Pay™ transactions are processed in a similar way as credit and debit cards, with the same fees as credit and debit cards, they are accumulated under the respective card brand invoice line on your invoice.

What is a DPAN?

A DPAN is a Device Primary Account Number, which is a device-specific tokenized card number. The DPAN is generated after a consumer added a debit or credit card to the Apple Pay app.

Who is the merchant of record?

The merchant is the seller of record.

How are disputes handled?

Disputes are handled in the same way as disputes are handled for credit and debit cards.

How does fraud checking work with Google Pay?

Normal fraud checking can be done and is advised with Google Pay™, in case the consumer has used a card on file (with Google) to pay with, which is referred to as PAN_ONLY in the documentation of Google.

Google Pay

FAQ