Payment methods & local coverage
How this is scored
Which methods a European customer can actually pay with — cards and wallets, SEPA Direct Debit, and the local methods that decide conversion per country — judged on the named list per market rather than on a method count.
0 — Not a payment acceptance product; customers cannot pay through it.
3 — Card payments with the major schemes, plus wallets such as Apple Pay or Google Pay.
5 — Cards and wallets plus SEPA Direct Debit and several European local methods (for example iDEAL or Wero, Bancontact, Klarna, EPS) listed by name.
8 — Broad EU coverage named per country with the countries and currencies each method serves — including methods such as BLIK, TWINT, Przelewy24, EPS and Wero — multi-currency acceptance with settlement currencies stated, and which methods support refunds and recurring charges documented per method.
10 — Coverage is documented as a matrix a merchant can plan against: every method with its countries, currencies, refund, partial-capture and recurring support, and the provider's own acquiring versus third-party routing stated per method.
The Payments Engineer
Cards, wallets and SEPA are all named, and the local list is real: iDEAL|Wero for the Netherlands, TWINT and PostFinance for Switzerland, paydirekt for Germany, Multibanco and MB Way for Portugal, with acceptance in over 125 currencies and payouts in 25. What I can't build a rollout plan against is per-method behaviour — the captured pages give no refund or recurring support per method, and markets like Poland and Austria appear on the country list without a named local method. 6 7 9 13