> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ledig.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Transactions

> View deposits, conversions and payments in your business's transaction history.

Transactions show the activity in your Ledig business account. Use them to match deposits and payments with records in your own system. For a payment currently in progress, use the [transfer endpoint](https://docs.ledig.io/guides/transfers.md#follow-payment-progress).

## List transactions

For example, request the last 30 days of USDT transactions:

```http theme={null}
GET /v1/transactions?currency=USDT&period=30d&limit=20
```

| Query | Meaning |
| - | - |
| `status` | Filter by transaction status. |
| `displayStatus` | Filter by the status shown to the customer. |
| `currency` | Filter by currency, such as `USDT`. |
| `category` | Filter by category. |
| `type` | Filter by transaction type. |
| `reference` | Find activity with your reference. |
| `isCredit` | Use `true` for credits or `false` for debits. |
| `isFiat` | Use `true` for fiat or `false` for crypto. |
| `period` | Choose `7d`, `30d`, `90d` or `1y`. |
| `from`, `to` | Set a date range instead of `period`. |
| `limit` | Number of results per page, up to 100. |
| `cursor` | Continue from the returned `pagination.nextCursor`. |
| `sort` | Choose `asc` or `desc`. |

This fictional response excerpt shows a completed USDT payout:

```json theme={null}
{
  "status": "success",
  "data": [
    {
      "id": "txn_example",
      "reference": "order-1042",
      "category": "payout",
      "type": "crypto",
      "amount": "100",
      "currency": "USDT",
      "status": "completed",
      "description": "Payout to recipient",
      "isCredit": false,
      "isFiat": false,
      "createdAt": "2026-10-22T09:00:00.000Z"
    }
  ],
  "pagination": {}
}
```

Amounts are decimal strings. In this example, `isCredit: false` means an outgoing amount and `isFiat: false` identifies a crypto transaction.

Use the returned cursor for the next page. Stop when `pagination.nextCursor` is absent, as in this final-page example. See [Pagination](https://docs.ledig.io/guides/pagination.md).

## Read one transaction

Call `GET /v1/transactions/{id}` using an ID returned in your history.

The response may include:

| Field | Use it to |
| - | - |
| `displayStatus`, `displayStatusDescription` | Show a clear status and explanation in your interface. |
| `balanceImpact` | Understand whether funds are held, deducted or returned. See [Transfers](https://docs.ledig.io/guides/transfers.md#what-happened-to-the-funds). |
| `transactionHash`, `network` | Identify a crypto transaction on its network. |

Use receipt references or download links when they are returned. Some fields are only present for relevant transaction types.

## Deposits awaiting release

A deposit can appear in history before it is available to spend. A deposit receipt can have `data.recordKind: "deposit_receipt"` and `data.affectsBalance: false`. If `displayStatus` is `frozen`, the funds are held and are not yet available.

When the deposit is credited, the transaction replaces the receipt-only entry. Looking up the original receipt ID can return that transaction. Match records using the returned ID and reference so you do not count the same deposit twice.

## Check available funds

Use [Balances](https://docs.ledig.io/guides/balances.md) for your available and reserved amounts. Do not calculate a spendable balance by adding every history entry: some records are informational and have `data.affectsBalance: false`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.