How to sell software online

Selling software online comes down to six things. Where you sell it, how you get paid, who handles the tax, how you stop it being copied, how customers get it, and how they get updates. Here's how to set up each one.

A key floating out of an open cardboard box

To sell software online you need a way to take the payment, a way to deliver the software, and a way to make sure the people using it are the people who paid. Everything else is detail on top of those three.

This guide is for people who've built something that runs on the customer's machine: a desktop app, a plugin, a game, a command-line tool. If you've built a web app (SaaS), payments and tax work the same way, but you can skip the parts about license keys and downloads, since your login is your license.

Here's the whole thing in order:

  1. Decide where you'll sell: an app store, your own site, or both
  2. Pick how you'll take payments
  3. Sort out sales tax and VAT
  4. Add license keys so only paying customers can use the app
  5. Deliver the download
  6. Ship updates
  7. Handle refunds and support

1. App store or your own website

There are two places to sell software: someone else's store, or your own site.

An app store (the Mac App Store, the Microsoft Store, Steam for games) gives you a checkout, tax handling, delivery, updates and an audience that's already there. You pay for it with a commission and with rules.

Selling direct means a page on your own website with a buy button. You keep much more of each sale, you know who your customers are, and nobody reviews your releases. In exchange, you set up the pieces yourself. That's what the rest of this guide covers, and it's less work than it used to be.

App store Direct from your site
What it costs 15% to 30% of each sale About 3% to 5% plus a small fixed fee
Who finds you Store search and features, plus your own marketing Only your own marketing
Who owns the customer The store You
Tax Store handles it You, or a merchant of record
Review and rules Yes None
Licensing and updates Built in You add them
Pricing freedom Store's models Anything: trials, upgrades, bundles, discounts

The published commissions: Apple takes 30%, or 15% if you're in the App Store Small Business Program, which is for developers who earned up to 1 million USD in the prior calendar year. The Microsoft Store takes 15% for apps and 12% for games, and lets non-gaming apps use their own commerce platform and keep 100%.

On a $49 app, 30% is $14.70. Selling the same app directly through Stripe costs $1.72.

You don't have to choose one. Plenty of developers sell direct and list in a store too, treating the store as a discovery channel. If you do, keep in mind that store customers and direct customers will be on separate licensing and update systems.

2. Taking payments

To take a card payment on your own site you need one of two kinds of company.

A payment processor, like Stripe. It moves money from the customer's card to your bank. You are the seller. It's the cheapest option at 2.9% + 30¢ per sale, and you can be selling in an afternoon with a Stripe Payment Link and no code.

A merchant of record, like Paddle, Polar, Creem, Dodo Payments or Gumroad. It legally sells your software to the customer and pays you. Because it's the seller, the sales tax and VAT are its job. That costs more.

Platform Type Rate per sale Fee on a $49 sale
Stripe Payment processor 2.9% + 30¢ $1.72
Creem Merchant of record 3.9% + 40¢ $2.31
Dodo Payments Merchant of record 4% + 40¢ $2.36
Paddle Merchant of record 5% + 50¢ $2.95
Polar Merchant of record 5% + 50¢ $2.95
Gumroad Merchant of record 10% + 50¢ $5.40

Each rate was read from the platform's own pricing page on November 17, 2026. They're headline rates: international cards, currency conversion and subscriptions can add to some of them. The fee calculator lets you put in your own price and see the same sale on every platform, and there's a detailed Paddle vs Stripe comparison if you're down to those two.

3. Sales tax and VAT

This is the part people skip, and then worry about later.

Digital products are generally taxed where the customer is. If you sell to a consumer in France, French VAT applies. If you sell into a US state that taxes software and you're over that state's threshold, its sales tax applies. The rules differ by country and by state, and this isn't tax advice, but you have three ways to deal with it:

  • Use a merchant of record and it's entirely their problem. This is the simplest route if you sell to consumers around the world.
  • Use a payment processor with a tax tool. Stripe Tax, for example, calculates and collects the right tax for 0.5% per transaction where you're registered. You still register and file.
  • Handle it yourself with an accountant. Reasonable if nearly all your customers are in your own country.

If you want to stay on Stripe and still have the tax handled, Stripe Managed Payments makes Stripe the merchant of record for an extra 3.5%.

4. License keys: making sure only buyers can use it

Once someone has your installer, nothing stops them from passing it on. A license key is how your app tells a paying customer from everyone else.

The flow is simple:

  1. A customer pays
  2. A unique license key is generated and emailed to them (the license key generator shows what a good one looks like)
  3. They paste it into your app
  4. Your app checks the key with a licensing server and unlocks

The part that makes it work is software activation: when the key is first used, it's tied to that device, and you set how many devices one purchase covers. That's what stops one key from being shared with a whole forum.

