US 1099-DA backup withholding: the 24% rule crypto brokers face
1099-DA is not only a reporting form. Miss a valid TIN and US brokers can owe 24% backup withholding. How the two obligations connect, and how to avoid it.
People usually file Form 1099-DA under "reporting": US crypto brokers report customer disposals of digital assets to the IRS. True enough. But there's a second obligation sitting right beside it, easy to miss and able to cost the broker real money. Backup withholding. This guide covers what it is, what sets it off, and why the cleanest way to dodge it is the same TIN discipline that produces a clean 1099-DA.
What backup withholding is
In the US, when a payee doesn't hand over a correct taxpayer identification number, or the IRS notifies the payer of a mismatch, the payer can be required to withhold a flat 24% of reportable payments and send it to the IRS. This is an old rule that runs across many kinds of reportable income, and crypto brokers inherit it the moment they enter the 1099 world. The withholding isn't a penalty on the user. It's an obligation on the broker, and a broker who fails to withhold when required can end up on the hook for the amount.
What actually triggers it
It comes down to a TIN problem: a missing TIN, one that's plainly wrong, or a mismatch the IRS flags through a B-notice. You collect the TIN on a Form W-9 and, in a solid setup, run it through TIN matching before you lean on it. That's the same data point reporting runs on, and that's the link worth noticing: the TIN validation you do for CARF onboarding is basically the same check that keeps you clear of backup withholding, just under a different regime. Fail it and you've got both a reporting problem and a withholding liability.
Two layers, one dataset
For a broker with US users, this is a domestic layer sitting under the global one. CARF and DAC8 cover cross-border reporting; the US 1099-DA obligation, backup withholding included, is the American piece CARF leaves out. Both run off the same customer and transaction data, which is the case against treating them as separate projects with separate vendors.
Avoiding it by design
The clean setup validates TINs once, at onboarding, and reuses that result for both the 1099-DA filing and the backup-withholding decision. A bad or missing TIN surfaces while the user can still fix it, not at year end when 24% starts coming off payments. It also handles the B-notice flow, switching withholding on and later off as the IRS status changes.
Handling both from one place
Our platform runs 1099-DA reporting and CARF and DAC8 on one data layer, and the same withholding engine behind Austrian KESt generalises to a rule like the 24% backup rate, so US brokers cover both the reporting and the withholding from one integration. The IRS digital assets guidance is the primary source for the US rules.
