SuperiorPayments
All insights
ComplianceFebruary 14, 20265 min read

Form 1099-K and the $600 Threshold in 2026: What Merchants and Marketplace Sellers Actually Need to Do

The 1099-K threshold landed at $600 for tax year 2026 after multiple delays. Here's the merchant-side view of what's reportable, where the operational gaps usually surface, and how to handle the customer-experience implications for marketplace sellers and small operators.

After several years of phase-ins and delays, the IRS Form 1099-K reporting threshold lands at $600 for tax year 2026 — the level originally set by the American Rescue Plan Act in 2021 and repeatedly postponed during the years since. The change has direct implications for marketplace sellers, small operators, and the merchant category broadly. The headline is that the threshold is now low enough that essentially anyone accepting meaningful card-or-marketplace payment volume will receive a 1099-K. The operator-level reality is that most established merchants are unaffected, while smaller and less-established sellers face real operational and customer-experience implications that aren't always obvious from the headlines.

This is the merchant-side view of what's reportable, what merchants and marketplace operators need to do, and where the operational gaps surface.

1. The threshold in plain terms

For payment-card transactions and third-party network transactions (the latter covering most marketplace and peer-to-peer payment platforms), payment settlement entities — payment processors, marketplaces, P2P apps — are required to issue a Form 1099-K to any payee whose total gross transaction volume exceeds $600 in the calendar year. The previous threshold was $20,000 and 200 transactions, and the gap between the two is large enough that the change effectively brings every active marketplace seller and most casual sellers into the reporting framework.

Two things matter for understanding the actual operational impact. First, this is a reporting-side change, not a tax-liability change — income that was already reportable to the IRS remains reportable. Second, the threshold is per-payee per-payment- settlement-entity, which means a seller using multiple platforms gets multiple 1099-Ks each crossing the threshold separately.

2. Where established merchants are mostly unaffected

For most operating businesses with formal accounting practices, the $600 threshold change is procedural rather than substantive. The merchant's revenue was already being reported on a 1099-K (since it easily exceeded the prior $20,000 threshold), and the merchant's tax filing already incorporated that revenue. Nothing about the actual tax calculation changes.

What does change for these merchants is the completeness of the IRS's third-party-data picture. Where reporting gaps previously existed below the old threshold (cash transactions, very small side-business volume), the new threshold closes those gaps. Merchants whose books are clean have no additional exposure. Merchants whose books have historical inconsistencies between gross processing volume and reported revenue may face increased scrutiny.

3. Where the impact is real

The operational impact concentrates in a few categories:

  • Marketplace sellers and casual operators for whom the marketplace activity has historically been below the reporting threshold. Whether the activity rises to the level of a taxable business versus a personal-use activity (where some transactions are treated as sales of personal property at a loss, often non-deductible) is now a tax-filing question for many more people.
  • Resale and consignment sellerswho frequently sell items at less than original cost. These transactions appear on a 1099-K as gross revenue but produce no taxable gain — the seller needs to claim the cost basis correctly to avoid paying tax on what wasn't income.
  • Service providers using P2P apps (handymen, tutors, gig workers, household-service providers) who've previously stayed below the threshold. The threshold change brings them definitively into the reporting framework.
  • Friends-and-family payment recipients where the payments are not income but the platform may not always distinguish business-versus-personal payment categorization correctly.

4. The merchant-side and platform-side operational gaps

For merchants and marketplace operators, the operational gaps tend to be:

  • Taxpayer information collection. Issuing a 1099-K requires the recipient's taxpayer ID. Platforms that have allowed casual sellers to operate without W-9 collection now need to capture it — before the seller crosses the threshold rather than after.
  • Backup withholding triggers.Sellers who don't provide a valid taxpayer ID become subject to 24% backup withholding on their processing volume. The customer-experience cost of that surprise is real.
  • Personal-versus-business categorization on payment platforms. Mistakes here generate 1099-Ks for personal payments that shouldn't have been reported as business activity, and the downstream cleanup with the IRS is the recipient's problem.
  • Multi-platform reconciliation. A seller receiving 1099-Ks from several platforms needs to reconcile them against actual revenue — and the platforms may not all use the same definitions of gross volume (refunds and returns are handled differently in different reporting frameworks).

5. The customer-experience implications

Marketplace operators in particular face customer-experience implications that don't exist for traditional merchants:

  • Sellers who've used the platform casually for years now receive what looks like an unexpected tax form. The platform's help center, support documentation, and customer-service scripts all need to handle the question.
  • Sellers with cost-basis issues (resale at a loss) may push back on the platform for "reporting revenue I didn't earn." The platform isn't doing anything wrong — but the customer-perception cost is real and the communication burden lands on the platform.
  • The reporting timing — 1099-K issued in January for the prior tax year — concentrates customer-service volume around tax season, requiring operational capacity planning.

6. The merchant-side checklist

  • For traditional merchants: verify your gross processing volume reconciles to your reported revenue. The 1099-K matching is happening earlier and more comprehensively now.
  • For marketplace operators: audit your taxpayer-ID collection coverage and backup withholding triggers. Build the customer-service capacity for the seller-facing tax-form questions.
  • For platforms supporting personal-versus- business categorization: review the categorization defaults and edge cases — the friends-and-family payment misclassification scenarios are where customer pain concentrates.
  • For all operators: the reporting framework is unlikely to retreat. Treating the $600 threshold as durable rather than as a continually-postponed deadline is the right operational posture.

How Superior Payments helps

Superior's gateway and merchant-side tools handle 1099-K issuance, taxpayer-ID collection, and backup withholding automatically — including the multi-entity reporting scenarios that come up for merchants operating across multiple legal structures. For marketplace operators, our integration team can review your platform's seller-onboarding flow against the 2026 framework and surface the gaps before tax season exposes them.

Stay ahead of the changes.

Superior AI monitors the card networks for you and surfaces only what matters to your portfolio.