Clavem

Launch checklist for paid software sold with Stripe and license keys

Most launch-day failures in paid software come from the gap between test mode and live mode, not from the code. Run one purchase, one renewal, one refund and one offline launch in test mode, switch to live on purpose, and make one real purchase yourself.

How to use this list

The items are in the order a launch goes wrong. Each has a way to check it, because “I think it works” is not a launch condition. Work through a section at a time, and write down the date you checked.

1. The purchase path

Item How to verify
Checkout shows the right price, currency and product name Open the live checkout link in a private window
The Stripe product or price is mapped to a license product Open the product in the licensing dashboard and look for the mapping
A test purchase issues a key Pay with 4242 4242 4242 4242, any future expiry and any CVC, then look in the license list
The buyer gets the key email and the order page Use a real inbox you can read, including spam
The key activates in a build of the app Paste it into the release build, not a developer build
The webhook shows 200 in Stripe Open Developers, then Webhooks, then the endpoint, and read the recent deliveries

Check the email in more than one client. A key sent as an image, or wrapped across two lines, causes support requests. If your checkout allows delayed payment methods such as bank debits, test one: Clavem issues nothing for them until the payment settles and Stripe sends checkout.session.async_payment_succeeded.

2. What the app does in each license state

A license can be inactive, active, expired or disabled, and the network can be down. Your app needs a defined behavior for every combination.

Situation Expected behavior
No key Free mode, or a prompt, never a crash
Valid key, online Paid features on
Valid key, offline, token younger than 14 days Paid features on
Valid key, offline, token older than 14 days A message that explains it needs a connection
Key unknown (HTTP 404) Ask for the key again
Key at its device limit Show the server’s error text and a link to the device page
Expired Renewal link, no data loss
Disabled or refunded A clear message, paid features off
HTTP 429 or 503 Keep running on the stored token, retry later

Test the offline rows by turning off the network, and the clock rows by changing the system date on a spare machine. Do not trust a diagram. See offline-first apps and licensing.

3. Refunds, renewals and failures

Rehearse the three events that will happen after launch, ready or not.

  • Full refund. Refund a test payment in full in Stripe. In Clavem the license becomes disabled and the order is marked refunded. A partial refund changes nothing, which is easy to forget when you refund half to resolve a complaint.
  • Renewal. For a subscription, use a Stripe test clock, advance past the period end and confirm the expiry moves forward. See subscription licenses with Stripe Billing.
  • Failed renewal. Use the card 4000 0000 0000 0341, which attaches successfully and then fails when charged, and watch what your app tells a customer whose payment is retried.

A refund of a subscription invoice does not disable the license in Clavem. Cancel the subscription, or disable the license by hand.

4. Delivery and updates

Item How to verify
The release has a platform label per file macos, windows and so on, matching what the app asks for
The newest published release is the one you want “Latest” means most recently published, not the highest version number
The download works from the order page Click it on each operating system
The app does not store download links Links expire after one hour, so ask for a fresh one each time
The update check works with and without a key Without a key the endpoint reports the version but gives no files
An unpublished bad build can be pulled Practice unpublishing; the previous release becomes the latest again

Practice uploading a second version before launch. Your first update will happen under pressure, and it is better to meet the process once beforehand.

Item Why
macOS build signed and notarized, Windows build signed Customers see warnings and some will not run an unsigned installer
A terms page and an EULA You need a document that says what the license allows
A privacy statement that matches what the app sends Include exactly what the license check transmits
A refund policy shown before payment Tell customers what you will do
A tax decision Collect and file yourself, use Stripe Tax, or use a merchant of record
Your support address on the Stripe account Receipts and disputes use it

The pages code signing certificates explained, writing an EULA and terms for selling software cover the first three. Tax is a decision for you and an accountant.

6. The switch from test to live

This is the step that catches people. In Clavem’s setup, an account has one Stripe connection. A test key makes a test connection and a live key makes a live one. To move from one to the other, disconnect and connect again with the live key.

Stripe product ids differ between modes, so a mapping made in test mode points at nothing in live mode. After you connect the live key, map the live products again. Then:

  1. Make a real purchase with your own card at the real price.
  2. Check the license, the email and the order page.
  3. Check the live webhook endpoint in Stripe for a 200.
  4. Refund the payment and check the license is disabled.
  5. Check the test_mode flag: licenses from test purchases are marked, so decide whether a release build accepts them.

Do this before you announce anything. A live purchase is the only test that covers the live key, the live webhook secret and the real email path.

7. Launch day and the first week

Keep a simple routine for the first days:

  • Look at the Stripe webhook deliveries each morning. A failed delivery is a customer without a key.
  • Check the licensing event log for purchases recorded as unmapped. They mean a Stripe product exists that no license product is mapped to.
  • Watch your license count against your plan. Going over a limit does not stop sales or customer validation, but it pauses manual creation and imports.
  • Read the support inbox twice a day. Lost keys and device limits are the usual questions. See lost license keys.
  • Keep a short note of everything you had to do by hand. That list is next month’s backlog.

Doing this with Clavem

Clavem covers sections 1 to 4 and part of 6: the key, the email, the order page, the device limit, the downloads and the update endpoint. It does not sign your builds, write your terms or handle tax. The quickstart walks through the test purchase, and the Stripe page lists the events and the troubleshooting table for when a purchase issues no license.

Questions

Do Stripe product ids carry over from test mode to live mode?

No. Stripe objects differ between modes, so a product mapping made in test mode points at nothing in live mode. After you connect a live key, map the live Stripe products to your license product again.

How do I test a failed payment before launch?

Stripe publishes a test card, 4000 0000 0000 0341, that attaches to a customer successfully and then fails when charged. Use it with a subscription and a test clock to see what your app shows through the failed-payment period.

Should I make a real purchase before announcing?

Yes, with a card of your own and a real price, then refund it. It is the only test that covers live keys, the live webhook, real email delivery and a real bank statement entry.

Sources

  1. Stripe testing documentation, test cards (as of November 2026)
  2. Stripe test clocks (as of November 2026)