If you sell to German consumers and your orders ship quickly, adding Wero to your checkout is a reasonable afternoon's work. It moves money bank to bank in seconds, and Stripe's documentation for the method says it supports no disputes at all, which means no chargeback path on those orders. The same page says it supports no manual capture and no subscriptions. That combination decides everything: Wero is good for in-stock goods paid for once, and wrong for pre-orders, made-to-order work and anything you bill monthly.
What is actually live
Wero is run by EPI Company SE, a Brussels payment institution authorised by the National Bank of Belgium on 20 February 2024. Its own site lists Belgium, France and Germany as live markets, with the Netherlands planned for 2026.
E-commerce acceptance is the newer part. EPI announced its first German online merchants in mid-November 2025, citing more than 46 million European users at that point and naming Eventim, Decathlon, Rossmann, CEWE, Zooplus, Hornbach and BAUR among the early adopters. On 24 July 2026 Lidl said it had switched Wero on in its German online shop, describing itself as the first food retailer in the country to do so in e-commerce. The Lidl release says shoppers need an account at one of 18 participating banks, must activate Wero once inside their banking app, and then pay by redirect or QR code.
For a small merchant the relevant fact is not the user count. It is the acquirer list. EPI names Stripe, Nexi, Nuvei, PAYONE, Unzer, Worldline, PPRO, Buckaroo, Pay.NL, payabl, Deutsche Bank, Societe Generale and VR Payment as supporting the method. If you already bill through one of those, Wero is a setting rather than a project.
What the documentation commits to, and what it does not
The clearest published specification is Stripe's. Here is what its Wero page states, read on 26 July 2026:
| Capability | Stripe's Wero page |
|---|---|
| Customer location | Germany |
| Merchant location | 28 European countries |
| Currency | EUR only |
| Availability | Preview, access requested via the docs registration endpoint |
| Products | Checkout (non-subscription), Payment Links, Elements |
| Refunds | Full and partial, up to 730 days after payment |
| Disputes | Not supported |
| Manual capture | Not supported |
| Amount limits | Minimum EUR 0.50; maximum set by the customer's bank |
| Connect | Supported |
What nobody publishes is the price. PAYONE's November 2025 announcement markets "low transaction costs" and "fewer chargebacks due to active customer consent management", but no rate card for Wero exists on EPI's, PAYONE's or Stripe's public pages. Treat any specific Wero-versus-cards saving you read as unverified until your own acquirer quotes you one in writing. Ask for it before you enable the method, not after.
The mix shift, in numbers
Our arithmetic, using assumptions you should replace with your own. Take a store shipping 1,000 German orders a month at an average of 60 euros, a dispute rate of 0.4% and a return rate of 6%. Suppose 15% of orders move to Wero after you add the button.
- 150 orders a month now sit on a rail with no dispute mechanism. At 0.4% you would have expected about 0.6 disputes on that slice, so the dispute saving is real but small at this volume: roughly seven disputes a year, plus whatever your processor charges per case.
- Those same 150 orders produce about nine returns a month. Every one of them is now a refund you have to issue yourself, on time, because the buyer has no card issuer to appeal to.
That is the honest trade. You are exchanging a small, lumpy risk you cannot control for a steady service obligation you can. It is a good trade for a store that already refunds promptly, and a bad one for a store with a backlog in its support inbox. If your dispute rate is materially above 0.4%, the calculation moves in Wero's favour fast, and you should also read our note on where card disputes actually come from before assuming a new rail fixes it.
Which orders belong on it
| Order type | Wero | Why |
|---|---|---|
| In stock, ships within 48 hours | Yes | Short liability window, refund path rarely used |
| High value, low fraud category | Yes, with a bank-limit warning at checkout | Maximum per payment is set by the shopper's bank, not by you |
| Pre-order or backorder | No | No manual capture, so you cannot authorise now and take payment at dispatch |
| Made to order or long lead time | No | You hold the customer's money with no dispute route for months |
| Subscription or repeat billing | No | Stripe lists Checkout support as non-subscription only |
| Digital goods with instant delivery | Yes | Chargeback abuse is the main loss here, and it is not available |
One structural caveat. Adding Wero does not reduce your dependence on the acquirer that fronts it. If Stripe or PAYONE suspends you, both your card and Wero volume stop together, which is the same single point of failure described in our platform dependency audit. A second payment method inside one processor is convenience, not resilience.
Enabling it today
- Confirm your acquirer supports it. If you are on Stripe, request preview access by posting your email to the registration endpoint documented on the Wero page with the preview name
wero_preview. On PAYONE, Unzer, Nexi or Worldline, open a ticket asking for Wero acceptance and a written rate. - In Stripe, go to Dashboard, then Settings, then Payment methods, and enable Wero. If you use Checkout, Payment Links or Elements, the button appears for eligible German shoppers without further front-end work.
- Exclude your subscription and pre-order flows explicitly. If those run through the same Checkout configuration, split them into a separate one before you enable the method rather than after a customer finds the gap.
- Rewrite two lines of your returns page: state that refunds on bank transfers are issued to the originating account, and give a target turnaround. This is the promise replacing the chargeback the shopper no longer has.
- Set a review date 60 days out. Compare Wero's share of orders, refund turnaround on those orders, and the rate your acquirer actually charged against your card rate. If it is not cheaper and not faster, it is just another button.
The decision rule is short. Enable Wero when the gap between payment and delivery is measured in days, keep cards for everything measured in weeks, and do not move a single order onto it until someone has sent you the price in writing.
Discussion
Sign in with Google or just a name. No email link, no password to remember.