Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

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

by PAYONE GmbH · www.payone.com

Compare with Mollie → Compare with Unzer → Report an error on this page Is this your product? →

Link to this page

PAYONE: AI-assisted analysis on whats-best.ai PAYONE: 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.

PAYONE at a glance

Vendor
PAYONE GmbH
Headquarters
Incorporated in France source, captured 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates PAYONE 2.5/5, the mean of 6 judges. PAYONE GmbH of Frankfurt am Main, supervised by BaFin as an E-Geld-Institut and owned by Worldline and the DSV-Gruppe, earns persona-weighted totals spanning 4.5 to 5.2 on this bench. how scores are made
As of
Vendor pages captured 8 Nov 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

PAYONE alternatives, European ones first →

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

The panel's verdict

PAYONE GmbH of Frankfurt am Main, supervised by BaFin as an E-Geld-Institut and owned by Worldline and the DSV-Gruppe, earns persona-weighted totals spanning 4.5 to 5.2 on this bench. The strongest result is checkout and SCA at 7-8, where the Exemption Engine is documented in unusual detail: low-value exemptions below 30 € with the five-transaction and 100 € caps, acquirer transaction risk analysis, automatic soft-decline recovery, and liability written down for both flows. Payment methods at 5-6 and recurring billing at 5-6 rest on the named Klarna suite with twelve countries and seven currencies and on SEPA Direct Debit mandates handled as first-class API objects. The weak side is uniform: licence and account terms, sovereignty and pricing transparency each scored 4, with settlement and reconciliation at 4-5 — payouts appear only as FAQ topics with no figures, the Disagio attached to the published Starter and Pro transaction prices is not quantified, and no public information states where payment and cardholder data are processed or stored. The judges did not meaningfully split: no criterion's scores diverge by more than a point.

Report an error

Speaks for it

  • Checkout and SCA scored 7-8, with low-value exemptions below 30 €, five-transaction and 100 € caps, acquirer transaction risk analysis, automatic soft-decline recovery and liability rules written down for both flows.
  • SEPA Direct Debit mandates are first-class API objects with separate creation and revocation endpoints, mandate reuse, a 36-month lifecycle and an eight-week contestation period for valid mandates.
  • The regulated entity is fully public — PAYONE GmbH, registered at Amtsgericht Frankfurt am Main under HRB 116860, admitted and supervised by BaFin as an E-Geld-Institut — with general terms published as downloads and online contract termination offered.
  • E-commerce package prices are published exactly: Starter at a 49,00 € one-time setup fee, 0,00 € monthly fee and 0,99 € + Disagio per transaction; Pro at 99,00 € setup, 19,00 € monthly and ab 0,09 € + Disagio.
  • The developer platform documents webhooks, result-polling endpoints, a five-day finality rule and a test environment with documented test cases.

Report an error

Held against it

  • Payouts appear only as FAQ topics — timing, cycle changes, limits and fees — with no payout schedule, fee itemisation or reconciliation reports stated on the captured pages.
  • The Disagio, the rate that decides the real transaction cost, is not quantified on the captured pages, so an effective rate cannot be computed from them.
  • We found no public information on where payment and cardholder data are processed or stored, or on a data processing agreement for merchants.
  • We found no public information on subscription logic such as trials, proration, dunning or smart retries, or on exporting payment tokens to another provider.
  • We found no public information naming local methods such as iDEAL, Bancontact, EPS, BLIK or TWINT, and wallets appear only as generic contactless payment by smartphone.

Report an error

Best for

  • You run an online shop aimed at Germany and Austria and want SEPA Direct Debit with full mandate handling plus the named Klarna suite.
  • You accept American Express, Mastercard and Visa in the EEA and want exemption handling with automatic soft-decline recovery and liability rules in writing.
  • You want a German contracting entity supervised by BaFin, with a published register entry and downloadable terms per product line.
  • You bill by recurring SEPA mandate — subscriptions, on-demand or pay-as-you-use services — and build subscription logic on your own side.

Report an error

Avoid if

  • You must compute your effective card rate before committing; the published prices stop at "0,99 € + Disagio" and "ab 0,09 € + Disagio" with no Disagio figure.
  • Your finance team needs a stated payout schedule, per-transaction fee itemisation and reports that tie payouts to their transactions from day one.
  • You sell into markets that rely on methods such as iDEAL, Bancontact, EPS, BLIK or TWINT beyond the documented Klarna, SEPA and card families.
  • Your subscription business expects dunning, smart retries, trials or proration from the provider; the documented recurring story is mandate mechanics.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Payment methods & local coverage

