> 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/paywall-payment-integration.md).

# Paywall Payment Integration

## <mark style="color:red;">**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.

* **Public URL**
* **Private URL**
* **Public Key**
* **Public Client**
* **Private Key**
* **Private Client**

## <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, it will be accessible under a new tab on the payment screen as it is a credit card type payment integration.

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

One payment option must be defined in Omnitron to use credit card payments. Explanations on how the settings should be made at this stage are in the table below.

{% hint style="info" %}
Do not set more than one active payment option with the type “masterpass” or “credit card”.
{% endhint %}

| Field               | Description                           |
| ------------------- | ------------------------------------- |
| Payment Option      | “Credit Card” option must be selected |
| Payment Option Name | “Credit Card” or any related text     |
| Payment Option Slug | credit\_card                          |
| Config\*            | {}                                    |
| Status              | True                                  |

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

One POS integration must be defined in Omnitron to use credit card payments. Explanations on how the settings should be made at this stage are in the table below.

| Field                | Description                            |
| -------------------- | -------------------------------------- |
| Name                 | Paywall                                |
| Slug                 | paywall                                |
| Gateway              | paywall                                |
| Three d resource url | To be filled with Public URL           |
| Resource URL         | To be filled with Public URL           |
| Public URL           | Requested URL from provider            |
| Private URL          | Requested URL from provider            |
| Public Key           | Requested Public Key from provider     |
| Public Client        | Requested Public Client from provider  |
| Private Key          | Requested Private Key from provider    |
| Private Client       | Requested Private Client from provider |
| Three d enabled      | Yes/No                                 |

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

* There can be a maximum one credit card (or masterpass) payment option per sales channel in Omnitron but POS integrations connected to the payment option can be multiple for different payment providers.
* For additional information, refer to the [POS Integrations](/tutorials/omnitron/sales-channels/payment-management/how-to-manage-pos-integrations-in-omnitron.md) tutorial.


---

# 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/paywall-payment-integration.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.