# Saferpay — Payment

Saferpay by Saferpay AG (Worldline) holds a panel rating of 2/5 from 6 AI judges (category median 2/5), as of 2026-10-15. Provenance: provenance unknown; sovereignty: not determined.

- Vendor: Saferpay AG (Worldline) (https://www.saferpay.com)
- Category: [Payment](https://whats-best.ai/software/payment.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/payment/saferpay
- Alternatives: https://whats-best.ai/software/payment/saferpay/alternatives ([markdown](https://whats-best.ai/software/payment/saferpay/alternatives.md))
- Data as of: 2026-10-21 · evaluated 2026-10-15 · oldest source captured 2026-10-13

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## 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

## The panel's verdict

Saferpay AG (Worldline) is a payment product whose public documentation is strongest at the checkout and thinnest on the money and contract around it. Payment methods scored a flat 7, with local methods named per country alongside their routing acquirer, and checkout and SCA scored 7-8 on exemption limits — low value at 30 Euro, re-authentication after five transactions or a cumulative 100 Euro — soft-decline recovery and liability shift per transaction. The bottom of the score table is commercial: settlement and reconciliation 2-4, licence and account terms 1-2, sovereignty 1-2, with no public information on payout terms, the regulated entity and its supervisor, or where payment data is processed. Two splits stand out. Recurring billing runs 4-6 — the merchant-initiated rails are documented in depth, but every schedule, retry and dunning step is the merchant's own cronjob (engineer 6, SaaS founder 4). Settlement runs 2-4 for the same reason: a documented JSON API and test environment against no published payout or fee reporting (finance lead 2). No prices are published; pricing questions are routed to the account manager or sales team.

**Speaks for it:**
- Checkout and SCA scored 7-8, with exemptions, soft-decline recovery and per-transaction liability shift documented to parameter level
- Payment methods scored a flat 7, naming local methods per country alongside the acquirer that routes each one
- Merchant-initiated transactions are documented in depth, including five-year retention of the initial transaction
- The JSON API is documented in detail, with a test environment that can force declines
- The merchant's order reference is routed through to the processor and appears in reconciliation files

**Held against it:**
- Licence and account terms scored 1-2, with no public information on the regulated entity, safeguarding of merchant funds, reserves or termination terms
- Sovereignty scored 1-2, and the record shows no sovereignty attributes
- Settlement and reconciliation scored 2-4, with no public information on payout frequency, settlement currencies or per-transaction fee breakdowns
- Subscription scheduling, retries and dunning are left to the merchant's own systems, on a published 24-hour retry recommendation
- No public prices exist, with the licensing page directing pricing questions to the account manager or sales team

**Best for:**
- You sell into Germany, Switzerland, Liechtenstein or Austria and need local methods such as TWINT, eps, BLIK or Bancontact
- You want granular control of 3D Secure — forced challenges, exemptions with stated limits, and liability shift returned per transaction
- You have engineering capacity to build scheduling, retries and dunning on top of documented merchant-initiated transaction rails
- You want to evaluate against a documented JSON API and a test environment before contracting

**Avoid if:**
- You sell mainly outside Germany, Switzerland, Liechtenstein and Austria — the feature licences apply only to those countries, with others referred to legacy licensing
- You want a provider-run subscription product — every charge is triggered by your own system, and merchant-initiated transactions require the Business licence
- Your finance close depends on published payout schedules and fee reports — the pages route reconciliation questions to the account manager
- Your procurement requires documented data residency and a subprocessor list before signature — the sovereignty record carries no attributes

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price.

| Criterion | The Finance Lead | The E-Commerce Lead | The SaaS Founder | The Payments Engineer | The Compliance Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Payment methods & local coverage | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Checkout, SCA & fraud | 4/5 | 3.5/5 | 3.5/5 | 4/5 | 3.5/5 | 4/5 |
| Subscriptions & recurring payments | 2/5 | 2/5 | 2/5 | 3/5 | 2.5/5 | 2/5 |
| Settlement, reconciliation & API | 1/5 | 1.5/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Licence, risk & account terms | 1/5 | 0.5/5 | 1/5 | 0.5/5 | 1/5 | 0.5/5 |
| European sovereignty | 0.5/5 | 0.5/5 | 1/5 | 0.5/5 | 0.5/5 | 0.5/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **1.5/5** | **2.5/5** | **2/5** | **2.5/5** | **1.5/5** | **1.5/5** |

### The judges

- **The Finance Lead** (v1.0): Closes the month and owns the cash position. Wants payouts on a stated schedule, fees itemised per transaction rather than netted into a lump, reports that match the bank statement, and a rolling reserve written into the contract with a limit rather than discovered on a Tuesday.
- **The E-Commerce Lead** (v1.0): Sells to customers in eight EU countries and is measured on conversion. Wants the local methods each market actually uses named per country, a checkout that stays on her domain, and 3-D Secure that challenges only when it must. Reads "100+ payment methods" as a count, not a list.
- **The SaaS Founder** (v1.0): Runs a B2B subscription business where every failed renewal is churn nobody chose. Wants SEPA mandates as well as cards, dunning that recovers, proration that is correct, and the payment tokens exportable — because a provider that keeps the tokens keeps the customer base hostage.
- **The Payments Engineer** (v1.0): 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.
- **The Compliance Officer** (v1.0): Handles data protection and outsourcing risk, and wants the regulated entity named with its supervisor and register number, not "licensed in Europe". Asks where transaction and cardholder data are processed, who the subprocessors are, and where the provider acts as controller rather than processor.
- **The Skeptic** (v1.0): Knows the headline rate covers the cheapest card in the cheapest country. Reads for the currency conversion markup, the chargeback fee, the payout delay and the clause that lets the provider freeze funds without a reason — and treats a missing licence number as an answer.

## European sovereignty — proven facts

No sovereignty finding yet.

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Product**
- 3ds API response fields: Transaction Authorize · PaymentPage Assert · AuthenticationType · LiabilityShift · LiableEntity · Liability [S4]
- 3ds configuration datapoints: MerchantId (Backoffice: Settings > Terminals) · Acquirer BIN [S4]
- 3ds frictionless threshold: global · 30 · 5 [S4]
- 3ds no extra integration cost: yes [S4]
- 3ds supported flows: Payment Page · Transaction Interface · Standalone Secure Card Data registration (ONLINE_STRONG check) [S4]
- 3ds supported schemes: Visa (Visa Secure) · Mastercard (Mastercard ID check) · American Express (SafeKey) · Diners Club (ProtectBuy) [S4]
- Alias API function: Transaction Authorize Direct (AuthorizeDirect) with Secure Card Data alias [S5]
- Alias method use case: Alias method used for one-time or irregular subsequent charges [S5]
- Alias sca update: yes [S3]
- Automation via cron: Automated MITs triggered by merchant system, e.g. via cronjob or Windows Task [S5]
- Basic license count: 4 [S7]
- Batch close both: yes · yes [S8]
- Batch processing availability: yes · yes [S7]
- Block business cards: Risk Management in Backoffice · yes [S4]
- Business card detection: BIN range · no · PaymentMeans.Card.HolderSegment [S4]
- Business is extension: yes [S8]
- Business tagging: yes [S8]
- Capture required: Authorized transactions must be captured to initiate money transfer [S5]
- Condition flag: Payment Page Initialize · Transaction Authorize · Condition [S4]
- Exemption low value: after 5 transactions or cumulative value of 100 EUR, SCA must be performed again · LOW_VALUE · 30 [S3]
- Exemption low value rules: 5 · 100 [S3]
- Exemption recurring: RECURRING · do not use unless you know you are allowed [S3]
- Exemption tra: TRANSACTION_RISK_ANALYSIS [S3]
- External 3ds providers: Authorize Direct · Insert Direct · Authentication.ExternalThreeDS · 1.47 [S4]
- Force 3ds challenge parameter: always request Challenged Flow on issuer side · Authentication.ThreeDsChallenge=FORCE [S4]
- Force challenge payment page: Payment Page Initialize · Condition=WITH_SUCCESSFUL_THREE_DS_CHALLENGE [S4]
- Force challenge standalone registration: ONLINE_CHALLENGED [S4]
- Force challenge transaction interface: Authentication.ThreeDsChallenge=FORCE (Transaction Initialize) · Condition=WITH_SUCCESSFUL_THREE_DS_CHALLENGE (Transaction Authorize) [S4]
- Force sca condition parameter: WITH_SUCCESSFUL_THREE_DS_CHALLENGE · Condition [S3]
- Force sca parameter: FORCE · Authentication.ThreeDsChallenge [S3]
- Fraud intelligence tra: yes [S3]
- Hosted entry form availability: yes · yes · yes [S7]
- Initial transaction flag: Initial transactions flagged via Payment.Recurring/Installment container in PaymentPage Initialize or Transaction Initialize requests [S5]
- Initial transaction retention: 5 [S5]
- Integration support availability: yes · yes · yes [S7]
- Legacy licenses: Go Card Secure PayGate · Go Card ePayments · Go Card QR-Payments · GoCard [S7]
- Legacy licensing other countries: yes [S7]
- Liability no shift exemption: no [S3]
- Liability shift only via 3ds: yes [S4]
- Licence models: Saferpay eCommerce · Saferpay Business [S8]
- License API example package: SAFERPAY_FLEX [S7]
- License check API: API · yes [S7]
- License check backoffice: Settings > License overview · Backoffice [S7]
- License countries: Germany · Switzerland · Liechtenstein · Austria [S7]
- License tiers: QR Payment · Go · Easy · Flex · all-in-one [S7]
- License upgrade option: Business licence available via sales contact; plugin users may only need to switch to Payment Page interface [S8]
- Management API availability: yes · yes · yes [S7]
- Mandatory datapoints: mandatory · recommended · mandatory [S4]
- Merchant triggered: yes [S5]
- Mit definition: MITs are a feature subset of the Transaction Interface enabling merchants to trigger subsequent transactions without cardholder presence [S5]
- Mit requirements: Requires Saferpay Business License, Backoffice login, one active e-commerce terminal with TerminalId and CustomerId, and valid acceptance agreement supporting recurring payments [S5]
- Omni channel availability: yes · yes [S7]
- Order id optional: yes · yes [S6]
- Order id reconciliation: Payment.OrderId (reference number) is defined by the merchant's system and routed by Saferpay to the processor; it appears in reconciliation files. [S6]
- Order id unique recommendation: no · yes [S6]
- Other acquirers cards: Alpha Card · Luxembourg, Belgium · American Express · Europe [S2]
- Other acquirers misc 1: Lunch-Check, boncard PAY, OeV-Voucher · boncard · Switzerland · Mastercard, Visa, V PAY, American Express · Chase Paymentech · USA, Canada · SEPA direct debit · creditPass/Intercard · Germany · Przelewy24 · Dialcom24 · Poland · Diners Club… [S2]
- Other acquirers misc 2: eps · eps · Austria · Billie (Open Invoice B2B) · Klarna Pay Now · Klarna Pay Later · Klarna Financing · Klarna · Europe [S2]
- Other acquirers misc 3: PayPal · International · PostFinance Pay · PostFinance Instant Payout · PostFinance · Switzerland · Reka-Pay, Reka-Meal, Reka-Rail · Reka · Switzerland · American Express · SIA · Italy · American Express · SwissCard · Switzerland · Masterc… [S2]
- Payer activation message: PayerMessage [S4]
- Payment API availability: yes · yes · yes [S7]
- Payment methods: Saferpay lists supported payment methods by acquirer/bank/provider, with method type, brand/scheme and coverage [S2]
- Paymentpage interface ecommerce: yes · yes [S8]
- Payone methods: PAYONE · Europe primarily; Alipay+, Click to Pay, WeChat Pay international [S2]
- Permission denied error: ABORT · PERMISSION_DENIED [S7]
- Psd2 requirement: PSD2/SCA via 3D Secure required for EEA merchants handling MITs [S5]
- Psd2 scope parameter: Liability.InPsd2Scope [S3]
- Psd2 scope rule: applies when acquiring contract signed inside the EEA, regardless of merchant HQ location [S3]
- Qr payment features: Pay by link/Secure PayGate · Secure PayGate Multiuse Links · 3D Secure · Dynamic Currency Conversion (DCC) · Payment Page · Risk Management · Backoffice · Test Environment [S7]
- Recommended 3ds check: Proceed only if Authenticated and LiabilityShift are true (3D Secure) [S5]
- Recommended alias validation amount: 5 · 500 [S5]
- Reconciliation third party processors: For third-party processors such as PayPal connected via Saferpay, reconciliation data comes from that processor. [S6]
- Referenced API function: Transaction Authorize Referenced (AuthorizeReferenced) [S5]
- Referenced method use case: Referenced Transaction method is used for scheduled payments; primary method for subscription models [S5]
- Rejection retry recommendation: 24 [S5]
- Sca flows: SCA-capable flows: Payment Page, Transaction Interface, Standalone Secure Card Data Registration with ONLINE_STRONG check [S3]
- Sca transfer from saferpay: Transaction.IssuerReference · Payment Page Assert · Transaction Authorize [S3]
- Sca transfer parameters: Authentication.IssuerReference.TransactionStamp · Authentication.IssuerReference.SettlementDate · Authentication.IssuerReference.MastercardTLID [S3]
- Sca transfer pci requirement: yes [S3]
- Sca transfer to saferpay: Authorize Direct with direct card data post, MIT only · yes [S3]
- Secure card data availability: yes · yes [S7]
- Soft decline error: ABORT · PAYER_AUTHENTICATION_REQUIRED · 65 · 1A [S3]
- Soft decline handling: re-initiate process with forced SCA, old alias invalid, must re-create [S3]
- Supported payment methods: Apple Pay · American Express · Diners Club International & Discover · Google Pay · JCB · Mastercard · Postfinance Pay · SEPA Direct Debit · TWINT · Visa & V PAY · PayPal [S5]
- Test accounts business default: yes [S8]
- Test cards soft decline: yes [S3]
- Threeds avoid: AVOID · Authentication.ThreeDsChallenge [S3]
- Transaction ecommerce supported: Transaction Capture · Transaction Cancel · Transaction AssertCapture · Transaction MultipartCapture · Transaction MultipartFinalize · Transaction Inquire [S8]
- Upselling note: yes [S7]
- Worldline bancontact: Bancontact · Worldline · Belgium [S2]
- Worldline bank transfer coverage: Worldline · Blik (Poland) · Worldline Account-to-Account Payments (Europe excl. Switzerland) [S2]
- Worldline card coverage: Mastercard · Maestro Intl. · Visa · V PAY · JCB · Diners Club International/Discover Card · UnionPay · Worldline · Europe (incl. Switzerland and UK) [S2]
- Worldline ideal: iDEAL 2.0 · Worldline · Europe [S2]
- Worldline tagline: Worldline payment services from a single source [S2]
- Worldline wallets: TWINT (Switzerland) · Apple Pay (International) · Click to Pay (International) · Google Pay (International) · Alipay+ (International) · WeChat Pay (International) · Wero (Europe) · payconiq (Belgium) · Worldline [S2]
- Wrong license error: PERMISSION_DENIED [S8]

**Support**
- Pricing contact: no [S7]
- Reconciliation contact: Reconciliation questions go to the merchant's Account Manager; if unsure who the SPOC is, contact the processor's sales team. [S6]

## Questions

### 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)](https://whats-best.ai/software/payment/adyen), [Mollie (3/5)](https://whats-best.ai/software/payment/mollie) and [Checkout.com (3/5)](https://whats-best.ai/software/payment/checkout-com) 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](https://whats-best.ai/software/payment/adyen) (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Saferpay alternatives](https://whats-best.ai/software/payment/saferpay/alternatives).

## What this page leaves out

- We found no public information on pricing on the pages we read (docs.saferpay.com/home/integration-guide/payment-methods, docs.saferpay.com/home/master/payment-methods-and-acquirers, docs.saferpay.com/home/integration-guide/general-information/psd2, docs.saferpay.com/home/integration-guide/general-information/3d-secure, docs.saferpay.com/home/integration-guide/licences-and-interfaces/transaction-interface/recurring-payments, docs.saferpay.com/home/master/reconciliation and 2 more). If the vendor publishes it somewhere else, send us the page.
- We found no public information on compliance on the pages we read (docs.saferpay.com/home/integration-guide/payment-methods, docs.saferpay.com/home/master/payment-methods-and-acquirers, docs.saferpay.com/home/integration-guide/general-information/psd2, docs.saferpay.com/home/integration-guide/general-information/3d-secure, docs.saferpay.com/home/integration-guide/licences-and-interfaces/transaction-interface/recurring-payments, docs.saferpay.com/home/master/reconciliation and 2 more). If the vendor publishes it somewhere else, send us the page.
- 19 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.

## Sources

- [S1] Payment methods & local coverage — found from sitemap: https://docs.saferpay.com/home/integration-guide/payment-methods (checked 2026-10-13)
- [S2] Payment methods & local coverage — found from sitemap: https://docs.saferpay.com/home/master/payment-methods-and-acquirers (checked 2026-10-13)
- [S3] Checkout, SCA & fraud — found from sitemap: https://docs.saferpay.com/home/integration-guide/general-information/psd2 (checked 2026-10-13)
- [S4] Checkout, SCA & fraud — found from sitemap: https://docs.saferpay.com/home/integration-guide/general-information/3d-secure (checked 2026-10-13)
- [S5] Subscriptions & recurring payments — found from sitemap: https://docs.saferpay.com/home/integration-guide/licences-and-interfaces/transaction-interface/recurring-payments (checked 2026-10-13)
- [S6] Settlement, reconciliation & API — found from sitemap: https://docs.saferpay.com/home/master/reconciliation (checked 2026-10-13)
- [S7] Licence, risk & account terms — found from sitemap: https://docs.saferpay.com/home/master/licensing (checked 2026-10-13)
- [S8] Licence, risk & account terms — found from sitemap: https://docs.saferpay.com/home/master/licensing/licences-and-interfaces (checked 2026-10-13)

---

Cite as: whats-best.ai, "Saferpay — Payment", AI panel analysis, as of 2026-10-21. https://whats-best.ai/software/payment/saferpay

Corrections: https://whats-best.ai/correct/813?target=page