Show reasoning
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.

Report an error

The Finance Lead

The developer pages name the full Klarna suite — Pay Later, Pay in 3/4, Pay Now bank transfer and direct debit, Billie B2B, Fair Financing — with twelve supported countries and seven currencies, and SEPA Direct Debit is documented with its own country list, girocard participation terms exist, and cards appear as Visa, MasterCard and American Express. However, we found no public information on wallets or local methods such as iDEAL, Bancontact, BLIK or EPS, or on a per-country matrix stating settlement currencies. 5 6 7 8

Report an error

The E-Commerce Lead

The developer docs are plannable for two families — Klarna with twelve named countries, seven currencies, refunds and capture rules, and SEPA Direct Debit with its country list and mandate lifecycle — plus girocard participation terms and Visa, MasterCard and American Express named in passing. For the rest of my markets, we found no public information naming iDEAL, Bancontact, EPS, BLIK or TWINT, and the homepage sells "alle gängigen Bezahlverfahren" with contactless via smartphone as the only wallet signal. 1 6 7 5 8

Report an error

The SaaS Founder

The developer pages document Klarna end to end — Pay Later, Pay Now by bank transfer and direct debit, instalment financing, a B2B variant — with twelve named countries and seven named currencies, and SEPA Direct Debit has its own country list and a full mandate flow; the homepage adds credit and debit cards plus contactless smartphone payments. I found no public information naming iDEAL, Bancontact, EPS, BLIK, TWINT or Przelewy24 on the captured pages, so I cannot plan conversion country by country the way an 8 would require. 1 6 7 11

Report an error

The Payments Engineer

Cards (Visa, Mastercard, Amex), SEPA Direct Debit with full mandate handling, girocard participation conditions, and Klarna's Pay Now, Pay Later and instalment variants are each documented by name, and the developer pages list the twelve countries and seven currencies Klarna serves plus its refund and cancellation behaviour. What holds this below the top of the scale: we found no public information naming methods such as iDEAL, EPS, BLIK, TWINT or Wero, settlement currencies per method are not stated, and the homepage positions the offer around Germany and Austria. 1 5 6 7 8

Report an error

The Compliance Officer

The developer documentation names the full Klarna product suite with the twelve countries and seven currencies it serves, and SEPA Direct Debit with its country list and euro processing, including refund and recurring support for those methods; the card schemes American Express, Mastercard and Visa appear in the SCA documentation. The homepage mentions contactless payments by smartphone, tablet or smartwatch without naming a wallet. We found no public information naming local methods such as iDEAL, BLIK, EPS or Wero, so coverage reads as cards plus two detailed method families rather than a per-country matrix with settlement currencies. 1 6 7 8

Report an error

The Skeptic

Cards (American Express, MasterCard, Visa), SEPA Direct Debit with a long country list, and Klarna's named variants (Pay Now, Pay Later, Pay in 3/4, Billie, Fair Financing) are documented with their currencies, and girocard participation terms are published — that reaches the local-methods level. Wallets appear only as generic contactless payment by smartphone with no Apple Pay or Google Pay named, and we found no public information on iDEAL, Bancontact, EPS, BLIK, TWINT or a per-method matrix of refund and recurring support; girocard is evidenced through a terms document rather than a stated method list. 1 5 6 7 8

Report an error

Checkout, SCA & fraud

Show reasoning
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 — No checkout or payment form; the product does not take a payment to authorisation itself.

3 — A hosted payment page or payment links with 3-D Secure.

5 — Hosted and embedded checkout options, 3-D Secure 2 with SCA handled by the provider, and fraud screening with configurable rules.

8 — SCA exemptions (low value, transaction risk analysis, merchant-initiated) applied and documented, the PCI DSS scope of each integration type stated, 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 Finance Lead

The Exemption Engine documentation is unusually concrete: low-value exemptions below €30 with the five-consecutive-or-€100 caps, acquirer transaction risk analysis, automatic soft-decline recovery when frictionless flow is refused, and the merchant's liability for fraudulent exemptions stated plainly. Integration modes include hosted checkout, hosted tokenization, server-to-server and mobile, with 3-D Secure steps covered automatically, SCA exclusions auto-detected, and the issuer covering fraud losses; we found no public information on authorisation-rate reporting, network tokens or an account updater. 8 9

