Checkout automation
Settles the checkout, reports what really happened.
Card fields are read from the checkout itself, the challenge step is completed, and every value shown here is the gateway's own status, decline code and charge id.
Payment intent—
Status—
Latest charge—
Live state
Everything below comes from the worker's last run.
Badgeidle
Client secret—
Publishable key—
Decline code—
ACS URL—
ACS vendor—
3DS2 id—
Challenge step—
Challenge result—
Reason—
Relay POST—
Poll HTTP—
lock_timeout retries0
Switches
Each toggle writes straight to extension storage.
Auto-runFire as soon as a checkout needs 3D Secure.
3DS bypassComplete the issuer's authentication step.
Blacklist bypassStrip payment method types and configuration details.
Fraud bypassDrop risk checks and card three_d_secure options.
Decline retryRe-confirm once when the gateway says declined.
Bypass closedDeny path only — checkout shows the gateway's own failure message.
Force ACS failDrive a failing result so the gateway rejects the card.
LoggingKeep a rolling trace of every step.
How it runs
Five stages, each reported as it happens.
- Detect — the checkout signals that a challenge step is needed.
- Authenticate — the issuer's authentication step is completed on the checkout's behalf.
- Confirm — the authentication result is submitted and the checkout advances.
- Settle — the intent is polled until it reaches its final state.
- Report — the gateway's real status, decline code and charge id are shown, and a settled card is posted to the relay endpoint.
Outcomes are the gateway's own. When the issuer demands a real approval the extension reports the exact message instead of inventing a success.
Trace
Rolling history from the worker, newest at the bottom.
no steps recorded yet