Checktiv

Can marketplaces be held liable for unverified sellers?

Can marketplaces be held liable for unverified sellers?

TL;DR

  • Can marketplaces be held liable for unverified sellers? Yes, when a legal duty or actionable marketplace conduct supports liability.
  • The FTC’s INFORM Consumers Act guidance separates seller verification duties from responsibility for individual transactions.
  • Identity verification establishes identity evidence, not product safety, ownership, or permission to sell.
  • Review your marketplace’s obligations before choosing seller screening software or promising that sellers are verified.

Yes, marketplaces can be held liable for unverified sellers when they breach a verification duty, make misleading claims, or engage in conduct that creates liability under applicable law. In 2026, an unverified seller does not automatically make a marketplace liable for every loss, and completing an identity check does not excuse separate failures involving seller information, disclosures, or product safety.

Why this matters

A verified identity is not a legal shield. Your marketplace needs to distinguish who a seller is from whether that seller meets the requirements for listing and selling particular goods.

That distinction matters when you set onboarding rules, describe verification to buyers, and respond to complaints. Start with the actual duties your business has, then build your seller verification workflow around them. Buying an identity check first and defining its purpose afterward reverses that order.

This guide addresses U.S. marketplace obligations in 2026. It provides general information, not legal advice for a particular platform or dispute.

Can marketplaces be held liable for unverified sellers?

Yes, but the legal basis matters more than the label “unverified.” A regulator enforcing seller-verification requirements faces a different question from a buyer seeking compensation for a defective product.

Legal issueWhat creates exposureWhat verification does not resolve
INFORM Consumers Act complianceFailure to meet applicable collection, verification, disclosure, or suspension dutiesProduct safety or every seller’s performance
Misleading marketplace claimsStatements about screening that misrepresent what the platform actually checksWhether the buyer understood an accurate, limited claim
Product liabilityThe marketplace’s legally relevant role under applicable state lawWhether the product was defective
Contract obligationsFailure to perform an enforceable promiseWhether identity checks satisfied a separate buyer-protection promise
Other statutory dutiesConduct within a law’s scope, including regulated goods or servicesCompliance with laws outside the identity check

The Federal Trade Commission’s INFORM Consumers Act business guidance explains the federal seller-information framework. The statute, 15 U.S.C. § 45f, is the starting point for covered consumer-product marketplaces, not a universal rule for every platform business.

For your 2026 review, separate regulatory compliance from transaction liability. Passing an onboarding check does not decide either question by itself.

Which sellers trigger the INFORM Consumers Act requirements?

The INFORM Consumers Act applies to qualifying online marketplaces and high-volume third-party sellers of new or unused consumer products. It does not impose the same requirements on every account simply because that account sells something online.

Under the statute, a high-volume third-party seller generally meets both thresholds during a continuous 12-month period within the previous 24 months:

  • 200 or more separate sales or transactions involving new or unused consumer products.
  • $5,000 or more in gross revenue from those sales or transactions.

The statutory calculation concerns sales through the marketplace for which the marketplace processed payment directly or through its payment processor. Gross revenue is not the seller’s profit.

For covered high-volume sellers with $20,000 or more in annual gross revenue on the marketplace, additional seller-information disclosure requirements apply, subject to statutory exceptions.

These are legal coverage thresholds, not recommended onboarding targets. A marketplace can choose to verify sellers below them, but that policy choice is different from saying federal law requires every seller to complete the same check.

Do not treat INFORM as a universal marketplace identity law. A short-term rental platform, a services marketplace, and a marketplace selling new consumer goods need separate scope assessments. Their business models are not interchangeable.

What must a covered marketplace actually do?

For covered sellers, INFORM requires more than a document upload. The FTC’s business guidance describes obligations involving bank-account information, contact information, tax identification information, and specified identification records.

The statute generally requires collection within 10 days after a seller qualifies as high-volume and verification within 10 days after receiving the required information. Your legal review should map the precise trigger, required records, and applicable exceptions before those deadlines become operational rules.

Use this sequence to turn the legal requirements into a workable process:

  1. Determine coverage. Establish whether your marketplace and the seller fall within the statute. Track qualifying activity rather than relying only on a seller’s self-description.
  2. Collect information. Request the records required for the seller’s circumstances. Explain the purpose and provide a clear completion path.
  3. Verify information. Check the required information using methods that meet the applicable legal standard. A completed upload is not the same as verified information.
  4. Review exceptions. Resolve inconsistencies and document the basis for approval or further action. Keep incomplete cases distinguishable from completed checks.
  5. Maintain records. Support annual certification, required disclosures, reporting mechanisms, and follow-up obligations. Apply the statute’s suspension requirements when triggered.

The process needs an owner at every stage. A useful internal question is: who decides what happens when a seller submits records but the information cannot be verified?

*Collecting seller information and verifying it are separate steps.*

Does a verified seller protect the marketplace from liability?

No. Identity verification answers a limited question about identity evidence. It does not establish that merchandise is authentic, that a seller owns it, or that a listing satisfies product-specific rules.

Keep these checks separate in your operating policy:

  • Identity: Does the evidence support the claimed identity?
  • Business authority: Is the person authorized to act for the seller business?
  • Listing eligibility: Is the product or service allowed under applicable rules?
  • Account control: Is the person operating the account entitled to use it?
  • Seller conduct: Does activity after approval require further review?

