Stripe Tax for SaaS & Digital Goods — Limitations 2026
Stripe Tax solves one problem cleanly: it calculates the applicable sales tax rate on a transaction at the moment the charge is processed and adds it to the customer’s total. For sellers who route all revenue through Stripe, this is a meaningful convenience.
For digital goods and SaaS sellers — who often operate across multiple billing systems, sell in states with inconsistent digital taxability rules, and face rapid product evolution — Stripe Tax’s limitations create real audit exposure.
The Fragmented Taxability of Digital Goods
Section titled “The Fragmented Taxability of Digital Goods”Physical goods have decades of case law and administrative guidance behind their taxability determinations. Digital goods do not. Each state has independently decided whether and how to tax software, SaaS, digital downloads, ebooks, streaming services, and online courses — and reached very different conclusions.
States that tax SaaS and digital downloads:
| State | SaaS | Digital Downloads | Notes |
|---|---|---|---|
| Texas | Yes (20% of SaaS) | Yes | Only 20% of SaaS revenue is taxable as a “data processing service” — unique rule |
| New York | Yes | Yes | Cloud-based software generally taxable |
| Washington | Yes | Yes | Broad digital goods definition; active enforcement |
| Kentucky | Yes | Yes | Expanded taxability in 2022 |
| Pennsylvania | Yes | Yes | Downloaded software taxable; some SaaS disputed |
| Nebraska | Yes | Yes | |
| Wisconsin | Yes | Yes | |
| Connecticut | Yes | Yes | |
| Colorado | Yes | Yes | Added digital goods in 2022 |
| Minnesota | Yes | Yes | |
| South Dakota | Yes | Yes | |
| Rhode Island | Yes | Yes | |
| Indiana | Yes | Yes | |
| Iowa | Yes | Yes | |
| Tennessee | Yes | Yes | |
| Vermont | Yes | Yes | |
| West Virginia | Yes | Yes |
States that generally do NOT tax SaaS or digital downloads:
| State | SaaS | Digital Downloads | Notes |
|---|---|---|---|
| California | No | No | |
| Florida | No | Partial | Downloaded software sometimes taxable |
| Illinois | No | No | |
| Virginia | No | No | |
| Arizona | No | No | |
| Michigan | No | No | |
| Missouri | No | No | |
| Nevada | No | No | |
| New Jersey | Partial | Partial | Complex rules; some SaaS taxable |
| Massachusetts | Partial | Partial | Prewritten software taxable; custom SaaS disputed |
The classification matters enormously. A SaaS product generating $200,000 of annual revenue from Texas customers produces a very different tax obligation than the same revenue from California customers.
Texas’s 20% Rule deserves particular note. Texas taxes SaaS as a “data processing service” at 6.25% state + local rates, but only on 20% of the charge. This is unique to Texas and must be configured explicitly — most generic tax tools will not apply this correctly without custom product classification.
What Stripe Tax Actually Does
Section titled “What Stripe Tax Actually Does”Stripe Tax is activated in your Stripe dashboard and assigned to your products via product tax codes. When a charge is processed, Stripe looks up the rate for the customer’s billing address and the assigned product code, applies the rate, and includes the tax amount in the charge.
For sellers who do everything through Stripe, this covers the calculation step reliably.
What Stripe Tax does not do:
- It does not register you with state tax authorities
- It does not file returns or remit tax to states
- It does not monitor nexus thresholds across channels outside Stripe
- It does not automatically apply state-specific product classification nuances (like Texas’s 20% rule) without your explicit configuration
- It does not handle nexus for invoices issued outside Stripe (e.g., via your own billing system, via wire transfer, or through a reseller)
The Nexus Tracking Gap
Section titled “The Nexus Tracking Gap”Stripe Tax tracks your economic nexus based only on revenue processed through Stripe. This creates a critical blind spot for any business that receives revenue through multiple processors or channels.
Common multi-processor scenarios:
- SaaS + physical merchandise: Your SaaS subscription is billed via Stripe; your physical product sales go through Shopify Payments. Neither system sees the combined total.
- Enterprise contracts via invoice: High-value customers pay by ACH, wire, or check against invoices issued in your ERP or accounting system. None of this revenue appears in Stripe.
- Multiple Stripe accounts: Some businesses run separate Stripe accounts for different products or regions. Stripe Tax does not aggregate across accounts.
- Reseller or distributor channels: Revenue that flows through a reseller does not appear in your Stripe account, but it may still count toward your economic nexus thresholds.
- PayPal, Braintree, Square, or other processors: Revenue through any non-Stripe processor is invisible to Stripe Tax’s nexus tracking.
The audit risk: If a state tax authority audits your business, it will examine your total revenue into that state — from all sources. If your Stripe-reported nexus position says you are below threshold but your combined-channel revenue is above it, you face uncollected tax liability for the gap period, plus penalties and interest.
Product Tax Code Configuration in Stripe
Section titled “Product Tax Code Configuration in Stripe”Stripe uses a taxonomy of product tax codes (PTCs) to determine taxability by product type and state. The most relevant codes for digital product sellers:
| Code | Description |
|---|---|
txcd_10000000 | General — tangible personal property |
txcd_20030000 | Software as a Service (SaaS) |
txcd_20060000 | Digital audio/visual works |
txcd_20070000 | Electronically delivered software (downloaded) |
txcd_20090000 | Digital books / ebooks |
txcd_10103000 | Online courses / educational services |
If you do not assign a PTC to your products, Stripe applies a generic fallback that may misclassify your products. For example, assigning txcd_20030000 (SaaS) to a product that is actually a perpetual software license would result in incorrect taxability determinations in several states.
Manual verification is required: After configuring PTCs, test transactions from addresses in your key revenue states and verify that Stripe is applying the rate (or zero rate) you expect based on that state’s law for your specific product type.
Multi-Product Businesses and Bundle Taxability
Section titled “Multi-Product Businesses and Bundle Taxability”Many SaaS companies offer bundled products — a software subscription that includes training resources, downloadable templates, and live support. How a bundle is taxed depends on:
- Whether the state taxes the bundle’s dominant component — or requires unbundling
- Vendor vs. true object test — some states look at the primary purpose of the transaction
- Separately stated pricing — some states exempt a component only if it is separately priced on the invoice
Stripe Tax cannot reason about the content of your bundles. You must configure PTCs that reflect your products’ actual taxability in each state, which may require consulting a tax attorney for complex product structures.
When You Need a Dedicated Digital Tax Compliance Layer
Section titled “When You Need a Dedicated Digital Tax Compliance Layer”Stripe Tax is sufficient if:
- All your revenue flows through Stripe
- Your products are simple and clearly classified (pure SaaS, pure physical goods)
- You are registered in all nexus states and filing returns separately
You need an additional compliance layer if:
- You receive revenue outside of Stripe (invoicing, ACH, other processors)
- You sell digital products across a mix of taxable and non-taxable states and need state-specific classification validation
- You have crossed nexus thresholds and need to file returns (Stripe Tax does not file)
- You sell internationally and need to handle both EU VAT (IOSS/OSS) and US sales tax
Tools that handle digital goods classification and filing alongside Stripe:
- Anrok — purpose-built for SaaS and digital subscriptions; integrates with Stripe Billing, Chargebee, and Recurly; tracks multi-channel nexus; handles US sales tax and EU VAT place-of-supply logic. See Stripe Tax vs Anrok for a full comparison.
- Quaderno — payment-processor-agnostic; handles EU VAT (OSS/IOSS) and US sales tax across Shopify, WooCommerce, Stripe, and PayPal in a single dashboard; managed filing available. See Stripe Tax vs Quaderno for a full comparison.
- Avalara — enterprise-grade; broadest coverage for complex digital goods classification across all states and international jurisdictions. See Stripe Tax vs Avalara for a full comparison.
- Taxually — EU and UK VAT filing specialist; handles Non-Union OSS registration and filing for digital services sellers; strong for businesses with heavy EU exposure alongside US obligations. See Stripe Tax vs Taxually for a full comparison.
- TaxJar — now Stripe-owned; reasonable digital goods support; AutoFile for US return submission; tightly integrated with Stripe Dashboard but limited for multi-processor businesses.
Common Mistakes
Section titled “Common Mistakes”- Assuming Stripe Tax handles compliance, not just calculation. Tax collected by Stripe Tax still needs to be reported and remitted via state returns — Stripe does not do this.
- Not assigning product tax codes. Without explicit PTCs, Stripe applies generic rules that frequently misclassify digital goods.
- Treating all SaaS identically across states. Texas’s 20% rule is one example; several states have unique SaaS treatments that require state-specific configuration.
- Ignoring revenue outside Stripe for nexus monitoring. Enterprise invoices, ACH payments, and revenue through other processors all count toward your nexus thresholds.
- Not re-evaluating classification when product features change. A SaaS tool that adds downloadable exports or AI processing may change its taxability classification in several states.