> 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/apple-pay-via-tap-payment-installation.md).

# Apple Pay via Tap Payment 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**

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

* **Apple Pay Merchant Identifier**
* **Apple Pay Certificates (PEM and KEY)**

## <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](/tutorials/omnitron/sales-channels/payment-management/how-to-manage-pos-integrations-in-omnitron.md)

### <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              | { "pos\_slug": "tap\_applepay" }     |

### <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                | Apple Pay via Tap                                                                 |
| Slug                | tap\_applepay                                                                     |
| Gateway             | tap\_applepay                                                                     |
| 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                                           |
| Pay Url             | <https://apple.com/apple-pay>                                                     |
| Domain Name         | Domain Name of Shop (without https) *Example*: [example.com](http://example.com/) |
| Display Name        | Display Name on Apple Pay Payment Frame *Example*: My Store                       |
| Country Code        | ISO\_3166-1\_alpha-2 - Example: “SA”                                              |
| Merchant Identifier | Merchant Identifier value of Apple                                                |
| Certificate PEM     | Base64 Encoded pem file                                                           |
| Certificate KEY     | Base64 Encoded key file                                                           |

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

Useful links:

* [Apple Pay Token (Tap)](https://developers.tap.company/docs/apple-pay-token)
* [Sandbox Testing - Apple Pay](https://developer.apple.com/apple-pay/sandbox-testing/)


---

# 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 dynamically by asking a question.

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

```
GET https://docs.akinon.com/technical-guides/3rd-party-integration/payment-integrations/apple-pay-via-tap-payment-installation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.