For payment platforms and enterprise compliance teams, Form 1099-K sits at the intersection of high-volume transaction data, per-platform threshold tracking, backup withholding obligations, and state-level rules that diverge from the federal standard. The 2025 threshold changes added a recalibration requirement on top of an already complex reporting structure.
The compliance challenge is not the headline threshold. It is the operational detail: which payment types fall under which rules, when backup withholding overrides the threshold, which states require reporting below the federal level, and how per-platform aggregation works across your network. This guide addresses each.
What Form 1099-K Reports and Who Must File
Form 1099-K reports payments for goods and services made through payment settlement entities (PSEs). Two distinct categories apply, with materially different threshold rules.
Third-Party Settlement Organizations (TPSOs) settle third-party network transactions: payment apps, online marketplaces, and platforms facilitating peer-to-peer or business-to-consumer payments (PayPal, Venmo for Business, Stripe, Square, eBay, Etsy, Amazon Marketplace).
Merchant Acquiring Entities (MAEs) are banks or organizations with the contractual obligation to settle payment card transactions, covering credit card processors, debit card processors, and stored-value card networks. The threshold rules that apply to TPSOs do not apply to MAEs.
The OBBBA Threshold Change: What It Means for TPSOs
The One Big Beautiful Bill Act (OBBBA), signed July 4, 2025, permanently restored the TPSO reporting threshold that applied before the American Rescue Plan Act of 2021 altered it. Per IRS Fact Sheet FS-2025-08, TPSOs are not required to file Forms 1099-K unless gross reportable payment transactions to a payee exceed $20,000 as well as the number of transactions exceeds 200.
The restoration is retroactive to tax years beginning after December 31, 2021. Platforms that issued 1099-Ks under lower transitional thresholds do not need to amend or withdraw them; those that did not file under ARPA rules will not face penalties.
The threshold change reduces TPSO form volume. It does not simplify the underlying compliance program. Backup withholding obligations, state-level requirements, and per-platform tracking all remain active regardless of where the federal threshold sits.
Payment Card Transactions: No Threshold Applies
The most consequential compliance distinction in the 1099-K rules is independent of the OBBBA: no threshold applies to payment card transactions. MAEs must issue Form 1099-K to every merchant that accepts credit, debit, or stored-value cards, covering every dollar of volume. A merchant receiving $50 in card payments receives a 1099-K.
A platform combining card-based and network-based settlement must segregate volumes for threshold calculation purposes. Applying the TPSO threshold to card transaction volume that carries no threshold is a systemic compliance error.
| Transaction type | Filer category | Federal threshold | Notes |
| Payment card (credit, debit, stored value) | Merchant Acquiring Entity | None; all amounts reportable | Applies regardless of transaction count |
| Third-party network (apps, marketplaces) | TPSO | Over $20,000 and more than 200 transactions | Both conditions must be met; per-platform |
Per-Platform Aggregation: How the Threshold Applies
The $20,000 and 200-transaction threshold applies per platform. A payee receiving $15,000 through Platform A and $10,000 through Platform B has not crossed the threshold on either and receives no 1099-K from either, even though the combined volume exceeds $20,000.
When the same payee is active on multiple platforms operated by the same parent company, determine whether each platform is a separate TPSO or whether the parent aggregates across platforms for reporting. That determination depends on contractual structure, not organizational hierarchy.
Backup Withholding: The Obligation That Overrides the Threshold
Backup withholding operates independently of the reporting threshold. If a TPSO applied backup withholding under IRC Section 3406(a) for a payee, it must file a Form 945 and a Form 1099-K with the IRS regardless of transaction volume.
Backup withholding at 24% is required when a payee fails to provide a valid TIN, provides an incorrect TIN, or the IRS notifies the platform of a name/TIN mismatch through the B-Notice process. Every payee receiving payments for goods or services requires a validated TIN on file. The OBBBA threshold change reduces form volume; it does not reduce the scope of TIN validation required.
Payee Identity Management at Platform Scale
Payee identity management is a continuous operational function.
- W-9 at onboarding: Require Form W-9 from all US persons and entities before activating accounts for payment receipt. No W-9, no settlement.
- W-8 for foreign merchants: Non-US merchants require Form W-8BEN or W-8BEN-E and may be subject to 30% withholding unless a tax treaty applies.
- Bulk TIN matching: Run the full active payee roster through IRS TIN Matching before Q4. 1099Pro’s TIN matching workflow flags mismatches before the 1099-K production run.
- Annual re-verification: Payees who update name, EIN, or address must re-submit a W-9 before settlement resumes.
- Backup withholding trigger: Payees failing to provide a valid TIN after B-Notice solicitation require 24% withholding on future settlements, enforced through real-time logic in your settlement engine.
1099-K Box-by-Box Compliance Guide for Platform Filers
Form 1099-K has a simpler box structure than 1099-B or 1099-INT, but each field carries compliance weight at platform scale.
| Box | What it reports | Compliance note | Detail |
| 1a | Gross amount of payment card / third-party transactions | Report GROSS payments. Do not net out refunds or fees. | Refunds reported separately in Box 1b. |
| 1b | Card Not Present (CNP) transactions | Relevant for MAEs distinguishing card-present vs online transactions. | |
| 2 | Merchant category code (MCC) | Required for MAE filers. | Must be maintained in payee records. |
| 3 | Number of payment transactions | Report total transaction count for the year. | |
| 4 | Federal income tax withheld (backup withholding) | Report 24% backup withholding if applicable. | Requires Form 945 at year-end. |
| 5a-l | Monthly gross amount breakdown | Monthly detail required. | Critical for platforms with strong seasonality. |
State-Level Reporting: Where Federal Clarity Ends
The OBBBA restored a clear federal threshold; it did not resolve state compliance. Multiple states maintain thresholds below the federal standard and do not automatically conform to federal changes. Confirmed current thresholds per IRS Fact Sheet FS-2025-08:
- Massachusetts, Maryland, Virginia, Vermont, Washington DC: $600
- New Jersey: $1,000
- Illinois: $1,000 with four or more transactions
A payee with $8,000 in annual platform payments may be below the federal threshold but above the state threshold. The platform must apply the correct state-level rule and issue a state-specific 1099-K with no federal counterpart.
States not in the IRS Combined Federal/State Filing (CF/SF) Program require separate direct filings. CF/SF participation does not resolve compliance in states with non-conforming thresholds. Florida and Tennessee are examples of non-participating states. Payee segmentation must capture state of residence or business operation, and threshold monitoring logic must run federal and state calculations in parallel. A jurisdiction-by-jurisdiction review is an annual standing task.
Filing Deadlines and eFile Requirements
| Obligation | 2027 deadline (TY2026) | Notes |
| Recipient copy furnished | February 1, 2027 | January 31 falls on Sunday; moves to next business day |
| Paper filing with IRS | March 1, 2027 | February 28 falls on Sunday; moves to next business day |
| eFile with IRS | March 31, 2027 | Mandatory for organizations filing 10 or more total information returns. |
The eFile mandate applies to organizations filing 10 or more total information returns in the calendar year, aggregated across all return types. For enterprise platforms, that threshold is crossed immediately. For a full deadline breakdown, see When Are 1099s Due?.
Corrections follow the standard workflow. Type 1 errors (amount, code, or data) require a corrected form with the “CORRECTED” box checked. Type 2 errors (recipient name or TIN) require a two-step process: void the original, then file a new original with correct information. For penalty details, see IRS Penalties for Late 1099 Filing and Corrections.
Managing 1099-K Disputes and Corrections at Scale
At enterprise scale, a significant percentage of 1099-Ks will require post-issuance action. Four correction categories apply.
- Merchant TIN disputes: Require W-9 re-submission, verify via TIN matching, and issue a corrected 1099-K within 30 days if the error is confirmed.
- Gross amount disputes: Reconcile against platform transaction logs and issue a corrected form if substantiated.
- Duplicate 1099-Ks: Implement deduplication logic for merchants operating across multiple accounts or platforms.
- VOID forms: Where a 1099-K was issued in error, file a VOID with the IRS using the original form data.
Enterprise platforms should implement a merchant self-service portal for viewing, downloading, and disputing 1099-K data. This reduces inbound support volume and creates an audit trail that supports correction workflows.
Voluntary Filing Below the Threshold
The OBBBA threshold is a minimum requirement, not a ceiling. A TPSO may still issue a Form 1099-K below the threshold, which reduces the risk of payees mischaracterizing income in states where the platform has no federal obligation, but the state still taxes it.
The countervailing risk is the form volume and correction exposure. This decision should be made at the organizational level, documented, and applied consistently across the payee file. If backup withholding was applied to any payee below the threshold, that payee requires a form regardless of policy.
Building a 1099-K Compliance Program That Holds
The OBBBA settles the TPSO federal filing question. It does not reduce the compliance infrastructure required to operate correctly. Backup withholding obligations, the zero-threshold rule for payment card transactions, and state-level requirements all operate independently of the federal TPSO threshold.
Start the compliance review in Q4: audit your payee TIN file, confirm backup withholding workflows, identify payees approaching state thresholds, and verify per-platform aggregation logic. For a structured checklist, see the 1099 Filing Season Prep Checklist.
Start a free trial now to see how 1099Pro supports enterprise payment platform 1099-K compliance with bulk TIN matching, high-volume IRIS transmission, state filing management, and audit-ready correction workflows.
FAQs
What is the difference between a TPSO and a merchant acquiring entity for 1099-K purposes?
A TPSO settles third-party network transactions and must report when a payee exceeds $20,000 and more than 200 transactions per platform. A merchant acquiring entity settles payment card transactions with no threshold: all card volume is reportable at any amount. Platforms processing both transaction types must apply distinct rules to each.
Do the $20,000 and 200-transaction thresholds apply across all platforms a payee uses?
No. The thresholds apply per platform. A payee receiving $15,000 on one platform and $10,000 on another has not crossed the threshold on either. Combined volume across platforms is not aggregated for federal reporting purposes.
Does backup withholding trigger a 1099-K filing obligation regardless of the threshold?
Yes. If backup withholding was applied under IRC Section 3406(a), the TPSO must file a Form 1099-K regardless of transaction volume. A Form 945 must also be filed with the IRS for the total amount withheld.
How should enterprise platforms handle payees in states with lower 1099-K thresholds?
State requirements operate independently of the federal threshold. A payee below the federal level may still trigger a state filing obligation. Conduct a jurisdiction-by-jurisdiction review annually and build state threshold logic into payee segmentation. CF/SF Program participation does not resolve compliance in non-conforming states.