Marketplace Fraud

Marketplace Fraud: Why Two-Sided Payment Platforms Face More Than Buyer Fraud A marketplace can correctly authenticate the buyer, correctly authorize the payment, and still lose money. That is what makes marketplace fraud structurally different from ordinary merchant fraud. In a conventional ecommerce transaction, the business largely asks whether it should trust the customer and the payment. A marketplace has more questions: Should we trust the buyer? Should we trust the seller? Should we trust the account controlling the seller? Did the transaction represent genuine economic activity? Was the promised product or service actually delivered? Should the seller's balance become withdrawable? Is the payout still going to the legitimate recipient? Fraud can enter at any of those points. That is why marketplace fraud is not simply fraudulent checkout activity occurring on a platform. It is a participant-trust and money-flow problem. The useful model is: Buyer → payment → platform → seller balance → payout with seller identity, accounts, fulfillment, refunds, disputes, and incentives surrounding that flow. The risk program therefore needs to evaluate the parties and the movement of value separately. The editorial brief makes this the article’s central thesis: marketplace fraud should be analyzed across buyer, seller, transaction, fulfillment, balance, and payout rather than being reduced to fraudulent buyer payments. What is marketplace fraud?

Marketplace fraud is an umbrella term for fraudulent or abusive activity involving the participants, accounts, transactions, fulfillment processes, balances, incentives, or payouts of a multi-party marketplace. It is not one attack mechanism. Depending on the event, the actor might be: * a fraudulent buyer; * a fraudulent seller; * an external attacker controlling a buyer account; * an external attacker controlling a seller account; * multiple parties acting together; * a legitimate participant abusing a marketplace process. The targeted value can also differ. An attacker may seek: * merchant goods; * buyer funds; * seller proceeds; * marketplace incentives; * refunds; * account balances; * payout funds. This is precisely why the cluster assigns marketplace fraud its own territory rather than treating it as ecommerce card fraud with an additional participant. Marketplace fraud starts with the actors The clearest first question is not: “Was this transaction fraudulent?” It is: “Which participant—or account representing a participant—created the risk?” That produces four useful starting categories. Buyer-side fraud The suspicious or fraudulent activity originates with the buyer side of the marketplace. Examples can overlap with: * stolen-card fraud; * buyer account takeover; * refund abuse; * cardholder disputes. These mechanisms already exist outside marketplaces. What changes is the platform context around them. A marketplace may need to determine whether: the buyer was fraudulent or:

the seller failed to fulfill correctly before interpreting the resulting refund or dispute. That ambiguity matters. Seller-side fraud The risk originates with the seller or seller account. Potential problems include: * fabricated or misrepresented seller identity; * seller accounts created for fraudulent activity; * non-fulfillment or materially deceptive fulfillment; * misuse of seller privileges; * payout-related fraud. A payment can be perfectly legitimate from the buyer's perspective and still generate marketplace fraud loss if the seller side is fraudulent. That is the article's primary asymmetry. Account compromise Neither the buyer nor seller may originally be fraudulent. Instead, a legitimate marketplace account may be taken over. For a buyer account, an attacker might gain access to: * stored payment credentials; * balances; * profile information. For a seller account, compromise may be more dangerous because the account can control: * listings; * seller balances; * fulfillment information; * payout details. The dedicated Account Takeover Fraud article should own the compromise mechanics. This article owns what account takeover means inside the marketplace money flow. Collusion Sometimes the fraud problem is not one bad participant. It is the relationship between multiple participants. Buyer and seller accounts can potentially coordinate activity to exploit marketplace processes, incentives, transaction flows, or other platform mechanisms. The important classification is: Single-party fraud

One participant acts against another participant or the platform. versus: Collusion Two or more supposedly independent parties coordinate activity. Do not infer collusion merely because two accounts are linked. Households, businesses, shared networks, repeat commercial relationships, and legitimate buyer-seller relationships can all create connections. Evidence needs context. The Marketplace Fraud Actor Map The article's practical framework starts with three surfaces. Surface Actors Typical object at risk Important adjacent fraud Buyer side Buyer or compromised buyer account Payment, goods, refund Stolen card, ATO, refund/friendly fraud Seller side Seller or compromised seller account Buyer funds, fulfillment, seller balance, payout Synthetic identity, ATO Platform interaction One or multiple participants Marketplace incentives, transaction integrity, balances Promo abuse, collusion Then map those actors onto the money flow: Buyer payment → Platform → Seller balance → Payout Fraud analysis becomes much clearer when every incident is assigned both: an actor and: a point in the money flow. Stage 1: Buyer payment The first marketplace fraud surface looks most like conventional ecommerce fraud. A buyer submits payment. Potential risk mechanisms can include: * unauthorized card use; * compromised buyer account; * suspicious automated payment behavior; * other unauthorized payment activity. The marketplace still needs the standard distinction between: risk signal and: confirmed fraud.

