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

# Payments

> Your order ledger — every payment, every status, and what the columns mean.

One table, every order, whichever rail it came in on.

## Columns

| Column      | Meaning                                                   |
| ----------- | --------------------------------------------------------- |
| Order       | Your reference, if you supplied one                       |
| Amount      | Expected, in the settlement token                         |
| Received    | What actually arrived — differs on under- and overpayment |
| Token       | What was paid                                             |
| Network     | Which chain                                               |
| Rail        | Wallet (connect) or pay-to-address (deposit)              |
| Status      | Where it is in its lifecycle                              |
| Customer    | Payer address, where known                                |
| Time        | When it arrived                                           |
| Transaction | Explorer link                                             |

<Tip>
  **Amount** against **Received** is the first thing to check on any query. A mismatch explains most "the customer says they paid" tickets immediately.
</Tip>

## Statuses

<Columns cols={2}>
  <Card title="Normal" icon="check" color="#10B981">
    `waiting` → `confirming` → `paid` → `swept`

    Money in your pool at `swept`.
  </Card>

  <Card title="Needs you" icon="triangle-exclamation" color="#F59E0B">
    `underpaid`, `overpaid`, `wrong_token`, `expired_paid_late`, `held_sanctioned`

    [What each means](/money/edge-cases).
  </Card>
</Columns>

## The fees strip

Above the table: what you received, what fees were taken, and what went to a referral partner — over the period shown. Sourced from actual on-chain distributions, not estimates.

Reconcile against this rather than multiplying your gross by 1%, since it reflects what really happened including any partial claims.

## Filtering and export

Filter by network, token, and status. CSV export includes transaction hashes and block heights so an accountant can verify every line independently.

<Tip>
  Filter to the "needs you" statuses once a week. It's usually empty, and when it isn't, it's a customer waiting on you.
</Tip>

## Arrivals without a matching order

Someone reuses an old address, or pays long after expiry, and money arrives that no open order accounts for.

The funds are safe — the address can only pay your pool. What's missing is knowing which customer they belong to.

<Warning>
  There is no dedicated view for these yet. They appear in this table without a matching order, so finding one means scanning for it. A dedicated **Unsettled deposits** surface is designed and coming. [Roadmap](/reference/roadmap).
</Warning>

## What this tab shows

<Note>
  Payments shows the **pool rails** — the current product. If you were on an older integration, a small number of legacy payments may not appear here. Everything created through the current checkout does.
</Note>

<Card title="Claim your balance" icon="hand-holding-dollar" href="/dashboard/pool" horizontal>
  Payments accumulate; the Pool tab is where you withdraw.
</Card>