Report
Every value is the gateway's own.
Payment intent, status, charge id, decline code, ACS vendor, challenge step and result — read from the last run. Nothing is approximated, and nothing is invented.
Runs on any checkout page you already open. Reversible in one deploy.
How it works
Read the intent
The client secret, publishable key and payment intent are read from the checkout itself.
Poll to settle
The intent is polled until it reaches its final state, and the HTTP code of each poll is kept.
Record the fields
Status, charge id, decline code, ACS URL and vendor, 3DS2 id, challenge step and result are persisted.
Show it live
The menu and popup repaint the moment storage changes, so a finished run appears without a refresh.
Poll HTTP, lock_timeout retries and ACS vendor are stored beside the outcome.
One source, no paraphrase
Every value in the panel is the gateway's own. The extension never writes a success message when the issuer returned a failure.
- Gateway status
- Gateway decline code
- Gateway charge id
State that survives a tab close
The last run and the trace are kept in storage, so the menu still shows the outcome after the checkout tab is gone.
- Persisted last result
- Rolling trace
- Live repaint
Questions about this one.
More on the full FAQ, or write to [email protected].
01Where does the data come from?
From the checkout's own responses and the polling of the intent. No value is computed locally.
02Does it survive a reload?
Yes. The last result and trace are stored, so the menu repaints them after the checkout closes.
03Can I copy the snapshot?
Yes. Copy snapshot puts the current state on the clipboard for a report or a ticket.
Report
Read the outcome instead of guessing it.
Run one checkout and the menu shows status, decline code, charge id and relay response, all from the gateway.
- Gateway values only
- Persisted state
- Copy snapshot