# Google Pay

The Tieto E-Commerce Payment Gateway (EGW) provides native support for Google Pay, enabling merchants to accept fast, secure, and tokenized payments from Android and Chrome users. Google Pay simplifies the checkout experience by removing the need for manual card entry and leverages stored credentials with biometric authentication to ensure high conversion and strong security.

## Google Pay – Gateway Owner Responsibility

To enable Google Pay for live transactions, the Gateway Owner (e.g., Bank or PSP) must register and manage the Google Pay Merchant account. This includes:

* Registering a valid Google Pay Merchant ID
* Accepting the terms of use for Google Pay APIs
* Ensuring adherence to Google’s branding and usage guidelines

These responsibilities apply to both deployment models:

* Managed Service – Tietoevry handles technical integration, but legal/commercial enablement is the responsibility of the Gateway Owner.
* On-Premises – The Gateway Owner is accountable for the full setup and regulatory registration with Google.

## Integration via EGW

Google Pay is supported through both the EGW Hosted Checkout Page and API-based integrations, with all required token handling and scheme compliance managed by EGW. Merchants benefit from streamlined onboarding and simplified compliance requirements.

Integration Highlights:

* Hosted Checkout: - Google Pay button appears automatically for eligible browsers and devices.
* API-Based Checkout - Merchants using custom checkout can integrate via Google Pay JS and route payment tokens through EGW.
* Tokenized Transactions - Uses Visa Token Service (VTS) and Mastercard MDES for secure, network-based tokenization.
* Merchant Registration - Managed by Tietoevry; no direct setup with Google is required from the merchant.

### Customer Checkout Flow

1. Customer selects Google Pay on the checkout page.
2. Google Pay interface opens with pre-filled card and address data.
3. Customer authenticates using biometrics or device passcode.
4. EGW processes the token and completes the transaction securely.
5. Real-time confirmation is provided on the site or in the app.

## Merchant Capabilities

| Feature                 | Description                                                                          |
| ----------------------- | ------------------------------------------------------------------------------------ |
| Hosted Checkout Support | Google Pay button is dynamically shown for compatible Android/Chrome users.          |
| Custom Integration      | Use Google Pay JS for frontend, integrated with EGW’s backend token processing APIs. |
| Custom Button Styling   | Support for dark/light theme, button text (“Buy with GPay”), and placement options.  |
| Refund Support          | Refunds processed using standard EGW refund APIs or portal.                          |
| Stored Token Support    | With consent, token can be stored for one-click payments or subscriptions.           |

##  Security and Compliance

* Tokenized Transactions: Uses MDES and VTS for secure processing.
* PCI DSS scope reduced: No raw card data handled by merchant or EGW.
* Strong Customer Authentication (SCA): Biometric or passcode verification handled by the customer’s device.
* Compliant with Google’s wallet standards and brand guidelines.

## Business Benefits

* Improved conversion on Android and Chrome devices.
* Frictionless checkout with saved card details and biometric security.
* Reduced fraud through tokenization and secure device authentication.
* No additional registration or PCI burden for merchants.
* Fully white-labeled within EGW — appears under the bank or PSP’s branded checkout environment.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.ecomm.api.tietoevry.com/payment-method/digital-wallets/google-pay.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.