Wero at Lidl: Europe's Bank-to-Bank Wallet Reaches the Checkout

On 24 July 2026, Lidl added Wero as a payment method on lidl.de, its German online shop. Lidl and the European Payments Initiative plan to bring it to the Belgian and French online shops later this year. The announcement said nothing about paying with Wero in Lidl's stores.

On its own, a discounter adding a wallet is not news. What makes this one worth paying attention to is what Wero is: a European account-to-account payment method that settles over SEPA Instant Credit Transfer and does not route through Visa or Mastercard at all. When a retailer with Lidl's footprint puts that in front of consumers, the rest of the market starts getting questions from its own board.

This is a practical look at Wero for anyone who has to decide whether to integrate it, and what integrating actually costs.

What Wero Is

Wero is the wallet built by the European Payments Initiative, a consortium of European banks and payment processors formed to reduce the continent's dependence on non-European card schemes.

The mechanics are straightforward. A customer pays directly from their bank account. The transfer runs on SEPA Instant Credit Transfer, so funds land in the merchant account in roughly ten seconds, around the clock. There is no card number, no card scheme in the middle, and no acquirer authorisation and settlement cycle in the traditional sense.

That is the substantive difference from a card payment, and from PayPal. It is not a card wrapper with a different logo. It is a push payment from the payer's bank to the payee's bank on instant rails.

Where It Stands

Wero launched with person to person transfers in 2024 across Germany, France and Belgium. Adoption there was fast: roughly 43 million registered users and about 7.5 billion euros transferred in the first year, largely because the wallet is embedded inside the banking apps people already use rather than being a separate app they have to be persuaded to download. In September 2026, EPI put the figure at 60 million users.

E-commerce came next. Germany went live in late 2025 and Belgium followed on 3 March 2026. In France the first e-commerce payments went through in April 2026, with the rollout continuing through the year. Luxembourg launched in September 2026 with person to person, e-commerce, invoice and in-store payments together. The Netherlands follows as iDEAL migrates to Wero, which EPI plans for 2027. In-store payment is only starting: in September 2026, EPI announced that shoppers in Belgium can pay by scanning a Wero QR code on Payworld terminals, and it plans broader point of sale availability in France and Germany progressively from 2027.

Merchant adoption in Germany has moved quickly. Alongside Lidl, current or announced acceptance includes Decathlon, dm, Rossmann, Hornbach, Eventim, Zooplus, CEWE, Cineplex, BAUR, Dott, Air Europa and Veepee. In France, Air France, Decathlon, Fnac Darty and Orange have confirmed they are adopting it. EPI reported in September 2026 that more than 48,000 merchants had processed Wero payments across its five markets. Between the participating banks, the wallet reaches something in the region of 80 percent of consumers in its live markets.

There is also a small business variant, sometimes referred to as P2Pro, that lets merchants accept payment by QR code at a fee in the region of 0.7 percent of the transaction.

Why Merchants Are Interested

Three reasons come up repeatedly in the conversations we have.

Cost. Card acceptance carries interchange, scheme fees and acquirer margin. An account-to-account push payment removes most of that structure. Actual pricing depends on your payment service provider, but the underlying cost base is lower.

Settlement speed. Funds arrive in seconds rather than in a settlement batch days later. For a business with thin margins and real working capital constraints, that is a genuine operational difference, not a marketing line.

Chargeback profile. A completed SEPA Instant Credit Transfer is a push payment authorised by the payer in their own banking app. It does not carry the card chargeback framework. That reduces one category of loss, though it also removes a dispute mechanism customers are used to, which has customer service implications you should plan for.

There is a fourth reason that shows up in European boardrooms and is worth naming honestly: payment sovereignty. Several large retailers have been explicit that reducing dependence on non-European payment infrastructure is a strategic goal in itself. Lidl's parent framed its launch around European standards for data protection and IT security. Whether you find that argument compelling or not, it is influencing procurement decisions.

How Integration Works

Wero uses a four-corner model, the same shape as card payments: payer, payer's bank, payee's bank, payee. As a merchant you do not integrate with Wero directly in most cases. You integrate through your payment service provider or acquirer, who handles onboarding and relays the payment request.

The flow at checkout:

1. Customer selects Wero at payment.
2. Your PSP creates a payment request through the Wero API.
3. The customer confirms, either by scanning a QR code with their phone on desktop, or by being redirected into their banking app on mobile.
4. The customer authorises in their bank app, with whatever strong authentication their bank uses.
5. The SEPA Instant transfer executes and you receive confirmation, typically within seconds.
6. You release the order.

Wero can also share the customer's stored contact and delivery details with the merchant, which shortens the checkout form considerably for new customers. That is a conversion argument and, incidentally, a data protection consideration: you are receiving personal data through a new channel and it belongs in your record of processing activities.