An unusual device, foreign-issued card, different delivery address, or failed authentication can increase risk without proving fraudulent intent. The cluster explicitly requires suspicious activity to remain separate from confirmed fraud. But buyer-payment controls solve only this first surface. A marketplace that stops here is protecting the entrance to the money flow while leaving the rest of the system comparatively unexamined. Stage 2: Who is the seller? Seller identity is not merely an onboarding administration issue. It is part of payment risk whenever the platform will eventually allow that seller to obtain economic value. The platform may need to understand, subject to its business model and applicable law: * who the seller claims to be; * whether the seller represents an individual or business; * what identity or business information was validated; * which account controls the seller; * what payment account will receive funds; * whether material details later change. Current U.S. marketplace law illustrates this distinction. For covered marketplaces and qualifying high-volume third-party sellers, the INFORM Consumers Act requires collection and verification of seller information including bank-account, tax, and contact information. The FTC states that verification methods must allow the marketplace to reliably determine that specified information and documents are valid, correspond to the seller or representative, and are not misappropriated or falsified.

The EU Digital Services Act provides another jurisdiction-specific example. Article 30 requires covered online platforms that allow consumers to conclude distance contracts with traders to obtain specified trader information, including identity and payment-account details, and to make best efforts to assess whether the information is reliable and complete. The provision has specific scope rules and exceptions, so it should not be presented as a universal marketplace KYC rule. These laws should not be converted into generic fraud-prevention prescriptions. They do demonstrate an important structural point: The seller is part of the marketplace trust model. Fake seller does not mean “seller we do not like” Use the term carefully. A seller account can be unusual without being fraudulent. New sellers may have: * little transaction history; * limited platform reputation; * new payment accounts; * new devices; * unfamiliar business models. Those are conditions requiring appropriate risk evaluation. They do not prove fraud. Likewise, a seller identity that requires additional verification is not automatically a fraudulent seller. The platform should distinguish: new seller unverified seller seller with inconsistent information suspicious seller and: confirmed fraudulent seller. Stage 3: Transaction integrity A marketplace transaction can have a legitimate buyer and a legitimate seller while still creating a risk question about the transaction itself.

The platform may need to determine whether the transaction resembles genuine marketplace commerce. Useful questions can include: Does the transaction fit the seller's normal business? Does order value change abruptly? Is purchasing behavior unusual for the buyer? Are supposedly independent accounts repeatedly interacting in an unusual way? Does fulfillment evidence make sense? These are diagnostic questions. They are not universal fraud rules. The brief explicitly requires behavioral signals to be compared against an appropriate customer or cohort baseline rather than treated as proof. Stage 4: Fulfillment Checkout success is not the end of marketplace fraud risk because money and merchant obligations continue after payment. Suppose the buyer's payment is legitimate. The seller may still: * fail to deliver; * materially misrepresent the product or service; * provide fulfillment inconsistent with the marketplace transaction. But the platform must preserve a crucial distinction: Bad fulfillment is not automatically fraud. Shipping mistakes happen. Service quality disputes happen. Customers misunderstand listings. Products arrive late. Commercial disagreements are not automatically fraudulent activity. That gives marketplaces an important classification problem: Fraud Intentional deceptive or unauthorized activity designed to obtain value. Commercial dispute A legitimate transaction followed by disagreement over performance, quality, delivery, or terms. Operational failure

The marketplace or seller failed to execute correctly without evidence of fraudulent intent. The broader cluster specifically warns against turning refunds, chargebacks, or customer complaints into fraud labels without context. Stage 5: Seller balance The balance stage makes marketplace economics structurally different. Once the buyer pays, the platform may attribute some amount to the seller before final payout. That creates a new object of value: the seller balance. The platform now needs to know more than whether the incoming payment was legitimate. It may also need to know: * whether the seller should have access to those funds; * whether disputes or refunds remain possible; * whether fulfillment has occurred; * whether the seller account remains controlled by the legitimate seller; * whether other risk events emerged after payment. This stage can create a timing problem. Payment certainty and payout certainty are different A successful buyer payment means: the pay-in completed. It does not necessarily mean: the platform now has sufficient confidence to release an irreversible seller payout. That distinction is critical. The brief specifically identifies the payout stage as important because marketplace fraud can move from transaction risk into funds-disbursement risk. Stage 6: Payout Payout risk deserves its own fraud model. The marketplace is no longer deciding whether to collect money. It is deciding whether to send money. Those are opposite directions of value movement.

Pay-in fraud versus payout fraud Pay-in fraud The platform accepts money that should not have been accepted. Typical question: Should this buyer payment enter the marketplace? Payout fraud The platform releases funds to an illegitimate recipient or under fraudulent circumstances. Typical question: Should these marketplace funds leave, and to whom? A strong buyer fraud system can therefore coexist with weak payout controls. The buyer may be completely legitimate. The order may even be real. The loss can still occur when money leaves the platform. Seller account takeover can become payout fraud A seller account is economically different from many ordinary customer accounts because it may eventually control the destination of funds. If a legitimate seller account is compromised, signals could include—depending on the platform and lawful data availability: * unusual login context; * credential changes; * profile changes; * unexpected payout destination change; * abrupt behavior change. The brief specifically lists payout-destination change as a potentially relevant account-takeover signal while warning that no single signal proves takeover. That qualification matters. A legitimate seller can change banks. A business can move countries. A corporate reorganization can change the payout entity. A new finance employee can update payment details. So: payout change ≠ payout fraud. It is a trust transition that may warrant appropriate verification.

