> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/other-features/connectors/available-connectors/cybersource/google-pay.md).

# Google Pay

Enable Google Pay as a payment method via CyberSource in Juspay Hyperswitch.

{% hint style="info" %}
This page describes how **Google Pay** can be enabled in Hyperswitch via CyberSource.
{% endhint %}

> This guide assumes that you have already configured CyberSource as a connector in your Hyperswitch Control Center. If not, follow the steps mentioned [here](/other-features/connectors/available-connectors/cybersource.md).

### Steps to Configure Google Pay

* On your Hyperswitch Control Center, click on `Connectors > Payment Processors`.
* If you have already configured CyberSource successfully, you will land on the page shown in the image below.

  <figure><img src="https://1943537505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf7BGdsPkCw9nalhAIlE%2Fuploads%2Fgit-blob-101b51afda8cbd2be6f47189b7972f3d12d7218b%2FScreenshot%202024-03-14%20at%201.36.58%20PM.png?alt=media" alt=""><figcaption></figcaption></figure>
* Click on CyberSource and then click the `Edit` icon to **update** the configuration of the CyberSource connector.

  <figure><img src="https://1943537505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf7BGdsPkCw9nalhAIlE%2Fuploads%2Fgit-blob-e2031c90e1f35b684786cfe8c89b71b43321e6aa%2FScreenshot%202024-03-14%20at%201.38.05%20PM.png?alt=media" alt=""><figcaption></figcaption></figure>
* Click **Proceed** after making any necessary changes to your API keys.
* Select **Google Pay** under the **Wallet** section to enable it.
* Enter the Google Pay details in the overlay form and click **Proceed**:
  1. **Google Pay Merchant Key**: Your CyberSource Merchant ID.
  2. **Google Pay Merchant Name**: The display name that customers will see in their Google Pay app when making a payment.
  3. **Google Pay Merchant ID:** \[<mark style="color:red;">For Production Only</mark>] Your Google Pay Merchant ID provided by Google after you sign up and receive approval to use Google Pay in production.

{% hint style="success" %}
**\[SANDBOX ENV]:** For the sandbox test environment, you can enter any **dummy value** for **Google Pay Merchant ID** — it will not affect the payment experience.
{% endhint %}

<figure><img src="https://1943537505-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf7BGdsPkCw9nalhAIlE%2Fuploads%2Fgit-blob-4244334109a79de26fa968c83872174762b8c645%2FScreenshot%202024-03-14%20at%201.46.32%20PM.png?alt=media" alt=""><figcaption></figcaption></figure>

* Click **Proceed**, review your changes, and click **Done**.

### Points to Remember for Google Pay Payments via CyberSource

* Required fields for a Google Pay payment request via CyberSource:
  * Email
  * Billing address details:
    * First Name
    * Last Name
    * Address Line 1
    * Zip/Postal Code
    * City
    * State
    * Country

{% hint style="warning" %}
We recommend passing these fields when creating the Payment Intent with Hyperswitch. Otherwise, the Hyperswitch SDK will collect this information from the customer at checkout, which may not provide the best payment experience.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/other-features/connectors/available-connectors/cybersource/google-pay.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.