Transaction endpoints help you build activity pages, payout history, support views, and reconciliation flows for the user context supplied by your backend. Only expose activity that belongs to the product surface you are building. Do not show transaction categories your integration does not support.

​
Endpoints

GET  /api/v1/transactions
GET  /api/v1/transactions/{id}

​
List transactions

GET /api/v1/transactions?limit=20&page=1
Example response: 
{
  "status": "success",
  "message": "Success",
  "data": {
    "page": 1,
    "pages": 4,
    "limit": 20,
    "total": 75,
    "data": [
      {
        "_id": "transaction_id",
        "uid": "SMFY-12345678",
        "amount": 100,
        "amountToReceive": 136000,
        "coin": "usdt",
        "chain": "tron",
        "currency": "usdt",
        "type": "CRYPTO_TO_CASH",
        "status": "completed",
        "payoutStatus": "completed",
        "remark": "Customer payout",
        "fee": 1,
        "rate": 1360,
        "createdAt": "2026-05-22T10:15:30.000Z",
        "updatedAt": "2026-05-22T10:16:10.000Z"
      }
    ]
  }
}
Always keep transaction reads behind your backend. Do not expose transaction IDs or API credentials directly to frontend clients.