# Terminology

**maibmerchants** - portal dedicated to the Merchant, where they can configure the necessary settings for integration with **maib** e-commerce, perform certain financial operations (such as payment refunds), and access additional functionalities.

The portal is continuously evolving, and in the future, it will also include other tools that will streamline and enhance the digital experience of the Merchant.

**maib ecomm** - the **maib** system that processes ecommerce transactions.

**maib ecomm checkout** - the page where the Customer is redirected to enter the card data (or pay via Apple Pay™ / Google Pay™).

The merchant has the ability to modify this page. Upon request, they will receive the page template and the requirements according to which they will make the modifications.

**Merchant** - an entity engaged in commercial activity that owns an ecommerce solution and initiates integration with **maib** e-commerce to accept online payments.

**Project** - an entity in the **maibmerchants** platform that contains information and settings related to integrating a solution with **maib** e-commerce.

For each website/app a new Project will be opened and the following settings will be made:

1. Domain - website/app domain, must belong to the Merchant.
2. IP - hosting/server IP.
3. Platform - refers to the platform used to build/develop and manage the ecommerce solution. This can be a CMS (content management system), framework or a specific programming language.
4. Callback URL - the link where the Merchant will receive the final response with the transaction status and data.
5. Ok URL - the link where the Customer will be redirected if the transaction is successful.
6. Fail URL - the link where the Customer will be redirected if the transaction failed.

**Project Secret** - is used together with **Project ID** to generate the Access Token, used to authorize requests to **maib ecomm**.

**Signature Key** - used to validate notifications with transaction status and data on the Callback URL. See more details in the [Notifications on Callback URL](https://docs.maibmerchants.md/e-commerce/notifications-on-callback-url) section.

**Intermediate response** - response from **maib ecomm** to Merchant containing the transaction identifier and the link to the **maib ecomm checkout**.

**Final response** - response from **maib ecomm** to Merchant (on Callback Url) containing the status and basic data of the transaction. Callback Url is set in **maibmerchants** but can also be sent in request (*callbackUrl* parameter).

### **Test Project**

The Test Project is intended for conducting transactions in the testing environment. In the test environment, all types of payments provided in the **maib** e-commerce API can be performed: direct payments, two-step payments, recurring payments, and one-click payments.

{% hint style="info" %}
Testing is one of the mandatory conditions for activating the Production Project. 

Execute successful tests according to the endpoints for the [type of payment](https://docs.maibmerchants.md/e-commerce/payments-types) you intend to use, using [test card](#user-content-fn-1)[^1] data.
{% endhint %}

### Production Project

The Production Project is intended for carrying out real transactions and can be activated only after signing the e-commerce contract and configuring the project in the platform (Domain / IP / Platform / Callback URL / Ok URL / Fail URL).

After activating the Project, you will have access to the Project Secret and Signature Key for integrating your solution with **maib** e-commerce API.

[^1]: Cardholder: Test Test

    Card number: 5102180060101124 

    Exp. date: 06/28 

    CVV: 760


---

# 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.maibmerchants.md/e-commerce/terminology.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.