Digital Products Tax Guide 2026: VAT, GST, and Sales Tax by Country

Selling digital products globally in 2026 involves navigating a complex set of tax obligations that often change faster than an internal product roadmap. For a founder, one incorrect step can lead to significant penalties, back taxes, or compliance challenges that stall operations just as a business begins to scale.

This guide provides an exhaustive look at digital product tax requirements across major global markets. Whether you are selling Software as a Service (SaaS), Infrastructure as a Service (IaaS), API access, digital downloads, or software licenses, you need to identify which taxes apply, where they apply, and the specific threshold or triggering condition that requires collection.

What Counts as Digital Products for Tax Purposes

Tax authorities focus on how revenue flows through their specific jurisdiction. In the eyes of most global tax regimes, digital products typically include:

• Software Subscriptions (SaaS): Standard recurring access to software hosted in the cloud.
• Infrastructure as a Service (IaaS): While similar to SaaS, some jurisdictions treat raw computing and storage infrastructure differently than application-level software.
• API Access: Any consumption-based or usage-based billing model.
• Digital Downloads: E-books, design templates, and software plugins.
• Software Licenses: Both one-time activation keys and recurring gated access.

A critical distinction is that many jurisdictions now tax based on the location of the customer, the place of consumption, not the location where your business is registered. For example, a business selling digital services to consumers in Germany may be required to collect and remit German VAT depending on the transaction structure, customer classification (B2B vs. B2C), and whether a Merchant of Record model is used.

The European Union (EU): VAT on Digital Services

The EU treats digital services as "electronically supplied services," creating a specific administrative framework for non-EU businesses.

Non-Union OSS and the €0 Threshold

For non-EU businesses, the threshold for the VAT One-Stop Shop (OSS) is generally a €0 threshold for Business-to-Consumer (B2C) sales, meaning you are generally required to collect VAT from your first European customer. Non-Union OSS registration allows a non-EU vendor to account for VAT on B2C digital sales across all EU member states through a single portal.

By utilizing a specialized solution (Kiwy Option as Global Merchant of Record (MoR)), the platform acts as the legal seller for the transaction and assumes significant responsibility for tax collection, remittance, and compliance operations within the scope of its MoR framework.

B2B Reverse Charge Mechanism

For Business-to-Business (B2B) digital transactions within the EU, VAT may not need to be charged if the customer provides a valid VAT identification number and the reverse charge mechanism applies. Vendors are generally expected to validate and retain the customer's VAT information for audit purposes.

Evidence Conflicts and Retention

To remain compliant, you must typically maintain two non-contradictory pieces of evidence regarding the customer's location. Valid evidence includes the customer's billing address, IP address, bank details, or the country code of the SIM card. All such records, along with tax-compliant invoices, must be retained for 10 years.

United Kingdom: Post-Brexit VAT Realities

Since Brexit, the UK operates a digital services VAT system that is entirely separate from the EU OSS.

• Registration Threshold: Non-established businesses generally have a £0 threshold for digital services sold to UK consumers.
• Currency Conversion: Businesses filing UK VAT returns must ensure that VAT amounts can be accurately represented in GBP for reporting and audit purposes, even when customer transactions occur in other currencies.

United States: The Sales Tax Nexus Patchwork

Navigating the United States sales tax landscape is a significant compliance challenge because the rules are determined at the state level.

Economic Nexus and Threshold Changes

Economic nexus thresholds vary significantly by state. While many states historically adopted thresholds such as $100,000 in annual sales or 200 transactions following the Wayfair decision, a growing number of states have since removed the transaction-count requirement and now rely primarily on revenue thresholds.

SaaS Taxability and Customer Classification

In some states, SaaS taxability may vary depending on the purchaser type, industry classification, or how the software is used operationally. Certain exemptions may apply in limited scenarios, such as manufacturing or research. States such as Florida and Georgia have historically treated certain SaaS arrangements as non-taxable, though treatment can vary depending on implementation details and evolving administrative guidance.