Treat payout-detail changes as a different event from ordinary seller activity A useful platform principle is to distinguish routine commercial behavior from changes to where money will leave the system. For example: new listing and: new payout account are not economically equivalent events. The first changes what the seller can sell. The second changes where merchant funds may be sent. The marketplace can therefore calibrate controls according to value exposure rather than assigning one static risk score to the seller forever.

Payout fraud is not the same as seller fraud These categories overlap but should remain separate. Seller fraud The seller itself is the fraudulent actor. Seller-account takeover A legitimate seller account is compromised by someone else. Payout diversion The payment destination is improperly changed or controlled. A payout loss might therefore occur even though: the original seller was legitimate. That distinction is essential for investigation and remediation. If the platform labels every payout incident: “fraudulent seller” it may miss the real account-security problem. Refund and dispute abuse create another marketplace ambiguity Now consider the other direction. The buyer receives the product and later seeks funds back. That may be: * legitimate refund; * legitimate service complaint; * refund abuse; * cardholder dispute; * suspected friendly fraud; * unauthorized-payment dispute. Those should not be collapsed. Refund abuse Uses the marketplace or merchant's own refund process. Friendly or first-party dispute behavior Uses the issuer/card-dispute process. Genuine commercial dispute Reflects an actual disagreement over the seller's performance. Fraudulent buyer payment The original payment itself was unauthorized. The dedicated Refund Abuse and Friendly Fraud articles should own their mechanics. Marketplace Fraud owns the platform's need to determine which participant and which mechanism created the post-payment loss. Buyer protection can itself become a fraud surface

Marketplace protections are designed to make legitimate commerce safer. But any platform process capable of transferring value can potentially be abused. That does not mean the marketplace should reduce legitimate customer protection. It means refund and dispute decisions need contextual evidence. For example, repeated refund behavior might be relevant. So might: * seller fulfillment history; * buyer history; * delivery/use evidence; * support contacts; * dispute reason. But frequency alone should not become a universal fraud threshold. The brief explicitly prohibits treating frequent legitimate returns or disputes as automatic proof of abuse. Collusion breaks the assumption that one side is the victim Many fraud systems model marketplace transactions as: buyer versus seller. One is presumed to be acting properly while the other may create risk. Collusion removes that assumption. Two accounts can potentially coordinate. The platform must then evaluate: participant relationships as well as: individual participant behavior. Possible high-level evidence can include unusual relationship patterns among: * buyer accounts; * seller accounts; * transactions; * devices; * addresses; * payment instruments; * fulfillment events. But linkage should not itself become a fraud verdict. A repeat buyer can legitimately purchase from the same seller. A household can share devices. A business buyer can place multiple orders. One seller can serve a concentrated customer base. The correct question is:

Does the relationship make economic sense for legitimate marketplace activity? Not: Are the accounts connected? Incentive abuse can involve both sides too Marketplaces may offer: * buyer credits; * seller incentives; * referral rewards; * new-user promotions; * transaction subsidies. Those incentives can create a different motive for coordinated behavior. But this article should not become the Promo Abuse article. The boundary is: Marketplace Fraud Owns how multiple marketplace participants and money flows create the opportunity. Promo Abuse Owns the economics and mechanics of exploiting promotional eligibility. The cluster explicitly assigns promotional incentive exploitation to its own article. The Marketplace Fraud Actor and Money-Flow Map A complete investigation can use this structure. Money-flow stage Buyer-side risk Seller-side risk Platform/inter-party risk Account creation Fake/compromised buyer context False seller identity or risky onboarding Linked-account anomalies Pay-in Unauthorized payment

Transaction manipulation Order Buyer abuse Seller deception/fulfillment risk Possible collusion Refund/dispute Refund or dispute abuse Seller non-performance Conflicting participant evidence Seller balance

Improper access to proceeds Balance manipulation risk Payout

Fraudulent seller or compromised seller Payout diversion This table is deliberately not a universal fraud-rule checklist. It is an investigation map. For each incident ask: 1. Who acted? 2. Which account did they control? 3. Which stage did they exploit? 4. What value moved? 5. Where did the platform actually lose money? Signals should be attached to actors and stages A generic marketplace fraud score can hide more than it reveals. Consider: new device For a buyer making an ordinary low-value purchase, that may be modest contextual evidence. For a mature seller account immediately followed by a payout-account change, the same device event may matter differently. The signal did not change. The economic event surrounding it changed. This is why marketplace fraud detection should consider: signal + actor + lifecycle stage + economic exposure. Buyer-side signals Depending on the marketplace and available data: * payment authorization context; * authentication outcome; * account history; * unusual purchase behavior; * device/network context; * shipping or fulfillment changes; * payment-attempt velocity. No single one establishes fraud. Seller-side signals Potentially relevant evidence may include: * seller identity/verification status; * account age; * sudden product or value changes; * unexpected account changes; * complaint patterns; * unusual fulfillment behavior; * payout-account changes. Again: signal ≠ confirmed fraud. Relationship signals Possible analytical questions include:

