Founder deal: 75% off the lifetime licence. Unlimited sites, one payment, every update.See the founder plan
NMIWP
Download freeGet Pro
Home / Features / Fraud rules

Stop the orders you already know are trouble.

Address and security code results come back on every transaction. Acting on them by rule, rather than reading them afterwards, is the cheapest fraud control available to a store on its own merchant account.

See the roadmap See it in the demo

Planned. Pro and above when it ships. Some checks are available today from your gateway.

What is planned

Rules applied at the moment of the transaction, before the order is accepted.

AVS and CVV rules

Decline, or accept and flag for review, when the address or security code does not match. Configurable per result code.

Velocity limits

Cap attempts per email address, IP or card fingerprint over a time window, which stops card testing before it costs you in fees.

BIN and country blocking

Refuse issuing countries you do not sell to, or specific card ranges that have caused you losses.

Review queue instead of decline

Hold a suspicious order for a human rather than losing a legitimate sale to a strict rule.

How it works

Checks run between the gateway response and the order being accepted.

  • The gateway returns a resultEvery authorization comes back with an AVS code and a CVV result, whether or not anyone looks at them.
  • Rules are evaluatedYour rules decide whether that combination is acceptable, needs review, or should be reversed.
  • The order is accepted, held or voidedA declined rule voids the authorization so the customer is not left with a pending charge on a sale you refused.
Order #10904, screeningHeld for review
AVSN, no match
CVVM, match
Attempts from IP4 in 10 min
Issuing countryOutside sales region
Rule triggeredVelocity, AVS
Approve and captureVoid authorization

Worth knowing

Strict rules cost you real sales. Loose rules cost you chargebacks.

Ask support

Start by flagging, not declining

Run new rules in review mode for a few weeks and see what they would have caught. A rule that declines every AVS mismatch will also decline plenty of honest buyers who typed their old address.

Does the gateway not do this already?
Your gateway has its own fraud settings and you should use them. These rules act inside WooCommerce, where the cart, customer history and order data are also visible.
Will this stop chargebacks?
It reduces obvious fraud. It does not stop a cardholder disputing a legitimate purchase, which is a different problem answered by delivery evidence.
Can I apply rules only to large orders?
Yes, that is the intended use. Thresholds by amount, product or customer history keep the friction where the risk is.
When will this ship?
On the roadmap after ACH return handling. Priority is driven by support requests.

Related

Other parts of the plugin people read next.

3D Secure 2

Liability shift alongside screening rules.

Security

How card data is handled end to end.

All features

What ships today versus what is planned.

Start free, upgrade when the store needs it.

Install from WordPress.org, connect your gateway, take a real order today.

Download from WordPress.org See pricing