# Google Pay

> **Information**
>
> Google Pay is available for Flow. Flow enables you to [accept payments on your website](https://www.checkout.com/docs/payments/accept-payments/accept-a-payment-on-your-website.md) using Checkout.com's global network of payment methods with a single integration.

[Google Pay](https://www.checkout.com/payment-methods/googlepay) enables customers to securely perform one-touch payments on your website or Android app, using any credit or debit card connected to their Google account.

> **Information**
>
> To enable Google Pay in the UAE or Saudi Arabia, contact your account manager or [request support](https://dashboard.checkout.com/support/new?topic=case_account_management_and_access&issue=issue_account_changes).

---

## Google Pay with 3D Secure

Google Pay offers the following authentication modes:

- `PAN_ONLY` – The card is stored on file with your customer's Google account. The payment credentials are not bound to an Android device. For example, desktop or non-Android mobile web.
- `CRYPTOGRAM_3DS` – Google Pay offers SCA compliance by binding payment credentials to an Android device and allowing issuers to delegate the authentication to Google for all subsequent payments on that device.

`CRYPTOGRAM_3DS` credentials receive liability shift by default; to enable liability shift for `PAN_ONLY` transactions, apply 3DS.

To comply with SCA requirements for `PAN_ONLY` scenarios, see [Desktop (or when device binding is unavailable)](#Desktop_(or_when_device_binding_is_unavailable)).

### Liability shift

Google Pay transactions authenticated with 3DS can benefit from liability shift when the cardholder adds their card:

- To Google Chrome or a Google product directly – The card is saved as a Funding Primary Account Number (FPAN) and supports liability shift for payments explicitly authenticated with 3DS.
- To the native Google Pay app using their Android device – The card is saved as a Device Primary Account Number (DPAN) and supports liability shift, because authentication occurred when the card was added.

Card schemes may downgrade a payment's liability shift during the authorization stage. This can happen even if the ECI value indicates that the downgrade occurred during authentication. The liability shift outcome is determined after authorization.

> **Information**
>
> To benefit from liability shift for Visa transactions processed using Google Pay, Visa requires you to opt in to [Fraud liability protection for Visa device tokens](https://developers.google.com/pay/api/android/guides/resources/shift-liability-to-issuer#liability-shift-visa).

### Tokenize Google Pay payment data with 3DS

When you receive the payment data from Google, request a Checkout.com token to encrypt the payment data.
The response returns a new `token_format` that identifies whether subsequent payments using this token already meet SCA requirements.

#### Android native app and mobile web

| token_format | SCA compliance |
| --- | --- |
| `CRYPTOGRAM_3DS` | Google handles the authentication and provides a payload that meets the SCA requirements. |

> **Note**
>
> When a Google Pay payment does not require a 3D Secure setup (for example, payments using a `CRYPTOGRAM_3DS` token), we handle the authorization request without 3DS.

#### Desktop (or when device binding is unavailable)

| token_format | SCA compliance |
| --- | --- |
| `PAN_ONLY` | For in-scope transactions, the payment must use a 3D Secure exemption or be processed as 3D Secure. |

#### Response example

```json
{
  "type": "googlepay",
  "token": "tok_xac73j6l7rue7freatxtonf3pi",
  "expires_on": "2026-09-15T11:14:15Z",
  "expiry_month": 12,
  "expiry_year": 2026,
  "last4": "1111",
  "bin": "411111",
  "token_format": "pan_only"
}
```

### Request a 3D Secure payment using Google Pay

After receiving your token, you can authenticate the transaction as follows:

1. Include the Google Pay token in the payment request body.
2. To process this transaction as a 3D Secure payment, set the `3ds.enabled` field to `true`.

#### Request example

```json
{
  "source": {
    "type": "token",
    "token": "tok_lrn2umaznynuvkcjc6unno663u"
  },
  "amount": 1234,
  "currency": "GBP",
  "3ds": {
    "enabled": true
  }
}
```

#### Response example

If the card is enrolled in 3D Secure, you receive a `202 Success` response. This response contains a redirect link for your customer.

```json
{
  "id": "pay_hl4k4b5n6pfklmfayflhzw3ovq",
  "status": "Pending",
  "customer": {
    "id": "cus_rtr7qq37wzhujcp5iv36qys43i"
  },
  "3ds": {
    "downgraded": false,
    "enrolled": "Y"
  },
  "_links": {
    "self": {
      "href": "https://{prefix}.api.sandbox.checkout.com/payments/pay_hl4k4b5n6pfklmfayflhzw3ovq"
    },
    "redirect": {
      "href": "https://3ds2-sandbox.ckotech.co/interceptor/3ds_bicq62vdvrbuznjzcmcfrhtswy"
    }
  }
}
```

---

## Available for

- [Web](https://www.checkout.com/docs/payments/add-payment-methods/google-pay/web.md): Accept Google Pay payments on your website with Flow, our pre-built, customizable payment user interface.
- [Android](https://www.checkout.com/docs/payments/add-payment-methods/google-pay/android.md): Accept Google Pay payments in your Android app with Flow for mobile, our pre-built, customizable payment user interface.
- [Payment Setup API](https://www.checkout.com/docs/payments/add-payment-methods/google-pay/payment-setup-api.md): Build your own UI and integrate with our Payment Setup API to process Google Pay payments.
- [Unified Payments API](https://www.checkout.com/docs/payments/add-payment-methods/google-pay/unified-payments-api.md): Build your own UI and integrate with our API to process Google Pay payments.