Report an error

The E-Commerce Lead

The Exemption Engine requests frictionless first, applies the low-value exemption below 30 € and acquirer transaction risk analysis, and auto-recovers via soft decline when the issuer refuses, with SCA exclusions like MOTO detected automatically and fraud scoring modules alongside hosted, tokenized, server-to-server and mobile integration modes. Liability is written down both ways — the issuer covers fraud on 3-D Secure while the merchant carries fraudulent exemptions. We found no public information on authorisation-rate reporting by method or issuer country, PCI scope per integration beyond "Low PCI requirements", or an embedded checkout on the merchant's own domain. 9 8 6 7

Report an error

The SaaS Founder

Exemption handling is documented in unusual depth: low-value exemptions below 30€ with the five-transaction and 100€ caps, acquirer transaction risk analysis, automatic recovery via soft decline when the issuer rejects frictionless flow, and liability written down for both flows — issuer covers fraud under 3-D Secure, merchant is liable for exemptions that turn out fraudulent. Four integration modes including a hosted tokenization page and fraud scoring modules are named, but I found no public information stating the PCI scope of each integration type, network tokens, an account updater or authorisation-rate reporting. 8 9 6

Report an error

The Payments Engineer

The Exemption Engine documentation is what I wish everyone shipped: low-value exemptions for transactions below 30 € with the 100 € single-transaction and five-consecutive limits, acquirer transaction risk analysis, which card methods qualify, who is liable when an exemption turns out fraudulent, and automatic recovery via soft decline when the issuer rejects frictionless; SCA exclusions like MOTO are auto-detected and issuer liability under 3-D Secure is stated plainly. Hosted checkout, hosted tokenization, server-to-server and mobile integration modes are documented with a test environment and written test cases. We found no public information stating the PCI DSS scope per integration type, on an account updater or network tokens, or on authorisation-rate reporting by method and issuer country. 6 7 8 9

Report an error

The Compliance Officer

The exemption engine is documented in unusual detail: the low-value exemption below 30 € with the five-transaction and 100 € caps, acquirer transaction risk analysis, exclusion rules, automatic detection of out-of-scope transactions, and automatic soft-decline recovery when the issuer refuses the frictionless flow. Liability is explained per flow — the issuer compensates fraud losses on authenticated 3-D Secure transactions while the merchant accepts liability for fraudulent exemptions — and four integration modes plus fraud modules are listed. We found no public information stating the PCI DSS scope of each integration mode, network tokens, or an account updater. 6 8 9

Report an error

The Skeptic

The exemption documentation is unusually candid — low-value thresholds, acquirer transaction risk analysis, the 500 € cap, out-of-scope cases listed, automatic soft-decline recovery when an issuer rejects frictionless flow, and the plain warning that the merchant is liable for fraudulent exemptions, with the issuer covering fraud on authenticated 3-D Secure payments. Four integration modes including hosted checkout and a tokenisation page are named with 3-D Secure steps handled automatically; what I cannot see is the PCI DSS scope of each integration type, an account updater or network tokens, or authorisation-rate reporting. 6 7 8 9

Report an error

Subscriptions & recurring payments

Show reasoning
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 — One-off payments only; the product stores no payment method for a later charge.

3 — Saved cards (card-on-file) charged again for repeat or recurring payments.

5 — Stored cards and SEPA Direct Debit mandates for recurring charges, merchant-initiated transactions, and subscriptions or scheduled payments with notification of failed payments.

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 Finance Lead

SEPA mandate handling is properly built out: a separate CreateMandate API, a RevokeMandate endpoint, a 36-month mandate lifecycle, an eight-week contestation period for valid mandates, recurring mandates valid for an indefinite run of charges, and webhook status codes that flag declines. But we found no public information on subscription logic such as trials, proration or plan changes, on smart retries and dunning beyond 1-cent transfer guidance for failed direct debits, or on exporting payment tokens to another provider. 7 10 11

Report an error

The E-Commerce Lead

SEPA mandates are first-class: create standalone or inside a payment, reuse via an existing mandate reference also for card-on-file, revoke through a dedicated endpoint, RECURRING mandates valid for an indefinite run, a 36-month lifecycle and an 8-week contestation window, with webhooks delivering declines. For subscription logic itself — trials, proration, plan changes, smart retries, dunning, account updater, or exporting payment tokens to another provider — we found no public information. 7 8 11 10

