# Benefit via Tap

## <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**
* **URL**

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

The installed extension must also be defined to the project via Omnitron. This can be done on the **Payment Options & Add/Edit POS Integration** pages. After the settings are completed, it will be accessible under a new tab on the payment screen as it is a redirection type payment integration.

### <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      | Redirection                                                                                                                                                                                                    |
| Payment Option Name | Benefit via Tap                                                                                                                                                                                                |
| Payment Option Slug | benefit\_tap\_po                                                                                                                                                                                               |
| Config              | { "pos\_slug": “benefit\_tap”, "rule": { "klass": "omnishop.payments.rules.AndRule", "params": { "children": \[ { "klass": "omnishop.payments.rules.CurrencyRule", "params": { "currencies": "bhd" } } ] } } } |

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

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

| Field           | Description                                                          |
| --------------- | -------------------------------------------------------------------- |
| Name            | Benefit                                                              |
| Slug            | benefit\_tap                                                         |
| Gateway         | benefit\_tap (omnicore.libs.payment\_gateways.tap.BenefitTapGateway) |
| Resource URL    | Requested URL from the provider (ex: <https://api.tap.company/v2>)   |
| 3D Resource Url | Requested URL from the provider (ex: <https://api.tap.company/v2>)   |
| Secret Key      | Requested Secret Key from the provider                               |
| Merchant Id     | Requested Merchant Id from the provider                              |

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

It supports payments in BHD currency only.

Useful links:

* [Tap Documentation](https://developers.tap.company/docs/benefit)


---

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