Dutch webshops enter the next phase
Wero is opening online commercial payments in the 
Netherlands as the next stage of the 
iDEAL migration. 
European Payments Initiative says the service is available through all 11 participating Dutch banks, enabling payment service providers to progressively bring merchants onto Wero from 26 October.
This is a staged deployment, rather than an overnight change at every checkout. Each merchant can follow its own migration calendar and that of its provider. EPI says the first merchants are already processing transactions, with completion of the wider transition targeted before the end of 2027.
A migration plan becomes a checkout decision
For a webshop, the useful question is when its provider can deliver a working payment flow, not simply when the new name appears. A broader European payment route could help merchants serve customers beyond their home market, but acceptance still needs to fit the shop’s checkout, support and accounting processes.
A phased transition gives businesses room to test payments, refunds and reconciliation before switching their full customer base. Merchants should ask for a deployment plan that identifies which functions work at launch and which require later changes.
Later features are still on the roadmap
Subscriptions and pay-on-delivery are planned for the second quarter of 2027. Purchase protection for Dutch consumers is scheduled by January 2028; its design is still being developed with the parties involved. EPI plans workshops during this quarter and an announcement in the first quarter of 2027.
Consumers do not need to take action or subscribe to a new service. Their banks will communicate through official channels. The launch does not mean that every webshop is already enabled, or that every future Wero function is available to Dutch shoppers today.
Check the provider’s actual offer
Merchants should confirm activation timing, pricing, settlement reporting and dispute procedures with their provider. Test the complete journey on mobile as well as desktop, and make support instructions clear while customers encounter both names. Treat the end-2027 migration target and later protection timetable as separate milestones.
