> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/technical-guides/3rd-party-integration/payment-integrations/google-pay-via-tap-payment.md).

# Google Pay via Tap Payment

## <mark style="color:red;">POS Installation</mark>

### <mark style="color:red;">Preliminary Works</mark>

The following information is requested from the provider for the brand-specific and production (live) environment.

* Secret Key
* Merchant ID

## <mark style="color:red;">Omnitron Settings</mark>

This payment method’s configuration can be done on the **Payment Options & Add/Edit POS Integration** pages. See also: [Payment Management Tutorials](https://developers.akinon.com/docs/tutorialsv2/omnitron/sales-channels/payment-management/pos-integrations/)

### <mark style="color:red;">Payment Options</mark>

One payment option must be defined in Omnitron to be specific for the extension installed. Explanations on how the settings should be made at this stage are in the table below.

| **Field**           | **Description**                                      |
| ------------------- | ---------------------------------------------------- |
| Payment Option      | Digital Wallet                                       |
| Payment Option Name | “Digital Wallet” or any related text                 |
| Payment Option Slug | wallet                                               |
| Config              | <p>{</p><p>"pos\_slug": "tap\_googlepay"</p><p>}</p> |

### <mark style="color:red;">POS Integration</mark>

One POS integration must be defined in Omnitron to be specific for the extension installed. Explanations on how the settings should be made at this stage are in the table below.

| **Field**       | **Description**                                                    |
| --------------- | ------------------------------------------------------------------ |
| Name            | Google Pay via Tap                                                 |
| Slug            | tap\_googlepay                                                     |
| Gateway         | tap\_googlepay                                                     |
| Resource URL    | Requested URL from the provider (ex: <https://api.tap.company/v2>) |
| 3D Resource Url | Empty                                                              |
| Secret Key      | Requested Secret Key from the provider                             |
| Merchant Id     | Requested Merchant Id from the provider                            |
| Country Code    | ISO\_3166-1\_alpha-2 - Example: “SA”                               |
| Auto Duration   | Time (in hours) to cancel or capture payments if it’s pending      |
| Auto Type       | Process type after X hours if payment is pending, Void or Capture  |

## <mark style="color:red;">Additional Sources</mark>

* [Google Pay Document](https://developers.tap.company/docs/google-pay)


---

# 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.akinon.com/technical-guides/3rd-party-integration/payment-integrations/google-pay-via-tap-payment.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.