E-commerce · Strategy & fundamentals
Wero at Online Checkout: What to Check Before Enabling It
Wero is expanding across European e-commerce. Understand the Dutch rollout and check availability, costs, refunds and payment operations before enabling it.
By Boaz Lichtenstein Prefer us on Google
Fact-checked 3 November 2026. Based on published sources; payment providers have not been tested first-hand.
A new payment logo is easy to add to checkout. The work starts with what happens behind it: who can pay, when an order can reach the warehouse, and how a partial return appears in the accounts.
Wero is becoming more relevant to merchants serving European customers. The Dutch rollout is a good reason to contact your payment provider. A useful implementation starts with an approved flow for your store and finishes only when the incoming funds have been reconciled. This article helps you prepare that assessment.
Key takeaways
- Check country, customer bank and payment provider separately. A headline reach figure does not describe the customers your checkout can serve.
- Confirm which payment method sits behind the displayed logo and which features your contract covers.
- Establish refunds, complaints and payouts before the first regular purchase.
- Assess a limited pilot using completed orders and costs. An extra logo does not guarantee better conversion.
What Wero actually is
Wero is the European Payments Initiative’s (EPI) account-to-account payment scheme. It uses SEPA instant transfers; customers approve purchases in their banking or Wero app, for example after scanning a QR code. Merchants connect through their payment provider or acquirer. Source: Wero for merchants.
SEPA Instant describes the transfer infrastructure; Wero adds the purchasing flow. Treat Wero as a separate payment method: do not carry over your card processes or SEPA direct debit assumptions without checking them.
Wero should also be distinguished from the digital euro. Wero uses bank accounts; the digital euro would be digital central bank money, as the ECB explains. Our digital euro explainer provides more background on the distinction between forms of money.
What the Dutch rollout changes
EPI says online payments launched across participating Dutch banks on 26 October 2026, with payment providers progressively enabling merchants. The announcement page is dated 25 October. The target is to complete the iDEAL migration by the end of 2027. EPI plans to introduce purchase protection for Dutch consumers by January 2028. This country-specific plan does not describe protection in Germany. Source: EPI’s Dutch rollout announcement.
This was not the first Dutch Wero activity: bunq had already announced online payments there in September. Source: EPI/bunq.
For stores offering iDEAL, the shared logo does not prove a completed
migration either. Adyen documents “iDEAL | Wero” as co-branding for
existing iDEAL checkouts and still uses the technical identifier
ideal. Source: Adyen’s iDEAL | Wero documentation.
Ask your provider explicitly about the underlying payment method
and the migration plan for your contract.
Where online payments are already documented
These examples establish specific rollout milestones. They are not a promise that every bank or store in each country can already participate.
Sources: BNP Paribas/EPI and EPI on Luxembourg.
Provider selection deserves careful reading. On the review date, Mollie’s product page displays both “Coming soon” and activation instructions. That does not establish reliable availability for your account. Source: Mollie.
Ask your contact to confirm country, customer banks, store integration and enabled features in writing. Save the answer with a date. An announced feature belongs in your planning, but not in a promise to customers today.
Five checks before launch
1. Choose a specific purchase flow
Start with how your business actually works: immediately paid goods, pre-orders, subscriptions and split shipments need different flows. Do not accept a broadly advertised product family as the answer to a specific use case.
For a clothing store, the first example might be an order containing a jacket and trousers, followed by a return of just the trousers. For a furniture retailer, an order with a long lead time may be the important case. Write a short sequence: purchase, payment approval, dispatch, possible refund. Ask your provider to explain what is supported today at each step.
2. Separate confirmation, processing and payout
Adyen’s technical Wero documentation is marked as in development on the review date. It separates authorisation, automatic capture and payout: a bank’s commitment is not receipt of funds; payout is scheduled after successful capture. It also lists dispute support from February 2027. These are provider-specific statements, not a promise of immediate availability. Source: Adyen’s Wero documentation.
Your implementation needs an unambiguous mapping from notifications to order states. Which notification may release goods for dispatch? What happens if a response arrives late? Who investigates an order that looks paid but does not appear in the payout report?
A practical acceptance check: follow the same test order through the store status, provider reference and eventual payout. Returning successfully to the thank-you page does not answer these questions on its own.
3. Make refunds and disputes manageable
Plan for three separate situations: a refund you initiate, a customer complaint about goods or delivery, and a disputed payment. Your provider needs to explain the applicable processes for each market. The word “instant” does not establish a comprehensive payment guarantee.
Decide who owns cases and who covers absences. Ask about applicable deadlines, notification channels, evidence requirements and possible fees. Document how a refund already issued is reconciled with an open case. This helps prevent support and accounting from handling the same matter independently.
For partial returns, your team should be able to identify the amount refunded and any amount still pending without developer assistance. Test a rejected or pending refund too. The objective is a traceable workflow, not simply a visible refund button.
4. Compare the full cost
Use the offer for your merchant contract in your calculations. Ask about fixed and percentage transaction fees, minimum charges, refund and dispute fees, and any subscription charges. Establish whether terms differ by market or transaction type and whether fees already paid are refunded when goods are returned.
Add your own costs: setup, maintenance, support and accounting work. If a new payment method mainly replaces an existing one, the cost difference of that switch matters. Only attribute additional order value to it when your comparison provides credible evidence. Our article on e-commerce unit economics explains the underlying approach.
5. Close the accounting loop
Record which references connect the order, transaction, fees, refund and payout. Check the export to see whether your team can identify an individual order even when several payments are paid out together.
For example, a customer orders two items and returns one. Your reconciliation needs to explain the original amount, refund and remaining proceeds. Any difference should remain visible as an item to investigate, rather than disappearing into a combined accounting entry. Use your provider’s actual reports for this.
A small pilot that includes failure cases
The following checklist is an editorial acceptance template. It does not claim that every provider offers the same states or testing facilities. Agree on the cases with your provider and start in its test environment where available.
Agree on a fallback before a production pilot: who can hide Wero, which alternatives remain available, and how will payments already started be handled? Then test the flow actually offered using eligible accounts and document the limits of the assessment.
For evaluation, you need at least the number of checkouts where Wero was offered, payments started and purchases completed. Add abandonments, refunds, support cases and costs. Compare similar markets, devices and baskets where possible. Looking only at customers already likely to buy can turn an attractive payment share into a misleading claim of additional business.
Expand availability when the operation and benefit are clear. If your provider has not approved access, or a difference in the money flow remains unexplained, you have a specific issue to resolve. Assign an owner and a review date to those issues before enabling the next customer group.
Sources and limits
Public primary sources were checked on 3 November 2026. EPI, banks and payment providers describe their own products; their statements do not establish independent improvements in conversion or costs. The acceptance template is our practical synthesis. Individual merchant accounts, contracts and live transactions were not tested.