Transactions

GET/v1/transactions

List merchant transactions across every rail. There is no request body.

Query parameters

Query params that exist

Param	Type	Required	Notes
`type`	`string`	No	`payin` or `payout`
`limit`	`number`	No	1–100, default 20
`offset`	`number`	No	default 0

Do not send rail or status as query filters — they are not accepted. Filter in your own code using fields on each item.

Example

cURL

curl -X GET https://api.transacty.ai/v1/transactions?type=payin&limit=10 \
  -H "X-Transacty-Key: $TRANSACTY_KEY" \
  -H "X-Transacty-Timestamp: $TS" \
  -H "X-Transacty-Signature: $SIG" \
  -H "Content-Type: application/json"

Response fields

Field	Type	Description
`items`	`object[]`	Transaction list
`items[].id`	`string`	Transaction id
`items[].type`	`string`	`payin` or `payout`
`items[].status`	`string`	`pending`, `success`, or `failed`
`items[].amount`	`string`	Requested amount
`items[].currency`	`string`	Currency / wallet pocket (e.g. `BDT`, `INR`, `USDT`, `USDC`, `NGN`, `PYUSD-USDC`)
`items[].rail`	`string`	`bangladesh`, `brazil`, `india`, `europe`, `nigeria`, `pyusd`, `internal`, or `unknown`
`items[].railLabel`	`string`	Human label for badges / filter chips
`items[].paidAmount`	`string \| null`	Paid amount (if applicable)
`items[].platformOrderId`	`string`	Platform reference id
`items[].createdAt`	`string` (ISO datetime)	Creation timestamp
`items[].completedAt`	`string \| null` (ISO datetime)	Completion timestamp
`total`	`number`	Total matching records
`limit`	`number`	Returned page size
`offset`	`number`	Returned page offset

Get one transaction

GET/v1/transactions/:transactionId

Single row, same item shape as items[] above. Sign with {timestamp}..

Use this path in India (and other) flow tables — not /v1/transactions/:id.

To list PYUSD pay-ins: GET /v1/transactions?type=payin, then filter rail === "pyusd" in your app. For Nigeria: filter rail === "nigeria". There is no rail= query parameter.