Klarna Subscriptions Can Renew Automatically on Stripe. A New UK Rule Means Some Still Need the Customer There.

We wrote recently about Billie, Stripe's B2B buy-now-pay-later method, and the whole piece turned on one word buried in Stripe's docs: single-use. Klarna, sitting a few rows up in the same payment method reference table, is built the opposite way. It can be saved to a customer object, charged off-session on a schedule, and reused renewal after renewal — Stripe's own properties table lists "Recurring payments support: Yes" and "Subscriptions" under product support, no caveats attached. For a SaaS business that's been treating Klarna as a checkout-only novelty for one-time purchases, that's new ground worth understanding before you turn it on for a subscription price point.

The mechanics are close enough to a card that it's tempting to treat Klarna as a drop-in replacement for one. It mostly is — until a renewal needs authentication Klarna can't get without the customer standing in front of a screen, at which point the resemblance to a card stops.

How a Klarna subscription renewal actually works

Setting up a Klarna subscription looks almost identical to setting up a card for future use. You create a PaymentIntent or SetupIntent with setup_future_usage or usage: off_session, pass a subscription_reference — an arbitrary ID you choose, like GYM_ANNUAL_MEMBERSHIP — along with the billing interval, and redirect the customer to Klarna to authorize it. Klarna hands back a reusable PaymentMethod ID tied to that reference.

On renewal, you create a fresh PaymentIntent with off_session: true and confirm: true, pass the saved PaymentMethod and customer IDs, and send the same subscription reference again. If the amount or terms changed, you send the new numbers under the old reference. Get the reference wrong and Stripe rejects the charge outright — a small but real integration trap that doesn't exist with a plain card token.

The part that actually matters for churn is one line in Stripe's own guidance: setting off_session to true "causes the PaymentIntent to throw an error if authentication is required." A card renewal that needs 3D Secure typically resolves through Stripe's usual authentication handling, similar to what we've covered with SCA on European card renewals. A Klarna renewal that trips Klarna's own authentication requirement has no such quiet path off-session — it fails, full stop, and the customer has to be brought back through a redirect to clear it.

What each country's Klarna will actually rebill

Klarna doesn't offer the same payment options everywhere, and critically, not every option that exists in a given country is eligible for a subscription in the first place. Pulled directly from Stripe's own country-by-country Klarna reference:

Source: Stripe, Klarna payment method documentation — supported payment options by country (2026).

That 16% is the number worth sitting with. Pay Later — the "buy it now, get a single bill in 30 days" option most people picture when they hear Klarna — barely exists for subscriptions at all outside three markets. For nearly every other country, a monthly or annual SaaS plan billed through Klarna gets quietly routed to Pay in Full behind the scenes, which functions like a card or bank debit pass-through rather than actual installment credit. If you turned on Klarna expecting it to widen who can afford your product through spread-out payments, check which option your subscribers are actually being offered before you count on that effect showing up in conversion.

The UK carve-out that shipped alongside the regulation

The FCA's Deferred Payment Credit rules didn't just add paperwork for BNPL lenders — they changed a specific technical behavior Stripe had to build around. Per Stripe's own documentation: because of the Consumer Credit Act reforms starting July 15, 2026, Klarna handles GBP tokenized payments differently depending on whether the customer is present in the flow. On-session GBP renewals now require step-up authentication, meaning the customer has to be redirected to authorize the charge in the moment, the same way a first-time payment works. Off-session GBP renewals — the kind your billing system fires automatically at 3am with nobody watching — get automatically converted to Pay in Full.

Translate that into what actually happens to a UK subscriber's bill: someone who signed up under a Pay in 3 or 4 plan can find their renewal silently becomes a single full-amount charge instead, with no installment split, because the off-session path doesn't support the authentication the installment option now needs. The total owed doesn't change. The experience does, and an unexplained shift from three payments to one is exactly the kind of thing that generates a "why was I charged the whole amount" ticket — or, worse, a dispute that reads as fraud to your reporting even though nothing about the charge itself was wrong.

