Events

Every paid request leaves a trail. Proceeds emits an event at each step so when something breaks, you can see exactly where. Use Events to answer one question: where did this flow stop? Filter by All, Request, Success, or Error. Expand a row to inspect the response payload. Events are also available via GET /v1/events and webhooks.

​

Event types

A healthy paid request emits REQUEST → SUCCESS. An unpaid challenge emits REQUEST only.

​

Filters

All, Request, Success, Error.

​

How to read the stream

Start at the latest event and walk backwards:

1. Did REQUEST fire? If not, the URL never reached Proceeds — check DNS or the client’s URL.
2. Did SUCCESS fire? If not, either the client never paid, payment was rejected, or settlement/upstream failed.
3. If you see an ERROR event, open it for the underlying reason — see Forward upstream auth and Custom headers and query parameters when the failure is upstream.