Load the extension.

One unpacked folder, the switches you choose and a checkout you already open. This guide takes you from a fresh load to a settled run with a relay POST.

Download samurai-bypasser-3.2.0.zip Security model

Load the extension

Download the zip, extract it, then open Chrome's extension page, enable developer mode and load the folder. The extension attaches to any checkout that renders card fields.

chrome://extensions
  → Developer mode
  → Load unpacked
  → samurai-bypasser-3.2.0

Set the switches

Open the menu and choose what runs. Auto-run fires without a click; 3DS, blacklist and fraud bypass can be judged separately; logging keeps the trace.

auto-run        on
3ds bypass      on
blacklist       on
fraud           on
decline retry   on
logging         on

Run one checkout

Open a checkout page and fill the card fields. When a challenge step appears the extension completes it inline and polls the intent until it settles.

detect      → checkout host read
authenticate → http 200
poll        → succeeded
probe       → pi-view 200
relay       → sent (200)

Verify the outcome

Read the menu. Status, decline code, charge id, ACS vendor and relay response are the gateway's own values, stored beside the last run.

status      succeeded
charge      ch_3UZW0X…R6l6L
decline     —
relay       200

Questions

01Do I need to change my checkout code?

No. The extension runs inside the checkout page and reads the fields it renders. Nothing in your application has to change.

02How do I update a build?

Replace the folder and press reload on the extension card. Switches and stored state persist across the reload, so the next checkout follows the same settings.

03What should I do if the extension is not loading?

Check chrome://extensions for errors on the card, confirm developer mode is on and the folder is the unpacked build, then reload the checkout tab so the content scripts attach.

04Can I scope it to one checkout?

Yes. Auto-run fires on any checkout that needs a challenge step, and the switches can be turned off so only the bypasses you want act on the run.

Next reads

Webhooks and replay →Retry scheduling →Changelog →

Done reading

Run one checkout and read the trace end to end.

The trace records detect, authenticate, poll, probe and relay with their HTTP codes. If the last line is a relay POST, the run settled.

Download the extension Read the docs

Five stages, all recorded
Gateway values only
Reversible in one deploy