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
Visa, Mastercard, Apple Pay, Google Pay and PayPal sit alongside named European local methods — iDEAL, Bancontact, EPS, Multibanco, Przelewy24, Klarna — and SEPA Direct Debit gets a proper per-method treatment across 36 European countries with EUR processing and settlement, refunds, partial refunds and recurring support all stated. But that country, currency, refund and recurring detail is documented for SEPA only; the other methods appear as names on a list, so a merchant still cannot plan a per-market rollout from the captured pages. 7 8 10 2