Suspicious Account

How to flag suspicious high-value orders from new accounts in WooCommerce

Flag high-value orders from very new accounts using non-PayPal payment

Highlights large orders from accounts created within the last 3 days that did not use PayPal, surfacing potentially fraudulent purchases for immediate review.

Review critical
The problem

Fraudsters frequently create new accounts and place large orders using stolen card details. PayPal provides buyer verification, so non-PayPal payments from brand-new accounts with high order values carry elevated risk and warrant manual review before dispatch.

The solution

OrderBadger can automatically flag high-value orders from very new accounts that did not use PayPal, routing them for urgent review.

Who this is for

Luxury retailers, electronics stores, and any business with high-value products that are attractive to fraudsters.

At a glance
Account age under 3 days Value threshold: order total over £1000 Excludes PayPal payments 2-hour SLA with Approve/Block buttons Badge: Suspicious Account (red, critical)
People also search for
WooCommerce fraud alert for large orders from brand-new accounts how to review high-value orders from new customers WooCommerce flag suspicious new account orders for manual review WooCommerce WooCommerce detect potentially fraudulent first orders over £1000 stop fraud on new account high-value card payments WooCommerce

How it works

Combines three conditions: account age under 3 days, order total over £1,000, and a non-PayPal payment method. When all conditions are true, the order gets a critical-severity badge with Approve/Block interaction buttons and a 2-hour SLA.

Verify the customer's identity before dispatch. Check the billing and shipping addresses match, look for signs of fraud (disposable email, mismatched details), and use the Approve or Block buttons to record your decision within the 2-hour SLA window.

Rule template

Plain English rule Customer account age is less than 3 days and order total is over £1000 and payment method is not paypal

Write this (or something similar) in the OrderBadger rule builder. The AI compiler turns it into executable logic automatically.

Make it yours

Adjust thresholds
  • Widen 'less than 3 days' to 'less than 7 days' to catch fraud attempts from slightly older accounts that are still relatively new.
  • Lower 'over £1000' to 'over £500' if your product range has a lower price point but fraud is still a concern at that level.
Add or remove conditions
  • Add 'and shipping address differs from billing address' to tighten the rule to the most suspicious pattern. …d order total is over £1000 and payment method is not paypal and shipping address differs from billing address
  • Replace 'payment method is not paypal' with 'payment method is not paypal and payment method is not apple_pay' to also exclude Apple Pay, which has strong device-level verification.

Badge preview

Default: Suspicious Account
Passed: Suspicious Account
Failed: Suspicious Account

This badge appears in the WooCommerce order view with action buttons. Your team can respond directly from the badge pill.

When this rule matches

New Account High Value Card Payment
Order total: £1500.00  |  Guest: no
Account is 1 day old, order total is £1,500, and payment method is stripe - all three conditions are met.
New Account Boundary Values
Order total: £1000.01  |  Guest: no
Account is 2 days old (under £3), order total is £1,000.01 (over £1000), and payment method is bacs - all conditions just met.

When this rule does not match

New Account High Value Paypal
Order total: £1500.00  |  Guest: no
Account is 1 day old and order total is £1,500, but payment method is PayPal - excluded by the 'not paypal' condition.
Established Account High Value
Order total: £2000.00  |  Guest: no
Order total is £2,000 and payment is stripe, but account is 30 days old - not a new account.
New Account Low Value Card
Order total: £150.00  |  Guest: no
Account is 1 day old and payment is stripe, but order total of £150 is below the £1,000 threshold.

Workflow

This rule includes workflow features that help your team act on flagged orders.

Inbox
Yes
Interaction
Approve / Block
SLA
2h (from created at)

Good to know

  • This is a review aid, not a fraud detection engine. It highlights orders that statistically carry more risk based on account age, value, and payment method.
  • PayPal is excluded because it provides buyer verification. If your PayPal setup does not include address verification, consider removing the PayPal exclusion.
  • Guest checkouts may have null account_age_days. Consider a separate rule for high-value guest orders.

Frequently asked questions

  • Why is PayPal excluded from this rule?
    PayPal provides its own layer of buyer verification and fraud protection. Orders paid via PayPal carry lower fraud risk than direct card payments from unknown accounts, so they are excluded to reduce false positives.
  • What happens if I don't act within the 2-hour SLA?
    The badge remains on the order but the SLA will show as breached. The order is not automatically blocked - it is up to your workflow to decide next steps. The short SLA ensures suspicious orders get timely attention.
  • Does this rule catch guest checkouts?
    No. Guest checkouts do not have a registered account, so account_age_days is null and cannot satisfy the 'less than 3 days' condition. Consider a separate rule for high-value guest orders.
  • Can I adjust the account age or order value thresholds?
    Yes. Edit the natural language rule text to change the 3-day account age limit, the £1,000 order threshold, or the payment method exclusion, then recompile.

Related rules

Try this rule in your store

OrderBadger is free on WordPress.org. Install it and create this rule in minutes - no code required.

Install OrderBadger Free