Wero – Digital payment wallet, made in Europe

Goals and Motivation

  • Framed as Europe reducing dependence on US-controlled payment rails (Visa, Mastercard, PayPal) for reasons of cost, control, and sovereignty.
  • Seen as leveraging existing SEPA Instant rails but adding a standardized “payment network” and identity/UX layer.
  • Some argue this is mainly about fees; others emphasize strategic autonomy and avoiding US extraterritorial influence.

What Wero Actually Is

  • Multiple commenters note Wero is not really a “wallet” but:
    • A P2P app (like Swish/Venmo/Tikkie) using phone/email aliases.
    • An e‑commerce payment method based on the Dutch iDEAL model (bank-backed online payments via redirect/QR/app).
  • Several say the marketing is confusing and underplays the ecommerce angle and iDEAL lineage.

Relation to Existing Systems

  • Compared/contrasted with: Taler (more cash-like, bank-optional), Vipps/Swish/Bizum/BLIK (national instant-pay apps), and SEPA transfers.
  • Key point: transfers ≠ payments. Many merchants don’t support direct SEPA transfers; Wero is a standardized payment scheme on top of SEPA Instant.
  • Plan is eventual interoperability via a central hub with existing national schemes (Vipps MobilePay, Bancomat, Bizum, SIBS, etc.), not one single app.

Rollout Scope

  • Currently works only in a few countries (Germany, France, Belgium; Netherlands/Luxembourg “soon”), so “pan‑European” is seen as aspirational.
  • Some see 40% of EU population covered (once NL joins) as meaningful; others call it far from Europe-wide.

UX and Merchant Economics

  • For consumers, proponents say iDEAL-style flows are faster and smoother than cards/PayPal, with no card numbers shared and clear bank authentication.
  • For merchants, fees are reported as much lower than card schemes; used successfully for years in the Netherlands.
  • Critics complain about needing to scan QR codes from desktop screens and say it feels like “PayPal but worse” today.

Device, OS, and Access Concerns

  • Major criticism: no web/desktop option; app-only and smartphone-centric.
  • Official FAQ excludes rooted/custom ROM phones and even devices with developer options; some report it working on degoogled Android anyway, others blocked.
  • This is justified by some as regulatory security/attestation requirements for instant payments; others see it as locking users into Google/Apple and a civil-rights issue.

Identifiers, Privacy, and Security

  • Using phone numbers as identifiers is widely criticized: ambiguity with multiple bank accounts, privacy concerns if someone can infer bank and name from number.
  • Some clarify phone/email is optional for certain banks and primarily for P2P lookup; backend allows only one bank per alias (last registration wins).
  • Debate over whether instant, strongly authenticated bank payments reduce fraud or instead erode consumer protection vs chargeback-friendly cards.

Broader Perspectives and Alternatives

  • Some argue Europe doesn’t “need a PayPal” because SEPA is already cheap and fast; others point out PayPal’s browser-based accessibility is still unmatched.
  • Crypto advocates dismiss Wero as KYC-heavy, proprietary, and inferior to Lightning/other chains for cross-border transfers.
  • A few want card-based or non-phone options and worry about tying everyday payments to battery-powered, US-vendor-approved devices.
  • There is mild criticism that even this “sovereign” project relies on US cloud/SaaS tooling for its own infrastructure.