Report an error

The SaaS Founder

SEPA mandates are treated as a real product: a separate mandate-creation API, reuse of an existing mandate reference for card-on-file charges, a dedicated revoke endpoint, a 36-month lifecycle, a reduced eight-week contestation period for valid mandates and a creditor-ID option. What decides renewals for a business like mine is undocumented here — I found no public information on smart retries, dunning, a card account updater, trials or proration, and no process for exporting stored payment tokens to another provider, which is the silence that would worry me most at contract time. 7 11 10

Report an error

The Payments Engineer

SEPA mandates are engineered properly: separate mandate creation and revocation endpoints, reuse of an existing mandate across transactions, recurring validity for an indefinite number of subsequent charges, a creditor-ID service, and webhook status codes that tell you a debit was declined. Card-on-file flows appear through the challenge-indicator handling. We found no public information on subscription logic such as trials, proration or plan changes, smart retries or dunning, a card account updater, or a documented process for exporting payment tokens to another provider. 7 8 10 11

Report an error

The Compliance Officer

SEPA Direct Debit mandates are a first-class object of the API: a separate mandate-creation request, mandate creation inside payment requests, reuse of an existing mandate reference for later charges, a dedicated revocation endpoint, a thirty-six-month lifecycle with automatic revocation, and a reduced contestation period of eight weeks for valid mandates. Recurring mandates run for an indefinite number of subsequent transactions, subscriptions and on-demand services are named as the use case, declines arrive via webhooks, and card-on-file flows appear in the SCA documentation. We found no public information on dunning or smart retries, pre-notification of debits, or a process for exporting payment tokens to another provider. 7 8 11

Report an error

The Skeptic

SEPA mandates are documented end to end — creation via API or hosted checkout, a dedicated revocation endpoint, a 36-month lifecycle with automatic revocation, recurring mandates valid for an indefinite number of subsequent transactions, a contestation period cut to 8 weeks for valid mandates, and failed payments surfacing through webhook status codes. The subscription layer is thin: we found no public information on trials, proration, plan changes, dunning, an account updater, or a process for exporting payment tokens to another provider. 6 7 8 10 11

Report an error

Settlement, reconciliation & API

Show reasoning
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 — No merchant reporting: the product is a payment button or link with no dashboard, report or API.

3 — A dashboard of transactions and payouts, a stated payout schedule, and CSV export.

5 — The payout schedule stated, reports or exports that link each payout to its transactions and fees, and a documented API with webhooks and a test mode.

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 Finance Lead

Payouts are addressed only as an FAQ section — where to view them, when they arrive, how to change the cycle, and whether there are limits or fees, with no values stated on the page — so we found no public information on a stated payout schedule, fee itemisation per transaction, or reports that tie each payout to its transactions and charges. The developer platform does provide a documented API with webhooks and a test environment, which is the part a finance team could build on. 7 12 13

Report an error

The E-Commerce Lead

The developer platform is real — documented APIs, webhooks, status transitions with a five-day finality rule and a test environment with test cases — but the money side gives me FAQ titles only: viewing payouts, payout timing, changing the payout cycle, and limits and fees with no values stated, plus merchant customer portals. The payout cadence, fee itemisation per transaction and reconciliation exports to match a bank statement did not appear in the captured pages. 7 12 13 10

Report an error

The SaaS Founder

A documented API with webhooks, payment-result polling endpoints and a test environment with test data and test cases is there, and the payout help centre indexes timing, cycle changes, limits and fees, missing transactions and payout problems. But I found no public information stating the payout cadence itself, itemising fees per transaction, or providing a reconciliation report that ties payouts to their transactions — I could build payment flows on this, not a month-end close. 6 7 12 13 10

Report an error

The Payments Engineer

The developer platform documents webhooks, polling via GetPaymentDetails and GetHostedCheckout, status-code transitions with a five-day finality rule, and a test environment — the pieces I actually build against — but we found no public information on a versioned API with idempotency keys, published rate limits, or a status page with incident history. Payouts appear as FAQ topics (viewing payouts, timing, changing the payout cycle, limits and fees) with no figures stated on the captured pages, and fee itemisation per transaction or reconciliation exports linking payouts to bank lines are not evidenced. 6 7 9 12 13

