# Google Pay™

> Let customers pay with cards saved to their Google Account, on Chrome and Android browsers.

Google Pay™ lets your customers pay with any credit or debit card saved to their Google Account — including cards from Google Play, YouTube, Chrome, or an Android device — without typing card details. Use it in place of a traditional card form wherever possible, for physical goods, donations, subscriptions, and more.

Google Pay is fully compatible with VINR's web checkout products (Hosted Checkout, Payment Links, and Elements), and settles on the card rail — so pricing, disputes, and refunds work exactly as they do for standard card payments.

## Google Pay terms and resources

By integrating Google Pay, you **must** accept the [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos) and **must** comply with the [Google Pay API Acceptable Use Policy](https://payments.developers.google.com/terms/aup).

For technical reference, see the [Google Pay Web developer documentation](https://developers.google.com/pay/api/web/overview), the [Web integration checklist](https://developers.google.com/pay/api/web/guides/test-and-deploy/integration-checklist), and the [Web Brand Guidelines](https://developers.google.com/pay/api/web/guides/brand-guidelines).

##### Payment method properties

| Property                  | Value                                                                                                                                              |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Customer availability     | Chrome on any platform, and Android browsers, with a saved card                                                                                    |
| Presentment currencies    | Same as your VINR card-processing configuration                                                                                                    |
| Payment confirmation      | Customer-initiated                                                                                                                                 |
| Payment method family     | Wallet — settles on the card rail                                                                                                                  |
| Card networks             | Visa, Mastercard                                                                                                                                   |
| Authentication methods    | `PAN_ONLY` and `CRYPTOGRAM_3DS`                                                                                                                    |
| SCA / 3D Secure           | Applied automatically — see [Authentication methods](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/authentication-methods) |
| Disputes                  | Yes — handled like standard card payments                                                                                                          |
| Refunds / Partial refunds | Yes / Yes                                                                                                                                          |
| Recurring payments        | Contact your VINR account manager                                                                                                                  |

##### Availability

Google Pay is available to customers in Google Chrome on any platform and in Android browsers, wherever they have a card saved to their Google Account. There are no geographic restrictions beyond the card networks and currencies enabled on your VINR account.

Customers on browsers that don't support Google Pay simply won't see the button — VINR's hosted products (Checkout, Payment Links, Elements) detect eligibility automatically and fall back to other eligible payment methods.

VINR supports **Visa** and **Mastercard** for Google Pay — this is fixed for every merchant and region; set `allowedCardNetworks` to `['MASTERCARD', 'VISA']`. Other networks (American Express, Discover, JCB, and so on) are not supported. Contact your VINR account manager to confirm the settlement currencies available for your region.

##### Product support

- Hosted Checkout
- Payment Links
- Elements

## How Google Pay works

When a customer chooses Google Pay at checkout:

1. The browser checks whether Google Pay is available (`isReadyToPay`).
2. The Google Pay payment sheet appears with the customer's saved card.
3. The customer confirms with a biometric, PIN, or Google Account authentication.
4. Google encrypts a one-time payment token and passes it to VINR.
5. VINR decrypts the token, applies risk and authentication controls, and authorizes the payment through the card network.
6. VINR returns the authorization result and emits a payment webhook — the same as a standard card payment.

> **Identifying a Google Pay payment in the response / webhook:** the exact field VINR returns to mark a completed payment as Google Pay is being confirmed. Verify the payment-object / webhook shape with your VINR contact before building reconciliation or reporting logic on it.

## Authentication methods

Google Pay can return two types of credential depending on how the card was saved:

- **`CRYPTOGRAM_3DS`** — the card was tokenised onto the customer's device (a DPAN). The one-time cryptogram satisfies SCA and carries inherent liability shift. No 3DS step-up is triggered.
- **`PAN_ONLY`** — the card was saved to the customer's Google Account but never tokenised onto a device (an FPAN). VINR unconditionally routes these through its 3D Secure step-up engine; when the step-up passes, the transaction becomes SCA-compliant and liability shifts to the issuer.

You do not configure this per transaction — VINR applies it automatically based on the credential type in the token. See [Authentication methods](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/authentication-methods) for the full SCA and liability breakdown.

## Enable Google Pay

Before Google Pay appears at checkout, toggle it on in the VINR Dashboard:

1. Go to **Settings → Payment methods**.
2. Toggle **Google Pay** to enabled.

For Hosted Checkout and Payment Links, that's all that's needed — Google Pay appears automatically for eligible customers. For Elements or the direct API, continue to the relevant integration guide below.

## Integration paths

Google Pay works across all VINR web checkout surfaces. Choose the path that matches how your checkout is built:

| Path                                                                                                     | Google Pay support                 | Code required |
| -------------------------------------------------------------------------------------------------------- | ---------------------------------- | ------------- |
| [Hosted Checkout](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/hosted-checkout) | Automatic when enabled             | None          |
| [Payment Links](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/payment-links)     | Automatic when enabled             | None          |
| [Elements](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/elements)               | Mount the `GooglePayElement`       | Minimal       |
| [Direct API](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/setup)                | Full Google Pay JS API integration | Yes           |

## Check eligibility before rendering the button

Always call `isReadyToPay()` before showing the Google Pay button. The button must only appear when the customer's browser and device support Google Pay and they have an eligible card enrolled.

```javascript
const googlePayClient = new google.payments.api.PaymentsClient({
  environment: 'PRODUCTION', // use 'TEST' in development and QA
});

googlePayClient.isReadyToPay({
  apiVersion: 2,
  apiVersionMinor: 0,
  allowedPaymentMethods: [{ type: 'CARD', parameters: { allowedAuthMethods, allowedCardNetworks } }],
}).then(response => {
  if (response.result) {
    // Show the Google Pay button
  }
  // Otherwise: keep the button hidden — do not disable it
});
```

Elements and Hosted Checkout handle this check for you — the button only renders when eligible.

## Environments

Google Pay operates in two environments:

| Environment  | Purpose                                             |
| ------------ | --------------------------------------------------- |
| `TEST`       | Development and QA — no real cards, no real charges |
| `PRODUCTION` | Live payments — requires VINR account approval      |

The VINR sandbox maps to the Google Pay `TEST` environment automatically. In `TEST` mode, `isReadyToPay` returns `true` regardless of enrolled cards, making it easy to test without a real device. When you go live, VINR moves you to the Google Pay `PRODUCTION` environment after approval — see [Test & go live](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/test-and-go-live).

## In this section

**Integration paths**

[Hosted Checkout](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/hosted-checkout) — Google Pay in VINR's hosted checkout — automatic, no extra code.

[Payment Links](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/payment-links) — Google Pay in payment links — appears automatically when enabled.

[Elements](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/elements) — Add a Google Pay button to your custom Elements-based checkout.

[Set up Google Pay (API)](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/setup) — Direct API integration: Dashboard configuration and token submission.

**Reference & guidance**

[Authentication methods](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/authentication-methods) — CRYPTOGRAM\_3DS vs PAN\_ONLY: security profiles, SCA, liability, and configuration.

[Dynamic checkout updates](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/dynamic-updates) — Why VINR finalizes the order total before the Google Pay sheet opens — live callback updates are not supported.

[Recurring payments](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/recurring-payments) — Save a Google Pay payment method and charge it off-session.

[Disputes and refunds](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/disputes-and-refunds) — Liability shift, chargeback handling, and refunds for Google Pay payments.

[Button guidelines](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/button-guidelines) — Google-compliant button styles, types, sizing, and what not to do.

[Go-live checklist](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/go-live-checklist) — Verify your integration before accepting live payments.

[Best practices](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/best-practices) — Improve conversion and maintain your Google Pay integration.

[Test & go live](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/test-and-go-live) — Test both credential types before switching to production.

## Trademarks

> Google Pay and the Google Pay logo are trademarks of Google LLC.

## See also

[Wallets](/docs/payments/payment-methods/add-payment-methods/wallets) — Apple Pay, Revolut Pay, and other digital wallets.

[Cards](/docs/payments/payment-methods/add-payment-methods/cards) — The card rail behind most Google Pay payments.

[Strong Customer Authentication](/docs/payments/strong-customer-authentication) — How SCA and 3D Secure interact with Google Pay credentials.