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.
Pick a state to see how it treats SaaS and digital products:
Is it taxable? 50 states + DC
- Taxable 18
- Partly taxable 4
- Not taxable 24
- No sales tax 5
- Change coming
Pick a state on the map or from the list to see how it taxes SaaS and digital products, what’s changing and where the rule comes from.
Checked 6 November 2026 against each state’s guidance. Sources: Kintsugi (SaaS) and Quaderno (digital products).
Ask which states you owe →As of 6 November 2026, 21 states and DC tax SaaS (4 of them only in some cases), 24 don’t, and 5 have no statewide sales tax. Changes that haven’t started yet are flagged in the table.
| State | SaaS | E-books, music, video | What to know |
|---|---|---|---|
| Alabama | Not taxable | Taxable | Not taxed in practice: Alabama taxes software licenses, but has no rule or ruling that reaches software customers only access online. Ask the Department of Revenue if your sales there are large. |
| Alaska | No sales tax | No sales tax | No state sales tax, but many cities and boroughs have one. Those in the Alaska Remote Seller Sales Tax Commission tax SaaS, streaming and downloads sold by remote sellers. |
| Arizona | Taxable | Taxable | Taxable under the transaction privilege tax (TPT), which treats access to software as renting it out. Cities add their own tax on top. |
| Arkansas | Not taxable | Taxable | Not taxable: software delivered electronically, including access online, is outside Arkansas sales tax. |
| California | Not taxable | Not taxable | Not taxable until 31 December 2026. From 1 January 2027, prewritten software is taxable however it’s delivered, including SaaS. From 1 January 2027: SaaS and downloaded software become taxable (SB 122). |
| Colorado | Not taxable | Taxable | Not taxable by the state until 31 December 2026, but home-rule cities such as Denver and Boulder already tax it. From 1 January 2027 the state taxes software however it’s delivered, except custom and negotiated-license software. From 1 January 2027: SaaS and downloaded software become taxable statewide (HB26-1223). |
| Connecticut | Partly taxable | Taxable | Taxable, at 1% when a business buys it for business use and at the full 6.35% for personal use. |
| Delaware | No sales tax | No sales tax | No sales tax. Delaware taxes the seller’s gross receipts instead, which isn’t charged to the customer. |
| Florida | Not taxable | Not taxable | Not taxable when nothing tangible is delivered. Software sold together with hardware is taxable. |
| Georgia | Not taxable | Partly taxable | Not taxable: Georgia law excludes remote access to software. |
| Hawaii | Taxable | Taxable | Taxable: Hawaii’s general excise tax (4%, plus a county surcharge in most counties) falls on the seller’s income from SaaS. Sellers usually pass it on. |
| Idaho | Not taxable | Partly taxable | Not taxable: software accessed remotely isn’t tangible property in Idaho. |
| Illinois | Not taxable | Not taxable | Not taxable by the state, unless the customer is given software to install. Chicago is different: its lease tax charges 15% on cloud software used in the city. |
| Indiana | Not taxable | Partly taxable | Not taxable when the customer only accesses the software online and downloads nothing. |
| Iowa | Partly taxable | Taxable | Taxable for consumers. Exempt when a business buys it only for use in its business, which covers most B2B sales; collect an exemption certificate. |
| Kansas | Not taxable | Not taxable | Not taxable when the software is hosted by the seller and the customer never receives a copy. |
| Kentucky | Taxable | Taxable | Taxable at 6% since 1 January 2023, as a “prewritten computer software access service”. |
| Louisiana | Taxable | Taxable | Taxable since 1 January 2025, at the state rate plus parish taxes. The business exemptions are narrow. |
| Maine | Not taxable | Partly taxable | Not taxable when the software runs on servers outside Maine and nothing is downloaded. If the license lets the customer download it, it’s presumed taxable. |
| Maryland | Taxable | Taxable | Taxable at 6%, or 3% when a business uses it only in its own enterprise systems (since 1 July 2025). |
| Massachusetts | Taxable | Not taxable | Taxable at 6.25% as standardized software. Business customers using it in several states can apportion the tax. |
| Michigan | Not taxable | Not taxable | Not taxable when it runs entirely in the browser. Installing a desktop agent or app can make it taxable at 6%. |
| Minnesota | Not taxable | Taxable | Not taxable: subscriptions to hosted software aren’t taxed. |
| Mississippi | Not taxable | Taxable | Not taxable when the software is hosted outside Mississippi and used only over the internet (since 1 July 2023). Software hosted in the state is taxable at 7%. |
| Missouri | Not taxable | Not taxable | Not taxable: SaaS isn’t tangible property or a taxable service in Missouri. |
| Montana | No sales tax | No sales tax | No general sales tax. The resort-town taxes don’t cover software. |
| Nebraska | Not taxable | Taxable | Not taxable in practice: Nebraska taxes software furnished to the customer, but access-only SaaS isn’t listed and there’s no ruling taxing it. |
| Nevada | Not taxable | Not taxable | Not taxable: nothing tangible changes hands. |
| New Hampshire | No sales tax | No sales tax | No general sales tax. |
| New Jersey | Not taxable | Taxable | Not taxable, unless the service counts as an “information service”, which is taxed at 6.625%. |
| New Mexico | Taxable | Taxable | Taxable under the gross receipts tax, which falls on the seller. Sellers usually pass it on. |
| New York | Taxable | Not taxable | Taxable as a license to use prewritten software, at the state rate plus local tax. Customers with users in several states can split it. |
| North Carolina | Not taxable | Taxable | Not taxable: remote access to software isn’t taxed, because nothing is delivered. |
| North Dakota | Not taxable | Not taxable | Not taxable in practice: hosted access isn’t on the taxable list, and there’s no ruling taxing it. |
| Ohio | Partly taxable | Partly taxable | Taxable when bought for business use, as a data processing or information service. Not taxable when bought for personal use. |
| Oklahoma | Not taxable | Not taxable | Not taxable: electronically delivered software is exempt, and a September 2026 ruling applied that to SaaS. |
| Oregon | No sales tax | No sales tax | No sales tax. |
| Pennsylvania | Taxable | Taxable | Taxable at 6% as canned software, plus 1% in Allegheny County and 2% in Philadelphia. |
| Rhode Island | Taxable | Taxable | Taxable at 7% since 1 October 2018. |
| South Carolina | Taxable | Partly taxable | Taxable as a communications service, at the state rate plus local tax. |
| South Dakota | Taxable | Taxable | Taxable: every service is taxed in South Dakota unless the law exempts it, and SaaS isn’t exempt. |
| Tennessee | Taxable | Taxable | Taxable, at the state rate plus local tax, based on where the customer uses it. |
| Texas | Partly taxable | Taxable | Taxable as a data processing service, on 80% of the price: 20% is exempt. At the 6.25% state rate that’s an effective 5%, before local tax. |
| Utah | Taxable | Taxable | Taxable when used in Utah. Custom software isn’t. |
| Vermont | Taxable | Taxable | Taxable since 1 July 2024. It was exempt before that. |
| Virginia | Not taxable | Not taxable | Not taxable: nothing tangible changes hands. Software sold with hardware can be. |
| Washington | Taxable | Taxable | Taxable as a “digital automated service”, at the state rate plus local tax. IT services and custom software became taxable too on 1 October 2025. |
| Washington D.C. | Taxable | Taxable | Taxable as a data processing service, at 6%. |
| West Virginia | Taxable | Partly taxable | Taxable for most SaaS. The exemption only covers certain data processing and communications software. |
| Wisconsin | Not taxable | Taxable | Not taxable when it runs on your servers and the customer doesn’t operate or control them. Downloaded software is taxable. |
| Wyoming | Not taxable | Partly taxable | Not taxable in practice: SaaS isn’t on Wyoming’s taxable list, and there’s no guidance taxing it. |
Sources: Kintsugi, SaaS Sales Tax by State (SaaS) andQuaderno, US Sales Tax on Digital Products (digital products), each checked against the state’s own guidance. Each state’s guide links its source.
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, at least until California starts taxing SaaS on 1 January 2027.
Texas’s 80% rule deserves particular note. Texas taxes SaaS as a “data processing service” at 6.25% state + local rates, on 80% of the charge: the other 20% is exempt. 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.
Related Guides
Section titled “Related Guides”- US Sales Tax Overview
- Shopify Sales Tax Limitations
- Foreign Sellers Guide to US Sales Tax Compliance
- Does Your US SaaS Need to Charge VAT in Germany? — the EU VAT side of selling SaaS from the US
- State-by-State Sales Tax Index