Report an error

The Compliance Officer

The merchant help area carries a payouts section whose listed topics include viewing payouts, payout timing, changing the payout cycle, and limits or fees for withdrawals, with no figures stated on the pages we read. The developer platform documents webhooks, result-polling endpoints and a test environment with documented test cases and data. We found no public information on a stated payout schedule, reports linking each payout to its transactions and fees, CSV or accounting exports, or fee itemisation per transaction. 7 12 13

Report an error

The Skeptic

The payout story on the captured pages is a FAQ index — 'When will I receive my payouts?', 'How can I change my payout cycle?', 'Are there limits or fees for withdrawals?' — with no payout schedule, settlement currency or fee value stated, while the developer side is solid with a documented API, webhooks and a test environment with test cases. We found no public information on fee itemisation per transaction, reconciliation exports that match a bank line, accounting integrations, or a public status page. 6 7 9 12 13

Report an error

Licence, risk & account terms

Show reasoning
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 — The terms let the provider freeze funds or close the account at any time with no notice, reason or timeline.

3 — The regulated entity or the licensed partner behind the payments named, and a chargeback or dispute process described.

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

8 — Entity, supervisor, register number and passporting stated per country; safeguarding stated; 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 Finance Lead

The imprint names PAYONE GmbH with its Frankfurt commercial register number, its BaFin e-money institution licence, and ownership by Worldline and the DSV-Gruppe, and the terms library runs deep — girocard participation conditions, PAC & PPS conditions, factoring agreements — with online contract cancellation and chargeback FAQs. But we found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions with limits and release timelines, the chargeback fee, or a notice period for ordinary termination. 4 5 10

Report an error

The E-Commerce Lead

The licence layer is properly public: PAYONE GmbH of Frankfurt, registered at Amtsgericht Frankfurt under HRB 116860, licensed and supervised by BaFin as an E-Geld-Institut, owned by Worldline and the DSV-Gruppe. The bad-day terms thin out after that — chargebacks appear in support FAQs but the captures show no published fee, and for safeguarding of merchant funds, reserves, and freeze or termination notice periods we found no public information; online contract termination exists as a service option. 4 5 10 3

Report an error

The SaaS Founder

The imprint names the operating entity with its Frankfurt court and register number, BaFin admission and supervision as an e-money institution, European ownership by Worldline and the German savings-bank publisher, downloadable terms per product line, a chargeback FAQ and an online contract termination. The bad-day small print I read contracts for is what I could not find public information on: safeguarding of merchant funds, reserve or rolling-hold conditions, termination notice periods, or a route to appeal a freeze. 4 5 10

Report an error

The Payments Engineer

The imprint names PAYONE GmbH with its Frankfurt registry entry (HRB 116860) and states it is licensed and supervised by BaFin as an e-money institution, and chargeback handling is described in the billing FAQs. We found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions, a published chargeback fee, or notice periods for termination — only that cancellation is available online through the service area. 4 5 10

Report an error

The Compliance Officer

The imprint names PAYONE GmbH in Frankfurt am Main, registered at Amtsgericht Frankfurt am Main under HRB 116860 and admitted and supervised by BaFin as an E-Geld-Institut — the entity, supervisor and licence type a regulated buyer needs — with ownership by Worldline and the Deutscher Sparkassen Verlag stated. Chargeback handling is covered in the billing FAQs, general terms are published as downloads including girocard participation conditions, and online contract termination is offered. We found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions, notice periods for termination or freezes, or a published PCI DSS attestation level. 4 5 10

Report an error

The Skeptic

The imprint names the regulated entity, its supervisor and its licence type — PAYONE GmbH, admitted and supervised by BaFin as an E-Geld-Institut — together with the commercial register entry, and chargeback handling is addressed in the support FAQs with a CreditorID service that reduces chargeback risk. But the pages I read publish no chargeback fee, no safeguarding statement for merchant funds, and no reserve, freeze or termination terms — the general terms exist as downloads whose contents the captured pages do not show. 4 5 7 10

Report an error

European sovereignty panel opinion

Show reasoning
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 — Contracting entity and processing of payment data both shown to be outside the EU, with no transfer safeguard stated.

3 — A named contracting entity and a privacy policy or data processing agreement; the processing location of payment data not stated or partly outside the EU.

