Clavem

How to sell software online with Stripe

To sell software with Stripe, create a Product and a Price, take payment through a Payment Link or Checkout, and act on the checkout.session.completed event. Stripe moves the money. License keys, downloads and tax are separate jobs.

The short answer

Selling software through Stripe takes four steps. Create a Product and a Price in your Stripe account. Send buyers to a Stripe-hosted payment page. Wait for Stripe to tell your server that the payment succeeded. Then do the things Stripe does not do: create a license key, deliver the download, and deal with tax.

Stripe is good at the first three. It is not a licensing system, a file host or (by default) a tax agent. Most of the work in selling software is in that gap, and most of this article is about where the gap starts.

Pick a checkout surface

Stripe offers several ways to take the same payment. They differ in how much you build and how much of the page you control.

Surface You build Page control Works with Managed Payments
Payment Links Nothing. Create the link in the Dashboard. Limited: logo, colors, 20 preset fonts, 3 border radii Yes
Checkout, full page One API call that creates a Checkout Session, then a redirect Stripe hosts it, with the same limited styling Yes
Checkout, embedded form The same API call, plus an embed on your page Stripe’s form inside your page Yes
Elements with Checkout Sessions A custom payment page Full control of the layout No
Elements with Payment Intents The most custom code Full control No

The last column comes from Stripe’s Managed Payments documentation, which lists Elements with the Checkout Sessions API and advanced Payment Intents integrations as unsupported. If there is any chance you will want Stripe as merchant of record, stay on Payment Links or Checkout.

For a first product, use a Payment Link. For a product with several prices, a quantity selector or a buyer account on your own site, create Checkout Sessions from your server. Elements only pays off when the payment form must look like part of your app, which is rare for a software purchase.

The Stripe objects you will touch

Every sale produces the same chain of objects. Knowing which one holds which fact saves hours of reading JSON.

Object What it represents What you read from it
Product The thing you sell, such as “Inkwell for macOS” Name, tax code, metadata
Price One way to pay for a Product: amount, currency, one-time or recurring Price id, amount, nickname
Checkout Session One visit to the payment page payment_status, customer_details.email, line items, mode
Customer The buyer, when Stripe creates or links one Customer id, email
PaymentIntent and Charge The money movement Amount, refund state
Subscription A recurring agreement (subscription mode only) Status, current period
Invoice A bill for one subscription period Paid or not, period covered

For the events, two flows cover almost every software business.

One-time payment (mode=payment): the Checkout Session completes and you receive checkout.session.completed. Check payment_status on the session. It is paid, unpaid or no_payment_required. Delayed methods such as bank debits complete the session as unpaid and send checkout.session.async_payment_succeeded later. A refund produces charge.refunded.

Subscription (mode=subscription): you receive checkout.session.completed for the first payment, then invoice.paid for every renewal. customer.subscription.updated fires on any change, including a cancellation scheduled for the end of the period, and customer.subscription.deleted fires when the subscription actually ends. Stripe’s subscription webhook documentation says to provision access when you receive invoice.paid and the subscription is active.

Try it in a sandbox in ten minutes

You can run the whole flow without real money. Stripe’s testing guide says to use the card number 4242 4242 4242 4242, any future expiry date such as 12/34, and any three-digit CVC.

  1. Create a Product and a one-time Price in a sandbox or in test mode.
  2. Create a Payment Link for the Price, or a Checkout Session from your server.
  3. Pay with the test card.
  4. Open the event log in the Dashboard and find checkout.session.completed. Open it and read payment_status and customer_details.email.

A Checkout Session from your server is one request. This is the shape from Stripe’s documentation, with a placeholder key and Price id:

curl https://api.stripe.com/v1/checkout/sessions \
  -u "sk_test_...:" \
  -d "line_items[0][price]=price_..." \
  -d "line_items[0][quantity]=1" \
  -d mode=payment \
  --data-urlencode "success_url=https://example.com/thanks?session_id={CHECKOUT_SESSION_ID}"