A few decisions to make here:

  • How long it lasts. A perpetual license is a one-time purchase; a subscription license expires unless it's renewed.
  • How many devices. One, three, or a pool shared by a team with a floating license.
  • Whether it works offline. Some customers will run your app on machines with no internet, so the license needs to be verifiable without calling home.
  • What happens on refund. The license should stop working.

You can build this yourself, and a lot of developers have. It tends to take longer than expected, mostly because of the edge cases: clock tampering, device changes, offline grace periods, and keeping your key-signing secure. The other option is a licensing service.

LicenseSeat is one. You connect your payment platform, and each sale issues a key and emails it to the customer; a refund revokes it. Your app validates the key through an SDK, with device limits, offline validation and trials included. It connects to Stripe, Paddle, Polar, Creem, Dodo Payments, Lemon Squeezy, Gumroad, Shopify and FastSpring, charges a flat monthly fee and takes 0% of your revenue.

5. Delivering the download

The customer has paid and has a key. Now they need the app.

The simplest approach is a public download link: anyone can download the app, and it does nothing useful without a license. This is how most trial-based software works, and it has a nice side effect, because the trial download and the paid download are the same file.

If you'd rather only paying customers can download, you need download links that are tied to a license and that expire.

Either way, sign your builds. On macOS, an app distributed outside the App Store needs to be signed with a Developer ID certificate and notarized by Apple, or Gatekeeper will warn the user away from opening it (that's where the "app is damaged" message and xattr -cr come from). That requires the Apple Developer Program, which is 99 USD a year. On Windows, an unsigned installer triggers a SmartScreen warning, so you'll want a code signing certificate and SignTool to apply it. An app that the operating system calls dangerous doesn't get installed, no matter how good your checkout is.

And give it a proper icon. The PNG to ICNS converter makes the macOS .icns and the Windows .ico from one image.

6. Shipping updates

An app store pushes updates for you. When you sell direct, your app has to ask "is there a newer version?" on its own.

The usual pattern is an update feed: a small file on a server that lists your latest version and where to download it. The app checks the feed, and if there's something newer it downloads and installs it. There are well-established open-source updaters for this, like Sparkle on macOS and electron-updater for Electron apps. Each update should say what changed, and there's a release notes template for that.

If you sell paid upgrades or subscriptions, you'll also want updates to respect the license, so that a customer whose subscription has lapsed stops receiving new versions. That means the update feed needs to know about licenses, which is one more reason licensing and distribution work best as one system. LicenseSeat hosts your release files and serves updates to licensed users; here's the guide to shipping desktop updates.

7. Refunds and support

Decide your refund policy before your first sale and put it on your site. Then make sure a refund actually ends the license. If your licensing is connected to your payment platform, that happens on its own.

Expect three kinds of support email: "I lost my key", "I got a new computer", and "it says my key is already in use". A customer portal where people can see their keys and free up a device seat will save you from answering most of them.

What it costs to sell direct, all in

Here's a worked example for a $49 desktop app selling 100 copies a month, with US cards:

App store at 30% App store at 15% Direct with Stripe Direct with Paddle
Revenue $4,900 $4,900 $4,900 $4,900
Platform fees $1,470 $735 $172 $295
You keep $3,430 $4,165 $4,728 $4,605

Selling direct, you'd also pay for licensing and for somewhere to host your downloads, and you'd pay the Apple Developer Program fee either way. Even so, the gap is wide. Selling direct keeps roughly 94% to 97% of each sale, where an app store keeps 70% to 85% for you.

The honest downside is discovery. A store brings some customers to you; your own site brings none until you market it. If your customers already find you through search, word of mouth or your own audience, direct is usually the better deal.

Common questions about selling software online

Where can I sell my software online?

Your own website, with a payment processor like Stripe or a merchant of record like Paddle, is the option with the lowest fees. You can also list in the Mac App Store or the Microsoft Store, or on Steam for games, or use a marketplace like Gumroad.

What is the cheapest way to sell software online?

Your own site with a payment processor. Stripe charges 2.9% + 30¢ per sale, so a $49 sale costs $1.72. The trade-off is that you handle sales tax and VAT yourself. The cheapest platforms that handle tax for you publish rates from 3.9% + 40¢.

Do I have to charge sales tax or VAT on software?

Often, yes. Digital products are generally taxed where the customer is, and the rules vary by country and by US state. A merchant of record takes that on for you. With a payment processor it's your responsibility, with or without a tax tool to help.

How do I sell software without an app store?

Put a buy button on your own site, connect a licensing service so each sale issues a license key, sign your builds so the operating system trusts them, and add an updater so customers get new versions. That covers what a store would otherwise do for you.

How do I stop people from sharing my software?

Use license keys with activation. Each key is tied to a limited number of devices when it's first used, so a shared key stops working once the limit is reached. Nothing stops piracy completely, but it keeps honest customers honest.

Do I need a company to sell software online?

It depends on where you live and on the platform. Many payment platforms accept individuals and sole proprietors. Check your local rules on registering a business and declaring the income.