Search

The Transaction Search (Cloud) endpoint queries the transaction history stored in Kushki's acquirer backend. Results include all statuses and the full transaction detail for every operation processed by the authenticated merchant.

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 URL and endpoint

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

POST /terminal/v1/{terminalSerial}/sync/transaction_search

Authentication

WARNING

timestamp must be in milliseconds (13 digits). A 10-digit seconds value will be rejected.

Request

{
  "page": 1,
  "size": 10,
  "filters": {
    "last_four_digits": "5480",
    "start_date": 0,
    "end_date": 0,
    "transaction_reference": "",
    "transaction_type": ""
  }
}

Field	Type	Description
`page`	integer	Page number — starts at `1`
`size`	integer	Results per page
`filters.last_four_digits`	string	Filter by last 4 digits of the card
`filters.start_date`	integer	Start of date range (Unix ms). `0` = no filter
`filters.end_date`	integer	End of date range (Unix ms). `0` = no filter
`filters.transaction_reference`	string	Filter by Kushki transaction reference
`filters.transaction_type`	string	Filter by type: `charge`, `authorization`, `capture`, `void`, `refund`

Key characteristics

	Cloud Search
Source	Kushki acquirer backend
Works offline	❌ — requires internet
Full history	✅ — all statuses, all terminals
Best for	Reconciliation, reporting, end-of-day close

INFO

Cloud Transaction Search queries Kushki's backend directly — it is not limited to the terminal's local storage window. Use it for end-of-day reconciliation and full transaction reporting.

Got a suggestion on this documentation? Contact us.

Base URL and endpoint#

Authentication#

Request#

Key characteristics#

Base URL and endpoint

Authentication

Request

Key characteristics