Integration Requirements

When calling the API, it is necessary to provide:

For methods that require authentication, it is necessary to pass the Merchant Terminal identifier X-Terminal-Id in the request header.

• Whenever you send a requestId to a Payment Gateway API, its value must be unique and unused — never reuse the same requestId across two requests. The recommended way to guarantee this is to send a randomly generated UUID (v4) as the requestId. Data in requests must be encoded in UTF-8.

• Values of the amount field are represented according to the format 0.00 (two decimal places and a dot is used as a separator between the integer and the fractional part).

Upcoming requestId validation

A validation constraint will soon be enforced on the requestId field that requires a UUID value format to ensure uniqueness across systems. To avoid a breaking change when this goes live, start sending randomly generated UUIDs as your requestId now.