Payout Mefete (TRY) h2h¶
The request contains certain fields:¶
| Field | Description |
|---|---|
merchant |
unique merchant ID; |
method |
payout method, an integer number 57 – Payout Mefete; |
payout_id |
outgoing payment number in the merchant’s system; |
account |
Mefete account number; |
full_name |
first name, last name of the client. Maximum length 30 characters; (Only Turkish and Latin characters are available); |
customs_phone |
recipient's phone number; |
amount |
transaction amount in the TRY currency only, separator character is a point “.”; |
currency |
transaction currency in TRY only; |
sign |
digital signature with the merchant’s key. Available fields are: “merchant”, “method”, “payout_id”, “account”, “full_name”, “amount”, “currency” and “customs_phone”. It is hashed using the MD5 method (for more details, read the “Digital signature in requests” section). |
Example:
application/json
The response contains certain fields:¶
| Field | Description |
|---|---|
status |
transaction status:Success – the payment is completed successfully (final status)Pending – the payment is new or is in line for processing. The Pending status requires an additional request (for more details, read the section “Payment Status Request (Payout)”)Blocked – payment declined (final status)Error – received data error. The response contains a signature with an empty key (the status is not final and is the basis for finding out the reason for this status); |
code |
transaction status code; |
payout_id |
outgoing payment number in the merchant’s system; |
description |
status description; |
sign |
digital signature with the merchant’s key. |
Example of the response – Success status:
application/json
Example of the response – Pending status
application/json
Example of the response – Error status:
application/json
Final Status (Callback)¶
The callback mechanism notifies the merchant that the transaction has received a final status (for example, from “Pending” to “Success”).
For more information, read the Callbacks section.