The PSP-side API generally covers consent, authorisation and capture, with refund support. EPI has been consistent in messaging that one integration gives access to every Wero market and feature, which is the main promise distinguishing it from integrating a separate local method per country.

What It Actually Costs You to Build

The API call is the easy part. The work is everywhere else.

Checkout UI. A new payment method means a new option, a new logo, a new selected state, and a QR code display path on desktop that most checkouts do not currently have. Get the accessibility right on this: the QR code needs a text alternative and a fallback route, because a customer using a screen reader cannot scan a code from their own screen.

Order state machine. Wero introduces states you may not model today. Payment request created, awaiting customer authorisation, authorised, settled, expired, cancelled by user, rejected by bank. If your system currently thinks in terms of authorised and captured, this needs mapping work.

Timeouts and abandonment. The customer leaves your page to authorise in their banking app. Some of them will not come back. You need a reconciliation path that resolves an order whose payment succeeded but whose browser never returned, and you need to handle the customer who retries and creates a second payment request.

Refunds. Refunds are initiated through the API, but the operational model differs from card refunds. Your customer service tooling, your accounting integration and your refund SLAs all need to reflect that.

Reconciliation and accounting. Instant settlement changes your bank statement pattern. Individual credits arriving continuously rather than a daily aggregated payout from an acquirer. Your finance team will have an opinion about this, and it is better to hear it before go-live.

Fraud and risk. Push payments shift the risk profile. Card fraud largely disappears. Authorised push payment fraud, where a customer is socially engineered, becomes the thing to think about, alongside the fact that you have fewer levers once funds have moved.

Customer support. Your agents need to know what Wero is, how to help a customer whose bank does not support it yet, and what to say when someone asks for a chargeback that does not exist in this rail.

Budget for the surrounding work, not just the API call. In our experience the integration itself is a small fraction of the total.

Should You Integrate?

An honest answer depends on where you sell.

If you sell in Germany, France, Belgium, the Netherlands or Luxembourg, this is worth planning for now. Consumer reach is already high because the wallet lives inside existing banking apps, and the merchant list is growing fast enough that customers will start expecting it.

If your customers are heavy on bank transfer methods already, particularly in markets where iDEAL, Bancontact or Giropay-style payment habits are normal, Wero is a natural fit and the behaviour change for customers is minimal.

If you sell mainly outside those markets, wait. Coverage outside the launch countries is still limited, and adding an unused payment method to checkout adds cognitive load and code paths for no return.

If your margins are thin and volumes are high, run the numbers on cost per transaction against your current card mix. This is where the business case is strongest.

One thing we would not do is treat this as a replacement for cards in the near term. It is an addition. Plan for it to sit alongside your existing methods for years.

The Regulatory Backdrop

Wero is not a compliance obligation, but it exists because of regulatory groundwork, and it lands in the middle of several rules that are.

The Instant Payments Regulation made instant euro credit transfers something every euro area payment service provider must support, which is what makes a wallet like Wero viable at scale. The same regulation brought Verification of Payee, free of charge, from 9 October 2025. We covered the implications for checkout and payout flows in instant payments and Verification of Payee.

PSD3 and the Payment Services Regulation reached provisional political agreement in November 2025, and the final texts were published in April 2026. The Economic and Monetary Affairs Committee approved the agreed text on 5 May 2026, but as of 10 October 2026 the Council has not adopted its first-reading position and neither text is in the Official Journal. Parliament's procedure file gives 14 December 2026 as the indicative plenary date, so publication in early 2027 is more likely. Application then follows 21 months after entry into force, which means late 2028 at the earliest. The direction, stronger open banking interfaces and reworked fraud liability, already favours account-to-account methods.

And ordinary rules still apply. A new payment method means new personal data flows under GDPR, a new interface that must meet accessibility requirements, and new consumer information obligations at checkout.

What We Would Do

If we were advising a mid-sized European retailer today, the plan would be:

1. Ask your PSP what their Wero support looks like and what it costs. Many of the large European providers already support it, and the answer determines your effort.
2. Model the order state machine changes before writing any code. This is where projects overrun.
3. Ship it in one market first, ideally Germany, where consumer familiarity is highest.
4. Measure conversion at checkout, not just adoption. A method nobody selects is still costing you screen space.
5. Plan the point of sale question separately. Broader in-store acceptance in Germany and France is planned from 2027, and it is a different project with different hardware constraints.

We build and integrate payment flows for companies operating across Europe, including checkout, order orchestration, refunds and reconciliation. If you want help scoping a Wero integration or working out whether it makes sense for your market mix, write to office@c9group.dev. There is more about our European work on the market entry page, and the wider regulatory picture is in our 2026 EU digital compliance guide.