Cloud Services

In Cloud mode, your POS sends HTTP requests to Kushki's cloud infrastructure, which forwards commands to the target terminal via push. Use this mode when your POS runs in the cloud or on a different network from the terminal.

Beta — Early Access

Kushki ONE Cloud is currently in Beta for Mexico 🇲🇽. Do not deploy to production without coordinating with the Kushki integration team.

Base URLs

Environment	URL
Production	`https://cloudt.kushkipagos.com`
UAT	`https://uat-cloudt.kushkipagos.com`

All endpoints follow the pattern:

POST https://cloudt.kushkipagos.com/terminal/v1/{terminalSerial}/sync/{operation}

The terminalSerial is the serial number of the target SmartPOS terminal, assigned in DMS.

Authentication

All Cloud requests require two signed headers:

Header	Description
`Authorization`	HMAC-SHA256 signature of the raw JSON request body, Base64-encoded. Key = your `Business-Code`
`timestamp`	Current Unix timestamp in milliseconds (13 digits) — must be within ±5 minutes of server time

INFO

Omit Authorization on requests with no body (e.g. Abort).

APIs in this section

Payment API

Charge, pre-authorize, capture, void, refund, abort, and search transactions via Kushki's cloud.

Print API

Queue and monitor thermal print jobs on the terminal via Kushki's cloud. Async — 202 immediately.

Got a suggestion on this documentation? Contact us.

Base URLs#

Authentication#

APIs in this section#

Base URLs

Authentication

APIs in this section