whats-best.ai
Search Sign in

Payment

Saferpay

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Saferpay AG (Worldline) · www.saferpay.com

Report an error on this page Is this your product? →

Link to this page

Saferpay: AI-assisted analysis on whats-best.ai Saferpay: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Saferpay at a glance

Vendor
Saferpay AG (Worldline)
Headquarters
Not stated on the vendor’s pages as of 13 Oct 2026
Data hosting
Not stated on the vendor’s pages as of 13 Oct 2026
Free plan
Not stated on the vendor’s pages as of 13 Oct 2026
Panel verdict
The AI panel rates Saferpay 2/5, the mean of 6 judges. Saferpay AG (Worldline) is a payment product whose public documentation is strongest at the checkout and thinnest on the money and contract around it. how scores are made
As of
Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources

Saferpay alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Payments Engineer

Weighted verdict

Integrates the provider and gets paged when webhooks stop arriving. Wants a versioned API with idempotency keys, a test mode that behaves like production, the PCI scope of each integration stated, and a status page that admits incidents rather than a green dot.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Payments Engineer

Panel median The Payments Engineer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Payments Engineer
Payment methods & local coverage 3.5 of 5 3.5 of 5
Checkout, SCA & fraud 4 of 5 4 of 5
Subscriptions & recurring payments 2 of 5 3 of 5
Settlement, reconciliation & API 2 of 5 2 of 5
Licence, risk & account terms 1 of 5 0.5 of 5
European sovereignty 0.5 of 5 0.5 of 5

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.

Report an error

The Payments Engineer

The acquirer pages name a broad, per-country list — BLIK for Poland, Przelewy24, eps for Austria, TWINT for Switzerland, Wero, Bancontact for Belgium, iDEAL 2.0, SEPA Direct Debit and the Klarna variants — each with the acquirer that routes it, which is close to what a merchant plans against. We found no public information on settlement currencies or on which methods support refunds versus recurring charges, so it stops short of a complete matrix, and the licensing itself is written only for Germany, Switzerland, Liechtenstein and Austria. 2 5 7

Report an error

Checkout, SCA & fraud

How this is scored

The path from basket to authorised payment under PSD2: hosted and embedded checkout options, 3-D Secure and SCA exemption handling, fraud screening, and what the provider documents about keeping legitimate payments from failing.

0 — A single redirect page with no statement on 3-D Secure, SCA or fraud screening.

3 — Hosted checkout with 3-D Secure 2 mentioned, fraud screening as an unexplained add-on, and no word on exemptions or declined-payment handling.

5 — Hosted and embedded checkout options, 3-D Secure 2 with SCA handled by the provider, configurable fraud rules, and the resulting PCI DSS scope for each integration type stated.

8 — SCA exemptions (low value, transaction risk analysis, merchant-initiated) applied and documented, fraud tooling with rules and risk scores exposed to the merchant, network tokens or account updater, and liability shift explained per flow.

10 — Authorisation is engineered and shown: exemption strategy documented, soft-decline retry handled, authorisation-rate reporting by method and issuer country, and a checkout the merchant can run in their own domain while staying at the lowest PCI scope.

Report an error

The Payments Engineer

This is the strongest part: exemptions are documented and engineered — low value up to 30 Euro with the 5-transaction and 100-Euro cumulative re-authentication rules, transaction risk analysis via Saferpay Fraud Intelligence, and a merchant-initiated exemption the provider itself warns about — plus soft declines returning PAYER_AUTHENTICATION_REQUIRED, test cards to force them, and a documented re-registration path under forced SCA. Liability shift is returned per transaction with the merchant's exposure spelled out when an exemption is granted. We found no public information on authorisation-rate reporting, network tokens or an account updater, and PCI scope is stated only for the direct-post flow, which requires full PCI certification. 3 4

Report an error

Subscriptions & recurring payments

How this is scored

Charging the same customer again: card-on-file and merchant-initiated transactions, SEPA mandates, subscription logic and dunning — and whether the stored payment credentials can leave with the merchant.

0 — No stored payment methods; every charge needs the customer to pay again.

