Stripe Added Wero in Preview on October 28. Checkout's Subscription Mode Is the One Place You Can't Use It.
Stripe's new Wero payment method settles in under 10 seconds across 5 European markets. Its own docs list recurring payments as unsupported — by design.
Stripe quietly added Wero as a payment method in preview on October 28, 2026, in the same release that shipped the self-serve pause button and the 51 new webhook events we've covered elsewhere. Wero itself is a genuinely interesting rail — instant, bank-to-bank, built by a consortium of European banks specifically to compete with cards and PayPal. But read past the "new payment method" headline and into Stripe's own property table, and one line matters more than anything else if you're thinking about using it for a SaaS product: recurring payments, no.
That's not a temporary bug or a rollout gap Stripe forgot to patch. It's a documented property of the payment method, stated as plainly as the currency restriction (EUR only) or the settlement time (under 10 seconds). If you're weighing whether Wero belongs anywhere near your billing page, the "no" is the first fact to plan around, not a footnote to discover after a customer tries to subscribe with it.
What Wero actually is, mechanically
Wero comes out of the European Payments Initiative, a group of European banks and payment service providers that built it specifically as an account-to-account alternative to cards. Rather than moving money through a card network, a Wero payment moves it directly between bank accounts over SEPA Instant Credit Transfer — the same underlying rail that's made instant bank transfers normal across the Eurozone over the past few years. The customer-facing flow is simple: pick Wero at checkout, get redirected to Wero's authentication page, scan a QR code to open the Wero app already installed on their phone, and approve the payment there. Stripe's documentation puts settlement at typically under 10 seconds, and the customer lands back on the merchant's site with the payment already complete.
That's a meaningfully different mechanism from SEPA Direct Debit, which pulls money on a mandate the merchant initiates, or from a card, which authorizes first and settles later. Wero is customer-initiated and instant, every time — there's no concept of the merchant pulling a payment on a schedule the way a subscription needs. That single design fact is most of why recurring billing doesn't exist for it yet.
The geography doesn't match either, and it's not close
Before the recurring question even comes up, there's a second mismatch worth knowing about: where Wero actually works depends on whether you're asking about the merchant or the customer, and the two answers aren't close to the same size.
Source: Stripe, Wero payment method documentation — 30 business (merchant) locations vs. 5 customer locations, calculated as a share of the merchant-eligible set.
Stripe lets merchants registered in 30 European countries — everywhere from Austria and Bulgaria down to Slovakia and Slovenia — turn Wero on in their Dashboard. But a customer can only actually pay with it if they're located in Belgium, France, Germany, Luxembourg, or the Netherlands, because those are the only markets where EPI has rolled the consumer wallet out so far. A Stripe account based in Spain or Italy can flip Wero on today and see zero Wero payments arrive, not because of a configuration mistake, but because none of their customers live anywhere the wallet exists yet. EPI's own rollout notes describe Germany as live since late 2025 with France and Belgium phasing in through 2026, and Luxembourg and the Netherlands following — this is a live-expanding market, not a finished one.
Where Wero sits next to the other European bank methods we've covered
Wero isn't the first local European payment method we've written about that has an off-session wrinkle. It's useful to put it next to the others, because the gap looks different each time:
| Payment method | Market | Recurring billing on Stripe | How it actually works |
|---|---|---|---|
| Wero | Belgium, France, Germany, Luxembourg, Netherlands | No | Excluded from Checkout subscription mode and setup mode entirely — no off-session path exists |
| BLIK | Poland | Yes, capped | Mandate-based (Model O), but every off-session charge is capped at 2,000 PLN |
| Bancontact | Belgium | Yes, indirectly | Checkout silently converts a saved Bancontact payment into a SEPA Direct Debit mandate |
| SEPA Direct Debit | Eurozone-wide | Yes | Native mandate-based debit, but carries an 8-week unconditional refund right |
Every other row in that table has some mechanism for turning a one-time payment into a recurring one, even if it's capped, indirect, or carries its own refund risk. Wero doesn't have one yet. Stripe isn't quietly routing a Wero payment into a SEPA mandate the way it does with Bancontact, and it isn't shipping a capped off-session mode the way it did for BLIK. It's simply not available, and Checkout enforces that at the product level rather than leaving it to a decline code you'd discover at charge time.
Why the marketing and the docs seem to disagree
If you've seen Stripe's own France-market resources describe Wero as working for "one-time purchases and subscriptions as well as amounts charged after delivery," that's not actually a contradiction of the property table — it's describing a different thing. What that language refers to is Wero's wallet remembering a customer's payment and shipping details for a faster repeat checkout, the same convenience a saved address or a one-click reorder button gives you. The customer still has to open their Wero app and approve each transaction. That's a UX convenience for repeat purchases a customer actively initiates, not an off-session mandate a merchant can charge on a billing cycle without the customer present — which is the specific capability a subscription needs.
EPI's own public roadmap is honest about this gap: recurring payments and subscription management are listed as a planned "value-added service" for Wero later in 2026, alongside point-of-sale and loyalty integrations, not something already live. Stripe's "No" in the property table matches that roadmap exactly. If subscription support for Wero ships through EPI this year, expect it to arrive as a new mandate type with its own rules — the way BLIK's Model O mandate arrived separately from one-time BLIK payments — not as a quiet toggle on the existing one-time flow.
No dispute network either — which changes what "safe" means here
The second line in Wero's property table worth sitting with is dispute support: also "No." There's no chargeback mechanism behind a Wero payment the way there is behind a card network. What Stripe gives you instead is a notably generous refund window — merchants can issue full or repeated partial refunds on a Wero payment for up to 730 days after the original charge, versus the roughly 120-day window most card disputes allow a cardholder to file within.
That trade matters for how you think about refund policy as a retention and risk lever. With cards, a merchant who stonewalls a refund request risks the customer going around them straight to a chargeback. With Wero, there's no "around them" — the merchant's own refund policy is the entire dispute resolution system, for up to two years after the fact. That's a real advantage against chargeback abuse, and a real liability if your support team isn't equipped to handle refund requests directly and promptly.
What to actually do with Wero right now if you sell into these markets
If your SaaS has real volume from Belgium, France, Germany, Luxembourg, or the Netherlands, Wero is worth enabling for exactly the use cases it already supports: a one-time signup fee, an annual prepay a customer actively returns to pay each year, an add-on purchase, or a usage top-up a customer initiates themselves rather than one your billing engine triggers automatically. It is not, today, a replacement for whatever you're already using to rebill a monthly or annual subscription — keep a card or SEPA Direct Debit on file as the actual subscription rail, and treat Wero as an additional option at checkout rather than a substitute for one.
Don't build around the assumption that Wero will quietly start supporting subscriptions the way BLIK's recurring mode arrived as an upgrade to an existing one-time method. Watch EPI's own roadmap rather than Stripe's Checkout UI for the signal, because the mandate type for recurring Wero, if and when it ships, will need its own disclosures and its own decline handling — the same way BLIK's Model O did. In the meantime, a payment-method gap like this one is exactly the kind of thing worth sizing before you invest engineering time around it: our churn calculator is a quick way to check how much involuntary churn risk a missing recurring rail in a specific market is actually worth chasing, versus just keeping the card or SEPA Direct Debit fallback you already have. And whichever payment method a subscriber used to sign up, the moment they try to leave is still the moment that matters most — which is the exact gap a cancellation flow like CancelFlow is built to catch, regardless of what rail billed them in the first place.
Frequently asked questions
What is Wero and how does a Wero payment work on Stripe?+
Wero is a pan-European account-to-account payment method built by the European Payments Initiative (EPI), a consortium of European banks, and it runs on the SEPA Instant Credit Transfer rail rather than the card networks. A customer chooses Wero at checkout, gets redirected to a Wero authentication page, scans a QR code to open the Wero app on their phone, and approves the payment there. The transfer settles bank-to-bank, typically in under 10 seconds, and the customer is redirected back to the merchant's site. Stripe added it as a payment method in preview on October 28, 2026.
Can I use Wero for subscription billing on Stripe?+
Not today. Stripe's own payment method property table lists Wero's recurring payments support as "No," and its product support notes are explicit that Wero is not supported when using Checkout in subscription mode or setup mode. That rules out the two standard ways Stripe would normally let you save a payment method for off-session billing. Wero currently works only for a one-time charge taken through regular Checkout, Payment Links, Elements (excluding the Express Checkout Element), or a Connect-routed payment.
Which customers can pay with Wero, and which merchants can accept it?+
There's a real asymmetry here. Stripe only lets customers located in Belgium, France, Germany, Luxembourg, and the Netherlands pay with Wero, because that's where EPI has actually rolled it out to consumers. Merchants, on the other hand, can turn Wero on from a Stripe account registered in any of 30 European countries, from Austria to Slovakia. A merchant based in Spain, Italy, or Poland can enable Wero today and still get zero Wero payments, because none of their customers are in a country where the wallet exists yet.
Does Wero support chargebacks or disputes, and what's the refund policy?+
No dispute support at all — Stripe's property table lists dispute support for Wero as "No," meaning there's no chargeback network behind it the way there is for a card. What Stripe offers instead is an unusually long refund window: merchants can issue full or multiple partial refunds on a Wero payment for up to 730 days after the original charge, compared to the roughly 120-day dispute window most card networks give a cardholder. The absence of a dispute process shifts essentially all resolution responsibility onto the merchant's own refund policy.
Stop losing subscribers today
One script tag. One function call. A live cancellation flow in under 10 minutes.
Start free trial →