> ## 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 > Inspect payment attempts and payment state. The **Transactions** page lists every payment attempt against every paywall in your account. Each row is one transaction; transactions move through state as Proceeds validates the payment and proxies the request. ## States | State | Meaning | | ----------- | ------------------------------------------------------------------------- | | `Pending` | Payment attempt exists but is not yet validated and proxied. | | `Completed` | Payment was validated and the protected request was proxied successfully. | | `Failed` | Payment or fulfillment failed. | A healthy paid request passes through `Pending → Completed`. ## 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 payment**: filter to `Pending` and check the matching event stream in [Events](/dashboard/events). * **Reconcile revenue**: filter to `Completed` and group by paywall. * **Debug a failure**: filter to `Failed` and inspect the matching events for the step that failed. Events show every step of a request, not just the payment outcome. Push `payment.*` events to your server instead of polling.