At a Glance
Payment processors face one of the highest-impact FIRE-to-IRIS transitions due to massive 1099-K volumes and evolving reporting thresholds. The FIRE system shuts down December 31, 2026 — all 1099-K filing moves to IRIS. BoomTax accepts your existing FIRE-format files and handles the IRIS conversion automatically. No changes to your reporting systems required.
This article is part of our IRS IRIS Resource Center
— your complete guide to the FIRE→IRIS migration.
Why Payment Processors Face the Biggest FIRE-to-IRIS Challenge
Payment processors, payment settlement entities (PSEs), and electronic payment facilitators are among the highest-volume 1099 filers in the United States. A single mid-size payment processor may file hundreds of thousands or millions of 1099-K forms annually — one for every merchant or payee who exceeds the reporting threshold. Large platforms like payment aggregators, marketplace facilitators, and third-party settlement organizations can file tens of millions.
For over two decades, these filings flowed through a well-tested pipeline: your transaction reporting system generates a Publication 1220-format flat file, your operations team uploads it to the IRS FIRE system, and you receive an acknowledgment. On December 31, 2026, that pipeline permanently shuts down.
The replacement — IRIS (Information Returns Intake System) — uses XML instead of fixed-width text files and requires a fundamentally different integration approach. For payment processors operating under tight regulatory deadlines and handling enormous volumes, this transition demands serious planning.
The 1099-K Reporting Threshold: A Moving Target
The FIRE-to-IRIS transition arrives at the same time as ongoing changes to the 1099-K reporting threshold, compounding the challenge for payment processors:
| Tax Year | Reporting Threshold | Impact on Filing Volume |
|---|---|---|
| Before 2022 | $20,000 and 200 transactions | Relatively limited — only high-volume merchants triggered reporting |
| 2024 | $5,000 (IRS transition year) | Significant increase in reportable payees |
| 2025 and beyond | $2,500 (phased reduction toward $600) | Massive expansion — millions of additional payees become reportable |
As thresholds drop, the number of 1099-K forms payment processors must file multiplies dramatically. A platform that filed 500,000 forms under the $20,000 threshold may need to file 5 million or more under the $600 target. This volume surge is hitting at the exact moment these filings must transition from FIRE to IRIS — a dual challenge that requires robust infrastructure.
How the Current FIRE Workflow Operates
Most payment processors have a well-established year-end reporting pipeline built around FIRE:
- Transaction aggregation: Your platform aggregates gross payment amounts per payee across the calendar year, applying the applicable threshold and backup withholding rules
- File generation: Your reporting system generates a Publication 1220-compliant flat file with T (Transmitter), A (Payer), B (Payee), C (End of Payer), and F (End of Transmission) records
- TIN validation: Payee TINs are validated against IRS records, and B-notices are issued as required
- FIRE upload: The flat file is uploaded to the FIRE system using your Transmitter Control Code (TCC)
- Acknowledgment processing: FIRE returns an acknowledgment file that your system parses to identify accepted and rejected records
- Corrections: Any errors are corrected and resubmitted through FIRE
Every component of this pipeline is affected by the move to IRIS. The file format changes from fixed-width to XML. The upload mechanism changes from FIRE's web portal to IRIS's A2A (Application-to-Application) API. The TCC is different. The acknowledgment format is different.
IRIS Filing Options for High-Volume Payment Processors
Option 1: IRIS A2A (Direct API Integration)
The IRIS A2A channel is the IRS's direct filing API for high-volume filers. It uses SOAP web services with XML payloads. For a payment processor filing millions of 1099-K forms, A2A is the only viable IRS-direct option — the IRIS Taxpayer Portal caps CSV uploads at 100 forms per file, which is entirely impractical at payment processor volumes.
Building a direct A2A integration requires:
- Applying for an IRIS TCC (45+ days, with ID.me verification and background checks)
- Developing XML generation logic that conforms to IRS IRIS schemas
- Implementing SOAP client authentication with digital certificates
- Building acknowledgment polling and error-handling workflows
- Testing through the IRS IRIS sandbox environment
- Ongoing maintenance as IRS schemas change annually
This is a significant engineering investment — typically 3 to 6 months of development work for a team familiar with IRS specifications. See our IRIS API integration guide for full technical details.
Option 2: Use BoomTax — Keep Your Existing FIRE Files
BoomTax eliminates the integration burden entirely. Keep generating the same Publication 1220-format files your reporting system already produces. Upload them to BoomTax via web interface, REST API, or SFTP. BoomTax parses the FIRE records, converts them to IRIS XML, validates against IRS schemas, and submits through IRIS on your behalf.
For payment processors, this means:
- No file format changes: Your transaction reporting system continues to generate the same output it always has
- No TCC application: BoomTax holds the IRIS Transmitter TCC and files on your behalf
- No XML development: BoomTax handles the FIRE-to-IRIS format conversion
- No schema maintenance: When the IRS updates its XML schemas, BoomTax updates — your files stay the same
- Enterprise scale: BoomTax handles millions of forms per submission with no artificial limits
Ready to discuss your enterprise compliance needs?
Our compliance experts can walk you through a customized solution for your organization.
1099-K Specifics in IRIS XML
The 1099-K has several data elements that are unique among 1099 forms and require specific attention during the FIRE-to-IRIS transition:
Third-Party Settlement Organization (TPSO) vs. Payment Card
The 1099-K distinguishes between payment card transactions (Box 1a) and third-party network transactions (Box 1a, filed by TPSOs). In the FIRE format, this distinction is encoded in specific field positions within the B record. In IRIS XML, it maps to distinct elements within the 1099-K schema. BoomTax maps these fields automatically during conversion.
Gross Amount and Monthly Breakdowns
The 1099-K requires gross payment amounts broken down by month (Boxes 5a through 5l). In Publication 1220 format, these twelve monthly amounts occupy fixed character positions. In IRIS XML, each month maps to a named element. Any discrepancy between the gross amount and the sum of monthly amounts triggers a validation error — BoomTax's pre-submission validation catches these mismatches before filing.
Transaction Counts and PSE Information
IRIS XML captures the number of payment transactions, the PSE name and phone number, and the filer type (PSE vs. EPF) in structured elements rather than fixed-width fields. Payment processors must ensure these fields are populated correctly, particularly when filing on behalf of sub-merchants through marketplace or aggregator models.
Aggregation Rules and Filing Obligations
Payment processors need to be especially careful about aggregation during the IRIS transition:
- Per-payee aggregation: Gross amounts must be aggregated across all merchant IDs for the same TIN/payee. The IRIS transition doesn't change this rule, but it's a common source of errors during system transitions
- Third-party settlement organizations must report the gross amount of reportable payment transactions — refunds, chargebacks, and adjustments are not netted unless they constitute a separate reportable event
- Electronic payment facilitators (EPFs) that contract with PSEs have specific filing responsibilities that carry forward into IRIS unchanged
- State filing: Many states require 1099-K filing through the Combined Federal/State Filing Program. IRIS supports this, but ensure your state filing workflow transitions alongside your federal filing
Migration Timeline for Payment Processors
| Timeframe | Action |
|---|---|
| Now (Q2 2026) | Audit your current FIRE filing pipeline. Identify all systems generating Publication 1220 files. Quantify current and projected 1099-K volumes under the new thresholds. |
| Q2–Q3 2026 | Establish a BoomTax enterprise account. Upload a sample FIRE file to validate format compatibility. Begin parallel testing alongside your existing FIRE workflow. |
| Q3 2026 | Conduct a full-scale test with production-representative data. Validate that monthly breakdowns, PSE information, and aggregation rules are handled correctly. Update compliance documentation. |
| Q4 2026 | Finalize the cutover plan. Train operations staff. Update internal procedures and audit documentation. FIRE shuts down December 31. |
| January 31, 2027 | First post-FIRE 1099-K filing deadline. All filing goes through IRIS. Your FIRE-format files upload to BoomTax → BoomTax files through IRIS. |
For the complete timeline, see our FIRE-to-IRIS transition timeline.
Frequently Asked Questions
IRIS replaces FIRE as the IRS's electronic filing system. Instead of uploading Publication 1220 fixed-width text files, IRIS requires XML format. For payment processors filing hundreds of thousands or millions of 1099-K forms, the only viable IRS-direct option is the IRIS A2A API — a significant engineering project. Alternatively, BoomTax accepts your existing FIRE-format files and handles the IRIS submission automatically, eliminating the need for any format changes.
Only if you plan to file directly with the IRS through the IRIS A2A channel. The IRIS TCC application takes 45 or more days and requires ID.me identity verification for responsible officials. If you use BoomTax, you do not need your own TCC — BoomTax holds the transmitter TCC and files on your behalf.
Technically yes, but it is not practical for payment processors. The IRIS Taxpayer Portal limits CSV uploads to 100 forms per file. A processor filing 500,000 1099-K forms would need 5,000 separate uploads. The portal is designed for small businesses, not high-volume filers. Payment processors should use the A2A API (direct) or an IRS-authorized provider like BoomTax.
The IRS has been phasing in a lower 1099-K threshold — moving from $20,000/200 transactions toward $600. This dramatically increases the number of forms payment processors must file, and that increased volume must now flow through IRIS instead of FIRE. The combination of higher volumes and a new filing system makes planning critical. BoomTax handles any volume, regardless of how many payees cross the reporting threshold.
Yes — if you use BoomTax. Your transaction reporting system continues to generate the same Publication 1220-format files. Instead of uploading to FIRE, you upload to BoomTax. We convert to IRIS XML and file with the IRS. No changes to your aggregation logic, file generation, or internal processes are required.
For related guidance, see our IRIS filing guides for banks and financial institutions and CPAs and accountants. For the full migration walkthrough, read how to migrate from FIRE to IRIS, or explore our high-volume bulk filing guide.
Author
Ken Ham
Founder at BoomTax
View all posts
Passionate about making tax compliance simple so businesses can focus on what matters.
BoomTax and its affiliates do not provide tax, legal, or accounting advice. This material has been prepared for informational purposes only, and is not intended to provide, and should not be relied on for, tax, legal, or accounting advice. You should consult your own tax, legal, and accounting advisors prior to engaging in any transaction.
