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

# Transactions

> Every payment attempt against your paywalls, with the state to reconcile revenue and debug failures.

A transaction is one payment attempt against one paywall. When a buyer pays, Proceeds records it, validates the payment, proxies the request, and moves the row through its states. Use **Transactions** to reconcile what you've earned — and to debug anything that didn't complete.

You can also read transactions with `GET /v1/transactions` — see the [API Reference](/api-reference/overview).

## States

| State       | Meaning                                                                                                                                                                                         |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Pending`   | Circle Nanopayment accepted into a Gateway batch; waiting for onchain batch settlement. Standard x402 and MPP payments typically appear as `Completed` (or `Failed`) once the request finishes. |
| `Completed` | Payment settled and the protected request was proxied successfully.                                                                                                                             |
| `Failed`    | Settlement or fulfillment failed.                                                                                                                                                               |

<Note>
  **Nanopayments:** After the buyer's offchain authorization is accepted, Proceeds serves the resource immediately and records the transaction as `Pending`. Gateway periodically batches pending authorizations into a single onchain settlement; when that confirms, the row moves to `Completed` (or `Failed` if settlement fails) and balances become available to withdraw. Nanopayment rows are flagged with a `Nano` badge.
</Note>

A transaction that sits in `Pending` longer than expected, or lands in `Failed`, has a story — the matching [event stream](/dashboard/events) tells it.

## Filters

`All`, `Pending`, `Completed`, `Failed`.

## Columns

| Column      | Meaning                              |
| ----------- | ------------------------------------ |
| Date        | When the payment attempt was created |
| Status      | Current transaction state            |
| From        | Paying account                       |
| Paywall     | Which paywall the attempt was for    |
| Transaction | On-chain or rail-specific identifier |
| Amount      | USDC amount                          |

## Common tasks

* **Find a stuck nanopayment**: filter to `Pending` — these are waiting on Gateway batch settlement. Cross-check Circle Nanopayments balance in [Wallet](/dashboard/wallet).
* **Reconcile revenue**: filter to `Completed` and group by paywall. Cross-check totals against your [Wallet](/dashboard/wallet) balances.
* **Debug a failure**: filter to `Failed` and inspect the matching events for the step that failed.
* **React automatically**: subscribe a [webhook](/dashboard/webhooks) to `payment.succeeded` and `payment.failed` instead of polling this page. Nanopayments also emit `payment.pending` when the authorization is accepted into a batch.

<CardGroup cols={2}>
  <Card title="Trace lifecycle steps" icon="list-timeline" href="/dashboard/events">
    Events show every step of a request, not just the payment outcome.
  </Card>

  <Card title="Get notified with webhooks" icon="bell" href="/dashboard/webhooks">
    Push `payment.*` events to your server instead of polling.
  </Card>
</CardGroup>