Overview
The switches decide what the checkout does.
Auto-run, 3DS bypass, blacklist bypass, fraud bypass, decline retry, deny path, forced ACS failure and logging. Each toggle writes straight to extension storage, so the behaviour changes on the next checkout.
Runs on any checkout page you already open. Reversible in one deploy.
How it works
Turn on auto-run
The extension fires as soon as a checkout needs a challenge step, without any click.
Choose the bypasses
3DS, blacklist and fraud bypass can be enabled separately, so each one can be judged on its own run.
Set the fallback
Bypass closed uses the deny path only, and Force ACS fail drives a failing authentication result for testing.
Keep the trace
Logging keeps a rolling trace of every stage, so a run can be read back later.
A switch applies to the next checkout the extension runs on.
One switch, one behaviour
Every toggle maps to a single behaviour and writes straight to storage. Nothing is hidden behind a combination of settings.
- Auto-run
- 3DS, blacklist and fraud bypass
- Decline retry and deny path
- Forced ACS failure and logging
Reversible immediately
Turning a switch off restores the checkout's own behaviour on the next run. There is nothing to uninstall and nothing to redeploy.
- No redeploy
- Applies to the next run
- Storage-backed
Questions about this one.
More on the full FAQ, or write to [email protected].
01Does auto-run need a click?
No. It fires as soon as a checkout needs a challenge step, which is what makes the run unattended.
02What is bypass closed?
A deny-only path: the checkout shows the gateway's own failure message instead of settling it.
03Can the switches conflict?
No. Each maps to one behaviour, and the trace records which one acted on the run.
Switches
Pick the behaviour, then let the checkout run.
Every toggle writes straight to storage, so the next checkout follows the switches you set.
- Auto-run
- 3DS, blacklist, fraud
- Reversible immediately