Recovery
A declined renewal gets one re-confirm, not a cancellation.
Renewal payments fail on the same challenge step as first payments. The extension re-confirms the intent once and reports the gateway's own code, so a billing hiccup does not become churn.
Runs on any checkout page you already open. Reversible in one deploy.
How it works
Keep the tab open
A renewal renders the same card fields and the same challenge step. The extension runs in that checkout, not after it.
Re-confirm once
A declined intent is confirmed one more time with the card already entered, without a page reload.
Report the code
The gateway's decline code appears in the menu, so a soft decline is distinguishable from a hard one.
Record the run
Intent, status, charge id, ACS vendor and relay response are kept in extension storage for comparison.
The retry runs while the challenge step is still open, and the outcome is recorded against the same intent.
One retry, no reload
Retrying inside the open checkout keeps the session alive. Nothing restarts, and the customer sees the same page.
- Re-confirm once per intent
- No page reload
- Same card fields
Gateway values stay gateway values
The extension reports the gateway's status and decline code verbatim. It does not invent a result or rewrite the amount.
- Status verbatim
- Decline code verbatim
- Charge id shown when settled
Questions about this one.
More on the full FAQ, or write to [email protected].
01Does it create a second payment intent?
No. It re-confirms the intent already on the checkout and records the attempt against it.
02How many retries are allowed?
One re-confirm by default. The Decline retry switch controls it.
03What happens if the re-confirm also declines?
The gateway's code is reported and stored, so the failure is documented instead of guessed.
Protect renewals
Recover the renewal before it turns into churn.
Turn on Decline retry and a failed renewal gets one re-confirm with the gateway's own code recorded.
- One re-confirm
- Code reported verbatim
- Run kept in storage