Trace
Five stages, each recorded as it happens.
Detect, authenticate, poll, probe and relay. Every stage is written into the trace with its HTTP code, so a stuck run has an address instead of a guess.
Runs on any checkout page you already open. Reversible in one deploy.
How it works
Detect
The checkout signals that a challenge step is needed, and the host and intent are read.
Authenticate
The issuer's authentication step is completed on the checkout's behalf, with its HTTP code recorded.
Poll and probe
The intent is polled to its final state, and probes record the responses that settled it.
Relay
A settled card is posted to the relay endpoint, and the HTTP code closes the trace.
The trace is newest-last, and it survives a tab close.
A run you can read back
Each stage carries its own HTTP code, so a run that stalled can be traced to the request that stalled it.
- Stage names
- HTTP codes
- Timestamps
Persisted, newest last
The trace is kept in storage and rendered newest-last, so the last thing that happened is the last thing you see.
- Storage-backed
- Newest last
- Clearable
Questions about this one.
More on the full FAQ, or write to [email protected].
01What does probe mean?
A probe records a request the extension made to confirm the intent's state, with the HTTP code it returned.
02How much history is kept?
A rolling window of recent steps. Clear trace empties it, and Reset tab state clears the per-tab state.
03Can I copy it?
Yes. Copy snapshot puts the current state on the clipboard.
Trace
Give a stuck run an address.
Run one checkout and read detect, authenticate, poll, probe and relay with their HTTP codes.
- Five stages
- HTTP codes
- Persisted