The short answer
Offer a refund window you can live with, say it before the buyer pays, and make the license follow the money. A refund on Stripe costs you the processing fee, because Stripe does not give it back. A chargeback costs you the sale, a dispute fee and your time. The cheapest way to avoid chargebacks is to make refunds easy.
The rest of this article covers the policy choices, the numbers, and the exact things that happen to a license key at each step.
Design the policy first
Three choices define a software refund policy: how long, on what condition, and what the license does.
| Policy | Good for | Risk | What the license does |
|---|---|---|---|
| 14 or 30 days, no questions | Apps buyers cannot evaluate first | Some buyers use and refund | Disabled at refund |
| Refund only if never activated | Apps with a free trial | Buyers who hit a bug on day two are refused and may dispute | Disabled at refund |
| Refund within window, minus a handling fee | Recovers the processing fee Stripe keeps | Feels punitive, and some buyers dispute instead | Disabled at refund |
| Subscriptions: pro-rata after cancellation | Monthly plans | Needs manual proration | Expires at cancellation |
| No refunds | Nothing sold online | Chargebacks, bad reviews, and in some places a legal problem | Not applicable |
Write the policy where the buyer sees it before paying, in your terms and on the checkout page. A buyer who knew the window and did not use it has less standing in a dispute. Terms for selling software covers where to put it.
A trial reduces refund demand because the question “does it work for me” is answered before payment. Free trial vs freemium goes through the options.
What a refund costs on Stripe
Stripe’s refund documentation says you can refund all or part of a payment after it succeeds, and that “Stripe’s processing fees from the original transaction aren’t returned.” The pricing page repeats it: payment processing, Connect and currency conversion fees from the original transaction are not returned, and for most payment methods there is no extra fee for issuing the refund (bank transfers can have one).
Worked example, with stated assumptions. Take a $49 sale on an assumed 2.9% plus $0.30 rate. The fee is $0.30 plus $1.42, so $1.72, and the refund does not give it back. If you sell 1,000 licenses a month and 5% are refunded, you refund 50 sales:
- Refunded revenue: 50 x $49 = $2,450
- Fees you cannot recover: 50 x $1.72 = $86
The figure is small, which is why a generous policy is rarely expensive. Rates depend on your country, so use the Stripe fee calculator with your own.
Mechanics worth knowing, all from Stripe’s documentation:
- Refunds go back to the original payment method only. You cannot send one to a different card.
- Refunds use your available Stripe balance. If it does not cover the refund, a card refund stays pending, and if the balance is still short after 45 days the refund fails and you must pay the customer another way.
- You can cancel an eligible card refund in the Dashboard within 30 minutes of creating it, not after.
- You can issue several refunds against one charge, up to the original amount.
Refunds versus chargebacks
A chargeback is a dispute opened through the buyer’s bank. Stripe’s documentation describes the order of events: the card network pulls the disputed amount from your Stripe balance and holds it, plus a dispute fee, while you respond.
On the Swiss pricing page the fee for each dispute received is CHF 20.00, and a further CHF 20.00 applies if you counter it manually (returned if you win, not if you lose). Other countries differ.
Worked example on the same $49 sale, with the dispute fee assumed at $20: if you lose, you are out the $49, the $20 fee and the $1.72 processing fee, so $70.72. That is about 41 times what the refund cost. Even a dispute you win costs the time to answer it.
Stripe’s documentation says card networks typically allow cardholders to start a dispute within 120 days of the payment, and sometimes longer. So the exposure outlasts any refund window you set. Two practical consequences:
- Make asking for a refund easier than disputing. A support address on the order page and the receipt is enough.
- Do not count on a late refund to stop a dispute. Stripe’s guidance on early fraud warnings says a refund issued after the warning does not change it, and that a refund prevents the report only when processed as a reversal, which usually happens within 2 hours of the payment.
What should happen to the license
Money and access should move together. These are the cases, with Clavem’s documented behavior where it applies.
| Event | Stripe event | Right outcome | Clavem behavior |
|---|---|---|---|
| Full refund of a one-time payment | charge.refunded |
License disabled | Disables every license from the order and marks the order refunded |
| Partial refund | charge.refunded |
Your choice | Nothing changes |
| Refund of a subscription invoice | charge.refunded |
Cancel the subscription | Does not disable the license. Cancel the subscription, which expires it, or disable the license yourself |
| Dispute opened or lost | charge.dispute.created |
Disable the license | Not one of the six events Clavem listens to, so nothing changes until you act |
| Refund of one seat from a multi-seat order | charge.refunded |
Disable one key | A partial refund changes nothing, so disable that key by hand |
Clavem finds the order through the payment intent, which one-time Checkout payments have. A disabled license stays disabled until you enable it, whatever Stripe says later. To disable one by hand, use the dashboard or the management API:
curl -X PATCH https://clavem.io/v1/admin/licenses/123 \
-H "Authorization: Bearer sk_clavem_..." \
-H "Content-Type: application/json" \
-d '{"disabled": true}'
The refund-after-download problem
A refund does not take the software back. After a full refund, the license is disabled, and the next time the app validates online it receives valid: false. How fast that happens depends on how your app checks.
- An app that validates at every launch notices at the next launch with a connection.
- An app that trusts a signed token offline keeps working until the token’s
refresh_bytime. Clavem sets that to 14 days after issue.
That window is the price of working offline. You can shorten it by requiring online validation more often, at the cost of annoying honest travellers. A buyer determined to keep a refunded copy can often do it for a while whatever you do. The goal is to make it inconvenient, not impossible.
Edge cases
- Imported licenses. Keys moved in from another platform have no Stripe order, so a Stripe refund cannot disable them. Handle those by hand.
- Refunds in a merchant-of-record setup. Stripe’s Managed Payments documentation says you can issue refunds and update subscriptions in the Dashboard or through the API, and that the MoR handles transaction support.
- Refund requests after the window. Decide the policy for these too, since a refused request can become a dispute. In the example above a refund costs about $1.72 and a lost dispute about $70, which argues for granting late requests that look genuine.
- EU consumers. The EU’s consumer information site describes a 14-day cooling-off period for online purchases, with an exception for online digital content you started downloading after the buyer expressly agreed to lose the right of withdrawal, and for sealed software that has been unsealed. The details are national law, so this is general information, not legal advice. Ask a lawyer how to implement the consent before relying on it.
Doing this with Clavem
Clavem listens to charge.refunded on your Stripe account. A full refund of a one-time payment disables every license from that order. Partial refunds and subscription-invoice refunds change nothing, for the reasons above, and a dispute does not trigger anything, so watch your Stripe notifications for those. Plan limits never stop these events from being processed.
Everything else in this article remains your decision: the window, the wording and whether to refund late requests. The Stripe connection guide lists each event and its effect.
Questions
Does Stripe return its fee when I refund a payment?
No. Stripe's documentation says the processing fees from the original transaction are not returned when you refund. Disputes cost more: a fee per dispute is charged on top of the disputed amount.
Should a refund revoke the license key?
Yes, for a full refund. Otherwise the buyer keeps the software and the money. Clavem disables the licenses from an order when Stripe reports a full refund of the payment, and leaves them alone after a partial refund.
Do EU customers have a right to refunds on software downloads?
Often yes, for 14 days, with an exception for digital content once the download has started after the buyer expressly agreed to lose the right. The conditions are strict and differ by country, so ask a lawyer before relying on the exception.