5 — An EU contracting or regulated entity, with EU processing of core payment data stated or a subprocessor list published, and a data processing agreement offered.

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 Finance Lead

The contracting entity is German — PAYONE GmbH, registered at the Frankfurt local court and licensed by BaFin as an e-money institution — while the privacy policy places the parent Worldline group's seat in Paris and states that all group companies sit within the EU and EEA. We found no public information on where payment or cardholder data is processed or stored, on a data processing agreement, or on subprocessor locations; the published subprocessor list covers website tools such as Google Analytics and Facebook Pixel, with standard contractual clauses and adequacy decisions cited as transfer safeguards. 3 4

Report an error

The E-Commerce Lead

European at the entity layer: a German contracting entity, a BaFin licence, European ownership through Worldline of Paris and the German DSV-Gruppe, all group companies seated within the EU/EEA, and GDPR information documents for merchants and end customers. The captured pages do not state where payment and cardholder data are processed or stored, and we found no public information on a data processing agreement; the third-country transfers mentioned rely on standard contractual clauses and adequacy decisions. 4 3 5

Report an error

The SaaS Founder

This is a German BaFin-supervised e-money institution with its register entry published, European owners, a statement that every group company sits within the EU and EEA, GDPR information documents for merchants and end customers, a data protection officer and the Hessian supervisory authority named. Where payment and cardholder data is actually processed and stored is not stated on the captured pages and a data processing agreement is not evidenced, so the licence layer is proven but the data-location layer is not. 3 4

Report an error

The Payments Engineer

The operating entity is German with a BaFin licence, the parent Worldline is seated in Paris with ownership shared with the German DSV group, and the privacy policy states all group companies sit within the EU/EEA, with standard contractual clauses and adequacy decisions named for third-country transfers. The processing location of payment data itself is not stated and a data processing agreement for payment processing is not evidenced; the published processor lists cover website analytics and media tools. 3 4

Report an error

The Compliance Officer

The contracting and regulated entity is German — PAYONE GmbH, Frankfurt, supervised by BaFin — owned by Worldline, whose seat the privacy policy places in Paris, and the Deutscher Sparkassen Verlag; the same policy states that all group companies are seated within the EU and/or EEA, with EU standard contractual clauses and adequacy decisions named for third-country transfers. The policy publishes a data protection officer and lists website-level processors such as Google Analytics, Google Fonts and the moinAI chatbot, whose conversations are deleted after thirty days. We found no public information on where transaction and cardholder data are processed or stored, on a data processing agreement offered to merchants, or on the processing locations of the listed processors. 3 4

Report an error

The Skeptic

A German contracting and regulated entity with a BaFin e-money licence, European ownership — Worldline of Paris and the Deutscher Sparkassen Verlag — and a privacy policy stating that all group companies are seated in the EU/EEA, with standard contractual clauses and adequacy decisions for third-country transfers. But the processing location of payment and cardholder data is not stated, no subprocessor list with locations for the processing chain is published — the listed tools are website analytics — and no data processing agreement offer is evidenced. 3 4 5

Report an error

Pricing transparency

Show reasoning
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 rate published for one method or card type, or a "from" percentage.

5 — Rates published per main method with domestic and international cards distinguished, and any monthly or plan fee stated with its billing period; ancillary fees (currency conversion, chargeback, payout) may still be 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 Finance Lead

The e-commerce plans are published plainly: Starter with a 49,00 € one-off setup, 0,00 € monthly and a 0,99 € + Disagio transaction charge; Pro at 99,00 € once, 19,00 € per month and ab 0,09 € + Disagio; Individual priced individually; and POS price lists available as downloads. But the Disagio itself — the percentage a merchant actually pays — is never quantified, and we found no public information on chargeback, currency conversion or payout fees, so the effective rate cannot be computed from these pages. 2 5 13

Report an error

The E-Commerce Lead

Packages are priced publicly — Starter at 49,00 € one-off and 0,00 € monthly with "0,99 € + Disagio" per transaction, Pro at 99,00 € one-off and 19,00 € per month with "ab 0,09 € + Disagio" — but no Disagio percentage appears in the captured pages, so an effective rate for my card and country mix cannot be computed. Payout limits and fees are an FAQ topic without values, the Individual package is "individuell" throughout, and the POS price lists are PDF downloads whose contents the captures do not show. 2 5 13

