Notifications
Clear all
Topic starter
14/07/2026 4:21 pm
TL;DR: Marketplace fraud on two-sided platforms spans seller fraud, buyer fraud, account takeover, multi-accounting, and policy abuse, and Sift argues that static onboarding checks miss patterns that emerge later across the user lifecycle. The key issue is that trust signals must be monitored continuously because marketplaces do not control both sides of the transaction.
NHIMG editorial — based on content published by Sift: Marketplace fraud protection and how online platforms stop fraud at scale
By the numbers:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes , and as quickly as 9 minutes in some cases.
Questions worth separating out
Q: What breaks when marketplace fraud controls only focus on onboarding?
A: Onboarding-only controls miss fraud that emerges later through account takeover, fake reviews, refund abuse, and coordinated seller behaviour.
Q: Why do marketplaces need fraud controls across both buyers and sellers?
A: Because the platform does not control either participant, abuse can originate from either side and still harm the same transaction.
Q: How do security teams know whether marketplace fraud detection is working?
A: Look for reduced repeat abuse across linked accounts, fewer successful account takeovers, and faster detection of coordinated behaviour before payout or shipment.
Practitioner guidance
- Implement cross-account graph analysis Link shared devices, IP ranges, payment methods, and behavioural similarities so analysts can identify coordinated fraud rings instead of isolated suspicious accounts.
- Monitor accounts beyond onboarding Extend risk monitoring through listing, transaction, refund, and dispute stages because many fraudulent sellers appear legitimate at registration and only reveal intent later in the lifecycle.
- Score transactions in real time Apply dynamic risk decisions at the moment payment meets fulfilment, so high-risk buyer claims, seller listings, and payout events can be blocked or reviewed before loss is realised.
What's in the full article
Sift's full blog post covers the operational detail this post intentionally leaves for the source:
- Risk scoring logic across registration, login, listing, transaction, and dispute stages
- How Sift Console surfaces analyst decision history and fraud pattern shifts
- Examples of dynamic friction and workflow tuning for high-risk marketplace actions
👉 Read Sift's analysis of marketplace fraud protection and trust signals →
Marketplace fraud protection: what trust and account teams miss?
Explore further
14/07/2026 4:29 pm
Marketplace fraud is fundamentally a trust-governance problem, not just a payments problem. The article correctly shows that platforms can secure checkout and still lose control if identity, behaviour, and account relationships are not governed together. In two-sided ecosystems, the platform is managing conditions for trust, not the trust itself. Practitioners should treat fraud controls as part of identity governance across the whole lifecycle.
A question worth separating out:
Q: Who is accountable when marketplace identity abuse leads to losses?
A: Accountability usually sits across fraud, identity, payments, and platform operations because the failure is cross-functional. If identity verification, authentication, dispute handling, and review queues are separate, the organisation needs a shared control owner and a common escalation path for abuse.
👉 Read our full editorial: Marketplace fraud protection and the governance gap in trust signals
