> ## 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.

# Claiming your money

> How payouts work, what they cost, and how to choose a cadence.

Payments accumulate in your pool. Claiming moves your share to your payout address.

## How

<Steps>
  <Step title="Open Pool" icon="cube">
    Your balance per chain and per token is shown.
  </Step>

  <Step title="Press Claim" icon="hand-holding-dollar">
    A live network-fee estimate appears before you commit.
  </Step>

  <Step title="Sign" icon="signature">
    One signature. The balance splits and your share moves to your payout address.
  </Step>
</Steps>

No approval, no review, no minimum, no schedule.

<Note>
  Collapsing this into one button and one signature is coming; today it may take two steps. Either way it is your transaction and nobody can gate it. [Roadmap](/reference/roadmap).
</Note>

## What it costs

The network fee for one transaction, in that chain's native token.

<Warning>
  You need native gas on each chain you claim from — ETH, POL, BNB, AVAX, or TRX. A chain where you hold none is a chain where your money waits until you top up.
</Warning>

## Choosing a cadence

The fee is per **claim**, not per payment. So batching spreads one fee across many orders.

| Orders per claim | Fee per order |
| ---------------- | ------------- |
| 1                | the whole fee |
| 10               | one tenth     |
| 100              | one hundredth |

<Columns cols={2}>
  <Card title="On cheap chains" icon="feather">
    Base, Arbitrum, Optimism, Polygon, Avalanche. Claim whenever you like — the fee is negligible either way.
  </Card>

  <Card title="On Ethereum and TRON" icon="weight-hanging">
    Batching matters. Claiming a single small order can cost a meaningful fraction of it.
  </Card>
</Columns>

<Tip>
  A reasonable default: claim weekly on cheap chains, and on expensive chains claim when the balance is large enough that the fee is a rounding error.
</Tip>

## Nobody can stop you

`distribute()` — the function that releases funds — is callable by **anyone**. Not gated on us, not gated on an account review, not gated on a minimum.

<Info>
  This is deliberate and it's the core of the non-custodial claim. A processor that *could* withhold your funds is a custodian, with the counterparty risk that implies. We built ourselves unable to.
</Info>

A practical consequence: even if we vanished entirely, your funds remain claimable by anyone willing to send the transaction — including you, directly against the contract.

## The dormant-pool backstop

If a pool sits untouched for a month with a balance, we run a keeper that triggers distribution.

It never claims your share for you — your money goes to your address, as always. It exists so small balances don't sit stranded because someone forgot.

## Reconciliation

Each claim produces a `payment_claimed` webhook and a row in the dashboard with the transaction hash, so you can tie payouts to on-chain records for your accountant.

<Card title="How the fee is calculated" icon="percent" href="/concepts/fees" horizontal>
  1% flat, and the two network costs that are yours.
</Card>