INFORM Consumers Act: Marketplace Seller Disclosure Checklist
A practical INFORM Consumers Act compliance checklist for marketplaces: seller thresholds, bank verification, recertification and buyer disclosures.

Photo: Pixabay
On this page 9 sections
- What INFORM Consumers Act Compliance Means for Your Marketplace
- Defining an INFORM Act High-Volume Seller on Your Platform
- Information You Must Collect and Verify
- Using Payout Bank Data for High-Volume Third-Party Seller Verification
- Marketplace Seller Disclosure: Handling Buyer-Facing Details
- Seller Recertification and Suspending Non-Responsive Sellers
- INFORM Act Enforcement and Penalties: What to Confirm
- INFORM Act Checklist for Marketplace Operators
- Next Steps
Key takeaways
- Take the law's seller thresholds, required data, deadlines and disclosure rules from the official statute and FTC guidance, then automate seller monitoring against them.
- Processor-held payout bank data can support seller verification only if you can retrieve it promptly and keep it matched to the rest of the seller's profile.
- Build recertification, suspension and buyer-disclosure workflows with complete logs, so you can show how you handled any individual seller.
- Ask counsel who can enforce the law, how penalties work and how state rules interact with it, and treat your records as potential evidence.
If independent sellers list products on your platform and you process their sales, INFORM Consumers Act compliance belongs in your marketplace operations. This guide turns that compliance work into a practical checklist for marketplace operators. It covers how to monitor sellers against the law's thresholds, how to collect and verify seller information, how payout bank data may support verification, how to plan buyer-facing disclosures, and how to run recertification, suspensions and recordkeeping that will hold up if a regulator asks questions.
This article is general information, not legal advice. It does not state the law's specific thresholds, deadlines, required data fields, recertification frequency, disclosure rules, enforcing agencies or penalty amounts. Read the current statute text and the Federal Trade Commission's INFORM Consumers Act business guidance, and confirm your obligations with a qualified attorney before you finalize your policies.
What INFORM Consumers Act Compliance Means for Your Marketplace
The INFORM Consumers Act deals with transparency about third-party sellers on online marketplaces. The statute and FTC guidance define your exact duties. Treat everything below as a framework for organizing the work, not as a summary of the law.
In practice, compliance programs for laws like this one usually involve four operational areas:
- Monitoring: knowing when a seller's activity brings them within the law's scope.
- Onboarding and verification: collecting and checking the seller information the law requires.
- Listings: showing buyers seller details if and where the law requires it.
- Ongoing maintenance: recertification, suspensions, data security and recordkeeping.
Much of this overlaps with work your processor already expects. If you run a structured seller KYC process before releasing payouts, you already have a foundation. Expect the law to add its own triggers, documentation and possibly buyer-facing duties on top of it.
Defining an INFORM Act High-Volume Seller on Your Platform
The law separates covered sellers from everyone else. Don't rely on figures from blog posts or vendor marketing. Take the definitions from the official text and have counsel confirm how they apply to your business model.
Questions to Answer From the Statute and FTC Guidance
- What activity makes a seller "high-volume," and over what look-back period?
- If more than one measure applies, does a seller need to meet all of them or only one?
- Do different tiers trigger different duties?
- Which transactions count toward the definition, and which are excluded?
- How quickly must you act once a seller qualifies?
Build Threshold Monitoring Into Your Data
Once you have the answers, automate the counting. Set up a recurring job that measures each seller's activity against every tier counsel identifies. Have it flag sellers as they approach each tier, not only after they cross it.
Illustrative example: A handmade-goods seller does light volume most of the year, then sells heavily during the holiday rush. A monthly report might miss the moment they qualify. A daily rolling calculation flags them right away, so you can request information on time instead of finding the gap weeks later.
Off-platform payments create a blind spot. If buyers pay sellers outside your checkout, your data understates a seller's real activity. That's one more reason to work on keeping buyers paying through your platform.
Information You Must Collect and Verify
Confirm the exact data fields, deadlines and verification standards in the statute and FTC guidance. While you wait on that review, map where these categories, common in marketplace verification programs, already live in your systems:
- Payout bank account details.
- Legal name, plus business name and physical address for business sellers.
- Government-issued identification.
- Tax identification numbers.
- Contact details, such as email address and phone number.
Then compare the map with counsel's list of required fields. Close the gaps, and don't collect sensitive data the law doesn't require unless you have another legitimate need for it.
Verify, Don't Just Store
Collecting what a seller types into a form is not the same as verifying it. Write a policy that defines:
- Which document types you accept.
- How you check them: manual review, a third-party verification vendor, or both.
- Who reviews exceptions and mismatches, and within what timeframe.
- What happens when a seller can't or won't provide acceptable documentation.
Ask counsel which verification methods and documents the law treats as acceptable, and align your policy with that answer.
Protect What You Collect
ID images, tax IDs and bank details are highly sensitive no matter what the law says about handling them. Store them with encryption, strict access controls and defined retention periods. Ask counsel whether the law limits how you may use this information. As a matter of good practice, don't repurpose verification data for marketing.
Using Payout Bank Data for High-Volume Third-Party Seller Verification
The payout bank account is a useful identity data point for many marketplaces. Sellers have a strong incentive to keep payout details accurate, and account ownership can be cross-checked against the rest of the seller's profile. Whether and how bank data satisfies any legal verification requirement is a question for counsel.
When Your Processor Holds the Bank Details
Many marketplaces never touch raw bank numbers because a processor, payout provider or payment facilitator stores them. Ask counsel whether relying on a third party to hold this data fits your obligations. Then confirm these points in writing with your provider:
- Which seller bank data they store, and for how long.
- How quickly you can retrieve it on request.
- Whether you can export it for audits or regulator inquiries.
- How they notify you when a seller changes payout accounts.
If you're weighing whether to take on more of this responsibility yourself, our guide on whether your marketplace should become a payment facilitator covers the tradeoffs.
Match Names Across Records
Bank data is most useful when it agrees with the rest of the seller's profile. Flag these mismatches for review:
- The account holder name differs from the seller's legal or business name.
- The account belongs to a third party, such as a relative or an unrelated company.
- Multiple seller accounts pay out to the same bank account.
- The payout account changes shortly before or after a seller crosses a threshold.
Micro-deposits and instant bank verification help confirm that the seller controls the account. They do not replace name and document checks.
Keep Payouts and Verification Connected
Let verification status drive payout logic. A seller with incomplete verification shouldn't receive large payouts while the review is pending. Align your workflow with your approach to holding payouts for new marketplace sellers, so the rules stay consistent and easy to explain to sellers.
Marketplace Seller Disclosure: Handling Buyer-Facing Details
Before you change any listing templates, have counsel answer these questions from the statute and FTC guidance:
- Must you disclose any seller details to buyers, and for which sellers or tiers?
- Which details are required?
- Where may or must disclosures appear: listing pages, order confirmations, the buyer's account history or elsewhere?
- Are there exceptions, and under what conditions can a seller qualify for or lose one?
- Must you give buyers a way to report suspicious activity, and through which channels?
Build It Consistently
Whatever the answers, apply them the same way across web, mobile app and email receipts. Inconsistent disclosures between channels are an easy gap to miss and a hard one to explain. If exceptions apply, document every request a seller makes, your decision and the date.
Route Buyer Reports Into One Queue
Send suspicious-listing reports to the same team that handles policing prohibited items on your marketplace. A report about a counterfeit or unsafe listing often raises processor-rules issues too.
Seller Recertification and Suspending Non-Responsive Sellers
Seller information goes stale. Confirm in the statute and FTC guidance how often sellers must recertify, how long they have to respond and what must happen if they don't. Then build a process like this:
- Stagger recertification by seller start date instead of using one company-wide date, so your team isn't swamped all at once.
- Notify sellers in advance by email and in the seller dashboard, with a clear deadline.
- Pre-fill current data so sellers confirm or edit instead of starting over.
- Re-verify changed fields, especially bank accounts, addresses and business names.
- Send reminders as the deadline approaches.
- Apply your suspension policy to sellers who don't respond within the window counsel confirms, and reinstate them once they comply.
- Log every step, including notices sent, responses received, and suspension and reinstatement dates.
Write suspension triggers into your seller agreement. Typical triggers include non-response, false information and failure to meet disclosure obligations. Putting them in writing means enforcement doesn't surprise anyone.
Keep suspension separate from refund and dispute handling. A suspended seller may still have open orders, returns and chargebacks. Your systems should keep processing those so buyers aren't stranded and you aren't left absorbing refunds after a seller has already been paid.
INFORM Act Enforcement and Penalties: What to Confirm
Enforcement exposure is a question for counsel. Ask them to walk you through:
- Which federal and state authorities can enforce the law.
- How violations are treated and how penalties are calculated, including whether they can accrue per violation.
- How current penalty amounts are set and adjusted.
- How the federal law interacts with any state laws covering similar ground.
Whatever the answers, your practical risk usually comes from operational gaps:
- No reliable system for detecting when sellers fall within scope.
- "Verification" that means collecting data without checking it.
- Missing or inconsistent buyer disclosures across channels.
- No record of recertification notices, responses and suspensions.
Good documentation is your best defense. If a regulator asks how you handled a specific seller, you should be able to produce a complete timeline within days, not weeks.
INFORM Act Checklist for Marketplace Operators
| Area | Confirm With Counsel | Operational Control |
|---|---|---|
| Thresholds | Definitions, look-back period, tiers, qualifying transactions | Automated rolling activity tracking with early flags |
| Collection | Required data fields and deadlines | Information requests triggered when sellers qualify |
| Verification | Acceptable documents and methods | Written review policy; name matching across ID, tax and bank records |
| Bank data | Whether and how bank data supports verification; third-party storage | Written retrieval and change-notification terms with your provider |
| Disclosure | Whether disclosure applies, to which sellers, which details, where, and any exceptions | Consistent display across web, app and receipts; exception log |
| Reporting | Any required buyer reporting channels | Single queue shared with listing enforcement |
| Recertification | Frequency and response windows | Staggered notices, reminders and re-verification |
| Suspension | Required triggers and timing | Seller agreement terms; refunds and disputes keep flowing |
| Security | Any data-use limits | Encryption, access controls and retention rules |
| Enforcement | Enforcing authorities, penalties and state interaction | Complete, retrievable logs for every covered seller |
Next Steps
Start by mapping where seller data lives today: onboarding forms, your processor, your payout provider and your tax reporting. Much of it overlaps with what you need for 1099-K reporting on marketplace sellers, so aim for one seller record that serves both purposes. Then read the statute and the FTC's business guidance, and book time with counsel to fill in the "Confirm With Counsel" column above.
Next, review your payment setup. MannyPay provides online payment processing for e-commerce businesses, payment gateways and integrations, and merchant accounts for low- and high-risk businesses. Request a free quote from MannyPay, and a specialist will respond within one business day to discuss your processing setup.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


