> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dintero.com/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.dintero.com/feedback

```json
{
  "path": "/docs/checkout/google-pay/google-pay-overview",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Overview

> Compare Google Pay integration options with Dintero Checkout, including hosted, embedded, and native Android app integration via dintero_psp or Worldline.

[Hosted Checkout]: /docs/checkout/google-pay/google-pay-hosted-checkout

[Native App Integration]: /docs/checkout/google-pay/google-pay-native-app

Google Pay™ is a digital wallet platform and online payment system that allows users to make payments using cards stored in their Google accounts. It provides a fast, secure, and convenient way for customers to pay for goods and services both online and in physical stores.

### Integration Options with Dintero

There are primarily two ways to support Google Pay in your payment flow: hosted checkout or native app integration.

#### 1. Hosted Checkout

If you are using our checkout solution you can add Google Pay without any need to integrate with Google Pay.
You just enable Google Pay and we take care of the rest.

#### 2. Native App Integration

If you need more control over the payment experience, such as in a native mobile application,
you can integrate with Google Pay yourself.

### Google Pay Feature Support by PSP Provider

Dintero supports Google Pay payments through both our own PSP and via Worldline. The table below shows which integration types are supported by each provider.

| PSP       | Native | Hosted | Hosted Embedded |
| --------- | :----: | :----: | :-------------: |
| Dintero   |    ✅   |    ✅   |        ✅        |
| Worldline |    ❌   |    ✅   |        ❌        |

### Liability

Google Pay processes payments through the customer's underlying card (credit, debit, or prepaid) stored in their Google account. Transactions are subject to card network chargeback rules — customers can dispute charges through their card issuer following the same process and liability rules as regular card payments.

Liability shift (where the risk is on the card issuer rather than the merchant) depends on how the card is authenticated at the time of payment:

* **Cards authenticated with device security** (e.g., a card stored on a mobile device secured with biometrics): These payments include a device-generated cryptogram that satisfies Strong Customer Authentication (SCA). Liability shift typically applies without requiring additional 3D Secure authentication.
* **Cards stored in a Google account without device-level security** (e.g., a card added via a desktop browser): These payments carry the card number without a device cryptogram. Additional 3D Secure authentication is required to achieve liability shift. Without it, the merchant bears fraud liability.

Merchants can inspect the `card.eci` field on an authorized transaction before capturing to determine the authentication level and resulting liability. A value of `05` (Visa) or `02` (Mastercard) indicates full SCA with liability shift to the issuer. `06`/`01` indicates authentication was attempted. `07`/`00` indicates no authentication was performed and the merchant bears fraud liability.

### Next Steps

* Learn about [Hosted Checkout] for a simple, managed integration
* Explore [Native App Integration] for native Android implementation