# Payment Confirmation

## Marketplace Payment Confirmation Service Request Model;

<table><thead><tr><th width="101.33333333333331">Metod</th><th width="524">API URL</th><th>Parameter</th></tr></thead><tbody><tr><td>POST</td><td>https://posservice.esnekpos.com/api/services/PaymentConfirm</td><td>JSON File</td></tr></tbody></table>

In order for the store or stores to receive their payments, a request should be sent to the payment completion (confirmation) service by the marketplace. When all stores collect their receivables, the remaining amount is transferred to the marketplace.

#### The parameters to be sent to the service are as follows;

<table><thead><tr><th width="223">Parameters</th><th width="92">Type</th><th width="91">Compulsory</th><th>Description</th></tr></thead><tbody><tr><td>MERCHANT</td><td>string</td><td>Yes</td><td>It is a unique credential created specifically for the merchant (Marketplace).</td></tr><tr><td>MERCHANT_KEY</td><td>string</td><td>Yes</td><td>It is the key information created specifically for the merchant (Marketplace).</td></tr><tr><td>ORDER_REF_NUMBER</td><td>string</td><td>Yes</td><td>It is the reference number information given by the merchant (Marketplace) when sending the payment transaction request. The transaction is carried out by matching the payment transaction to be made to the reference number of the relevant merchant.</td></tr><tr><td>EXTERNAL_ID</td><td>string</td><td>Yes</td><td>It's the ID information in the marketplace (merchant) system of the store (submerchant). This information is assigned by the marketplace.</td></tr></tbody></table>

The sample JSON file to be sent to the service is as follows;

```json
                                            
{
    "MERCHANT": "TEST1234",
    "MERCHANT_KEY": "4oK26hK8MOXrIV1bzTRVPA==",
    "ORDER_REF_NUMBER": "412",
    "SubMerchantDetails": [
        {
            "EXTERNAL_ID": "EXTERNAL_ID1"
        },
        {
            "EXTERNAL_ID": "EXTERNAL_ID2"
        }
    ]
}
                                        
```

### Marketplace Payment Confirmation Service Reply Messag&#x65;**;**

#### The parameters of the reply message sent from the service after the transaction are as follows;

<table><thead><tr><th width="169">Parameters</th><th width="90">Type</th><th width="83">Compulsory</th><th>Descripiton</th></tr></thead><tbody><tr><td>Data</td><td>string</td><td>Evet</td><td>It is the data information of the approval process.</td></tr><tr><td>ResultCode</td><td>string</td><td>Evet</td><td>The status of the confirmation process is the code information.</td></tr><tr><td>ResultMessage</td><td>string</td><td>Evet</td><td>The status message is the result of the confirmation process.</td></tr><tr><td>Exception</td><td>string</td><td>Evet</td><td>It is the exception status information that occurs during the process for the approval process.</td></tr></tbody></table>

```json

{
    "Data": null,
    "ResultCode": "0",
    "ResultMessage": "SUCCESS",
    "Exception": null
}
                                        
```

In the marketplace payment confirmation response message, the value of the ResultMessage parameter is SUCCESS and the value of the ResultCode parameter is 0, indicating that the confirmation process was successful.


---

# 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://developer-eng.esnekpos.com/esnekpos-developer-environment/marketplace-integration/payment-confirmation.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.