Fraud detection and prevention for online stores
An order-risk check connects payment and fulfilment warnings to the underlying records, with a clear decision owner when the evidence remains uncertain.
- Published
- Last updated
Fraud detection checks an online store’s orders and payments for signs of unauthorised activity, then tests those signs against transaction records. A warning starts a review. It doesn’t establish that a customer committed fraud.
When an order looks suspicious, hold its release while the payments owner checks the actual transaction. Confirm what happened before asking the customer to pay again.
Start with the order and payment evidence
Find the order reference and the payment record that belongs to it. You need authorised access to the store’s order history and the merchant’s payment account. Assign a payments owner to resolve uncertain results and a fulfilment owner to control dispatch.
Keep these records together for the review:
- The order total, currency, items and any changes after checkout.
- The provider’s transaction reference, payment status and separate capture or refund records.
- Available authentication results and the rule or risk signal that prompted review.
- The fulfilment hold, delivery details and any dispatch or collection record.
An address mismatch, an unusual basket or repeated attempts can justify a check. Each still needs context. A customer sending a gift can have different billing and delivery addresses.
Payment fraud includes unauthorised use of a payment method and false claims that an order has been paid. A processing error or duplicate checkout attempt can produce similar symptoms. Record the observation as “two payment attempts” until the records establish more.
Check suspicious payments before releasing goods
Check the merchant-controlled payment record before treating a screenshot or message as proof. Follow this sequence for the order under review.
- Open the provider account or bank app through your usual trusted route. Match the transaction reference to the order and check the amount and currency.
- Read the exact payment state. An authorisation reserves funds for capture. A payment still processing needs its confirmed outcome before the team treats it as received.
- Compare repeated attempts individually. Check whether each attempt failed, remains pending or completed before deciding whether there was a duplicate charge.
- If the payer disputes authorisation, route the case to the payments owner. Preserve the provider reference and follow the provider’s case instructions before changing the order.
- Release the hold only when the payments owner records a decision and the fulfilment owner sees that decision against the correct order.
Stripe’s payment-status documentation distinguishes processing, uncaptured and succeeded payments. Its succeeded state confirms completion of that payment flow. Later refunds or disputes have separate records, so a successful payment doesn’t guarantee that it can never be challenged.
A bank transfer screenshot, PayID payment screenshot or PayPal screenshot is a customer-supplied image. It cannot confirm receipt in your account. Westpac’s payment warnings advise against relying on receipts or screenshots sent by a buyer. PayPal instructs sellers to log in and check the payment before shipping.
In a fictional example, order F-204 totals $240. The customer sends a payment screenshot, but the merchant’s account has no matching receipt. Keep the order on hold and ask the payments owner to investigate. Don’t label the image fake simply because the payment is absent, and don’t request another transfer while the first remains unresolved.
Incorrect decision: dispatch F-204 because the image says “paid”. Correct decision: record that payment remains unconfirmed and wait for the authorised release decision.
Use prevention controls at the right step
Fraud prevention assigns a control to the point where someone can act on it. Keep payment controls separate from staff access controls and dispatch approval.
Match each control to its decision
| Control | Evidence used | Decision and owner |
|---|---|---|
| Gateway risk rules | Payment attributes and provider risk signals | The payments administrator configures supported allow, block or review rules. |
| Payment monitoring | Attempts and changes in transaction status | The payments team investigates patterns and resolves exceptions. |
| Model-assisted review | A provider’s risk output plus the order records | A reviewer weighs the signal before an order decision. |
| Fulfilment hold | Recorded payment outcome and release approval | The fulfilment team releases only the authorised order. |
Stripe documents gateway rules that request 3D Secure authentication or allow, block and review payments. Custom rules depend on the Radar plan. A merchant-configured rule is separate from the provider’s model: changing a threshold doesn’t reveal how its private model works. A review flag also doesn’t itself stop dispatch unless your order process enforces that hold.
For staff access, use individual accounts with only the permissions each role needs. Apply multi-factor authentication to payment administration. The PCI Security Standards Council’s authentication guidance requires all authentication factors to succeed before access is granted under PCI DSS v4.x. Staff authentication protects access. Cardholder authentication checks a different part of the transaction.
Sanctions screening is another separate decision. It compares parties against designated lists and requires a compliance process. It doesn’t measure whether an order looks fraudulent. Australia’s Department of Foreign Affairs and Trade directs people who identify a Consolidated List match to seek legal advice before proceeding with relevant dealings. Escalate a possible match for assessment.
Text redaction only hides text and performs neither sanctions screening nor fraud scoring.
Keep customer support factual
Staff and shopping assistants must describe the recorded order state without making an accusation. Limit the reply to what the customer needs to know and send consequential decisions to the payments owner.
For fictional order F-204, the reply can state the hold: “Your order is on hold while our payments team checks the payment. Please don’t submit another payment while they investigate. We’ll update you after the review.”
Use that reply only when those facts match the order record. If the provider confirms receipt but the order remains under review, describe the order hold without claiming the payment failed. Give the customer a route to the support team, which can contact the payments owner.
Keep internal risk scores and sensitive transaction evidence out of chat. An assistant can communicate a confirmed outcome. The payments owner decides whether to release, cancel or refund the order. The fulfilment team acts on that decision.
Review the outcome without blocking genuine customers
Close the case with the provider’s confirmed result and the retailer’s action. Record the reason for that action, who approved it and any unresolved issue. Keep a link to the transaction record instead of copying unnecessary payment data into support notes.
A false positive is a genuine transaction flagged as suspicious. Review cleared orders as well as confirmed fraud cases before tightening a rule. Compare the warning that triggered review with the evidence that resolved it. A blanket block based on one unusual field can also reject genuine customers.
Before changing a rule, name the failure it is meant to address and decide who will monitor its effect. Check whether the change creates more unresolved holds or delays legitimate orders. Retain a route to reverse a poorly performing rule.
When the issue is misuse during a return or a card dispute already opened, use the relevant process for that case. For an order awaiting dispatch, the final check stays specific: the payment outcome and authorised release decision must match the goods being sent.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.