* Are supposedly independent parties repeatedly linked? * Is activity unusually concentrated? * Does the economic relationship make sense? * Are incentives or transfers disproportionately flowing between connected accounts? These should support investigation rather than automatic accusations of collusion. The marketplace false-positive problem has two sides An aggressive ecommerce fraud rule can block a good buyer. An aggressive marketplace fraud system can block: a good buyer or: a good seller. Seller false positives can create a different business impact. A legitimate seller may experience: * delayed onboarding; * payout delay; * extra verification; * account limitation; * manual review; * inability to list or transact. For a platform, incorrectly blocking good sellers can reduce: * marketplace inventory; * seller retention; * geographic expansion; * buyer choice. That is why this cluster's objective is explicitly profitable legitimate growth after fraud and prevention friction, not the minimum possible fraud rate. New sellers are not fraudulent sellers This deserves special emphasis. New sellers naturally have limited history. A marketplace risk model that relies too heavily on: “no history = high fraud” can create a self-defeating growth constraint. Likewise, an international seller may present: * unfamiliar identity formats; * new banking relationships; * different address conventions; * different business records. Those differences can require appropriate validation.

They should not be converted into geographic or demographic suspicion. The brief specifically requires market-specific evidence and warns against stereotyping whole countries or regions as inherently high-fraud. Seller verification and fraud detection are related—but not identical Verification answers questions such as: Who is this seller? Are the supplied documents or business attributes credible? Fraud analysis asks another question: How is this participant behaving now? A legitimate seller can later become compromised. A seller that passed onboarding checks can later engage in prohibited behavior. A seller's bank account can change. So marketplace risk requires both: Enrollment confidence and: Ongoing behavioral confidence. Current regulation illustrates this ongoing dimension. The FTC says covered U.S. marketplaces must require qualifying high-volume sellers to keep specified information current, while EU DSA Article 30 provides for action where covered platforms have sufficient indications that trader information is inaccurate, incomplete, or outdated. Again, those are jurisdiction-specific legal requirements—not universal fraud-control instructions. Separate pay-in controls from payout controls A useful operating model uses two control planes. Pay-in risk Focuses on: Can money safely enter? Potential owners include: * payments; * fraud/risk; * PSP/acquirer; * issuer. Payout risk Focuses on: Can money safely leave? Potential owners can include: * marketplace risk; * seller operations; * finance;

* identity/KYC; * payout/payment operations. The precise ownership depends on platform architecture. The important thing is that these two decisions are not represented as one generic transaction score. The time dimension matters Marketplace fraud can occur across very different time horizons. Immediate Unauthorized buyer payment. Short delay Seller does not fulfill. Post-purchase Refund or dispute abuse. Account lifecycle Buyer or seller account takeover. Balance lifecycle Funds accumulate before release. Payout Funds move to an external destination. A dashboard showing only fraud at authorization captures one slice of this lifecycle. Chargebacks are not a complete marketplace fraud label A chargeback can be evidence. It cannot define the marketplace fraud taxonomy. Chargebacks may involve: * stolen cards; * account takeover; * legitimate commercial disputes; * processing errors; * first-party disputes. Meanwhile: * seller fraud may occur without a chargeback; * payout fraud may occur without a chargeback; * blocked fraud never becomes a chargeback. The brief explicitly requires fraud rate and chargeback rate to remain separate. Refund rate is not marketplace fraud rate either The same logic applies to refunds. A high refund rate might indicate: * seller quality problem; * product problem; * legitimate returns; * service failure; * buyer abuse; * marketplace policy issue. Only some of those are fraud. Track the reason and actor. How marketplace fraud creates economic loss

The full net-revenue model belongs in the separate True Cost and Net Revenue cluster. For Marketplace Fraud, it is enough to map the main loss surfaces. Buyer-payment loss Unauthorized payment or reversal. Fulfillment loss Goods or services delivered without retained payment. Seller-side loss Buyer or platform value lost because of fraudulent seller behavior. Payout loss Funds released to an improper recipient or under fraudulent circumstances. Refund/dispute loss Funds reversed after merchant/platform value has already been delivered. Incentive loss Marketplace-funded credits or promotions misused. Operational cost Risk review, seller investigation, support, payment operations, dispute handling, engineering, and incident response. The brief makes clear that marketplace metrics should distinguish sides rather than collapse all of these into a generic fraud figure. Metrics for marketplace fraud A useful dashboard starts by separating buyer, seller, and payout losses. Buyer fraud loss Confirmed fraud-associated loss originating on the buyer side. Define exactly what counts. Seller fraud loss Confirmed fraud-associated loss originating with seller behavior. Do not include ordinary seller service failures unless classified as fraud under a defensible methodology. Payout fraud loss Confirmed loss from improper funds disbursement. Keep this distinct from buyer transaction fraud. Marketplace fraud rate by count Confirmed fraudulent marketplace events ÷ relevant marketplace events

