# Tap Saved Card Installation

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

This payment method’s configuration can be done on the **Payment Options & Add/Edit POS Integration** pages. After the settings are completed, the cards that have been saved before while using the credit card payment option will be accessible under a new tab on the payment screen as it is a saved card type payment integration. For additional information, refer to the [POS Integrations](/tutorials/omnitron/sales-channels/payment-management/how-to-manage-pos-integrations-in-omnitron.md) tutorial.

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

One payment option must be defined in Omnitron to be specific for the saved cards. Explanations on how the settings should be made at this stage are in the table below. A payment option of type credit\_card is assumed to have already existed because it is the only way to save new cards to show.

| Field               | Description                                                           |
| ------------------- | --------------------------------------------------------------------- |
| Payment Option      | saved\_card                                                           |
| Payment Option Name | Tap Saved Card                                                        |
| Payment Option Slug | tap\_saved                                                            |
| Config              | { "pos\_slug": "tap\_saved\_card", "provision\_enabled": true/false } |

### <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            | Tap Saved Card                                                             |
| Slug            | tap\_saved\_card                                                           |
| Gateway         | tap\_saved\_card (omnicore.libs.payment\_gateways.tap.TapSavedCardGateway) |
| 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                                    |
| Auto Type       | Desired Auto Type (VOID/CAPTURE)                                           |
| Auto Duration   | Desired Auto Duration in Hours                                             |
| Three D Enabled | True                                                                       |

Auto settings are specific to this integration. After authorizing the payment, Tap automatically cancels or captures it.

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

Useful links:

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


---

# 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/tap-saved-card-installation.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.