Is SaaS taxable in Wyoming? A developer's guide to the exemption

• Software is tangible property: Wyoming defines prewritten computer software as tangible personal property (Wyo. Stat. § 39-15-101(a)(ix)).
• Tax requires transfer of possession: A taxable "sale" legally requires a transfer of title or possession (§ 39-15-101(a)(vii)).
• The delivery split: Electronically downloaded software transfers possession and is taxable. Remotely hosted SaaS transfers neither and is exempt.
• The developer catch: If your application requires a downloadable CLI tool, background daemon, or desktop client, that component transfers possession and triggers tax. Keep those line items separately stated to protect your cloud subscription's exempt status.

There is no pending legislation changing Wyoming’s SaaS posture. Below is how to handle Wyoming's nexus triggers, local county rate variations, and checkout API logic.

Wyoming SaaS sales tax at a glance

Product Taxability Rules

State Registration & Collection Triggers

Which types of software does Wyoming tax?

Wyoming taxes software based on whether a sale, meaning a transfer of title or possession, actually occurs. The statute's definition of tangible personal property names prewritten computer software outright, with no exception for how it's delivered, so the operative question is possession, not product category.

Bundles are where implementations break, the same as anywhere else. Apply taxability per line item, not per order: a SaaS subscription that ships a required local agent, a hardware component, or a physical onboarding kit stays exempt on the pure-access portion, but the tangible or locally-installed portion is taxable, and an undifferentiated lump sum drags the whole invoice into taxable territory.

How do you charge the correct sales tax rate for SaaS in Wyoming?

Under current rules, you mostly don't. Because browser-based SaaS with no transfer of possession is exempt, the sales tax on a remotely accessed subscription sold to a Wyoming customer is $0. That changes the moment the product stops being pure SaaS: a downloaded client, a required local agent, physical media, or a bundled tangible good all bring tax back into the picture, and Wyoming has no pending transition to plan around, so this is the steady state, not a temporary one.

When some portion of a sale is taxable, engineering teams have two options for calculating the correct rate on that portion: call a real-time sales tax API, or manually build and maintain an internal rate engine.

Option 1: Use the Ziptax Sales Tax API

You send the buyer's address at the point of checkout, and the API evaluates which county's rate applies, since Wyoming's local option taxes are set at the county level rather than by individual cities.

To calculate a live rate against a Wyoming address, use the v60 endpoint:

curl -G https://api.zip-tax.com/request/v60 \
    -H "X-API-KEY: <apiKey>" \
    -d key=your-api-key \
    --data-urlencode "address=200 W 24th St, Cheyenne, WY, 82002"

To verify complete payload structures, explore the REST API documentation.

3 rules for handling the API response:

1. Use the returned combined rate. Don't sum local and state components manually; floating-point rounding errors will break your reconciliation.
2. Persist the jurisdiction ID on the order. Never attempt to reverse-geocode tax districts from raw addresses after checkout closes.
3. Store the calculation timestamp. Wyoming's county-level local option taxes are ballot-approved and can expire or renew on voter-set dates.

Handling mixed or hybrid catalogs

Pass taxability codes in your checkout request to automate exemptions. You can search for the correct product code and review Taxability Information Codes (TICs) to see how the engine handles pure SaaS vs. downloadable components.

The integration boundary

The API calculates rooftop rates—it does not track your physical or economic nexus status, nor does it decide whether an unbundled local agent taints your cloud contract. That logic lives in your application layer.

To automate the back-half of compliance—like threshold tracking, return generation, and multi-state remittance—set up merchant management.

Option 2: Build and maintain it yourself

Worth considering if you already hold jurisdiction data for other reasons. Wyoming is a lighter lift than most states on the geography side. Just make sure your setup handles these four things.

