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 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 of 5 3 of 5
Checkout, SCA & fraud 3.5 of 5 3.5 of 5
Subscriptions & recurring payments 3 of 5 2.5 of 5
Settlement, reconciliation & API 2 of 5 2 of 5
Licence, risk & account terms 2 of 5 2 of 5
European sovereignty 2 of 5 2 of 5
Pricing transparency 2 of 5 2 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 — 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 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

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

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

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

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

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

Pricing transparency

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

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 →