Worth separating from a plain decline: this isn't a payment that fails and needs a retry, it's a payment that succeeds differently than the customer expects. Your dunning stack won't catch it, because nothing failed. Your support team will catch it, eventually, as a billing confusion ticket that looks nothing like the failed-payment tickets they're used to triaging.

The other renewal event Klarna doesn't let you skip: an upgrade

Change the subscription amount — a plan upgrade, a seat added mid-cycle, a price increase — and Stripe's own guidance for Klarna is explicit that the resulting PaymentIntent "requires a redirect to Klarna to be completed." A card handles an upgraded charge amount silently, using the same authorization it already has. Klarna wants to re-confirm the new terms with the customer through its own flow, every time the numbers change enough to matter, because the underlying credit decision was made against the original terms, not whatever you decide to charge next.

That's a real operational difference from how most SaaS billing logic assumes upgrades work. If your upgrade flow charges an immediate prorated amount and expects a synchronous success response, a Klarna-paying customer mid-upgrade may instead need a browser redirect you didn't build for, on a code path that's normally instant for every other payment method.

The revocation path that skips your product entirely

Beyond authentication, Klarna gives the customer a cancellation lever with nothing to do with your product at all. A customer can deactivate a saved, reusable Klarna payment method from inside the Klarna app itself — no login to your dashboard, no visit to your cancel page. Stripe surfaces that as a mandate.updated webhook, and it's on you to call detach on the PaymentMethod once you see it, or your system keeps believing a working renewal method is on file until the next charge attempt fails against a method that's already dead.

It's the same structural gap we flagged with Mastercard letting cardholders cancel from their banking app — a channel the customer trusts more than your product becomes an exit they can take without ever touching your cancellation flow, your save offer, or your reason survey. The Klarna version is narrower (it only kills the payment method, not necessarily their intent to keep using your product), but the blind spot is the same: if you're not listening for mandate.updated, you find out about the revocation the hard way, at the worst possible moment — mid-renewal.

What to actually do if you're turning Klarna on for subscriptions

Check what your customer's country actually supports before promising installments

If your pricing or marketing implies "pay in installments with Klarna," verify that promise holds for the countries your subscribers are actually in. Outside Germany, Sweden, and the US, a subscription is far more likely to land on Pay in Full than a true BNPL split — don't build a pricing page around a payment experience most of your Klarna users won't see.

Subscribe to mandate.updated and treat it like a payment-method-expiring signal

Route it the way you'd route any other involuntary churn signal — flag the account, and either prompt for a new payment method proactively or make sure your next renewal attempt fails gracefully into a recovery flow instead of a silent decline nobody notices for days.

Segment UK GBP failures and format shifts separately from card declines

An "authentication required, off-session" failure and a "charge succeeded but the format changed" event are both distinct from an ordinary decline, and lumping either into a generic failed-payment bucket hides which fix actually applies. One needs a redirect link sent to the customer; the other needs a proactive heads-up email so a full-amount charge doesn't read as a billing error.

Keep a fallback payment method on file regardless

The same advice that applies to Billie's single-use design applies here for a different reason: any renewal that needs a redirect Klarna can't get automatically is a renewal that can fail through no fault of the customer's underlying creditworthiness. A card or bank account on file as backup turns that into a one-click recovery instead of a lapsed subscription.

None of this makes Klarna a bad subscription payment method — reusable, storable, off-session-capable puts it in a different category from Billie's single-use design, and for the right customer base it's a real conversion lever at checkout. It just isn't a card with a different logo, and the gap shows up exactly where SaaS billing tends to be least instrumented: renewal, upgrade, and the moment a regulator changes what "off-session" is allowed to mean. Run your current involuntary churn rate through our churn calculator with a UK-GBP segment modeled separately if Klarna makes up a meaningful share of that market, and if a subscriber's Klarna method does lapse for reasons that have nothing to do with wanting to leave, a cancellation flow that catches the ones who reach the cancel page on purpose — which is what CancelFlow is built to do — still won't recover the renewals that never made it that far without a fallback method in place.

Frequently asked questions

Stop losing subscribers today

One script tag. One function call. A live cancellation flow in under 10 minutes.