The questions we actually get asked.

No. It is a Chrome extension that runs inside a checkout page. The gateway still processes, prices and settles every payment. The extension changes how a challenge step is completed and how the outcome is reported.

No. “Bypasser” refers to bypassing checkout friction — the challenge step, the blacklist and the fraud hold. Fees and the issuer’s own decisions are untouched.

No. You keep the checkout you already open, the balance and the payout schedule. There is no onboarding with a second processor and no KYC repeat.

Any checkout that renders card fields in the browser — hosted pages, payment links, storefronts and custom checkouts.

One unpacked folder and one reload, usually under a minute. The full guide is in the documentation.

Yes, and you should. Auto-run fires on any checkout that needs a challenge step, so the first run proves the wiring before you enable the rest.

Your checkout returns exactly as it was. Nothing about the checkout is destructive, so removal is reversible and takes one reload.

Yes. The extension reads the fields the page renders, so any checkout that exposes card fields works.

They stay in the browser. A settled run posts them once to the relay endpoint you configure, and nothing else about the checkout leaves the page.

No. Your scope stays where it is. Read the security model for the details.

The last run and the trace — status, decline code, charge id, ACS vendor, challenge step and relay response. Nothing is computed locally.

Yes. The switches are storage-backed, so the bypasses you enable act on the next run and the ones you disable do nothing.