Guides
Checkout recovery, explained properly.
No growth-hacking listicles. These are the mechanics behind challenge steps, decline codes and the checkout link, written for the person who owns the checkout.
A decline code is the whole story
A decline arrives with a code, and the code is the issuer's decision rather than a verdict on the customer. Reading it verbatim is the difference between reporting and guessing.
Read the guide →Most 3DS failures are not authentication failures
The challenge usually succeeds. What fails is the page around it — the redirect, the remount, the cart that resets.
Read the guide →One re-confirm, then the truth
A declined intent deserves exactly one second attempt. Beyond that, the gateway's own code is the answer, not another attempt.
Read the guide →If you want the load rather than the theory, the documentation takes you from a fresh unpacked folder to a settled run with a relay POST.
Read the docsRead less, load more
See the challenge step complete on a real checkout.
The extension behaves the same on any checkout that renders card fields, including the trace and the relay POST.
- Free to load
- One unpacked folder
- Reversible in one reload