The denominator must match the event type. A buyer-transaction fraud rate should not be compared directly with seller-account fraud rate. Marketplace fraud rate by value Confirmed fraud-associated value ÷ relevant transaction or payout value Again, define the relevant population. The brief explicitly requires count and value fraud rates to use explicit denominators. Seller onboarding risk Possible measures might include: * accounts requiring additional review; * confirmed fraudulent seller accounts; * time to seller risk detection. Do not report reviewed seller = fraudulent seller. Account takeover Track buyer and seller ATO separately. A seller takeover can have different economic consequences because of payout control. Payout-change anomalies Measure events requiring risk review. Do not label every payout update fraudulent. Dispute rate Useful as post-payment evidence, not as the fraud denominator. Refund-abuse measures Track separately from legitimate refund rate. Collusion investigations Where the marketplace has a defensible methodology, measure investigated and confirmed cases separately. A marketplace fraud dashboard should look asymmetric That is a feature. It might include: Metric Buyer Seller Payout/platform Confirmed fraud loss ✓ ✓ ✓ Account takeover ✓ ✓

Unauthorized payments ✓

Seller onboarding risk

Fulfillment investigations

Refund/dispute abuse ✓ possible

Payout anomalies

✓ ✓ Payout loss

✓ ✓ Collusion cases ✓ ✓ ✓ If every marketplace fraud metric belongs only to the buyer column, the risk program is probably measuring ecommerce fraud rather than marketplace fraud. High-level marketplace controls This fundamentals article should remain defensive rather than becoming a detailed fraud-prevention architecture. A layered model can include: Buyer account and payment controls Relevant to payment credential risk and buyer ATO. Seller identity and onboarding controls Establish appropriate confidence before economically significant seller access. Ongoing seller behavior monitoring Seller verification at onboarding should not become permanent trust. Transaction and relationship monitoring Look for meaningful anomalies within appropriate buyer/seller cohorts. Fulfillment evidence Useful for distinguishing seller fraud, commercial disputes, and buyer abuse. Payout controls Treat payout eligibility and destination as their own risk decisions. Post-payment monitoring Use refunds, disputes, complaints, and confirmed fraud to update risk understanding. The brief explicitly cautions that not every marketplace requires every possible control and that controls should be connected to actual fraud exposure. Do not use one permanent seller risk score Seller risk evolves. A seller that passed onboarding may later: * change ownership information; * change device behavior; * change product category; * dramatically increase volume; * receive elevated complaints; * change payout destination.

The risk decision should therefore follow events as well as accounts. A better mental model is: Who is the seller? → What is the seller doing? → What value is becoming available? → Where will the money go? Risk should increase with irreversible value exposure Not every suspicious event needs the same response. If no money or goods can yet leave the platform, monitoring may be sufficient. Before an irreversible payout, the economics may justify stronger confidence. That creates an important rule: Match control intensity to the next movement of value. This is more precise than: “High-risk sellers need more checks.” It identifies why the check exists.

That supports a restrained marketplace positioning statement:

* seller onboarding for every marketplace model; * sub-merchant payout orchestration; * marketplace collusion detection; * seller-account-takeover detection; * marketplace-specific payout-diversion detection; * guaranteed marketplace fraud reduction; * a particular false-positive improvement. Those require internal product verification. Six questions for every marketplace fraud investigation 1. Who created the risk? Buyer? Seller? Compromised buyer account? Compromised seller account? Multiple coordinated parties? 2. Where did the activity enter? Account creation? Pay-in? Order? Fulfillment? Refund/dispute? Balance? Payout? 3. What value was targeted? Payment goods/service refund promotion seller balance or: payout? 4. Is the event actually fraud? Could it instead be: customer error seller service failure commercial dispute legitimate payout change or: suspicious but unconfirmed behavior? 5. What evidence belongs to this participant and stage? A buyer card signal cannot explain seller payout risk. A seller identity check cannot establish that every buyer transaction is legitimate. 6. What control protects value without unnecessarily blocking good participants? Measure the effect on: buyer acceptance seller acceptance seller payout experience fraud loss and: operational workload. That is the core marketplace risk decision. The conclusion: follow the money, then identify who controls it Marketplace fraud becomes easier to classify when the platform stops treating checkout as the center of every investigation.

A buyer payment is only the beginning of the marketplace money flow. After it comes: the seller relationship the fulfillment event the seller balance and: the payout. Each stage can have a different actor, a different target, and a different loss mechanism. That is why a marketplace can successfully stop stolen-card fraud and still have a serious fraud problem. The mature question is not: “Was the buyer payment safe?” It is: “At every point where marketplace value changes hands, do we know which participant controls it, why the transfer is legitimate, and what evidence would tell us that assumption has changed?” That is marketplace fraud management as a platform discipline rather than a checkout rule. Legal, privacy, and security note This article provides general information and does not constitute legal, regulatory, privacy, security, payments, or compliance advice. Marketplace definitions, seller-verification requirements, payout rules, identity obligations, and available fraud controls vary by jurisdiction and platform model. Merchants and marketplace operators should verify applicable requirements with qualified advisers, payment providers, identity specialists, and relevant authorities.

