Clavem

Selling software to businesses: tax IDs, invoices, security questions and hand-made licenses

Business buyers want a tax ID on the invoice, a way to pay without a card, an answer to "what data does this send", and a license that survives an employee leaving. Card checkout covers the first small purchases, and licenses for invoiced deals are created by hand.

How a business buyer differs

A person buying your app decides in a few minutes with a card. A company buys through a process. The software you sell is the same, and the transaction around it is not.

Individual Business
Who pays The user A manager, a department or accounts payable
How A card at checkout Often an invoice, sometimes a purchase order
Paper A receipt An invoice with the company’s name, address and tax ID
Decision Minutes Days or weeks, with approvals
Questions “Does it work?” “What data does it send? Can we run it offline? Who supports it?”
Licensing One key, one person Several keys, a pool of devices, or one company-wide key

A small business paying by card looks like an individual with a different invoice. A larger one asks for invoicing and paperwork. Decide how far you will go, because the work grows quickly.

Collect business details at checkout

Stripe Checkout can ask for a tax ID. Set tax_id_collection[enabled]=true when you create the Checkout Session, and Checkout shows a field and hides it where it is not relevant. Stripe’s documentation says displaying a customer’s tax ID and legal business name on invoices is a common requirement, and that you can satisfy it this way. It also says the Checkout Sessions API collects business tax IDs only, so you must not present the field as a place for personal IDs.

curl https://api.stripe.com/v1/checkout/sessions \
  -u "sk_test_...:" \
  -d "line_items[0][price]=price_..." \
  -d "line_items[0][quantity]=1" \
  -d "tax_id_collection[enabled]=true" \
  -d "tax_id_collection[required]=if_supported" \
  -d mode=payment \
  --data-urlencode "success_url=https://example.com/thanks"

Setting required to if_supported makes Checkout require a tax ID from customers in billing countries it supports. Stripe’s documentation also says that if you use Stripe Tax, it applies the reverse charge or a zero rate according to applicable law when the tax ID has the required number format, regardless of the government verification result. Whether reverse charge applies to your sale is a tax question. See EU VAT for software sellers and tax basics for indie software sellers, and ask an accountant.

The license record gets the buyer’s name and email from the session. If the person at the company who pays is not the person who will install the software, make the key easy to forward: the buyer gets a private order page with the key, the downloads and the activation instructions, and can send the link on.

Card checkout and invoices are different flows

This is the point that surprises sellers. Clavem creates licenses when a Stripe Checkout Session completes. A customer who pays on an invoice that you sent outside Checkout does not trigger that.

Flow How the license arrives Renewals
Card through Checkout, one-time Automatic when the session is paid Not applicable
Card through Checkout, subscription Automatic, and the expiry follows the subscription Automatic with each paid invoice
Invoice or purchase order, outside Checkout You create the license by hand You extend it by hand when the next invoice is paid

For the hand-made route, create the license with the management API when the deal is agreed:

curl https://clavem.io/v1/admin/licenses \
  -H "Authorization: Bearer sk_clavem_..." \
  -H "Content-Type: application/json" \
  -d '{
    "product_id": 75,
    "email": "it@acme.example",
    "name": "Acme GmbH",
    "activation_limit": 25,
    "expires_at": "2027-12-31T00:00:00Z"
  }'

Putting the company’s name in name makes it easy to find. The response includes an order_url, the buyer’s private page, which you send with the invoice. Licenses created by hand count toward your plan like any other. Stripe’s own events never change a hand-made license, because it has no Stripe subscription behind it. When the next invoice is paid, extend it:

curl -X PATCH https://clavem.io/v1/admin/licenses/412 \
  -H "Authorization: Bearer sk_clavem_..." \
  -H "Content-Type: application/json" \
  -d '{ "expires_at": "2028-12-31T00:00:00Z" }'

Keep a simple record, a sheet or your accounting tool, of each business customer, the license id, the device limit, the expiry and the invoice that paid for it.

A caution about invoiced subscriptions

If you bill a subscription by sending invoices instead of charging a card, Stripe’s documentation says the subscription becomes past_due when an invoice stays unpaid past its due date. Clavem treats past_due as entitled, so a license tied to such a subscription stays valid until Stripe changes the status. For invoiced customers, decide in advance when you will cancel or disable, and do it deliberately.

What a security questionnaire asks

Larger customers send questionnaires. You can pre-empt most of them with a short page that describes exactly what the licensing check does. The License API call has few moving parts:

Data Sent by the app Purpose
License key Yes Identifies the license
Device name (instance_name) At activation Shown to the buyer on the device page
Fingerprint Optional, at activation Recognizes the same device on reinstall
Instance id At validation Names the activation
Documents, content, usage data No Not part of the call

What comes back is the license status, limits, expiry, the buyer’s name and email, and a signed token. Say where the licensing service runs and what happens if it is unreachable: the app can verify its stored token offline with a public key and keep working for 14 days before it must check again. Those two facts, small data and graceful failure, answer most of what an IT department wants to know.

For customers with no internet access on the machines that run your software, describe the offline route: fetch a token on a connected machine, carry it over, and verify it locally.

Trials and proofs of concept

A company often wants to evaluate before it buys, with several people and a few weeks. Create a license by hand with a short expires_at, such as 30 days out, and a device limit that fits the pilot. When the deal closes, move the date and the limit with PATCH on the same license, so the people who installed the software keep their activations and do not need a new key. If the pilot lapses, the license expires by itself and the app drops to its free state. Moving the date forward later revives an expired license, so a slow approval does not force a restart. Note the pilot in your records, because a hand-made license for a trial counts toward your plan like a paid one until it expires.

Licensing choices that suit companies

  • Name the owner. Put the company in the license name, so the order page and the dashboard say who it belongs to.
  • Plan for departures. A person-based key dies with the employee’s laptop unless the customer can free the device. The buyer can remove devices on a page that needs no account.
  • Offer annual terms. Companies budget yearly, and an annual plan means one invoice and one renewal conversation.
  • Make renewals visible. Set an expires_at that matches the contract and tell the customer a month before.
  • Choose the unit that matches how they think: a seat per person, a pool of devices, or a site. See seat-based licensing for teams and site licenses for companies.

Doing this with Clavem

Clavem handles the card flow automatically and the invoice flow through the management API. It does not send invoices, handle purchase orders, collect tax or provide team accounts. Stripe’s invoicing does the first two, and your accountant or a merchant of record does the tax. The API reference lists every field used above.

Questions

Can Stripe Checkout collect a business's VAT or tax ID?

Yes. Turn on tax ID collection when you create the Checkout Session, and optionally require it where Checkout supports it. Stripe says the Checkout Sessions API collects business tax IDs only and shows the tax ID and business name on invoices.

How do I license a customer who pays by invoice?

Create the license by hand with the management API or the dashboard, setting the device limit and the expiry to match the contract, and extend it by hand when the next invoice is paid. Clavem creates licenses from Stripe Checkout purchases, so an invoice sent outside Checkout does not issue a key by itself.

What should a business customer know about the license check?

That it sends the license key, a device name and optionally a hashed fingerprint, never documents or content, and that a signed token lets the app run offline. Publish those facts on a short security page.

Sources

  1. Stripe, collect customer tax IDs in Checkout (as of November 2026)
  2. Stripe Billing, subscription statuses and unpaid invoices (as of November 2026)