The short answer
The Stripe customer portal is a Stripe-hosted page where a subscriber manages the billing side of their account. It saves you support email about expired cards, invoices and cancellations. It does not show a license key, list the devices a key is active on, or offer a download. For software you need both: the portal for money, and something else for the license.
The part that takes thought is the link between them. Every action in the portal becomes a Stripe event, and what your licensing layer does with that event decides whether a cancelled subscriber keeps the app for the paid period or loses it on the spot.
What the portal does
From Stripe’s documentation, a customer in the portal can:
- update billing information, including tax IDs
- update payment methods
- update subscriptions (switch plans or quantity, where you allow it)
- pause and resume subscriptions
- cancel immediately or at the end of the current billing period
- pay, download and view current and past invoices
You also get cancellation deflection, which offers a coupon when someone tries to cancel and lets those who cancel anyway give a reason. Stripe says you can collect those reasons through webhooks or Stripe Sigma. The portal is localised to the customer’s language and styled with your logo, colors and business information.
You do not need to write code to turn it on. In the Dashboard you activate a portal link, configure it, and share the link on your site or send it directly. Customers log in with their email address, and Stripe emails them a login link.
What it does not do for software
| A buyer wants to | Portal | Where it lives instead |
|---|---|---|
| See or copy their license key | No | The order page or the email with the key |
| See which computers use the key | No | A device page tied to the license |
| Remove an old laptop to free a seat | No | The same device page, or a deactivate call from the app |
| Download the latest version | No | A download page, or an update check in the app |
| Change the number of seats and get more keys | Changes the quantity on the subscription, but nothing issues keys | Your licensing layer, or a new purchase |
| Manage a one-time purchase | Little: there may be no Customer to log into | Receipts and the order page |
The last row has a cause worth knowing. The portal works on Stripe Customers. A one-time Checkout payment may not create one unless you set Checkout to, so a buyer of a perpetual license may have nothing to log into.
Two ways to open it
The no-code link. Activate it once and put the link in your app’s menu or on your order page. The buyer types their purchase email and Stripe sends a login link. Stripe notes that if several customers share an email, it picks the most recently created one that has an active subscription, and that customers cannot change their email through this link. If a buyer never receives the mail, the first thing to check is that the address matches an existing customer.
A portal session from your server. Your server creates a session for a known Stripe customer and redirects the buyer to the returned URL:
curl https://api.stripe.com/v1/billing_portal/sessions \
-u "sk_test_...:" \
-d "customer=cus_..." \
--data-urlencode "return_url=https://example.com/account"
Stripe’s current documentation also shows a customer_account parameter for its newer Accounts v2 model, so use the one that matches your integration. Portal sessions are temporary: a new one expires after 5 minutes if unused, and once used it expires within an hour of the last activity. Create the session when the buyer clicks, not when the page loads.
This route needs a signed-in user, so your server knows which customer it is. If your app has license keys but no accounts, the no-code link is the shorter path.
What each portal action does to a license
The portal changes the subscription. Stripe then sends events, and the licensing layer reacts. The right column below is Clavem’s documented behavior, which is a sensible default for any system.
| Portal action | Stripe event | What the license should do |
|---|---|---|
| Cancel at the end of the period | customer.subscription.updated with cancel_at_period_end true, then customer.subscription.deleted at the end |
Stay valid until the deleted event, then expire |
| Cancel immediately | customer.subscription.deleted now |
Expire now |
| Undo a scheduled cancellation | customer.subscription.updated |
Nothing changes |
| Update the card | No license-relevant event | Nothing changes |
| A renewal payment fails | Status moves to past_due |
Stay valid while Stripe retries |
| Retries give up | Status becomes unpaid or canceled |
Expire |
| A late payment succeeds | invoice.paid |
Revive the license and move the expiry |
| Pause | Status becomes paused |
Expire. Test the resume path before offering pausing |
| Switch plan or quantity | customer.subscription.updated |
No new key is issued, because keys come from checkout.session.completed |
Stripe’s cancel documentation says customer.subscription.updated is sent for any subscription update including cancel_at_period_end being set to true, and customer.subscription.deleted is sent when a subscription ends, either from a direct cancel or when one set to cancel at period end reaches its period end. A canceled subscription cannot be reactivated. A scheduled cancellation can be stopped until the period ends.
Configuration choices that matter for software
- Cancel at the end of the period. The buyer has paid for the period, and they will remember being cut off mid-month. Offer immediate cancellation only if your refund policy matches.
- Limit plan switching to prices that map to the same product. If your Basic and Pro tiers are different products with different keys, a switch in the portal changes the Stripe subscription but not the key. Either remove plan switching from the portal, or have your system handle the change.
- Check Stripe’s limits. A customer can cancel in the portal but cannot update a subscription that has multiple products, usage-based billing, trial offers, invoices sent for collection, or an unsupported payment method.
- Turn on cancellation reasons. They are a free survey of why people leave.
- Decide about pausing. A paused subscription expires the license in Clavem. If that surprises your customers, disable pausing.
- Mind trials. Stripe says by default a customer’s change to a trialing subscription ends the trial and creates an invoice for immediate payment, unless you configure the portal otherwise.
Doing this with Clavem
Clavem keeps the two halves separate on purpose. Stripe’s portal handles billing. Clavem handles the license: it listens to invoice.paid, customer.subscription.updated and customer.subscription.deleted, and moves each license to match, with three days of grace after the paid period so a late renewal does not lock anyone out.
For the buyer’s side of the license, Clavem has a device page at /licenses/manage where they enter their key to see and remove device activations. There is no account and no email round trip, so you can link to it from the same menu as the portal link. A buyer never creates a Clavem account. Clavem does not replace the portal and does not offer a billing page of its own.
Subscription licenses with Stripe Billing goes through renewals in more detail, and the Stripe connection guide lists every event.
Questions
Do I need the Stripe customer portal if I sell one-time licenses?
Usually not. One-time buyers have receipts, and they may not have a Stripe Customer at all unless you ask Checkout to create one. The portal earns its place when you sell subscriptions or want buyers to download invoices and update tax IDs.
Can a customer cancel in the portal and keep using the software until the period ends?
Yes, if you allow cancellation at the end of the billing period. Stripe then sends customer.subscription.deleted when the period ends, and a license tied to the subscription should end at that moment, not before.
Does the portal work with Stripe Managed Payments?
Stripe's portal documentation lists Managed Payments among the products it works with, while the Managed Payments documentation says buyers manage orders on the Link website. Check which one your account shows before you link to either.
Sources
- Stripe docs, customer portal (as of November 2026)
- Stripe docs, set up the no-code customer portal (as of November 2026)
- Stripe docs, integrate the customer portal with the API (as of November 2026)
- Stripe docs, cancel subscriptions (as of November 2026)
- Stripe docs, subscription webhooks (as of November 2026)
- Stripe docs, how Managed Payments works (as of November 2026)