Google Pay

With Google Pay, shoppers can make purchases using credit or debit cards stored in their Google account. Shoppers get to experience a simpler checkout process whether they are buying from their Android devices, on the web, or in-store through POS terminals.

When a shopper pays with Google Pay in apps and on websites, Google Pay shows a payment sheet where they select their preferred card payment method and confirm their purchase.

Payment type	Payment flow	Countries	Currencies	Recurring	Refunds	Partial refunds	Multiple partial refunds	Separate captures	Partial captures	Multiple partial captures	Chargebacks
Wallets	Direct	International	Multiple

Express payment method support

You can configure the Google Pay Web Component to use Google Pay as an express payment method.

Compatibility

For more information on Google Pay availability, refer to:

• List of payment methods that support Google Pay.
• List of countries or regions where you can use Google Pay.
• List of supported browsers.

Supported networks

Our integration supports the following card networks:

• Accel: Supported in the US.
• American Express: Supported globally, except in India.
• Discover: Supported in the US.
• Elo: Supported in Brazil. You must have a local business entity in Brazil to offer this to shoppers.
• Interac: Supported in Canada. You must have a local business entity in Canada to offer this to shoppers. Payments are automatically captured at the moment of authorisation.
• Maestro: Supported in the EU and Brazil.
• Maestro USA: Supported in the US.
• Mastercard: Supported globally.
• NYCE: Supported in the US.
• PULSE: Supported in the US.
• STAR: Supported in the US.
• Visa: Supported globally.

Liability shift

Google Pay allows storing cards as DPAN and FPAN.

A DPAN is tokenized in such a way that it is considered "strongly authenticated". A cryptographic value will be inside this token. When Adyen decrypts the token and passes the cryptographic value, the card issuer will not require the shopper to additionally go through 3D Secure to accept the transaction.

An FPAN is tokenized in such a way that when Adyen decrypts the token no "cryptogram" is available (as in the case with a DPAN). Therefore, Adyen will only have "raw" card data to send for processing. For this reason it is recommended to go through 3D Secure to accept the transaction.

The odds of receiving Liability shift for Google Pay transactions are influenced by:

• Google Pay guarantees liability shift on Mastercard cards that are issued globally, and Visa cards issued in the EU or UK, if they are tokenized as DPAN. Adyen's API will not respond with the suggestion to redirect to 3D Secure if the token contains a DPAN.
• Google Pay does not guarantee liability shift for FPAN transactions. To receive liability shift for FPAN transactions (or the below-mentioned brands that Google Pay also does not support liability shift for) it is advised to implement 3D Secure. Adyen's API will respond with the suggestion to redirect if the token relates to an FPAN transaction.
• Google Pay does not guarantee liability shift for Discover, American Express, JCB, or Visa cards issued outside the EU and UK.
• Google Pay offers the option to opt in an upgrade on Visa cards issued outside the EU and UK. This requires sending additional data points on the transaction. Adyen's APIs support sending these data points. For more information read this article by Google.

If you are a PCI DSS Level 1 compliant merchant you can decrypt the tokens yourself, determine if you have received a DPAN or FPAN, and determine how to proceed with the transaction, by using this documentation.

How do you want to integrate?