> 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/masterpass-integrations/masterpass-rest-pos.md).

# Masterpass REST POS

## <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**
* **Terminal Group ID**
* **Store 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. After the settings are completed, it will be accessible via defined bin numbers on the credit card tab at the checkout. For additional information, refer to the [POS Integrations](https://docs.akinon.com/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 extension installed. Explanations on how the settings should be made at this stage are in the table below.

| Field               | Description                                                   |
| ------------------- | ------------------------------------------------------------- |
| Payment Option      | Masterpass Rest                                               |
| Payment Option Name | Masterpass Rest                                               |
| Payment Option Slug | mp\_rest\_po                                                  |
| Config              | { “pos\_slug”: “mp\_rest”, "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                    | Masterpass Rest                                                                       |
| Slug                    | mp\_rest                                                                              |
| Gateway                 | Masterpass Rest (omnicore.libs.payment\_gateways.masterpass.MasterpassRESTGateway)    |
| Resource URL            | Requested URL from the provider (ex: <https://mp-test-backend.masterpassturkiye.com>) |
| 3D Resource Url         | Requested URL from the provider (ex: <https://mp-test-backend.masterpassturkiye.com>) |
| Secret Key              | Requested Secret Key from the provider                                                |
| Merchant Id             | Requested Merchant ID from the provider                                               |
| Terminal Group ID       | Requested Terminal Group ID from the provider                                         |
| Store Key               | Requested Store Key from the provider                                                 |
| Three D Enabled         | True/False                                                                            |
| Merchant Type           | Defines if pos selection made by Omnitron or masterpass (custom/macro merchant id)    |
| Hash Validation Enabled | True/False Defines if 3d return hash validation will be made                          |

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

Useful links:

* [Masterpass Documentation](https://entegrasyon.masterpassturkiye.com/merchant/api-list)


---

# 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/masterpass-integrations/masterpass-rest-pos.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.