• A product taxability decision separate from the rate lookup. Pure browser-based SaaS with no transfer of possession is exempt, which means the rate is not the operative question for it at all. Downloads, local agents or CLI components, physical media, and bundled tangible goods still need a rate.
• Threshold accumulation on the right basis. $100,000 in gross revenue from tangible personal property, admissions, or services, measured over the current or immediately preceding calendar year. The 200-transaction alternative that used to apply alongside it was repealed effective July 1, 2024, so transaction count no longer matters.
• Address-to-county rate resolution. Wyoming's local option taxes are approved by county voters and apply across the whole county, including its incorporated towns, rather than varying from one city to the next within the same county. That's simpler than a state with home-rule cities or police jurisdictions, but you still need to resolve an address to the right county rather than assuming a flat statewide rate.
• An effective date on every rule. Local option taxes are time-limited by the ballot measures that created them and can expire or renew on a schedule, so a stored county rate needs a refresh cadence, not a one-time load.

A few things to watch out for if you take this route:

1. Assuming a flat statewide rate. The 4% state rate is a floor, not the whole answer. Counties add their own voter-approved rate on top of it, generally landing the combined rate somewhere between 4% and 8%, and that figure moves as county ballot measures pass or expire.
2. Treating the local-option layer as city-level. Unlike a state with home-rule cities or special districts, Wyoming's local sales tax is a county-level decision. Don't build city-by-city override logic that doesn't exist here; resolve to the county instead.
3. Counting only taxable revenue toward the $100,000 threshold. Wyoming's statute measures gross revenue from tangible personal property, admissions, or services, not taxable revenue specifically. A pure-SaaS seller can realistically cross the threshold, register, and then file returns reporting $0 in tax due, because the product itself stays exempt even though the gross revenue counted toward registration.

When does a SaaS business have to collect sales tax in Wyoming?

Registration and collection are two separate obligations with completely different triggers. Conflating them is where most engineering implementations go wrong, and it's especially easy to get wrong in an exempt state, where it's tempting to assume no tax means no obligations at all.

To get this right, view collection requirements and nexus, and have your application and billing stack track these two operational rules:

Rule 1: Monitor your registration triggers (nexus)

You must legally register to file with the state the moment either of these conditions is met:

• Physical presence: an employee working in Wyoming, an office, inventory held in the state, or leased server capacity.
• Economic threshold: check economic nexus thresholds. Your gross revenue from tangible personal property, admissions, or services delivered into Wyoming crosses $100,000 in the current or immediately preceding calendar year. There's no transaction-count alternative anymore; that prong was repealed effective July 1, 2024. This revenue measure is not limited to taxable sales, so exempt SaaS subscription revenue absolutely counts toward it.

Rule 2: Apply the correct collection logic

Because Wyoming's threshold rides on gross revenue from tangible personal property, admissions, or services, rather than taxable sales specifically, a pure-SaaS company can cross $100,000 on subscription revenue alone.

If you do, you must register and file, but your billing system should calculate tax at $0 on every exempt SaaS line and submit zero-dollar returns on schedule.

If any part of your Wyoming revenue is a delivered, non-incidental software sale, a full download, physical media, or a bundled tangible good, that portion is taxable at the combined state-and-county rate for the customer's address and has to be calculated, collected, and remitted once you've registered.

Where Ziptax helps

If you're building a custom billing engine, a niche ERP, or a B2B SaaS platform, you don't need an enterprise compliance suite just to calculate an accurate checkout rate. You just need a fast, reliable endpoint.

Ziptax handles the infrastructure layer of sales tax calculation so your team can focus on your core product.

• Rooftop Precision: Resolves rates across 12,000+ U.S. tax jurisdictions using exact address and coordinate-based lookups, so a multi-state product applies Wyoming's county-level rate correctly alongside every other state's address-level complexity, without special-casing it in your own code.
• Engineered for Platforms: Built specifically to embed live tax calculations directly into checkout workflows, API endpoints, and marketplace billing frameworks.
• Frictionless Pricing: Designed for cost-conscious development teams who want to pay strictly for active calculation calls without committing to heavy enterprise software contracts.
• The TaxCloud Runway: When your transaction volume scales or your users demand automated filing and remittance services, you can pair Ziptax with TaxCloud for the rest of compliance. You get a lightweight API to deploy today and a filing and remittance backend ready when you need it.