Marketplace Facilitator Laws

In many jurisdictions, marketplace facilitator laws can shift tax collection and remittance obligations toward the platform operator depending on how transactions are structured and how the platform is classified under local law. Utilizing a Global MoR can centralize portions of these operational obligations under the platform’s infrastructure, depending on the transaction structure and jurisdiction (Kiwy Option as Global Merchant of Record (MoR)).

SaaS and Digital Goods: 2026 US State Taxability Snapshot

The following table provides a high-level informational overview of how selected US states commonly treat SaaS and digital goods for sales tax purposes as of early 2026. Tax treatment can vary depending on transaction structure, implementation details, purchaser classification, bundled services, administrative guidance, and ongoing regulatory changes.

This table is not legal or tax advice and should not be treated as a substitute for state-specific compliance analysis or professional tax consultation.

Important Limitations

Several important limitations apply to the table above:

• SaaS taxability in the United States is highly state-specific and frequently updated through administrative rulings, court decisions, and regulatory guidance.
• Some states distinguish between Business-to-Business (B2B) and Business-to-Consumer (B2C) transactions.
• Tax treatment may change depending on whether software is customized, bundled with services, or connected to tangible products.
• Economic nexus thresholds and transaction-count requirements continue to evolve following the Wayfair decision.
• Local taxes, home-rule jurisdictions, and marketplace facilitator laws can introduce additional obligations beyond state-level rules.

Because of this complexity, businesses selling digital products across multiple US states often rely on specialized tax infrastructure or Merchant of Record models to centralize compliance operations.

GCC Countries: VAT and Regional Infrastructure

The Gulf Cooperation Council (GCC) countries have developed VAT systems that include mandates for digital services, with active enforcement and compliance monitoring.

• United Arab Emirates: A standard 5% VAT applies to digital services supplied to UAE customers.
• Saudi Arabia: Maintains a 15% VAT rate with active enforcement and compliance monitoring by ZATCA for digital service providers.
• Other GCC Status: Bahrain (10%) and Oman (5%) maintain active VAT systems, while Qatar has not yet implemented a VAT system as of early 2026.

Regional Strategy

For founders in this region, there are two distinct paths:

1. Regional Dominance: Integrate with national payment systems (Kiwy Option as Local Infrastructure in GCC) to support compatibility with regional payment methods and local banking infrastructure.
2. Cross-Border Expansion: Use a partner that handles foreign tax filings and liability (Kiwy Option as Global Merchant of Record (MoR)) for sales into the US, EU, and UK.

Operational Mechanics: MoR vs. Gateway

The Merchant of Record model differs from tax calculation tools because the platform acts as the legal seller for the transaction and assumes responsibility for tax collection and remittance within the scope of the platform agreement.

Settlement and Tax Reversal Adjustments

Merchant of Record providers often operate on settlement schedules that differ from standard payment gateways because they reconcile taxes, refunds, and compliance obligations before issuing payouts. Furthermore, when a refund is issued, the MoR must perform tax reversal adjustments associated with refunds, ensuring the previously collected tax is correctly reversed in the next tax filing cycle.

Dispute Handling

In an MoR model, the platform generally manages portions of the dispute handling workflow within the scope of its payment and risk infrastructure. This includes managing supporting documentation required by card networks to respond to disputed transactions.

The Bottom Line for 2026

Global tax compliance for digital products is a persistent administrative requirement. For many SaaS businesses, outsourcing tax infrastructure allows engineering and operational resources to remain focused on product development rather than regulatory administration.

Tax authorities are increasingly expanding digital enforcement and cross-border compliance monitoring to identify unregistered foreign sellers. Consequently, businesses can expand internationally while reducing the operational burden associated with cross-border tax compliance by utilizing a partner that assumes portions of the operational and tax compliance responsibilities associated with cross-border digital sales.

Learn how Kiwy automates global tax and billing at kiwy.ai.