Wero is a European digital wallet developed by the European Payments Initiative (EPI), offering instant and secure account-to-account payments across Europe. Users pay in seconds using their bank's Wero-enabled app, either by scanning a QR code (web) or through an app-to-app redirection (mobile).
PRESENTATION
| Brand | Wero |
|---|---|
| Payment Flow | Redirection to Wero Hosted Checkout Page (Web / QR code & app-to-app (coming soon)) |
| Integration | Order API |
| Product Code | wero |
| Available country codes | DE 🇩🇪 BE 🇧🇪 FR 🇫🇷 |
| Currency | EUR |
| Minimum amount | 0.01 |
| Maximum amount | Defined by the customer’s bank |
| 3DS | No |
| Authentication | Via the customer's bank Wero-enabled app |
| Recurring payments | Not supported (scheme launch expected 2026) |
| Refund |
|
| Dispute / Chargeback |
|
ESSENTIAL INFORMATION
POPULARITY AND AVAILABILITY
Launched in 2024 by the European Payments Initiative, Wero is a unified pan-European wallet enabling instant account-to-account transfers between bank accounts in under 10 seconds, 24/7. It is initially available in Germany, Belgium and France, with the Netherlands and Luxembourg to follow.
PAYMENT PROCESS
The payment is made via redirection to the Wero Hosted Checkout Page. Once the customer selects Wero, they are securely redirected to complete authentication and validation directly through their bank's Wero-enabled app — by scanning a QR code on desktop, or via an app-to-app hand-off on mobile.
SECURITY AND COMPATIBILITY
Transactions are authenticated within the customer's banking app, complying with European security standards without storing sensitive data. Compatible across browsers and mobile devices.
CONFIGURATION AND COMPLIANCE
Ensure HiPay account is correctly configured. Only EUR transactions are supported. Use Redirect Pages Requirements.
USE CASES
Ideal for instant and secure account-to-account payments, Wero is perfectly suited for merchant sites targeting German, Belgian and French customers. The dual web (QR code) and mobile app-to-app experience provides a frictionless checkout and boosts conversion rates across both desktop and mobile devices.
INTEGRATION
INTEGRATION METHODS
| Method | Description |
|---|---|
| Order API | Enables direct creation and management of transactions. |
WEB VS MOBILE FLOWS
Wero always relies on a redirection to the Wero Hosted Checkout Page. Two customer experiences are supported depending on the device, determined by the browser_info object you send in the order request:
- Web Flow (QR code): On desktop, the customer is redirected to the Wero Hosted Checkout Page displaying a QR code, which they scan with their bank's Wero-enabled app to authenticate.
- Mobile Flow (app-to-app) (coming soon): On mobile, the customer is redirected (app-to-app hand-off) directly to their bank's Wero-enabled app to authenticate and validate the payment.
In both cases, the API response includes a forward_url field. You must redirect the customer to this URL to complete the payment.
USER EXPERIENCE
⚠️ The customer must have a bank account enrolled in Wero and the corresponding banking app installed.
- Customer selects Wero on the merchant site.
- HiPay prepares the transaction.
- Customer is redirected to the Wero Hosted Checkout Page.
Web Flow: Customer scans the displayed QR code with their Wero-enabled banking app.
Mobile Flow: Customer is handed off (app-to-app) to their Wero-enabled banking app. - Customer authenticates and validates the payment (max session duration: 15 min).
- Bank sends the status to HiPay.
- HiPay notifies the merchant and confirms transaction to the customer.
ORDER API INTEGRATION
MANDATORY PARAMETERS
| Parameter | Description / Example |
|---|---|
payment_product | wero |
orderid | Unique identifier (e.g., ORDER_1583157211) |
description | Brief description (e.g., Summer Sale) |
amount | Total amount (e.g., 99.99) |
currency | ISO 4217 code (EUR) |
firstname | Customer's first name |
lastname | Customer's last name |
country | Customer's country (DE, BE or FR) |
SPECIFIC INPUT PARAMETERS (OPTIONAL BUT RECOMMENDED)
| Parameter | Description |
|---|---|
browser_info |
Object describing the customer's device/browser (user agent, screen, language, etc.). Used to route the customer to the appropriate experience (Web / QR code on desktop, Mobile app-to-app on mobile). See browser_info specification. |
email |
Customer's email address |
streetaddress |
Postal address |
city |
Customer's city |
zipcode |
Postal code |
SPECIFIC OUTPUT PARAMETERS
| Parameter | Description |
|---|---|
forward_url |
Url to redirect the consumer to the Wero Hosted Checkout Page (Web / QR code & Mobile app-to-app) |
ENDPOINTS
| Environment | URL |
|---|---|
| Stage | https://stage-secure-gateway.hipay-tpp.com/rest/v1/order |
| Production | https://secure-gateway.hipay-tpp.com/rest/v1/order |
NOTE: Ensure that your HiPay account and redirection URLs are correctly configured to guarantee proper integration.
WERO SAMPLE REQUEST
curl --location 'https://stage-secure-gateway.hipay-tpp.com/rest/v1/order' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --header 'Authorization:*****'\ --data-urlencode 'payment_product=wero' \ --data-urlencode 'orderid=1769530975' \ --data-urlencode 'amount=1.50' \ --data-urlencode 'currency=EUR' \ --data-urlencode 'description=description Wero' \ --data-urlencode 'firstname=John' \ --data-urlencode 'lastname=Doe' \ --data-urlencode 'country=DE'
Best practices
- Send the
browser_infoobject so the customer is routed to the right experience (Web / QR code or Mobile app-to-app) - Set a client-side timeout corresponding to the maximum session duration (15 min)
- Use server-to-server notifications to track status changes in real time
- Test in the Stage environment before production
- Handle refunds (full, partial and multiple partial)
- Monitor disputes and chargebacks (120 days for general MCCs, up to 540 days for specific MCCs)
- Ensure the customer has a bank account enrolled in Wero and the banking app installed
- Check error codes and technical messages (general): HiPay Error Messages