A verification badge should describe the check actually completed. If your platform checks identity but not product authenticity, do not let the badge imply both.

For a 2026 policy review, compare every public verification claim with the underlying process. That includes onboarding screens, help text, listing badges, and buyer-support responses. Clear language gives your team a promise it can consistently explain.

Does Section 230 protect a marketplace from seller misconduct?

Section 230 is not a blanket exemption from marketplace liability. The federal provision, 47 U.S.C. § 230, addresses specified claims that treat an online service as the publisher or speaker of information supplied by another content provider.

Whether it applies depends on the claim, the alleged conduct, statutory exceptions, and controlling law. A claim about publishing a seller’s listing is not necessarily equivalent to a claim about the platform’s own promise or commercial conduct.

Do not assume that hosting third-party listings cancels an express seller-verification duty. Equally, do not assume that every dispute falls outside Section 230 just because a transaction occurred.

Your next step is a claim-specific legal review. Ask counsel to identify the conduct each potential claim targets, rather than giving the entire marketplace a single protected or unprotected label.

Why marketplace liability varies

The answer changes with the governing duty and the marketplace’s conduct. For a 2026 assessment, organize the review around these factors:

  • Jurisdiction. State product-liability rules and other applicable laws affect the analysis. A conclusion about one state does not settle the position nationwide.
  • Marketplace role. Examine the platform’s role in payment, fulfillment, sales terms, and representations. The legally relevant facts depend on the claim.
  • Seller coverage. INFORM obligations depend on the statutory definitions and thresholds, not a platform’s informal label for a large seller.
  • Public promises. A narrow identity-check statement differs from a promise that every seller or product has been fully vetted.
  • Information received. Complaints, inconsistencies, and notices matter where the relevant law makes knowledge or notice significant.
  • Required follow-up. Initial approval does not replace duties involving annual certification, disclosures, reporting channels, or suspension.

Avoid converting this list into a universal liability score. It is a structure for gathering facts and assigning responsibility, not a formula that predicts the outcome of a lawsuit.

What should you do when seller verification is incomplete?

Separate an unfinished application from an approved seller account. Define the permissions attached to each status, then apply the relevant legal requirements and your documented policy.

For covered INFORM sellers, suspension is not just an optional onboarding preference when the statutory conditions require it. Build the required notices and response periods into the process with legal oversight.

For other cases, decide which information is necessary before a seller can list or transact. Tell the seller what remains unresolved and how to correct it. Keep a record of the decision and the evidence supporting it.

Do not silently turn missing information into a pass. Your support team should be able to distinguish missing records, conflicting records, and a completed review without interpreting a vague status label.

Where shared-link verification fits

Some operators need a straightforward way to request identity verification without building a custom process. Checktiv provides shared-link verification with zero-code setup, with its primary experience designed for independent short-term rental hosts.

Checktiv guest verification is best suited to independent hosts who want zero-code shared links. The stated setup journey is three steps in five minutes: sign up, get a link, and review the verification.

The benefit is a clear way to request and review guest verification. The boundary is equally important: Checktiv guest verification does not, by itself, establish that a marketplace has met every INFORM requirement or other legal duty. A marketplace evaluating the service still needs to match its required evidence and decisions to the actual workflow.

Can a buyer sue a marketplace over an unverified seller?

Yes, a buyer can bring a claim, but an unverified account alone does not establish a right to recover. The buyer must satisfy the requirements of an applicable cause of action, including the necessary connection between the marketplace’s conduct and the alleged harm.

Distinguish the ability to file a lawsuit from the ability to win one. Also distinguish private claims from regulator enforcement of statutory duties.

Is a seller’s business registration enough?

No, business registration alone does not establish every fact relevant to seller approval. It does not necessarily establish who controls the account, whether a representative has authority, or whether particular goods can lawfully be sold.

Use registration evidence for the question it answers. Do not substitute it for all other required information.

One last thing

Review the meaning of “verified” before redesigning the badge. Write one sentence stating exactly what your marketplace checks, then ask whether a buyer would infer anything broader.

For your 2026 review, compare that sentence with the evidence retained for an approved seller. If they do not match, narrow the promise or change the process. A precise claim is more useful than a reassuring label your team cannot explain.

Related guides

Frequently asked questions

Can marketplaces be held liable for unverified sellers in 2026?

Yes, marketplaces can be held liable for unverified sellers when an applicable duty or actionable marketplace conduct supports liability. An unverified account does not automatically make the platform responsible for every seller-related loss.

Does every online seller need identity verification under INFORM?

No, INFORM does not apply the same verification requirements to every online seller. Its high-volume seller definition generally involves at least 200 qualifying transactions and $5,000 in gross revenue during a continuous 12-month period within the previous 24 months.

Does checking a seller’s ID prove their products are legitimate?

No, checking a seller’s ID does not prove product authenticity, ownership, or safety. Those questions require separate evidence and review.

Can a marketplace rely entirely on a verification provider?

No, using a provider does not itself establish that the marketplace has fulfilled its legal duties. The marketplace must assess what the service checks and how its results fit the required process.

Does Section 230 remove seller-verification obligations?

Section 230 is not a general exemption from seller-verification obligations. Its application depends on the particular claim, alleged conduct, statutory exceptions, and controlling law.

Is guest verification the same as marketplace seller compliance?

No, guest verification and marketplace seller compliance address different operational and legal questions. Checktiv supports shared-link guest verification, while a marketplace must separately assess its seller-information duties.