The strongest SEO differentiator is the article’s money-flow architecture. Instead of producing another “types of marketplace scams” list, it answers the more useful merchant question: where does fraud enter after the buyer has already paid? That lets the page cover buyer fraud, seller fraud, marketplace account takeover, and payout fraud while preserving the dedicated mechanism pages elsewhere in the cluster.

I’ve treated this as Creative Brief 13: Marketplace Fraud. The article’s distinctive territory is the platform’s multi-party trust and money-flow problem: buyer, seller, transaction, fulfillment, balance, and payout all create separate fraud surfaces. That positioning is reinforced by current regulation without turning the article into a compliance guide. In the U.S., the INFORM Consumers Act requires covered online marketplaces to collect and verify specified information—including bank-account information—from qualifying high-volume third-party sellers. In the EU, the Digital Services Act’s trader-traceability provisions for covered platforms include trader identity and payment-account details. Both are useful evidence that marketplace trust architecture extends beyond authenticating the buyer at checkout. Marketplace Fraud Actor Map Buyer side Actor Buyer or person controlling buyer account. Potential fraud surfaces * unauthorized payment; * buyer ATO; * refund/dispute abuse. Primary value at risk * goods/service; * payment; * refunds. False-positive risk Legitimate unusual buyer behavior.

Seller side Actor Seller or person controlling seller account. Potential fraud surfaces * fraudulent seller identity; * seller ATO; * fulfillment-related fraud; * improper payout control. Primary value at risk * buyer funds; * platform funds; * seller balance; * payout. False-positive risk New sellers, international sellers, legitimate account or banking changes.

Platform interaction Actors Buyer + seller or linked participants. Potential fraud surfaces * coordinated abuse; * incentive exploitation; * manipulation of platform transaction flows. Primary value at risk * platform subsidy; * transaction integrity; * marketplace balances. False-positive risk Legitimate repeat commercial relationships or shared infrastructure.

Marketplace Money-Flow Map BUYER ACCOUNT │ ▼ BUYER PAYMENT │ │ Pay-in risk ▼ PLATFORM │ ├──────────────► REFUND / DISPUTE │ ▼ ORDER / FULFILLMENT │ │ Buyer vs seller evidence ▼ SELLER BALANCE │ │ Seller/account risk ▼ PAYOUT DECISION │ │ Destination / eligibility risk ▼ SELLER PAYMENT ACCOUNT At every arrow ask: Who controls the next movement of value? That visual directly implements the brief's required actor-and-money-flow structure.

Measurement plan Buyer side Track: * confirmed buyer fraud by count; * confirmed buyer fraud by value; * buyer ATO; * unauthorized payment loss; * refund/dispute behavior by reason; * legitimate payment acceptance. Seller side Track: * seller accounts reviewed; * confirmed seller fraud; * seller fraud loss; * seller ATO; * fulfillment-related investigations; * seller onboarding risk outcomes; * legitimate seller approval/onboarding. Payout Track: * payout volume; * payout count; * payout-detail changes; * payout reviews; * blocked/held payouts by reason; * confirmed payout fraud; * payout fraud loss; * false-positive payout interventions where measurable. Platform relationships Where appropriate: * linked-account investigations; * confirmed collusion; * incentive abuse; * repeated buyer/seller relationship anomalies. Do not label every relationship anomaly as collusion. Operational Track: * manual review rate; * time to decision; * support contacts; * risk investigation volume; * fraud-related operational cost. Growth guardrails Track: * buyer payment acceptance; * seller onboarding completion; * legitimate seller retention; * payout delays for legitimate sellers; * false positives where defensibly measured. The brief requires fraud-control effectiveness to be judged alongside legitimate approval, review burden, latency, and operating cost—not by fraud capture alone.

SEO package SEO title: Marketplace Fraud: Buyer, Seller and Payout Risk Explained H1: Marketplace Fraud: Why Two-Sided Payment Platforms Face More Than Buyer Fraud Meta description: Learn how marketplace fraud can originate with buyers, sellers, compromised accounts, payouts or colluding participants—and how platforms can map fraud across pay-in, fulfillment, balances and payouts. URL slug: /marketplace-fraud Primary keyword: marketplace fraud Secondary keywords: marketplace payment fraud; seller fraud marketplace; buyer fraud marketplace; payout fraud; marketplace account takeover; marketplace scam payments; ecommerce marketplace fraud. Related entities: online marketplace, platform payments, buyer fraud, seller fraud, payout fraud, seller onboarding, account takeover, merchant fraud, marketplace risk, marketplace trust and safety, seller verification, payment disputes. Article excerpt: Marketplace fraud is not merely fraudulent buyer checkout. A two-sided platform can lose money through buyer fraud, fraudulent sellers, compromised seller accounts, fulfillment abuse, collusion and payout diversion. The right model follows both the participants and the movement of money. Suggested structured data: Article. I would not add FAQ schema by default. The Marketplace Fraud Actor Map and money-flow visual are stronger article-specific assets and better differentiate this page within the cluster. Search-intent coverage The article directly covers: What is marketplace fraud?