Report an error

The SaaS Founder

The e-commerce packages publish their setup fees, monthly fees with the billing period, and per-transaction prices quoted as "0,99 € + Disagio" and "ab 0,09 € + Disagio", and price and service lists for the card and terminal tariffs are published as downloads. But the Disagio — the percentage that actually decides my effective rate — is never quantified on the captured pages, no domestic versus international card distinction is shown, and payout limits and fees appear only as a help topic without values, so I cannot compute what a renewal would cost me. 2 5 13

Report an error

The Payments Engineer

Package prices are public and exact — Starter at a 49,00 € one-off setup with 0,00 € monthly and 0,99 € + Disagio per transaction, Pro from 19,00 € per month with 99,00 € setup and ab 0,09 € + Disagio, Individual quoted individually — and downloadable price lists exist for the card and terminal products. The Disagio carries no figure on the captured pages, and we found no public information distinguishing domestic from international cards or stating currency-conversion markups or chargeback fees; payout fees appear only as an FAQ topic with no values stated on the page. 2 5 13

Report an error

The Compliance Officer

The commerce packages publish entry prices on the public page: Starter with a 49,00 € one-time setup fee, 0,00 € monthly fee and a 0,99 € + Disagio transaction fee; Pro with 99,00 € setup, 19,00 € monthly and ab 0,09 € + Disagio; Individual priced at individuell for setup, monthly and transaction fees. Downloadable price-and-service schedules for All Card Flat, All Time Flex and debit/credit card terminal processing exist on the terms page, and a payout FAQ raises limits and fees without stating values. We found no public information quantifying the Disagio, distinguishing domestic from international cards, or listing chargeback, refund or currency-conversion fees. 2 5 13

Report an error

The Skeptic

The E-Com plans publish their billing periods honestly — 49,00 € one-time setup with 0,00 € monthly for Starter, 99,00 € setup and 19,00 € per month for Pro, transaction prices '0,99 € + Disagio' and 'ab 0,09 € + Disagio' — but the Disagio itself, the rate that decides the real cost, is not quantified on the captured pages, and the top tier is priced 'individuell'. We found no public information on currency conversion markups, chargeback fees or payout fee values — the payout FAQ raises limits and fees without stating them — and downloadable price schedules for the card and POS tariffs exist whose contents the pages do not show. 2 5 13

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about PAYONE

Is PAYONE European?

Yes. whats-best.ai classifies PAYONE as EU-Made. Its vendor, PAYONE GmbH, is incorporated in France, per the vendor’s page captured 16 Nov 2026.

Where does PAYONE store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does PAYONE have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to PAYONE?

As of 18 Nov 2026, the panel rates Novalnet (3.5/5), PayPal (3.5/5) and Mollie (3/5) highest among the other 45 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 Novalnet (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: PAYONE 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.

Sources (14)

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

  1. 1 Vendor homepage www.payone.com Checked 16 Nov 2026 Details →
  2. 2 Pricing page www.payone.com Checked 16 Nov 2026 Details →
  3. 3 Privacy policy www.payone.com Checked 16 Nov 2026 Details →
  4. 4 Legal notice www.payone.com Checked 16 Nov 2026 Details →
  5. 5 Terms of service www.payone.com Checked 16 Nov 2026 Details →
  6. 6 Payment methods & local coverage — found from sitemap developer.payone.com Checked 16 Nov 2026 Details →
  7. 7 Payment methods & local coverage — found from sitemap developer.payone.com Checked 16 Nov 2026 Details →
  8. 8 Checkout, SCA & fraud — found from sitemap developer.payone.com Checked 16 Nov 2026 Details →
  9. 9 Checkout, SCA & fraud — found from sitemap developer.payone.com Checked 16 Nov 2026 Details →
  10. 10 Subscriptions & recurring payments — found from sitemap www.payone.com Checked 16 Nov 2026 Details →
  11. 11 Subscriptions & recurring payments — found from sitemap www.payone.com Checked 16 Nov 2026 Details →
  12. 12 Settlement, reconciliation & API — found from sitemap www.payone.com Checked 16 Nov 2026 Details →
  13. 13 Settlement, reconciliation & API — found from sitemap www.payone.com Checked 16 Nov 2026 Details →
  14. 14 Structured-data backfill: markup only, no text or screenshot www.payone.com Checked 8 Nov 2026 Details →