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 — Cards only, or a method list with no statement of which countries and currencies each one covers.
3 — Major cards and wallets plus one or two European methods, with local coverage stated vaguely ("many local methods") and no SEPA Direct Debit.
5 — Cards, Apple Pay and Google Pay, SEPA Direct Debit, and the main local methods for DACH and Benelux (iDEAL or Wero, Bancontact, Klarna or invoice) listed by name with the countries they serve.
8 — Broad EU coverage named per country — 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 E-Commerce Lead
The named list covers iDEAL | Wero, Bancontact, BLIK and MB WAY alongside cards, Apple Pay and Google Pay, and Paddle decides at runtime which to show by customer country, currency and device so I write no routing logic myself. Bancontact gets a full per-method page — Belgium, EUR, refunds supported, subscriptions not supported — but only cards, Apple Pay and Google Pay get the comparison-matrix treatment, and I found no public information on SEPA Direct Debit, TWINT, EPS or Przelewy24, which my German, Austrian and Polish baskets need. 5 6