for agents/llms.txtv0.14.177

Home / Articles / Keys after payment: how to hand vault keys and access keys to customers once they have paid, what Stripe does and does not do after the money is taken, what FastSpring, Paddle, Lemon Squeezy, Polar, Gumroad and Square offer instead, and a design where the key is sealed to the buyer's own public key, keys are stock, and a payment provider can sell them without ever holding one

Keys after payment: how to hand vault keys and access keys to customers once they have paid, what Stripe does and does not do after the money is taken, what FastSpring, Paddle, Lemon Squeezy, Polar, Gumroad and Square offer instead, and a design where the key is sealed to the buyer's own public key, keys are stock, and a payment provider can sell them without ever holding one

By · 2026-11-17 · article v1.0.0 · newsroom v0.14.139 · paymentsstripekeyspkivaultsqr-codesproductarticle

Abstract: We now have things people want to buy: secure sends, vaults, access keys to our servers, and agentic cells. What they are buying, in the end, is a key. So we need a good way to hand a key to someone who has just paid, and today we do not have one. Our Stripe integration is a payment link, a payment, and a redirect. My research shows the picture is a little better than I thought, and still not enough. Stripe takes the money and screens fraud very well, sends a signed webhook and can put the session id in the redirect; it has products and prices, but no stock, it does not generate keys, and it knows nothing about the buyer's keys; its Workflows can chain Stripe's own actions after a payment, in preview, with custom code still in private preview. Others go further on keys: FastSpring can sell from a pre-defined list of keys, which is stock, or call your server; Paddle Classic did the same with an uploaded list; Lemon Squeezy, Polar and Gumroad generate keys per sale; Square has none. Not one of them seals a key to the buyer's own public key. So here is the design I want: the buyer's browser makes a key pair before checkout; Stripe takes the money; one small serverless function takes a key from our stock, seals it to the buyer's key, signs it, and hands it back as a link and a QR code that only they can open. And for stock managed by someone else: give the provider claim codes, not keys.

A key only the buyer can open: their key pair, Stripe for the money, our function seals the key, a QR code.

In short

The problem

We now have good reasons for people to buy things from us: secure sends, vaults, access keys to our servers, and, since this week, their own agentic cells (your own agentic cell, end to end). In almost every case, what they are buying, in the end, is a key: a vault key, an access token, a licence.

Our payments today are simple: I put a Stripe payment link on a page, the person goes to Stripe, pays, and is redirected back. That is all. What happens next, handing over the key, has to be built, and I wanted to know whether I was right that Stripe gives me nothing for it, and what the alternatives do.

What Stripe does, and does not

I was partly right. Stripe is very good at the payment: checkout, cards and wallets, fraud screening, receipts. After the money, it gives you the building blocks and not the building:

What it does not do: generate keys, hold a batch of keys and sell them one at a time, or know anything about the buyer's own keys. There is no PKI for customers. So with Stripe, the key hand-over is ours to build.

What the others do

Who can hand over a key after a payment: Stripe, FastSpring, Paddle, Lemon Squeezy, Polar, Gumroad, Square.

So the idea of keys as stock exists: FastSpring and Paddle Classic both sell from a list. But in every case the provider holds your keys in clear and hands them over in clear, by email or on a page. And not one of them knows the buyer's public key.

The design I want

The ideal starts before the payment: the buyer already has a key pair. On our page, their browser makes one, with pki.sgit.ai's module, the private half never leaving the browser (a secret is a QR code). Then:

  1. Checkout on Stripe, with the buyer's key fingerprint as the client_reference_id. A fingerprint is public, so it is exactly the kind of thing Stripe says is fine to pass; their public key itself is published beside it or posted from the page.
  2. The webhook reaches one small serverless function, a Lambda: it checks Stripe's signature, fetches the session from Stripe to confirm it is paid, and records the session id once, so a retried webhook cannot issue a second key.
  3. One key from stock: taken from a vault of pre-made keys, each used once, or minted for this sale.
  4. Sealed and signed: the key is sealed to the buyer's public key and signed with ours, as a pki.sgit.ai message, a link and a QR code.
  5. The redirect brings the buyer back to our page with the session id; the page shows the sealed link as a QR code, and only their private key, in their browser, can open it. An email copy can carry the same link, useless to anyone else.

Stripe never sees a key; the key never travels in clear; and the redirect really does carry the secret, because what it carries can only be opened by the person who paid. This is the same pattern we use for patient vaults and for onboarding a person to a cell (patient vaults, answered).

Keys as stock

Keys as stock: give the provider claim codes, let it count them; the buyer claims, we seal the real key.

I like keys as stock: make 50, sell 50, and the count is the inventory. I would love a provider to manage that stock for me, and FastSpring can. But I do not want any provider holding real vault keys.

So the answer is claim codes. Make a batch of 50 random, single-use codes, worth nothing on their own, and keep the 50 real keys in our own vault. Load the codes into a provider that sells from a list. The provider sells one code per sale, counts the stock and stops at zero. The buyer comes to our page with the code and their public key; the code is spent; we seal the real key to them. A leaked code can be claimed once and is then dead, and a real key never sat in someone else's database. The same batch can go to a reseller, an event, or an agent with a budget.

What I would do now

What this does not claim

Where this comes from

Stripe's documentation on payment link parameters, fulfilling orders and Workflows custom actions, and its Dahlia changelog; FastSpring on license key fulfilment; Paddle on fulfilment methods and transaction.completed; the Lemon Squeezy and Polar license key APIs; a Square community thread; all read on 17 November 2026. Earlier on this site: your own agentic cell, end to end, a secret is a QR code, patient vaults, answered.

Peer review Not reviewed yet. Review it

Threads

Startups & strategySite & engineering This article as a graph →

Builds on

Continued by

All articles · All graphs

Article No. 454 · start a reading list with it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.