Skip to main content
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.

​
States

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.
A transaction that sits in Pending longer than expected, or lands in Failed, has a story — the matching event stream tells it.

​
Filters

All, Pending, Completed, Failed.

​
Columns

​
Common tasks

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

Trace lifecycle steps

Events show every step of a request, not just the payment outcome.

Get notified with webhooks

Push payment.* events to your server instead of polling.