3 — Card-on-file tokens for repeat charges, but no SEPA mandate handling, no subscription logic, and failed-payment handling left entirely to the merchant.

5 — Stored cards and SEPA Direct Debit mandates, merchant-initiated transactions documented, and basic subscription plans with scheduled charges and failed-payment notifications.

8 — Subscription billing with trials, proration and plan changes, smart retries and dunning, card account updater, mandate management with pre-notification, and a documented process for exporting payment tokens to another provider.

10 — Recurring revenue is a first-class product: usage-based and invoice-based billing, dunning with measurable recovery, token migration in and out documented with a stated timeline and format, and recurring support stated for every local method that allows it.

Report an error

The Payments Engineer

Merchant-initiated transactions are a documented product: a Secure Card Data alias for irregular charges, referenced transactions kept for five years as the primary subscription path, aliases that get SCA data attached retroactively, and a clear statement that Saferpay only charges when the merchant's system requests it. However the retry guidance is a merchant-side cronjob after 24 hours, and we found no public information on subscription plan logic, dunning, SEPA mandate handling, an account updater, or exporting stored credentials to another provider. Recurring also sits behind the Business licence rather than the base product. 3 5 8

Report an error

Settlement, reconciliation & API

How this is scored

Getting the money and knowing what it was: payout cadence and currencies, fee itemisation per transaction, reports that match a bank statement, and an API and webhooks a team can build finance processes on.

0 — Payouts on an unstated schedule, one net amount per payout, and no API or report beyond an on-screen list.

3 — A stated payout schedule and CSV exports, but fees netted invisibly into payouts and an API with thin documentation.

5 — Payout frequency and delay stated, per-transaction fee breakdown in reports, a documented REST API with webhooks and a test mode, and exports that link each payout to its transactions.

8 — Configurable payout schedules and settlement currencies, reconciliation reports that match bank lines, accounting integrations or exports named, a versioned API with idempotency and published rate limits, and a public status page with incident history.

10 — Finance can close the month from the provider's data: interchange and scheme fees itemised per transaction, automated reconciliation to the ledger, a deprecation policy for the API, and full historical data exportable after the contract ends.

Report an error

The Payments Engineer

The reconciliation documentation is essentially one design decision — a merchant-defined order reference routed through to the processor's files — with PayPal and other third-party processors sending their own data that finance has to stitch together, and remaining questions routed to an account manager. The JSON API itself is deeply documented with a spec version, and the test environment can force declines, which is more than thin; but we found no public information on payout cadence or currencies, per-transaction fee breakdown, webhooks, rate limits or a status page. 6 7 8

Report an error

Licence, risk & account terms

How this is scored

Who holds the merchant's money under which licence, and what the contract lets the provider do on a bad day: freezes, reserves, termination, chargebacks. Scored on what the terms and the imprint state, not on reputation.

0 — No regulated entity named; terms allow freezing funds and terminating the account at any time with no notice, reason or timeline.

3 — A licence mentioned without the entity, supervisor or register number, and terms that permit reserves and holds with no stated limits.

5 — The regulated entity named with its supervisor and licence type, safeguarding of merchant funds stated, chargeback fees and dispute process published, and a notice period for ordinary termination.

8 — Entity, supervisor, register number and passporting stated per country; reserve and rolling-hold conditions defined with limits and release timelines; freeze and termination terms with reasons and a route to appeal; PCI DSS level and attestation published.

10 — The bad day is written down: every regulated entity in the chain named with register links, reserve calculation disclosed, funds release timelines after termination committed, a documented complaint route to the supervisor, and exit terms that include handing back payment tokens and transaction history.

Report an error

The Payments Engineer

The captured pages document feature licensing — Go, Easy, Flex, all-in-one and the Business extension, with a PERMISSION_DENIED error for the wrong tier — but that is software packaging, not the risk terms this criterion asks about. We found no public information on the regulated entity, supervisor or register number, safeguarding of merchant funds, reserves, freezes, chargeback fees, or a notice period for termination. 7 8

Report an error

European sovereignty

How this is scored

Who the contracting and regulated entity is, and where transaction and cardholder data are processed and stored. Independently sourced by the sovereignty pipeline. The card schemes are US-based for every provider, so the scheme layer is not held against any one vendor; the part the vendor controls is.

