Foundation · 2 min
What you need to know
What signals can indicate ecommerce fraud?
Signals may include unusual order patterns, rapid repeated failures, account changes or provider risk assessments. Use several relevant signals with context. No single address, device or order-size difference proves fraud.
Does billing/shipping mismatch indicate fraud?
No. Gifts, work addresses and moving home can explain a difference. Review the overall transaction and provider checks rather than automatically blocking every mismatch.
Should IP location be used in fraud detection?
IP location can provide context but can be inaccurate because of mobile networks, travel or privacy tools. It should not be the sole basis for rejection. Limit collection and retention to the lawful needs of the fraud process.
Can unusually large orders indicate fraud?
A large order can justify a closer look when unusual for that store, but it may be a genuine business or gift purchase. Check whether other risk signals support the concern and use the same respectful review process.
Should multiple failed payments trigger review?
Repeated failures may signal automated card testing, a technical issue or a customer struggling to pay. Review the pattern and provider controls. Apply proportionate protections without teaching customers to keep retrying an unresolved payment.
Foundation · 2 min
Frequently asked questions
How do merchants balance fraud prevention and false declines?
Compare fraud losses, review outcomes and known legitimate declines when changing rules. A stricter rule can reduce losses while also rejecting good customers. Test changes carefully and give legitimate customers a safe recovery route.
Why are legitimate customers being blocked?
A broad rule, unsupported method, authentication problem or issuer decision may block a real buyer. Review actual outcomes and identify which system made the decision. Do not switch off all fraud controls because one customer was declined.