Architecture · Safe overview

Protection before payment, whenever technically possible.

Cheap local checks run first. Uncertain traffic gets a recoverable challenge. Clear abuse is blocked before the gateway whenever the available signals allow it.

01

Establish checkout flow

A short-lived, signed, cache-safe token shows the client came through the expected checkout flow.

02

Evaluate local signals

Velocity is evaluated across IP, email, session, combinations, trust context, and recent failure history.

03

Challenge uncertainty

The local check, Turnstile, or reCAPTCHA can recover suspicious requests without a hard block.

04

Make the decision

The request is allowed, challenged, or temporarily blocked with a stable reason code.

05

Learn from payment feedback

Actual gateway declines increase suspicion; form errors and broad outages are handled differently.

06

Explain and recover

Aggregated logs show what happened, masked identifiers protect privacy, and admins can unblock mistakes.

Version 1.0.0 · Available on WordPress.org

Put a control between checkout abuse and your payment gateway.

Install the complete Free edition from the official WordPress.org Plugin Directory. New installations begin safely in Observe Mode.