WooPayments Fraud Review: Separate Rule Outcomes From Payment State

By Dave TanguayPublished Updated Editorial draft

Quick Answer

Read a WooPayments fraud-rule outcome separately from the payment and order state. A blocked attempt is not the same as an authorized, uncaptured payment. Record what the gateway actually reports and who owns the next decision before treating a status label as an instruction to capture, refund or fulfill an order.

Use current operating documentation

The WooCommerce fraud-protection article explains the vendor’s broader approach. Its current title and content have changed since this archive entry. A general strategy article does not establish the state of a specific transaction or guarantee protection from disputes.

Current WooPayments rule documentation states that a blocked payment is not charged and its order is set to Pending Payment. It also identifies rule outcomes on order and transaction details. Use those details to establish what happened rather than interpreting a customer’s generic error message as a complete diagnosis.

Keep authorization distinct from capture

The authorization and capture guide distinguishes a temporary reservation of funds from capture. By default, WooPayments performs them together. Manual capture is a separate setting, and the provider recommends leaving it disabled unless there is a specific, justified use case.

Do not turn on manual capture simply because a fraud article mentions review. Its availability, expiration, supported payment methods and operational responsibilities need their own review. This article changes no setting and makes no transaction decision.

Compare two different review records

The following orders are invented examples, not customer records or a gateway test:

Order A: blocked attempt
The order shows Pending Payment and the WooPayments rule result identifies a block. The reviewer verifies the gateway’s payment record instead of assuming money was captured. A refund is not inferred from the error message.
Order B: separate authorization
On a different hypothetical store with an already approved manual-capture workflow, the gateway reports an authorization that has not been captured. This is a different payment state from Order A. The responsible payment owner reviews its actual status, timing and the store’s approved process.
Decision record
For either case, keep the rule result, actual payment state, related order and observation time together. Record the authorized decision owner and any unresolved discrepancy.
Fulfillment boundary
Do not release an order because one screen looks complete while the payment review remains unresolved. Follow the store’s approved fulfillment and payment process after the relevant owner resolves the case.

Preserve evidence before changing the workflow

A mismatch between screens needs investigation, not a broad relaxation of fraud rules. Escalate an unexplained result to the payment provider through the store’s approved support process. Keep private payment and customer information out of public reports.

The rule guide also notes that the pending-order retention setting affects all Pending Payment orders. Do not treat that general setting as a narrowly targeted cleanup control for one blocked case.

The WooCommerce checkout guide covers the underlying block or classic checkout route. The Divi cart and checkout module archive covers a different compatibility question, and the cart review guide examines costs and the handoff into checkout.

Key Takeaways

  • Separate rule outcome, payment state and order state.
  • Distinguish a block from an authorization awaiting capture.
  • Keep the decision owner and unresolved evidence explicit.
  • Review workflow changes separately from an individual case.

Frequently Asked Questions

Does a blocked attempt mean money must be refunded?

Do not infer that. WooPayments documents its blocked rule outcome as not charging the payment method. Verify the actual gateway record for the case.

Should every store enable manual capture for fraud review?

No. The provider recommends leaving it disabled unless a specific, justified use case calls for it. Review the full current documentation and operational requirements separately.

Does the pending-order retention setting affect only blocked attempts?

No. WooPayments notes that it affects all Pending Payment orders. Review that wider scope before an authorized change.

Archives