Google Pay™

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 resourcesAskCopy

By integrating Google Pay, you must accept the Google Pay API Terms of Service and must comply with the Google Pay API Acceptable Use Policy.

For technical reference, see the Google Pay Web developer documentation, the Web integration checklist, and the Web Brand Guidelines.

How Google Pay worksAskCopy

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.

Authentication methodsAskCopy

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 for the full SCA and liability breakdown.

Enable Google PayAskCopy

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 pathsAskCopy

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

Check eligibility before rendering the buttonAskCopy

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.

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.

EnvironmentsAskCopy

Google Pay operates in two environments:

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.

In this sectionAskCopy

Integration paths

Reference & guidance

TrademarksAskCopy

See alsoAskCopy