# Show who gets a coin's fees

> For trading terminals: the fee recipient of any token, verifiable on chain.


Trading terminals show who receives a token's creator fees. For a Payday coin that is an X account, or the coin's holders for a Cash Payback coin.

```bash
curl -H "X-API-Key: pd_YOUR_KEY" https://payday.direct/api/v1/fees/MINT_ADDRESS
```

```json
{
  "mint": "MINT_ADDRESS",
  "feedrop": true,
  "feeRecipient": { "type": "x_account", "handle": "examplehandle", "profile": "https://x.com/examplehandle",
                    "paidOn": "xmoney", "since": "2026-11-12T10:04:00.000Z", "how": "launched for this account" },
  "payouts": { "paidUsd": 1240.5, "openOrdersUsdc": 120, "lastPaidAt": "2026-11-15T18:22:41.000Z" },
  "onchain": { "feeSharingConfig": "CONFIG_ADDRESS", "shareholders": [{ "address": "PAYOUT_WALLET", "shareBps": 10000 }],
               "adminRevoked": true, "payoutWallet": "PAYOUT_WALLET", "verified": true },
  "page": "https://payday.direct/x/examplehandle"
}
```

- `feedrop: false` means the token is not a Payday coin. These answers come from the registry in memory, so ask about every token you list.
- `onchain.verified` is true when pump.fun pays 100% of the coin's creator fee to Payday's payout wallet. Read `feeSharingConfig` yourself to check it.
- A Cash Payback coin answers `feeRecipient.type: "holders"` with a link to its rounds.
- For a page of tokens, `POST /fees/batch` takes up to 100 mints and costs one request plus one per Payday coin in it.

> Note: The fee endpoints keep the field names they launched with (camelCase, `feedrop`), so integrations built on them never break.