Get Wyoming SaaS tax rates from an API

Address-level rates for every Wyoming jurisdiction, plus the rest of the US, Canada, and select other markets.

Frequently asked questions

Do you have to register in Wyoming if your SaaS product is exempt there? Yes, and the path there is different from a state whose threshold is limited to taxable tangible personal property. Wyoming's $100,000 economic nexus threshold is measured on gross revenue from tangible personal property, admissions, or services delivered into the state, with no stated carve-out for exempt sales. A seller whose only Wyoming revenue is pure browser-based SaaS will cross that threshold on subscription revenue alone once they hit $100,000. If you do, you must register and file, but your billing system should calculate tax at $0 on every exempt SaaS line and submit zero-dollar returns on schedule. Registration and taxability are independent tests: registration turns on whether you have nexus; taxability turns on what you sell.

Does Wyoming tax software differently depending on how it is delivered? Yes, and possession, not the product label, is what decides it. Wyoming's statute defines tangible personal property to include prewritten computer software outright, with no delivery-method qualifier, but a taxable sale requires a transfer of title or possession. Software a customer downloads or receives on physical media transfers possession and is taxable. Software accessed only through a browser, with nothing transferred to the customer, doesn't meet that bar and is exempt. A SaaS product that bundles in a local agent or CLI tool risks losing that exemption on the local component.

Can you use a ZIP code to get the Wyoming sales tax rate? More reliably than in a state with city-level local taxes, since Wyoming's local option rates are set at the county level rather than varying from one city to the next, but not perfectly. A ZIP code can still straddle a county line, and Wyoming's Department of Revenue says on its own site that it doesn't yet have a working address-based rate lookup tool. Resolve the full address or confirm the county directly rather than assuming a ZIP code always lands cleanly in one county.

Is a Wyoming law change to SaaS taxability pending? Not currently. Wyoming is a stable, fully exempt state for SaaS, with nothing pending in the 2026-2027 window this template tracks.

Sources

1. Tangible personal property, computer software, and "sale" definitions: Wyoming Statutes § 39-15-101 (Definitions). https://law.justia.com/codes/wyoming/title-39/chapter-15/article-1/section-39-15-101/
2. Specified digital products taxation: Wyoming Statutes § 39-15-103 (Taxation Rate). https://law.justia.com/codes/wyoming/title-39/chapter-15/article-1/section-39-15-103/
3. Destination sourcing: Wyoming Statutes § 39-15-108. https://law.justia.com/codes/wyoming/title-39/chapter-15/article-1/section-39-15-108/
4. Economic nexus and the $100,000 threshold: Wyoming Statutes § 39-15-501 (Sales from remote sellers). https://law.justia.com/codes/wyoming/title-39/chapter-15/article-5/section-39-15-501/
5. Marketplace Facilitators: Wyoming Statutes § 39-15-502. https://law.justia.com/codes/wyoming/title-39/chapter-15/article-5/section-39-15-502/
6. State sales tax rate, county local option taxes, and sourcing: Wyoming Department of Revenue, Excise Tax Division, Frequently Asked Questions. https://excise-tax-div.wyo.gov/general-administrative/excise-tax-faqs
7. Current sales and use tax rate charts: Wyoming Department of Revenue, Excise Tax Division, Sales/Use Tax Rate Charts. https://excise-tax-div.wyo.gov/sales-use-tax-rate-charts
8. Streamlined Sales Tax (SST) status: Streamlined Sales Tax Governing Board, Wyoming state detail. https://www.streamlinedsalestax.org/state-details/wyoming