Payments

Agent Fund Transactions

List prepaid fund movements for the authenticated agent.

Usage Note

Use this route when the app needs to show how the agent's prepaid balance changed over time, for example a fund ledger or statement screen. To show only the current balance, use Agent Fund Balance.

List Agent Fund Transactions

GET /api/v2/agent/fund-transactions

Returns a paginated list of the authenticated agent's prepaid fund transactions.

Access note

  • treat this as a protected route and send Authorization: Bearer <access_token>
  • the response is scoped to the authenticated agent in the current bearer token context

Query parameters

All parameters are optional.

NameTypeDefaultNotes
transaction_typestring—CARD_REQUEST, REFUND, CARD_TOP_UP, CARD_CANCEL_REFUND, or CARD_CANCEL_DEBIT
directionstring—IN or OUT
source_typestring—card_request, card_top_ups, card_top_up, agent_top_ups, or card_cancellation_settlement
statusstring—PENDING, COMPLETED, SUCCESS, FAILED, or REVERSED
searchstring—Mobile user search: id or uid (exact match), full_name, phone, or email (partial match)
start_datestring—Inclusive start, as YYYY-MM-DD or RFC 3339 with timezone
end_datestring—Inclusive end, as YYYY-MM-DD or RFC 3339 with timezone
pageint1Page number
limitint20Items per page, max 100
sort_bystringcreated_atcreated_at, amount, balance_after, or id
sort_orderstringdescasc or desc

Request body

None.

Response fields

  • id, uuid: the fund transaction identifiers
  • mobile_user_id, mobile_user: the mobile user the transaction relates to
  • card: the related card; omitted when the transaction has no card
  • card_top_up: top-up details for top-up transactions; null otherwise
  • card_request: card-request details for card-request transactions; null otherwise
  • amount: the transaction amount
  • transaction_type, direction, source_type, status: see the query parameter values above
  • currency: the currency code of the transaction
  • balance_before, balance_after: the agent's prepaid balance before and after the transaction
  • note: a short description; omitted when empty
  • created_at: the transaction time in RFC 3339 format

Success response shape

{
  "trace_id": "b3f1c2a0-…",
  "status_code": 200,
  "message": "success",
  "data": [
    {
      "id": 9123,
      "uuid": "0d1e6b0e-3c2a-4b8f-9a55-1f2f6b1c7e10",
      "mobile_user_id": 5521,
      "mobile_user": {
        "id": 5521,
        "uid": 10005521,
        "uuid": "8a7c1f3e-2b0d-4e9a-8c41-6d2f9e0b7a33",
        "full_name": "Dara Sok"
      },
      "card": {
        "id": 311,
        "card_id": "550e8400-e29b-41d4-a716-446655440000",
        "uuid": "4c9b0d2a-6f1e-4a7b-9d3c-2e8f5a1b0c64",
        "card_type": "VIRTUAL",
        "card_number": "4111********1111"
      },
      "card_top_up": {
        "id": 6487,
        "uuid": "140496f3-4e33-4dd6-a032-70f0e75dad4e",
        "created_at": "2026-10-12T10:27:43+07:00",
        "currency": "USD",
        "amount": "21.15",
        "topup_fee": "2.65",
        "net_amount": "18.50"
      },
      "card_request": null,
      "amount": "21.15",
      "transaction_type": "CARD_TOP_UP",
      "currency": "USD",
      "direction": "OUT",
      "source_type": "card_top_ups",
      "status": "SUCCESS",
      "balance_before": "1,000.00",
      "balance_after": "978.85",
      "note": "Card top-up",
      "created_at": "2026-10-12T10:27:43+07:00"
    }
  ],
  "metadata": {
    "has_next": true,
    "has_prev": false,
    "total_page": 5,
    "current_page": 1,
    "limit": 20,
    "total_count": 93,
    "total_wallet_topup_amount": ""
  }
}

Values are illustrative.

card_request shape

For card-request transactions, card_request has this shape:

{
  "id": 701,
  "uuid": "6df4b096-a437-4b52-9f1d-52ab15ee5193",
  "created_at": "2026-10-12T10:27:43+07:00",
  "currency": "USD",
  "card_request_fee": "25.00"
}

Error response shape

Errors return HTTP 200; the real status is in status_code.

{
  "status_code": 400,
  "message": "Invalid query parameters",
  "trace_id": "b3f1c2a0-…",
  "data": null
}

Integration notes

  • always check status_code in the body, not only the HTTP status
  • all amounts are display-ready strings with 2 decimal places and thousands separators (e.g., "1,000.00"); remove separators and parse as a decimal before doing arithmetic
  • card and note may be missing from an item, and card_top_up / card_request may be null, so handle all of these cases in the client
Copyright © 2026