Skip to main content
Once buyers start paying, Proceeds gives you four surfaces to manage what’s happening: transactions for payment state, events for the request lifecycle, webhooks for pushing both to your own server, and revenue for the balances that accumulate.

​
Transactions

Open Transactions. Each row is one payment attempt against one paywall.
  • Standard x402 and MPP typically land as Completed (or Failed) once the request finishes.
  • Circle Nanopayments go Pending → Completed while Gateway batches the authorization onchain. A failed batch settlement ends in Failed.
Filter by Pending, Completed, or Failed to triage. See Transactions for the full state meanings.

​
Events

Open Events for the same paywall. The live API emits three event types:
  • REQUEST — paywall hit without payment (402 path)
  • SUCCESS — successful payment and fulfillment
  • ERROR — settlement or upstream failure
A healthy paid request emits REQUEST → SUCCESS. When a transaction stops short of Completed, scan the matching event stream for the missing SUCCESS or the ERROR that records why.

​
Webhooks

Transactions and events are pull — you open the dashboard to inspect them. To react automatically, configure Webhooks: Proceeds sends a signed HTTP callback to your server on payment.succeeded, payment.failed, and other events. Verify the X-Webhook-Signature header before trusting a payload.

​
Revenue

Open Wallet to confirm payments are landing. Balances accrue per chain (and under Circle Nanopayments for Gateway settlement). From there, withdraw USDC or off-ramp to a US bank via ACH.

​
Next

Production checklist

Confirm settings before moving a service to mainnet.

Troubleshooting

Common failures and how to resolve them.