0 — Non-EU contracting entity, no statement on where payment data is processed, and subprocessors unnamed.

3 — An EU licensed entity contracts, but payment and customer data is processed outside the EU by default without an explained safeguard, or the subprocessor list is absent.

5 — EU contracting and regulated entity, EU processing stated for core payment data, but the group parent or significant parts of the chain (fraud scoring, support, analytics) are non-EU without a stated safeguard.

8 — EU entity and EU licence, payment and cardholder data processed and stored in the EU on named infrastructure, subprocessor list published with locations, and a DPA covering the processing the provider does as processor versus as controller.

10 — Sovereign end to end and evidenced: European ownership, EU entity and licence, every processing location and subprocessor European, European rails (SEPA, Wero or national schemes) offered alongside cards, and certifications published.

Report an error

The Payments Engineer

The independently sourced sovereignty record shows no attributes, and we found no public information on where payment or cardholder data is processed, on the contracting entity's licence, or on subprocessors and their locations. The only territorial statement captured is that feature licensing applies to Germany, Switzerland, Liechtenstein and Austria. 7

Report an error

Pricing transparency not rated — the vendor publishes no price

How this is scored

Whether a merchant can compute the effective fee for their own mix of cards, countries and methods — including cross-border and currency conversion markups, chargebacks, refunds, payouts and monthly fees — from public pages alone.

0 — No public prices at all; every rate is a sales conversation.

3 — A headline percentage exists, but it is unclear which cards and countries it covers, and cross-border, currency conversion or chargeback fees are unstated — the effective fee is unknowable.

5 — Rates published per main method with domestic and international cards distinguished, but at least one commonly incurred cost (currency conversion markup, chargeback fee, payout or monthly fee) is missing or "on request".

8 — Every method priced publicly, cross-border and currency conversion markups stated, chargeback, refund and payout fees listed, minimum monthly fees and contract term given, and whether the model is blended or interchange++ said plainly.

10 — Complete fee computability: the effective rate derivable for a given volume, card mix and country mix — interchange++ with the markup published or a blended rate with every exception listed — plus volume tiers, reserves and every ancillary fee on a public page.

Report an error

The Payments Engineer

The captured licensing page routes every money question to sales — "if you have any questions about Saferpay licensing and/or pricing, please contact your account manager or our sales team" — and the upselling note likewise says to ask your contact. No rate of any kind appears publicly, so an effective fee for a given card and country mix cannot even be started from these pages. 7

Report an error

Questions about Saferpay

Is Saferpay European?

Not determined: the vendor’s pages as captured do not say where Saferpay is based.

Where does Saferpay store data?

Not stated on the vendor’s pages as of 13 Oct 2026.

Does Saferpay have a free plan?

Not stated on the vendor’s pages as of 13 Oct 2026.

What are the best alternatives to Saferpay?

As of 21 Oct 2026, the panel rates Adyen (3/5), Mollie (3/5) and Checkout.com (3/5) highest among the other 30 Payment products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Adyen (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Saferpay alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about Saferpay? Tell us Report an error on this page

Sources (8)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Payment methods & local coverage — found from sitemap docs.saferpay.com Checked 13 Oct 2026 Details →
  2. 2 Payment methods & local coverage — found from sitemap docs.saferpay.com Checked 13 Oct 2026 Details →
  3. 3 Checkout, SCA & fraud — found from sitemap docs.saferpay.com Checked 13 Oct 2026 Details →
  4. 4 Checkout, SCA & fraud — found from sitemap docs.saferpay.com Checked 13 Oct 2026 Details →
  5. 5 Subscriptions & recurring payments — found from sitemap docs.saferpay.com Checked 13 Oct 2026 Details →
  6. 6 Settlement, reconciliation & API — found from sitemap docs.saferpay.com Checked 13 Oct 2026 Details →
  7. 7 Licence, risk & account terms — found from sitemap docs.saferpay.com Checked 13 Oct 2026 Details →
  8. 8 Licence, risk & account terms — found from sitemap docs.saferpay.com Checked 13 Oct 2026 Details →