API Reference — Overview

The Incognito Payments API is a small REST API over HTTPS. Requests and responses are JSON. The shape — Bearer auth, the {success, message, data} envelope, the signature scheme — is Tripay-compatible.

Base URL

https://payment.incognito.asia/api/v1

The same base URL serves both environments; the environment is chosen by which API key you use.

Request format

• Authentication: Authorization: Bearer <api_key> on every request.
• Body: Content-Type: application/json for POST requests.
• IDs in the path (e.g. a reference) must be URL-encoded.

Response envelope

Every response — success or failure — uses the same envelope:

{
  "success": true,
  "message": "",
  "data": { "...": "..." }
}

Field	Type	Notes
success	boolean	true on a 2xx, false otherwise.
message	string	Human-readable; populated on errors.
data	object | array	The payload. Absent on failures.

On failure the HTTP status is non-2xx and data is omitted:

{ "success": false, "message": "Invalid signature." }

See Errors & status codes for the full list.

Endpoints

Method	Path	Purpose
GET	/payment-channels	List available payment channels.
POST	/transactions	Create a transaction (closed payment).
GET	/transactions/{reference}	Fetch a transaction and its status.
POST	/transactions/{reference}/simulate-pay	Sandbox only — settle a test transaction.

Tripay-compatible aliases

If you are pointing an existing Tripay client at this gateway, these alias paths behave identically to the ones above:

Alias	Same as
GET /merchant/payment-channel	GET /payment-channels
POST /transaction/create	POST /transactions
GET /transaction/detail?reference=…	GET /transactions/{reference}

Authentication

Bearer keys and environments — read the guide.

Signatures

How to sign requests and verify callbacks — read the guide.