> 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/garantipay-payment-integration.md).
# GarantiPay Payment Integration
## Installation
### Preliminary Works
The following information is requested from the provider for the brand-specific and production (live) environment.
* **Merchant ID**
* **Terminal ID**
* **Password**
* **Store Key**
## Omnitron Settings
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 GPay type payment integration.
### Payment Options
One payment option must be defined in Omnitron to use gpay payments. Explanations on how the settings should be made at this stage are in the table below.
| **Field** | **Description** |
| ------------------- | --------------------------------- |
| Payment Option | “gpay” option must be selected |
| Payment Option Name | “Garanti Pay” or any related text |
| Payment Option Slug | gpay |
| Config\* | {"pos\_slug": "gpay"} |
{% hint style="info" %}
Fields in config should be determined according to the requirements.
{% endhint %}
### POS Integration
At least one POS integration must be defined in Omnitron to use gpay payment. Explanations on how the settings should be made at this stage are in the table below.
| **Field** | **Description** |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | GPay |
| Slug | gpay |
| Gateway | gpay |
| Resource URL | Requested URL from provider
Test:
Prod:
|
| 3D Resource URL | Requested URL from provider
Test:
Prod:
|
| Mode | TEST or PROD |
| Version | v0.01 |
| Username | PROVAUT |
| Password | Requested Password from provider |
| Terminal | Requested Terminal ID from provider |
| Merchant | Requested Merchant ID from provider |
| Timeout period | Timeout period in seconds |
| Store Key | Requested Store Key from provider |
| Company Name | Company Name |
| Refund User | PROVRFN |
| Refund URL | Requested URL from provider
Test:
Prod:
|
| Company Bonus Usable | Yes/No |
| Card Owner Bonus Usable | Yes/No |
## Additional
* A Card with GPAY00 bin number must be created to use GPay installments. To use a different bin number, can be add it to Commerce Settings with `GPAY_BIN_NUMBER` key.
* Zero or Next packages must be installed
*
---
# 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/payment-integrations/garantipay-payment-integration.md?ask=&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.