Skip to Content

How LUXHUB enabled Wero’s launch in Luxembourg: a model that can be replicated across Europe

20 October 2026 by
How LUXHUB enabled Wero’s launch in Luxembourg: a model that can be replicated across Europe
LUXHUB, Alexandre Keilmann

On 1 September 2026, Wero, EPI Company’s pan-European instant payments solution, officially launched in Luxembourg, becoming its fourth European market. Behind the consumer-facing launch was a complex technical undertaking. Five of the country’s leading financial institutions, Banque Raiffeisen, BGL BNP Paribas, BIL, POST Luxembourg and Spuerkeess, migrated from an established local payment flows to EPI Company’s infrastructure and align with the scheme’s requirements, within a tight timeline. LUXHUB acted as for these five institutions, delivering the connectivity layer that made the deployment and the run possible. Here is how it worked, and why the approach matters for any PSP preparing its own Wero integration.

 

A market ready for Wero, and a demanding migration

Luxembourg is, in many respects, an ideal market to launch Wero. According to EPI Company’s 2026 European Payment Barometer, conducted by Kantar, 74% of Luxembourg consumers already use mobile payment apps for person-to-person payments. That is the highest rate across the five markets surveyed. In addition, 80% say they trust their bank when it comes to payments.

For the past decade, the Payconiq mobile payment app was widely used in Belgium, the Netherlands and Luxembourg: users were able to send money to friends, pay invoices, shop online, and pay in stores. The service was acquired by EPI Company with the goal of moving away from Payconiq and replacing it by Wero. The new European digital wallet therefore had to preserve that experience from day one with key use cases such as QR codes, POS, e/m-commerce, while opening the door to cross-border payments and additional features. Payconiq’s platform ended on 30 September 2026: there was no margin for delay.

For each participating bank, the challenge was the same. Each one needed to establish and maintain secure, scheme-compliant exchanges with EPI in a simplified manner.

 

LUXHUB’s Wero Integration Layer

Rather than having each bank build its own EPI connectivity, the five institutions relied on the LUXHUB Wero Integration Layer, a mutualized solution that sits between EPI Central Services technical platform and them.

The flow is straightforward: it starts with provisioning, when the payment service user (PSU) onboards on the Wero Standalone App and links its bank account. From then on, each payment the PSU initiates in the app passes through EPI Central Services and is routed to LUXHUB, which manages all technical exchanges with the scheme. LUXHUB then communicates with the PSP through interfaces the bank has already in place, including existing regulatory A2A payment rails.

This architecture brings three concrete benefits to issuing PSPs. First, the investment needed to expose and consume interfaces with EPI is shared across participants rather than duplicated by each institution. Second, banks can go to market faster, because they build on lightly adapted PSD2 interfaces instead of starting from scratch. Third, the integration is future-proof: as EPI evolves Wero’s user experience and extends it to new payment use cases and new features, LUXHUB absorbs the technical changes of the scheme.

 

Build in-house or mutualize?

For PSPs evaluating their Wero strategy, the choice usually comes down to building the integration internally or relying on a specialized partner. Building in-house means a long implementation cycle, the need to build and maintain connectivity with EPI Company, and higher operational risks. It also means carrying the initial implementation project alone, from discussing requirements and scope to delivery, whereas through a mutualized approach this effort is shared across participating banks.

A mutualized integration layer changes that. A Wero-ready solution can be integrated in weeks – not taking into account contract discussions with EPI Company, functional certifications, etc. Scheme alignment is built in and maintained by specialists, and dedicated experts support the bank at every step, which reduces implementation and operational risks. In Luxembourg, the model has now been proven in production with five banks serving a highly demanding, highly digital customer base.

“Wero’s launch in Luxembourg shows what European payments sovereignty looks like in practice: banks, EPI and technology partners working together toward a shared goal,” said Claude Meurisse, CEO of LUXHUB. “By acting as Technical Service Provider for five of the country’s leading financial institutions, we helped them connect to Wero quickly and securely, without each of them having to carry the full technical burden alone. This mutualized model is now proven, and we are ready to bring it to PSPs in every market where Wero is expanding.”

 

From Luxembourg to the rest of Europe

Wero already serves 58 million users in Belgium, France and Germany and is soon arriving in the Netherlands and Austria. Through EPI’s interoperability agreements, it will over time connect with payment ecosystems in Italy, Spain, Portugal and the Nordic countries. Each new market brings PSPs facing the same questions Luxembourg’s banks faced: how to connect to EPI efficiently, launch on time and stay aligned with an evolving scheme.

The Luxembourg deployment offers a replicable answer. The LUXHUB Wero Integration Layer is not tied to a single market. It builds on the standard interfaces every European bank already operates, which makes it deployable for issuing PSPs across the EU.

For banks and PSPs planning their Wero roadmap, the lesson from Luxembourg is clear: Wero integration does not have to be a long, resource-heavy project. With the right technical partner, it can be a fast, low-risk step toward offering customers a truly European payment experience.

 

Planning your Wero integration? Get in touch with the LUXHUB team to discuss how the Wero Integration Layer can support your deployment.

Share this post