# Google Pay in payment links

> Google Pay is available automatically in VINR payment links when enabled on your account.

Payment links use the same VINR hosted checkout as a full checkout session. When Google Pay is enabled on your merchant account, it appears automatically in every payment link for eligible browsers and devices — no code changes are required.

## How it works

A payment link opens a hosted checkout page. VINR checks `isReadyToPay` against your merchant account configuration and shows the Google Pay button if the customer's device is eligible. The entire token exchange, 3D Secure handling, and authorization run on the VINR platform — your link requires no Google Pay-specific configuration.

```
customer opens link → VINR hosted checkout → Google Pay button (if eligible) → payment.completed webhook
```

## Enable Google Pay

Enable Google Pay once in the Dashboard and it applies to all your payment links:

1. Go to **Settings → Payment methods** in the VINR Dashboard.
2. Toggle **Google Pay** to enabled.

> For production payments you must complete Google merchant registration or Google Pay tokens will be rejected. See [Register with Google](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/setup#register-with-google) — allow 1–2 business days for approval. Sandbox links work without registration.

## Authentication methods

Which credential types are offered — `CRYPTOGRAM_3DS`, `PAN_ONLY`, or both — comes from your merchant account configuration and applies to all payment links on that account. You cannot set auth methods per link.

To check or change your configuration, contact your VINR account manager. See [Authentication methods](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/authentication-methods#per-merchant-configuration) for details, including when to restrict to `CRYPTOGRAM_3DS`-only.

## Reusable vs one-time links

Google Pay works identically in both link types. Each time a customer pays via a reusable link, a fresh payment is created and the Google Pay flow runs from scratch. There is no stored token or recurring authorization — each payment is a new customer-present transaction.

## Testing

To test Google Pay in a payment link:

1. Create a payment link from the Dashboard or API with your account in sandbox mode.
2. Open the link in a browser with the Google Pay test environment active.
3. Complete a payment using the Google Pay test card sheet.
4. Verify that `payment.completed` fires on your webhook endpoint.

Test both credential scenarios if your account has both enabled — see [Test & go live](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/test-and-go-live) for the full test card reference.

## See also

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

[Payment links](/docs/payments/payment-links) — Create and share no-code payment links.

[Test & go live](/docs/payments/payment-methods/add-payment-methods/wallets/google-pay/test-and-go-live) — Test Google Pay and complete production approval.