Control
A declined run is retried, not refunded.
A failed attempt leaves the intent open. The extension re-confirms it once and keeps the gateway's own status, so the failure is documented next to the payment it belongs to.
Runs on any checkout page you already open. Reversible in one deploy.
How it works
Open the run
The menu shows the intent the attempt belongs to, so the amount and currency are already correct.
Read the code
The decline code comes from the gateway, not from a local guess, and is shown verbatim.
Re-confirm once
Decline retry confirms the intent one more time while the checkout is still open.
Keep the trace
Detect, authenticate, poll, probe and relay stay in storage for comparison against later runs.
The attempt stays visible after the tab closes, so the decline can be compared later.
The attempt stays visible
State persists across a tab close, so the decline is readable after the checkout is gone and can be compared with the next attempt.
- State kept in storage
- Readable after close
- Reset tab state clears it
A decline is the normal case
Most failed runs are declines, not refunds. The menu reports the gateway's status and code instead of inventing a settled result.
- Status verbatim
- Code verbatim
- Charge id only when settled
Questions about this one.
More on the full FAQ, or write to [email protected].
01How long does a declined run stay visible?
Until Clear trace or Reset tab state empties it. The state persists across a tab close by design.
02Can I see a run made before loading the extension?
No. The extension records the runs it observes, starting from the checkout it was loaded into.
03Does a decline affect the acceptance rate?
The menu reports each run separately; nothing is aggregated into a rate.
Operations
Take the decline out of the support queue.
Read the gateway's own code, re-confirm once, and leave the run in storage so the failure is documented.
- Code verbatim
- One re-confirm
- Run kept in storage