Stripe replaces {CHECKOUT_SESSION_ID} with the real id when it redirects the buyer, so your success page can look the session up. Treat that page as a convenience for the buyer. It is not your fulfilment path. Stripe’s fulfilment guide says you must use webhooks to make sure fulfilment happens for every payment, and that redirects let customers see details immediately after paying. When you set a success_url and also have a webhook endpoint, Checkout waits up to 10 seconds for your server to answer the webhook before redirecting, so answer fast.

What Stripe leaves to you

After the payment, four jobs remain. None are optional for desktop software.

  • A license key. Stripe has no license object. Something must create a unique key per purchase, and per seat when quantity is more than one. See does Stripe generate license keys.
  • Device limits and checks. The app needs an endpoint it can call to ask “is this key valid, and how many machines is it on”. Stripe cannot answer that, and the app must never hold a Stripe secret key to try.
  • File delivery. Stripe does not host your installer. The options are covered in deliver software downloads after payment.
  • Updates and refunds in the app. When a refund or cancellation happens in Stripe, something must turn it into “this key stops working”.

The practical consequence: plan the webhook handler on day one, not after launch. Stripe webhooks for license fulfilment lists the events and the signature check.

Fees and tax in one place

Stripe’s standard card rate depends on the country of your Stripe account, so read your own pricing page. The Swiss page shows 2.9% plus CHF 0.30 for Swiss cards, 3.25% plus CHF 0.30 for international cards, and a further 2% when currency conversion is needed. Refunds do not return the original processing fee, and a dispute adds a fee per dispute (CHF 20.00 on the Swiss page). The Stripe fee calculator turns these into a net figure for your price.

Tax is the part that surprises first-time sellers. Selling software to buyers in other countries can create VAT, GST or sales tax duties for you. Stripe gives you two routes:

  • Stripe Tax calculates and collects the tax. Stripe’s pricing page lists a per-transaction fee on the no-code integration where you are registered to collect, and a monthly Tax Complete tier that adds registrations and filings.
  • Managed Payments makes Stripe the merchant of record. Stripe’s documentation says it handles sales tax, VAT and GST in more than 80 countries, and it supports software, video games and downloads. It adds 3.5% per successful transaction to your standard Stripe fees. The trade-offs are covered in merchant of record vs Stripe.

This is general information, not tax advice. Check your obligations with an accountant who knows digital goods.

Doing this with Clavem

Clavem is the part after the payment, for sellers who keep their own Stripe account. You paste a restricted Stripe key, Clavem registers its own webhook, and you map a Stripe Product or Price to a Clavem product. Each paid Checkout Session then creates the license keys, an order page with the download, and an email to the buyer. Your app calls Clavem’s License API to activate and validate keys.

Clavem is not a merchant of record, takes no cut of sales and does not handle tax. If you want Stripe to handle tax through Managed Payments, the two work together, but test one purchase before you point live traffic at it. The setup steps are in the Stripe connection guide, and the free plan covers 50 active licenses.

Questions

Can I sell software with Stripe without building a website?

Yes. A Payment Link is a shareable link to a Stripe-hosted payment page. Stripe lists it as a no-code integration with limited visual customization. You still need somewhere to host the download and something to hand out license keys.

Does Stripe handle sales tax and VAT on software?

Not by default. Stripe Tax can calculate and collect tax, and its Tax Complete tier adds registrations and filings. Managed Payments makes Stripe the merchant of record in more than 80 countries. Without one of those, tax is your job.

Do I need a webhook if I use a Payment Link?

Yes, if anything must happen after payment, such as issuing a license key. Stripe's fulfilment guide says to use webhooks so fulfilment happens for every payment, because a buyer can close the tab before the success page loads.

Sources

  1. Stripe docs, online payments and payment UIs (as of November 2026)
  2. Stripe docs, Payment Links (as of November 2026)
  3. Stripe docs, fulfil orders after Checkout (as of November 2026)
  4. Stripe docs, Managed Payments eligibility (as of November 2026)
  5. Stripe docs, subscription webhooks (as of November 2026)
  6. Stripe API reference, Checkout Session object (as of November 2026)
  7. Stripe docs, testing (as of November 2026)
  8. Stripe pricing, Switzerland page (as of November 2026)
  9. Stripe Tax pricing (as of November 2026)