How We Vet Sellers

Why seller-side verification is separate from listing verification

Listing verification confirms that a specific listing's data matches what the seller can show in the recording. Seller verification is a separate and prior check that confirms the person offering the listing is who they say they are, has not been previously banned from SMProud or from comparable marketplaces, and is the legitimate owner of the account being listed. The two layers address different failure modes. A bad actor with a stolen account can produce a recording that looks legitimate (because they have credentials, even if illegitimately); seller verification is the layer that filters them out before listing review even begins.

The three checks every new seller goes through

1. Identity verification. A government-issued photo ID matched against a video selfie, processed through a third-party KYC vendor. The same identity verification flow that banks and crypto exchanges use. This catches the largest category of bad actors: people using fake or stolen identities to onboard with the intent to defraud.
2. Behavioral history check. The seller's email, payment instruments, and (where legally permissible) phone number are checked against an internal database of previously-flagged sellers and against industry-shared databases of marketplace-fraud actors. Sellers who have been banned from comparable marketplaces or who have been flagged for chargebacks elsewhere are restricted to lower-value listings and additional escrow timeframes.
3. Account-ownership proof. Before the first listing publishes, the seller must demonstrate that they own the specific account being listed — typically through the screen recording for that listing, which requires platform-side credentials access. This is technically part of listing verification, but it doubles as a seller-side ownership check because credentials access is the strongest available proof of ownership at the marketplace stage.

What we cannot catch and why we are honest about it

Seller verification reduces fraud risk; it does not eliminate it. The categories we catch: identity-fraud onboarding, repeat bad actors with traceable history, and sellers with behavioral patterns flagged in fraud-detection databases. The categories we do not catch as reliably: first-time sellers with clean identity records who plan to defraud (no behavioral history to check), sellers who acquired account credentials through hacking or social engineering and present them as their own (the recording shows access, not ownership chain), and sellers operating through proxies (where the verified identity is real but is fronting for someone else). For these categories, our protection layer is escrow rather than pre-verification — funds remain held until the buyer can confirm the deal completed cleanly, which limits the damage even when pre-verification misses something.

Trust-tier mechanics that affect the seller experience

Sellers who pass initial verification publish their first listings as "new seller" — the listing appears in catalog browse pages with a flag indicating limited transaction history, and the escrow flow holds funds slightly longer to allow a wider margin for buyer-side verification. As sellers complete clean transactions, they accumulate transaction history that lifts them out of the new-seller tier. At 5 clean transactions, the new-seller flag comes off. At 25, the seller becomes eligible for "established seller" status, which surfaces in listing cards as a positive signal to buyers. At 100+ clean transactions with no disputes, sellers reach "trusted" status, which carries no visible badge change but does affect how disputes involving them are weighted in our review process. Disputes against trusted sellers require stronger buyer-side documentation because the prior-history signal is genuinely informative.

What gets a seller restricted or removed

• Chargebacks initiated by buyers on payouts. Sellers cannot directly chargeback (they receive funds, they do not pay them), but they can be the cause of buyer chargebacks if the deal fails after release. Sellers who accumulate chargeback events get restricted to longer escrow windows or removed from the platform.
• Multiple disputes resolved in the buyer's favor. A pattern of disputes ruled against the seller (regardless of any single dispute's specific facts) indicates a systematic problem with the seller's listing accuracy or handover behavior. Sellers in this pattern get restricted; persistent patterns get removed.
• Identity fraud detected post-onboarding. If the identity used to verify the seller is later determined to be fraudulent (the real person whose ID was used reports identity theft, the documents fail a re-check), the seller is removed and any pending payouts are held for buyer protection.
• Selling stolen accounts. Verification cannot prove ownership chain, but accounts where the original owner reports the account as stolen and the platform confirms the report result in seller removal. SMProud cooperates with platform investigations and law enforcement on these cases.

What buyers can read from the seller-side signals on a listing

The signals visible on a listing card and seller profile that reflect seller verification: the new-seller flag (or absence of it), the cumulative transaction count, the dispute rate (visible as a percentage on seller profiles with sufficient history), the seller's join date, and the trusted-seller signal where applicable. None of these is conclusive on its own, and a high-quality listing from a new seller is often a perfectly fine purchase. The signals are most useful as one input among several — listing verification, asking price relative to recommended band, niche-content fit, and the seller's responsiveness in the deal conversation all matter alongside the seller-tier signals.

Related operational pages

• Listing verification process
• How escrow works
• Buyer protection policy