What are common types of marketplace fraud? What is seller fraud in a marketplace? What is buyer fraud in a marketplace? What is marketplace payout fraud? How does marketplace account takeover work? What is the difference between pay-in fraud and payout fraud? How can marketplaces identify seller fraud? How should marketplaces measure fraud? How can marketplaces reduce fraud without blocking legitimate buyers and sellers?

Internal-link plan Anchor Destination payment fraud What Is Payment Fraud? types of payment fraud Types of Payment Fraud stolen card fraud Stolen Card Fraud account takeover fraud Account Takeover Fraud synthetic identity fraud Synthetic Identity Fraud promo abuse Promo Abuse refund abuse Refund Abuse friendly fraud Friendly Fraud card-not-present fraud Card-Not-Present Fraud fraud and net revenue Relevant True Cost and Net Revenue article The Marketplace Fraud article should link outward to the mechanism-specific articles instead of re-explaining them. Its unique territory is multi-party fraud across marketplace money flows.

Supporting visual Marketplace Fraud Actor Map MARKETPLACE │ ┌────────────────┼────────────────┐ │ │ │ BUYER SELLER PLATFORM │ │ │ Buyer fraud Seller fraud Incentives Buyer ATO Seller ATO Relationships Refund abuse Fake seller Collusion │ Fulfillment │ └──────────────┬───────────────────┘ │ ▼ MONEY FLOW

BUYER PAYMENT │ ▼ PLATFORM │ ▼ ORDER / FULFILLMENT │ ▼ SELLER BALANCE │ ▼ PAYOUT Key annotation Fraud actor ≠ payment actor A legitimate buyer payment does not establish that the seller, seller account, fulfillment, or payout is legitimate. Image alt text Marketplace fraud actor map showing buyer fraud, seller fraud, account takeover, collusion and payout fraud mapped across buyer payment, platform, fulfillment, seller balance and payout stages.

Authoritative source recommendations Federal Trade Commission — INFORM Consumers Act guidance. Use narrowly for U.S. seller-traceability requirements applicable to qualifying marketplaces and high-volume third-party sellers, including collection and verification of seller bank-account and identity-related information. European Union — Digital Services Act, Article 30. Use for EU trader traceability on covered online platforms, including trader identity, payment-account information and reliability/completeness checks, with careful attention to the regulation's scope and exclusions.

Proposed author and reviewers

Primary reviewer: Marketplace risk or Trust & Safety specialist. Payments reviewer: Payments risk specialist. Payout reviewer: Payment operations or payouts specialist. Seller-risk reviewer: KYC/identity or marketplace onboarding specialist. Data reviewer: Fraud analyst responsible for buyer/seller/payout fraud-label methodology. Legal/compliance reviewer: Required for jurisdiction-specific marketplace verification or seller-traceability statements. Do not state review completion until it actually occurs.

Fraud-definition fact-check For each real incident or example record: Marketplace side: Buyer / Seller / Platform / Multiple parties Fraud type: ______ Actor: ______ Compromised account: ______ Money-flow stage: ______ Targeted value: ______ Confirmed versus suspected: ______ Evidence: ______ Loss mechanism: ______ Recovery: ______ Do not classify every: chargeback refund seller complaint payout change or: account link as fraud.

Attack-mechanism fact-check Before labeling an event, distinguish: Fraudulent buyer? Yes / No / Unknown Stolen payment credential? Yes / No / Unknown Buyer ATO? Yes / No / Unknown Fraudulent seller? Yes / No / Unknown Seller ATO? Yes / No / Unknown Payout diversion? Yes / No / Unknown Refund/dispute abuse? Yes / No / Unknown Collusion? Confirmed / Suspected / No evidence Commercial dispute instead? Yes / No / Unknown This prevents a payment event from defining the fraud mechanism prematurely.

Signal and data fact-check For any signal proposed in publication, verify: * platform actually has lawful access; * data quality is understood; * actor and lifecycle stage are defined; * legitimate explanations have been considered; * no universal threshold is invented; * signal is not called proof; * shared devices/networks are considered; * international seller/buyer variation is considered; * seller-account and payout events are distinguished. The brief explicitly requires risk signals, rules, and decisions to remain separate.

Fraud-statistics fact-check Every marketplace fraud statistic should identify: Fraud category Buyer / seller / payout Count or value Market Payment method Marketplace type Time period Denominator Confirmation methodology Do not publish: “Marketplace fraud rate = X%” without specifying what counted as marketplace fraud. The brief explicitly requires statistics to identify their fraud definition, basis, market, period, and denominator.

