Stripe Tax is a calculation engine, not a liability shield. The seller of record still owes the tax, files the returns, and gets the audit notice — that's you, not Stripe. A Merchant of Record (MoR) like Macropay becomes the legal seller, so tax sits on our balance sheet, not yours. On a $10M GMV business, the difference between "Stripe + Stripe Tax" and "Macropay MoR" is roughly $50k/yr in saved compliance cost and $0 vs. $1.2M in accrued tax liability on your books.
If you sell software to a small US business in Seattle, you charge them roughly 10.35% in combined state and local sales tax. Stripe Tax will compute that for you in 80 milliseconds. What it will not do is owe that 10.35% to the Washington Department of Revenue. You will.
This is the most consistently misunderstood thing about every modern payment stack: the company at the bottom of the receipt — the "seller of record" — is liable for every tax, refund, chargeback rule, and consumer protection law in the buyer's jurisdiction. Stripe is a payment processor. Stripe Tax is a calculator. Neither of them is the seller. The seller is whoever signed up for the account.
For an AI inference company billing $4 a month for chat and $400 a month for an annual API plan, that distinction is not academic. It is the difference between a 3-engineer team shipping product and a 3-engineer team responding to a Texas Comptroller audit notice on a Friday at 5pm.
What Stripe Tax actually does
Stripe Tax does four things well:
- Calculates the correct combined rate for the buyer's address at the moment of checkout, including state, county, city, and special district overlays.
- Categorises products against the SaaS / digital goods / SST taxability matrix per jurisdiction (Texas treats SaaS as 80% taxable; New York doesn't).
- Reports: gives you a monthly export of taxable sales per jurisdiction, ready to dump into Avalara or hand to your accountant.
- Charges 0.5% of every transaction it touches, on top of Stripe's base 2.9% + $0.30.
What Stripe Tax does not do, ever:
- Register your business in any jurisdiction.
- File your sales tax returns. (Stripe Tax Filing exists in private beta in a handful of states. It does not change the legal seller.)
- Pay the tax on your behalf to the state.
- Absorb the audit liability.
- Handle the buyer's exemption certificate workflow.
- Defend you if a state argues you crossed nexus a year earlier than you registered.
Stripe Tax is the tax equivalent of asking Stripe Atlas to incorporate your company. It computes the rate. The legal entity that owes the money is still you.
Who owes the tax — and where it comes from
Sales tax in the US is a destination-based, economic-nexus-triggered obligation. Three pieces matter:
1. The seller of record
Whoever the buyer is paying — i.e. the entity on the credit card receipt and the invoice — is the seller of record. That entity is responsible for collecting the right tax, remitting it to the right authority, and proving it did both, in audit. If you're running Stripe in your own corporate name, that's you.
2. Nexus
A state can only tax you if you have nexus there. Pre-2018, nexus essentially meant physical presence. Post-Wayfair, nexus is triggered by economic activity — usually $100,000 in annual sales OR 200 separate transactions into the state. Some states are lower (Kansas: $0), some higher (California: $500k).
3. Product taxability
SaaS is taxable in roughly 25 US states, partially taxable in 8, and exempt in the rest. AI inference billed by token is a gray area in most. Most states have not written explicit guidance on usage-based AI billing, which means their default classification applies — and their default for software-as-a-service is generally taxable.
Economic nexus, briefly — and where AI companies trip
For AI inference companies with prosumer pricing ($4–$20 per seat) the 200-transaction threshold is the killer. Three months of Twitter virality in Texas, you're past 200 transactions, you've owed sales tax since transaction #201, and Stripe Tax has been quietly logging it for you the whole time. The bill, retroactive to the day you crossed nexus, is yours.
A common pattern we see: an AI company crosses nexus in 4–7 states in their first 12 months, doesn't register, doesn't collect, and finds out 9 months later in a diligence call with a Series A lead. The catch-up bill, including penalties and interest, is typically 2–4× the original tax owed.
The 1099-K trap — and why "but Stripe holds the money" doesn't save you
There's a recurring belief that because Stripe holds funds in transit, Stripe is the seller. It is not. The IRS sends Stripe (and every other PSP) a 1099-K reporting obligation for every merchant they process for. The merchant on that 1099-K — i.e. your company — is the named seller for tax purposes at both the federal and state level. The 1099-K is the primary trail every state uses to identify unregistered sellers.
When you signed Stripe's terms, you agreed that you are the merchant. That same clause appears in Adyen, Braintree, Square, Checkout.com — every PSP, with no exceptions. Payment processors are intentionally not sellers. That's why their pricing is structured around interchange and not around taxable revenue.
What a Merchant of Record actually changes
A Merchant of Record (MoR) is not a payment processor with extra steps. It's a different legal contract.
When you sell through an MoR — Paddle, Lemon Squeezy, FastSpring, or Macropay — the MoR is the legal seller on the receipt. The buyer pays the MoR, the MoR pays you (minus fee). Three things follow from that single change:
- Tax liability transfers to the MoR. The MoR registered in the buyer's jurisdiction. The MoR computed and collected the right rate. The MoR files and remits. If a state audits the transaction, it audits the MoR, not you.
- Consumer protection / refund rules transfer too. EU distance-selling rules, UK Consumer Rights Act, India's DPDP — these all attach to the seller. If you're not the seller, you're not the entity subject to them.
- 1099-K stops being your trail. The PSP issues the 1099-K to the MoR, who reports it on their books. Your books show MoR payouts (which is ordinary B2B revenue, not consumer revenue).
"We're the seller. You're not." That single sentence is what you're paying for when you sign with an MoR. Everything else — the calculator, the filing, the audit defense — is downstream of it.
The math on a $10M GMV AI business
Let's run the numbers on a representative AI inference company:
- $10M annual GMV
- ~42% of revenue international (EU + UK + AU)
- Mixed B2C (consumer chat) and B2B (API customers)
- Operating in 14 US states above nexus thresholds
| Cost | Stripe + Stripe Tax | Macropay (MoR) |
|---|---|---|
| Card processing | $290,000 (2.9% + $0.30) | $450,000 (4.5%) |
| Stripe Tax | $50,000 (0.5% of GMV) | $0 — included |
| Intl card surcharge | $42,000 (~1% on intl) | $0 — included |
| FX spread | $63,000 (~1.5% on intl) | $0 — included |
| Tax filing (Avalara / firm) | $24,000–$60,000 | $0 — included |
| Per-txn fixed fee | $15,000 ($0.30 × 50k txns) | $25,000 ($0.50 × 50k) |
| All-in run rate | ~$484k–$520k | $475,000 |
| Sales tax owed on balance sheet | ~$1.2M accrued liability | $0 — MoR carries it |
The run-rate dollars are roughly a wash. The balance-sheet line is not. A Series A diligence team will look at the "accrued sales tax liability" figure and either discount your valuation by it (you'll write a check post-close to settle) or ask you to settle pre-close (you write a check now from your own balance sheet).
The single largest unrecognised liability we see on AI company balance sheets in 2026 is sales tax accrued during the "we'll deal with it later" phase. It is almost always there. It is almost always uncollected from customers. It is almost always going to come out of the founders' pocket if it stays.
When to switch — and when not to
Switching to an MoR is the right call when:
- You are sub-$5M ARR and any time spent on tax is time not spent on product.
- You sell internationally — the VAT/GST exposure dwarfs US sales tax cost.
- You have an upcoming financing or M&A event in the next 12 months.
- You bill consumer / prosumer at high transaction counts (the 200-transaction nexus rule).
- You sell AI inference and don't want to argue product taxability state-by-state.
Staying on Stripe + Stripe Tax is defensible when:
- You are pure US, pure B2B, pure single-state. (Rare.)
- You have an in-house tax person whose time is cheap relative to MoR fees.
- You're past $100M GMV and the MoR margin matters more than the compliance cost. (At that scale, custom Stripe Connect deals get interesting.)
For everyone else — which is most AI and SaaS companies under $50M ARR — the calculus is what it's always been: a Merchant of Record absorbs liability you don't want to carry, at a price that's competitive with what you're already spending on Stripe + Stripe Tax + Avalara + a fractional CFO's sales tax hours.
Stripe could meter our tokens. It couldn't tell us which customers were unprofitable. It also couldn't tell our auditors who owed Washington State $34,802.— Helena Park, COO, Pact Labs
If you'd rather not find out the hard way which states you crossed nexus in last quarter, run your numbers through our calculator — defaults are tuned for an AI inference company at $1.2M/month and the math comes out at about $79,000/yr saved versus a Stripe + Stripe Tax stack at the same volume.