Sales Tax on Crypto Payments: Three Rules Every State Agrees On (and Four They Don't)

A Shopify merchant I talked to last month sells handmade ceramics out of Oregon, ships to customers in twelve states, and recently turned on crypto checkout. The question that landed in my inbox: “Do I owe sales tax when a customer in Texas pays me in USDC?”

Short answer: yes, on the same terms as if they’d paid in dollars. The conversion mechanics and the paperwork trip people up.

I’ll cover what every state agrees on (three things), where they diverge (four schools of thought), and what records keep your audit defense intact. I’ll name specific states throughout. Treat any state-specific point as a starting point, not the final word. State sales tax guidance shifts often, and most of the on-point bulletins are buried in DOR FAQ pages that don’t get indexed.

Three things every state agrees on

Three rules are universal as of 2026:

1. The taxable amount is denominated in US dollars, at fair market value at the time of sale.

It doesn’t matter whether the customer paid in Bitcoin, USDC, USDT, or anything else. The transaction has a USD-equivalent value at the moment of the sale, and that’s the number the state cares about. Sales tax is calculated on that USD figure using the rate applicable in the destination jurisdiction.

2. The state ultimately receives sales tax in US dollars, even if a crypto payment rail is available.

The default is still: collect crypto from the customer, convert at your discretion, remit USD to the state. The exception to know is Colorado, which currently allows cryptocurrency as a payment option for state taxes, including sales and use tax, through the PayPal Cryptocurrencies Hub. Even there, the crypto is converted to dollars before it reaches the Department of Revenue. The crypto rail is a payment method, not a different tax calculation. Other states have launched, revised, or paused similar programs over time, so verify the current DOR page before you plan around any state-specific option.

If the price of the underlying crypto drops between the sale and the remittance date, the state does not care. You still owe the dollar amount that was due on the sale. Crypto price volatility is your problem.

3. Economic nexus rules apply to crypto-denominated sales the same as any other sales.

Since South Dakota v. Wayfair (2018), most states have economic nexus thresholds. The common shape is $100,000 in gross sales into the state, sometimes with a transaction count threshold on top. A sale paid in crypto counts toward those thresholds at its USD value. If you cross the threshold, you owe registration, collection, and remittance even if you’ve never had a physical presence in the state.

One 2026 change worth flagging: Illinois removed its 200-transaction threshold effective January 1, 2026. It is now $100,000 in gross sales only. If you had been clearing the 200-transaction count but not the dollar threshold, you may no longer have Illinois nexus. Some low-ticket / high-volume sellers will see their Illinois exposure drop because of this.

Where states diverge: four schools of thought

What states disagree on is the character of the transaction. That affects your paperwork and the edge cases. The basic tax calculation lands at the same place either way.

School 1: Cash equivalent. A handful of states have issued specific guidance treating crypto received in payment as functionally equivalent to cash, with a conversion to USD at FMV for tax purposes. Kansas and Kentucky have both issued bulletins on this approach. New York’s Department of Taxation and Finance has guidance treating cryptocurrency payments as taxable based on FMV at sale.

Under this approach, your sales tax filing looks the same as any other: gross taxable receipts at USD value, multiplied by the applicable rate, remitted to the state. The conversion is a non-event for sales tax purposes.

School 2: Barter transaction. Some states historically treated crypto-for-goods as a barter exchange (one property for another), with each side measured at FMV. The sales tax conclusion ends up identical (taxable at FMV at sale), but the framing affects how you document the transaction and how secondary taxes (use tax, gross receipts tax) may flow. Washington’s gross-receipts B&O tax is one example where practitioners have historically used the barter framing.

School 3: Silent / general principles apply. Most states haven’t issued crypto-specific sales tax guidance at all. Their position is implicit: digital assets are property, accepting property in payment is taxable on the FMV of the goods sold, and standard rules govern. The day-to-day math matches the cash-equivalent approach. The edge cases (refund handling, basis adjustments, multi-step transactions) are entirely up to interpretation.

School 4: Crypto payment rails for remittance. Colorado currently allows crypto payments for state taxes through a third-party conversion flow that sends dollars to the Department of Revenue. This is an alternative payment method. The underlying tax calculation does not change. Other state programs have been proposed, revised, or paused over time, so verify current availability with the relevant DOR before planning around it.

State-by-state quick reference (verify before relying on)

State	Approach (as commonly applied 2026)	Key thing to verify
California	General principles; FMV-based, USD remittance	BOE/CDTFA crypto guidance is sparse; talk to your sales tax preparer
New York	Cash-equivalent FMV; sale rate at destination	NY Tax Bulletin TB-ST series; confirm latest update
Texas	General principles; FMV USD-equivalent	No public crypto-specific Comptroller bulletin as of writing
Florida	General principles; FMV USD-equivalent	DOR has not issued crypto-specific letter rulings; rely on general property/barter analysis
Kansas	Cash-equivalent (explicit guidance)	KDOR Notice on cryptocurrency acceptance
Kentucky	Cash-equivalent (explicit guidance)	Kentucky DOR guidance
Washington	Barter framing historically; B&O on gross receipts	DOR’s barter-exchange guidance
Illinois	General principles; threshold $100K only after 2026-01-01	ROT/UseTax bulletins; threshold change
Colorado	Crypto accepted for state tax payments through PayPal conversion	CDOR program status, fees, account restrictions; remittance only, not calculation

To be blunt: every entry in this table is a starting point, not a tax position you can take to court. State guidance shifts. Department of Revenue bulletins get superseded. Letter rulings change scope. Before you take a position on a specific state, your sales tax preparer or counsel should pull the current bulletin and confirm.

Three documentation challenges unique to crypto

Crypto receipts create three documentation problems you don’t have with card payments:

Challenge 1: The FMV at “time of sale” question.

What is “the time of sale”? When the customer clicked checkout, when the gateway generated the invoice, when the transaction landed on-chain, or when your wallet credited the funds? These can be minutes or even hours apart on slow chains or low-fee transactions. Most states haven’t ruled on this directly. The defensible answer is one of:

• The block timestamp where the customer’s payment was confirmed (on-chain truth)
• The invoice generation timestamp on your gateway (consistent with how card sales are treated)

Pick one. Document it as your policy. Apply it consistently. Don’t switch mid-quarter to pick whichever number is lower.

Challenge 2: Which price source for FMV.

USDC is roughly $1, but exact-second prices vary. BTC at any given second has a different price on every major exchange. Your sales tax position depends on which price you use. Defensible options:

• A specific major exchange’s last-trade or mid-price (Coinbase, Kraken, Binance.US)
• An aggregator’s index price (CoinMarketCap, CoinGecko, CoinDesk reference rates)
• Your gateway’s quoted exchange rate at invoice generation

Same rule: pick one, document it, apply consistently across all sales for the period.

Challenge 3: Records that an auditor can verify.

An auditor at any state DOR will eventually ask: “Show me the transaction.” For crypto, the answer is the on-chain record: transaction hash, block number, timestamp, receiving wallet, and the price source you used. A non-custodial setup where the funds flow directly to your wallet (Aurpay and other non-custodial gateways operate this way) produces this trail by default. The tx hash is your audit defense.

What about refunds?

Same logic as any other sales tax return: when you refund a customer, the sales tax collected on that sale is no longer owed to the state. The state-specific mechanic for clawing back already-remitted sales tax varies. Most states allow a credit on your next return. Some require an amendment. A few impose time limits on the refund-driven adjustment.

The crypto-specific wrinkle: if you refund in the same crypto the customer paid (usually the simplest path, because crypto-to-USD-to-crypto roundtrips add friction), the USD value of what you send back may differ from what you originally received. The sales tax credit is on the original USD-denominated sales tax. It is not the current USD value of the refund crypto. Don’t confuse the two.

Marketplaces and facilitator rules

If you sell through Shopify, BigCommerce, WooCommerce, or another platform that is not a marketplace facilitator under state law, the sales tax obligation is entirely on you, regardless of how the customer paid. Crypto payments do not transfer the obligation to the gateway or to the platform.

If you sell through a marketplace facilitator (Amazon, eBay, Etsy, certain Walmart and Target storefronts), the marketplace generally collects and remits sales tax for you under state marketplace facilitator laws. Most marketplaces don’t yet accept crypto payments directly. If you accept crypto on a non-marketplace channel (your own Shopify store) but also sell through Amazon, the marketplace handles Amazon-side sales tax. The crypto-on-Shopify side is yours.

Nexus implications of crypto-only customers

One question I get a lot: “If I only sell to crypto-native customers in a state, does that change my nexus analysis?”

No. Economic nexus is about USD volume of sales into the state, regardless of payment method. A crypto-paying customer is the same as a card-paying customer for nexus purposes. The volume threshold is the volume threshold.

The exception worth flagging: some states’ click-through nexus and affiliate nexus rules can be triggered by digital advertising or referral relationships in the state. If your only way of reaching customers in a state is through a crypto-native advertising channel that has a presence in that state, you may have nexus exposure through that channel separately from your sales volume. That one is a “talk to your tax attorney” situation. I can’t give you a generalizable answer.

The compliance stack you actually need

For most crypto-accepting merchants of any meaningful size, sales tax compliance is a three-layer stack:

1. Sales tax software (TaxJar, Avalara, Anrok, Sovos) that registers your nexus footprint, calculates rates at checkout, and files returns. Most of these can handle crypto-denominated sales as long as you feed them USD-equivalent values per transaction.
2. Reconciliation layer between your crypto gateway’s transaction list and your sales tax software’s records. This is where you make sure every crypto sale shows up at the right USD value in the right state’s nexus calculation.
3. Documented FMV policy describing which price source and which timestamp convention you use, plus the supporting per-transaction records (tx hash + block timestamp + USD value + receiving wallet).

Miss any layer and the whole stack wobbles. The most common gap I see is layer three: merchants who outsourced layer one and assumed the software handled everything, then discovered at audit that nobody had documented the FMV methodology.

Three questions to bring to your sales tax preparer

1. For each state where I have nexus, has the DOR issued specific guidance on cryptocurrency-denominated sales? If not, what’s the defensible default position?
2. What’s our documented policy for FMV determination (price source and timestamp), and is it written into our sales tax compliance procedures?
3. For refunds in crypto: how do we handle the sales tax credit when the refund’s current USD value differs from the original sale’s USD value?

Sales tax on crypto is one of the more tractable parts of crypto compliance. The three universal rules cover most of what you need. The catch: documentation is unforgiving, and there is no 1099-DA-style reporting form for sales tax, which means the DOR has fewer cross-checks to lean on. Audits get more invasive when that happens. Build the documentation discipline now, while you’re not under one.

---

This article is general information for merchants and finance leads. It is not tax or legal advice, and does not establish a client relationship. State sales tax guidance varies significantly by jurisdiction and changes frequently — every state-specific point in this article should be verified against current Department of Revenue guidance before being relied on. Consult a sales tax preparer or state and local tax attorney for advice specific to your business.