Industry and market fact-check Before using examples, specify marketplace model: Physical-goods marketplace Digital marketplace Services marketplace Travel marketplace B2B marketplace Creator/platform marketplace and determine whether the platform actually controls: * buyer payment; * seller balance; * fulfillment; * refund; * payout. Not every marketplace has the same money-flow architecture. Likewise, do not generalize U.S. INFORM Act obligations or EU DSA trader-traceability provisions to every marketplace globally. Their definitions and scopes are specific.

Regulatory and privacy flags Marketplace fraud controls can involve: * seller identity data; * buyer identity data; * payment data; * bank/payment-account information; * device data; * behavioral information; * transaction relationships; * automated decisions. Applicable privacy, marketplace, payments, identity-verification, and consumer-protection obligations vary by jurisdiction. For example, current U.S. INFORM requirements apply to defined online marketplaces and qualifying high-volume third-party sellers of covered consumer products; they are not a universal seller-verification standard. Likewise, DSA Article 30 sits within a defined section applicable to particular online platforms and includes explicit scope rules.

Safety and abuse-enablement check The article intentionally explains: * actor classification; * money-flow stages; * defensive risk signals; * payout risk; * fraud-versus-dispute distinctions; * merchant measurement. It does not provide: * ways to evade seller verification; * instructions for compromising marketplace accounts; * methods for redirecting payouts; * collusion procedures; * transaction-laundering instructions; * fraud-rule thresholds; * methods for defeating authentication. This follows the brief's requirement to remain defensive and merchant-oriented.

Amber-flag claims “Marketplace fraud is mostly fraudulent buyer payments.” Too narrow. The marketplace model creates seller, account, fulfillment, balance, and payout surfaces. “If the buyer payment is legitimate, the transaction is safe.” Incorrect as a marketplace-wide conclusion. Seller or payout risk can remain. “A seller with incomplete verification is fraudulent.” Incorrect. Verification status is evidence state, not fraud confirmation. “A payout-account change indicates account takeover.” Too strong. It can be a risk event with legitimate explanations. “Every seller complaint is seller fraud.” Incorrect. Service failures and commercial disputes must be separated from fraud. “A high refund rate means buyer abuse.” Unsupported without context. “Linked buyer and seller accounts prove collusion.” Unsupported. Relationship evidence needs context and corroboration. “Chargebacks measure marketplace fraud.” Incomplete. Chargebacks cover only part of the fraud surface and include non-fraud disputes. “Seller KYC prevents marketplace fraud.” Unsupported. Identity verification addresses one part of marketplace trust; legitimate accounts can also be compromised later.

Not established by the current public material reviewed.

Not established.

Requires approved, cohort-defined merchant evidence.

Before strengthening the marketplace section, verify internally: Marketplace model support * marketplace/platform merchant eligibility; * sub-seller structures; * merchant-of-record treatment; * buyer/seller data model; * balance support; * payout/sub-merchant capability. Seller onboarding * KYC/KYB capabilities; * individuals versus companies; * supported jurisdictions; * verification refresh; * beneficial ownership where applicable; * seller payment-account verification. Seller risk * seller-specific risk profiles; * longitudinal behavior; * fulfillment data; * complaint/dispute integration; * seller-account takeover signals. Payout controls * payout-destination verification; * payout-detail-change controls; * payout holds; * seller balance monitoring; * payout-risk scoring; * payout reconciliation. Marketplace relationship analysis * linked-account capabilities; * buyer/seller relationship signals; * collusion detection; * incentive abuse. Performance * approved marketplace merchant outcomes; * seller-fraud reduction; * buyer-fraud reduction; * payout-loss reduction; * false-positive effect; * seller onboarding impact. Do not disclose proprietary fraud features, thresholds, investigation logic, or security architecture.

Cluster sameness audit Field Marketplace Fraud Opening device Legitimate buyer payment can coexist with marketplace fraud elsewhere Fraud actors Buyer, seller, compromised accounts, colluding parties Targeted assets Payment, goods/service, seller balance, platform incentives, payout Entry points Pay-in, account, fulfillment, refund/dispute, balance, payout Attack mechanism Varies by actor; multi-party structure is the distinctive feature Merchant/platform loss Buyer loss, seller-side loss, payout loss, operations Primary signals Actor- and lifecycle-specific signals False-positive risk Blocking legitimate buyers or legitimate sellers Format Marketplace actor and money-flow map Unique evidence anchor Buyer authentication alone cannot secure a two-sided platform Editorial position Evaluate every participant and movement of value separately Common assumption challenged Marketplace fraud prevention is mostly buyer-payment screening Merchant decision Which participant and money-flow stage needs intervention Original framework Marketplace Fraud Actor Map Primary metrics Buyer fraud loss, seller fraud loss, payout loss Conclusion Follow the money, then identify who controls it CTA Map fraud controls to participant + lifecycle stage Closing element Six-question marketplace investigation framework

This makes Article 13 structurally different from Stolen Card Fraud, Account Takeover Fraud, Synthetic Identity Fraud, Refund Abuse, and Friendly Fraud. Those own individual fraud mechanisms; Marketplace Fraud owns how those mechanisms interact inside a two-sided platform money flow.