| Key | Value |
|---|---|
| correlationId | Correlation{{randomNumber}} |
| PG-Auth-Token | {{merchantNumber}}:{{terminalNumber}}:{{hash}} |
| PG-Api-Version | v4 |
In the header section, correlationId and PG-Auth-Token parameters are expected to be transmitted. correlationId must be transmitted as a string unique value for each transaction. PG-Auth-Token parameter consists of merchantNumber, terminalNumber and hash information of the merchant as stated in the table. For hash information, merchantNumber, terminalNumber and secretKey information of the merchant is obtained by hashing with sha256 and converting it to string.
Response
{
"errorCode": 4003,
"errorMessage": " Inconsistent hash value sent in header",
"success": false,
"systemTime": "2024-03-30T12:08:40.526596076",
"correlationId": "correlation9975"
}
"PG-Auth-Token" parameter should be passed in the header in all sales, cancellation/refund, pre-authorization, pre-authorization closure, 3D sales and 3D sales completion requests.
This information consists of "merchantNumber:TerminalNumber:Hash" information of the merchant. The hash information is expected to be calculated according to the requested values and added to the PG-Auth-Token parameter.