Every Stripe payment, a license key.
Keep selling with Stripe Checkout or a Payment Link. LicenseManager.dev listens to your payments, creates the licenses each customer bought and emails them their keys. No webhook handler, no keys database, and no cut of your sales.
Free up to 100 active users. No credit card required.
// Your website: a Stripe Payment Link, nothing else
<a href="https://buy.stripe.com/7sI5lq…">Buy Acme Pro</a>
// Stripe takes the payment, LicenseManager.dev creates
// the license and emails the key to your customer.
// Your app: the customer pastes the key
import { LicenseManager } from "@licenseman/electron";
const license = new LicenseManager({
productId: "x7Kp2QaZ",
publicKey: PUBLIC_KEY,
});
await license.setLicenseKey(key); // "ACTIVE"Your customer pastes the key, your app unlocks
Stripe
The webhook code you won't have to write
Selling software with Stripe always ends with the same backend: keys, emails, renewals, refunds. Here's what each part takes, and what replaces it.
| Topic | Built on your own | Stripe, with LicenseManager.dev |
|---|---|---|
| Turning a payment into a key | A webhook handler, its signature check, a keys table | Map a price to a policy, in the dashboard |
| Events delivered twice | Idempotency to get right, or customers get two keys | Each checkout creates its licenses once |
| Emailing the key | A transactional email service and a template | Sent for you, with every key of the order |
| Validating in your app | An endpoint, a server to keep up, offline cases | SDKs with signed tokens, checked offline |
| Subscriptions | Syncing renewals, failed payments and cancellations | One license, valid while the subscription is paid |
| Refunds | A support email, then a refund by hand | Customers cancel in a portal, the refund is automatic |
| When it breaks | You find out from an angry customer | Checked every day, your admins emailed |
Setup
Four steps, then every sale ships a key
About ten minutes, most of them spent choosing your prices. No server to deploy.
- 1
Create a restricted key
In your Stripe dashboard, with read access to checkouts and prices. LicenseManager.dev never sees your secret key, and can't charge anyone.
- 2
Map your prices
Pick the Stripe prices that create licenses, and the policy of each: lifetime on 2 machines, a year of updates, a monthly plan…
- 3
Share a Payment Link
Or open Stripe Checkout from your site. Each paid checkout creates the licenses bought, and the keys land in your customer's inbox.
- 4
Unlock your app
The SDK activates the key on the customer's machine, and checks it again in the background, online or offline.
Anti-piracy
Sold to one customer, used by one customer
Stripe collects the payment. LicenseManager makes sure the key it pays for only unlocks the machines it was sold for, and that the license in your app can't be faked or stretched.
Node locking stops key sharing
Each license runs on the number of machines you sold, recognized by a fingerprint of their hardware. A customer's new computer takes the place of their old one. But when two computers in use keep taking turns on the same key, LicenseManager spots it and locks the newcomer out, for good.
Also in every SDK:
Code that runs on your customer's computer is never 100% safe from piracy: someone determined can always modify it. LicenseManager raises the bar well above casual sharing and tampering, the piracy that costs you the most.
Stripe integration
The hard parts are already written
Everything a Stripe sale needs after the payment, down to the refund of a license canceled in its first 30 days.
Checkout and Payment Links
Use the Stripe tools you already have. Delayed methods like SEPA create the licenses once the payment succeeds.
Subscription licenses
Monthly or yearly prices create a license that renews with each invoice, and a grace period while Stripe retries a card.
Money back guarantee
Customers cancel within your guarantee from their portal, and their share of the payment is refunded through Stripe.
Seats and quantities
Five units bought, five keys. A subscription of 3 seats multiplies the machines of its license.
A restricted key
Only the permissions it needs, each explained. Refunds and subscription cancellations are optional.
Test mode first
Connect a test mode key on a test product, pay with a test card, and see the whole flow before selling.
Pricing
Free for your first 100 active users. Then €29 a month.
Every feature, no time limit, no credit card. Only licenses used in the last 90 days count, and €29 / month covers 1,000 of them. Customers pay you on your own Stripe or Paddle account, and we never take a cut.
Say you sell 300 licenses at €49 this month:
- Your sales
- €14,700
- A 5% cut
- €735
- LicenseManager
- €29
FAQ
Questions before you start
No. Stripe takes payments and manages subscriptions, but has no notion of a license key, an activation or a machine. Without a tool like LicenseManager.dev, you write a webhook handler that creates the keys, stores them, emails them and keeps them in sync with refunds and renewals.
No. They go to your own Stripe account, and we take no cut of your sales. LicenseManager.dev reads your checkouts with a restricted key, and only writes the refunds and subscription cancellations you allow.
Read access to Checkout Sessions, Prices and Products, write access to Webhook Endpoints, and Subscriptions: Read to sell subscriptions. Refunds, subscription cancellations and the customer portal are optional. See the permissions.
Stripe Tax calculates and collects it at checkout; you file the returns. If you'd rather have a merchant of record handle taxes for you, sell with Paddle: LicenseManager.dev connects to it the same way.
Yes. Import your existing licenses with the API, then connect Stripe for the new sales. See the migration guide.
Something else? Write to us, a developer answers.
Turn your Payment Link into a licensing system
Create a free account, connect Stripe in test mode, and pay your first license with a test card.