Request Header
Colombia
Card Present API has a consistent header structure based on a set of parameters. To create the header, provide the following values:
Variable | Type | Description/Values |
---|---|---|
Content-Type | string | The content type. Valid Value (application/json) |
Client-Request-Id | string | A client-generated ID for request tracking and signature creation, unique per request. This is also used for idempotency control. Recommended 128-bit UUID format. |
Message-Authentication-Value | string | The Message Authentication Value (MAC) is optional header and it is only required for Card Present transactions or transactions originated from Terminals. The OpenAPI Header parameter format for the message authentication value of the complete payload follows the pattern ;;;[;][; |
Api-Key | string | Key given to merchant after boarding associating their requests with the appropriate app in Apigee. |
Timestamp | integer | Epoch timestamp in milliseconds in the request from a client system. Used for Message Signature generation and time limit (5 mins). Format: int64 Minimum value: -9223372036854776000 Maximum value: 9223372036854776000 |
Message-Signature | string | Used to ensure the request has not been tampered with during transmission. The Message-Signature is the Base64 encoded HMAC hash (SHA256 algorithm with the API Secret as the key.) |
Sample Header
{
"Content-Type": "application/json",
"Client-Request-Id": "CLIENT_REQUEST_ID",
"Api-Key": "API_KEY",
"Timestamp": "TIMESTAMP",
}
Updated 4 months ago