Payment
Paysafe
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Paysafe Holdings UK Limited · www.paysafe.com
Report an error on this page Is this your product? →
Link to this page
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.
Paysafe at a glance
- Vendor
- Paysafe Holdings UK Limited
- Headquarters
- Not stated on the vendor’s pages as of 20 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 20 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 20 Oct 2026
- Panel verdict
- The AI panel rates Paysafe 2/5, the mean of 6 judges. Paysafe's holding entity is UK-based Paysafe Holdings UK Limited; it scores strongest on recurring billing, 5 to 6, and weakest on sovereignty, 1 to 3. how scores are made
- As of
- Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Paysafe's holding entity is UK-based Paysafe Holdings UK Limited; it scores strongest on recurring billing, 5 to 6, and weakest on sovereignty, 1 to 3. Payment methods and checkout and SCA each hold at 4: SEPA Direct Debit is documented in depth — 36 countries, EUR processing, mandate flow, merchant-initiated pulls — but no European local method beyond SEPA is named in the captured pages, so per-market planning stops at the directory filter, and 3-D Secure is configurable, skippable or enforced above a USD limit under PSD2. Recurring billing rests on a Mandate API for SEPA, stored Visa and Mastercard charges, status callbacks and a query interface to check, cancel or extend, with no public information on dunning, retries or token export. Settlement scores 4 everywhere except the compliance officer's 2, with no public information on payout schedule or fee breakdown. Sovereignty spans 1 to 3, the compliance officer lowest at 1 — judges credit the Central Bank of Ireland-regulated Paysafe Payment Solutions Limited but find no published processing location or subprocessor list. Pricing transparency scores 0 and is not counted.
Speaks for it
- SEPA Direct Debit documented in depth — 36 countries, EUR processing, the Mandate API with pre-notification, merchant-initiated payments.
- 3-D Secure is configurable in the Business Portal — skip entirely or enforce above a USD amount limit — positioned as PSD2 SCA compliance with liability protection for fraudulent card payments.
- Regulated entities are named with supervisors and register numbers — two Central Bank of Ireland entities and FCA FRNs 900015, 900001 and 900021 — plus US ISO/MSP registrations with named sponsor banks.
- Recurring billing is buildable — stored Visa and Mastercard charges, SEPA mandates, per-payment status callbacks, and a query interface to check, cancel or extend a series.
- Settlement tooling is real — a Settlement Report API with named report schemas, settlement webhooks, a Postman collection, test cards and failure-scenario IBANs.
Held against it
- No European local method beyond SEPA is named in the captured pages — no iDEAL, Bancontact or Klarna — so a merchant cannot tell which methods cover DACH or Benelux.
- No public information on payout schedule, settlement currencies or per-transaction fee breakdown, so month-end close stays manual.
- Sovereignty attributes show nothing on record — no public information on where payment and cardholder data are processed or stored, and no subprocessor list.
- Bad-day terms are unevidenced — no public information on safeguarding of merchant funds, chargeback fees, dispute handling, reserve or freeze conditions, or termination notice.
- No public information on dunning, smart retries, an account updater, trials or proration, nor any documented process for exporting stored payment credentials to another provider.
Best for
- You collect recurring SEPA Direct Debit in EUR and want the mandate flow, pre-notification and merchant-initiated pulls documented for integration.
- You charge stored Visa and Mastercard cards or SEPA mandates on a schedule and will build retries, dunning and plan logic yourself on top of documented callbacks.
- Your compliance review needs a fully named regulated chain — the Central Bank of Ireland entities and FCA register numbers 900015, 900001 and 900021 are published.
- Your engineering team wants buildable public tooling — a Settlement Report API, settlement webhooks, a Postman collection, test cards and failure-scenario IBANs.
Avoid if
- Your rollout depends on named local methods per European market — the captured pages name none beyond SEPA, so coverage cannot be planned country by country.
- Your month-end close depends on a stated payout schedule and itemised per-transaction fees — we found no public information on either.
- You must clear data-sovereignty review before signing — no processing location or subprocessor list is public, and sovereignty scores span 1 to 3.
- You need subscription tooling out of the box — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 2 of 5 |
| Checkout, SCA & fraud | 2 of 5 |
| Subscriptions & recurring payments | 2.5 of 5 |
| Settlement, reconciliation & API | 2 of 5 |
| Licence, risk & account terms | 2 of 5 |
| European sovereignty | 1.5 of 5 |
Payment methods & local coverage
Show reasoningHide 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 — Cards only, or a method list with no statement of which countries and currencies each one covers.
3 — Major cards and wallets plus one or two European methods, with local coverage stated vaguely ("many local methods") and no SEPA Direct Debit.
5 — Cards, Apple Pay and Google Pay, SEPA Direct Debit, and the main local methods for DACH and Benelux (iDEAL or Wero, Bancontact, Klarna or invoice) listed by name with the countries they serve.
8 — Broad EU coverage named per country — including methods such as BLIK, TWINT, Przelewy24, EPS and Wero — multi-currency acceptance with settlement currencies stated, and which methods support refunds and recurring charges documented per method.
10 — Coverage is documented as a matrix a merchant can plan against: every method with its countries, currencies, refund, partial-capture and recurring support, and the provider's own acquiring versus third-party routing stated per method.
The Finance Lead
SEPA Direct Debit is properly documented — 36 SEPA countries, EUR processing currency, the full mandate flow — and there is a directory of local methods filterable by country and by type. But the captured pages name almost no European method individually beyond SEPA: ACH and Alipay are the only other named specifics, cards are evidenced as Visa and Mastercard in the recurring billing documentation, and no iDEAL, Bancontact, BLINK, TWINT or Wero appears by name. That is more than vague coverage, but short of a list a merchant can plan against market by market. 2 3 5
The E-Commerce Lead
Cards (Visa and Mastercard) plus a genuinely well-documented SEPA Direct Debit — Mandate API, pre-notification, 36 SEPA countries, EUR processing, merchant-initiated — are the only named European pieces I can plan against. The rest of the directory presents type filters (BNPL, eWallet, cash, vouchers) and a 'show all' control rather than a per-country named list; I found no public information naming Apple Pay or Google Pay, or the DACH and Benelux methods like iDEAL, Bancontact, BLIK or EPS that decide my conversion. 2 3 5
The SaaS Founder
SEPA Direct Debit is documented the way I need it — mandate-based, merchant-initiated, 36 SEPA countries, EUR processing — and there is a directory of local methods filterable by country and by type. But the captured pages name no iDEAL, Bancontact, Klarna, Apple Pay or Google Pay equivalents, and the only per-method recurring statement I found covers Visa and Mastercard, Skrill Balance and PaysafeCard, with no refund support documented per method. 2 3 5
The Payments Engineer
SEPA Direct Debit is documented the way I want to consume it — 36-country scope, EUR processing, mandate flow, merchant-initiated payments — alongside cards and a country-filterable directory spanning BNPL to local card schemes. But the captured pages stop short of naming the wallets and the DACH and Benelux local methods with the countries they serve, so I cannot plan a per-market rollout from them. 2 3 5
The Compliance Officer
SEPA Direct Debit is properly documented for the Single Euro Payments Area (36 countries, EUR, mandate flow), and a directory of local methods filterable by country and method type exists, but the captured pages name no Apple Pay, Google Pay or DACH/Benelux methods like iDEAL or Bancontact per market, and refund or recurring support per method is only documented for SEPA and the Skrill card flow. 2 3 5
The Skeptic
SEPA Direct Debit is documented in detail — 36 countries, EUR processing, mandates, merchant-initiated payments — and a directory filterable by country and method type exists. But no European local method beyond SEPA itself appears by name in the captured pages: no iDEAL, Bancontact, Klarna or EPS is named, and the only individually named non-card methods are Alipay and US-based ACH, so a merchant cannot tell which local methods cover DACH or Benelux. 2 3
Checkout, SCA & fraud
Show reasoningHide 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 — 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.
The Finance Lead
3-D Secure is documented as how Paysafe complies with Strong Customer Authentication under PSD2, configurable in the Business Portal with an option to skip it entirely or enforce it above a transaction amount limit, and liability protection for fraudulent card payments is stated. We found no public information on fraud screening, hosted versus embedded checkout options, or the PCI DSS scope of each integration type. The enforcement limit is specified in USD, an awkward unit for a European basket. 4
The E-Commerce Lead
3-D Secure is real and configurable — skip entirely or enforce above a USD amount, PSD2 and SCA compliance stated, liability protection against fraudulent card payments described — with test cards and test IBANs for failure scenarios. That amount switch is blunt rather than documented low-value or transaction-risk-analysis exemptions, and I found no public information on fraud screening tools, soft declines, or the PCI scope of each integration type. 3 4
The SaaS Founder
3-D Secure is properly engineered for PSD2: configurable in the Business Portal, skippable entirely or enforced above a set USD amount, and it carries liability protection for fraudulent card payments. I found no public information on hosted versus embedded checkout options, fraud screening, SCA exemption handling, or the PCI DSS scope each integration carries. 4
The Payments Engineer
3-D Secure is real and configurable — skip rules, a value limit in USD, PSD2 SCA compliance, a liability-protection statement, and test cards documentation — which is more than a bare redirect page. We found no public information on fraud screening, SCA exemption handling, or the PCI DSS scope of each integration type, so I would be integrating blind on scope. 4
The Compliance Officer
3-D Secure is genuinely configurable — skip entirely or enforce above an amount limit — positioned as PSD2 strong customer authentication, with a liability protection statement and published test cards; but I found no public information on exemption handling, fraud screening tooling, hosted versus embedded checkout options, or the PCI DSS scope of each integration. 4 6
The Skeptic
3-D Secure is documented as the SCA mechanism under PSD2, configurable in a business portal with a skip option and a USD amount limit, with liability protection explained and test cards published. We found no public information on hosted versus embedded checkout options, fraud screening rules, SCA exemptions such as transaction risk analysis, or PCI DSS scope — the skip-below-limit setting is the only exemption-like behaviour shown. 4 6
Subscriptions & recurring payments
Show reasoningHide 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 — 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.
The Finance Lead
Recurring charges work on stored Visa and Mastercard cards, Skrill Balance and PaysafeCard without the customer needing a wallet, and SEPA mandates run through a Mandate API with pre-notification and merchant-initiated payments — the card-on-file plus mandate skeleton is there. Every recurring payment posts a status callback to a merchant-supplied URL, with cancellation notified to a second URL. We found no public information on dunning or smart retries, a card account updater, or any documented process for taking stored payment tokens to another provider, and token portability is not something I will assume. 3 5
The E-Commerce Lead
The core is there: SEPA mandates via API with pre-notification, merchant-initiated payments documented, stored Visa and Mastercard credentials charged on a schedule through Skrill Quick Checkout, status callbacks on every recurring payment and a Merchant Query Interface to check, cancel or extend a series. I found no public information on smart retries and dunning, trials or proration, an account updater, or a way to take the payment tokens to another provider. 3 5
The SaaS Founder
The bones of renewal billing are there: stored cards for repeat charges without a wallet registration, SEPA mandates via a Mandate API with pre-notification, merchant-initiated transactions, per-payment status callbacks and a query interface to check, cancel or extend a recurring payment. What I cannot see is subscription logic — trials, proration, plan changes — plus smart retries and dunning, a card account updater, and any documented process for exporting payment tokens to another provider, which is exactly the lock-in I price against. 3 5
The Payments Engineer
A credible base exists: SEPA mandates via a Mandate API with pre-notification, documented merchant-initiated payments, and recurring card charges through Skrill Quick Checkout with scheduled start dates and status callbacks. We found no public information on dunning, smart retries, an account updater, or exporting tokens to another provider — and the recurring callback documentation requires an MD5 signature while the SHA-2 signature is optional, which I would raise before signing. 3 5
The Compliance Officer
Recurring charges run on Visa and Mastercard, Skrill Balance and PaysafeCard with signed status callbacks and a query interface to check, cancel or extend, and SEPA mandates are handled with pre-notification and merchant-initiated pulls — but I found no public information on subscription plan logic such as trials, proration, retries or dunning, nor any documented process for exporting stored payment credentials to another provider. 3 5
The Skeptic
Stored Visa and Mastercard recurring charges, SEPA mandates via a Mandate API with pre-notification, merchant-initiated payments and a query interface to check, cancel or extend a series are all documented. We found no public information on smart retries, dunning, account updater, trials or proration — and nothing on exporting stored payment credentials to another provider. 3 5
Settlement, reconciliation & API
Show reasoningHide 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 — 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.
The Finance Lead
A Settlement Report API with named report schemas, webhooks spanning the settlement lifecycle, and a proper test mode with test cards and test IBANs give a finance team something to build on. But the payout schedule itself is never stated, and we found no public information on a per-transaction fee breakdown, so I cannot tell whether fees are itemised or netted invisibly into payouts. For a month-end close, that silence is the problem. 3 4 6
The E-Commerce Lead
There is a Settlement Report API with a Postman collection, webhooks across the settlement lifecycle (processing, completed, cleared, returned, failed) and documented test cards, so my team can build. But I found no public information on payout cadence or settlement currencies, per-transaction fee breakdowns, or reports that tie each payout to its transactions and to a bank line. 3 4 6
The SaaS Founder
A Settlement Report API with named report schemas, webhooks that follow a SEPA payment all the way through settlement, and test cards and test IBANs for a sandbox — a finance engineer can build on that. But I found no public information on payout frequency or delay, per-transaction fee breakdowns, reports that tie a payout to its bank line, or API rate limits and idempotency, so month-end close stays manual. 3 6
The Payments Engineer
The pieces I build against exist: settlement lifecycle webhooks, a Settlement Report API with named report schemas, a Postman collection, and genuine test credentials including failure-scenario IBANs and test cards. We found no public information on payout cadence, per-transaction fee breakdown, API versioning, idempotency, rate limits, or a public status page with incident history. 3 4 6
The Compliance Officer
A Settlement Report API with named report schemas, a Postman collection and Business Portal transaction review give a development team something to build on, but I found no public information on payout frequency or settlement currencies, per-transaction fee itemisation, or reports that tie a payout to its transactions and bank lines. 3 6
The Skeptic
A Settlement Report API with named report types, settlement webhooks, a Postman collection and test IBANs for failure scenarios are documented. But we found no public information on the payout schedule, payout currencies or any per-transaction fee breakdown — a merchant cannot see from this evidence when the money arrives or how fees are itemised. 3 6
Licence, risk & account terms
Show reasoningHide 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 — 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.
The Finance Lead
The regulated chain is unusually well identified: an Irish entity supervised by the Central Bank of Ireland, three UK entities with FCA register numbers under the Electronic Money Regulations 2011, and North American ISO registrations with named sponsor banks. We found no public information on safeguarding of merchant funds, chargeback fees and dispute process, or termination notice periods. And the item I look for first — reserve and rolling-hold conditions with stated limits and release timelines — we found no public information on at all. 2 6
The E-Commerce Lead
The regulated chain is properly identified: two Central Bank of Ireland-regulated entities and three FCA-authorised entities with register numbers, plus the US ISO/MSP sponsor-bank registrations. What I could not find is the bad-day detail — I found no public information on safeguarding of merchant funds, chargeback fees or a dispute process, reserve and hold conditions, or termination notice and a route to appeal. 2 6
The SaaS Founder
The licence chain is unusually well lit: Paysafe Payment Solutions and Prepaid Services regulated by the Central Bank of Ireland, three FCA-authorised entities with register numbers, and US and Canadian ISO/MSP registrations with named sponsor banks. But I found no public information on safeguarding of merchant funds, chargeback fees and dispute handling, reserve or hold conditions with limits and release timelines, or termination notice and a route to appeal — the terms that decide a bad day. 2 6
The Payments Engineer
Regulated entities are named with supervisors and register numbers — the Central Bank of Ireland for two entities, FCA register numbers for three e-money entities, and US sponsor-bank registrations for the card side. The bad-day terms are the gap: we found no public information on safeguarding of merchant funds, reserve or freeze conditions, chargeback fees, or a termination notice period. 2 6
The Compliance Officer
The imprint side is genuinely strong: multiple regulated entities are named with their supervisors and register numbers — two Central Bank of Ireland entities, three FCA-authorised entities with FRNs, and ISO/MSP registrations against named US sponsor banks; but I found no public information on safeguarding of merchant funds, chargeback fees and dispute handling, reserve or freeze conditions, or termination notice periods. 2 6
The Skeptic
The regulated entities are named with their supervisors and register numbers — FCA FRNs 900015, 900001 and 900021, Central Bank of Ireland entities, plus US sponsor banks — which is real licence disclosure. We found no public information on safeguarding of merchant funds, chargeback fees, dispute processes, notice periods, reserves or freeze conditions, so the bad-day terms are entirely unevidenced. 2 6
European sovereignty
panel opinion
Show reasoningHide 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 — 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.
The Finance Lead
An EU-licensed entity, Paysafe Payment Solutions Limited under the Central Bank of Ireland, operates the payments brands, but the group entity in the site's legal notice is Paysafe Holdings UK Limited. We found no public information on where payment and cardholder data are processed and stored, on any subprocessor list with locations, or on a DPA. Without a processing-location statement I cannot clear this from a sovereignty standpoint. 2 6
The E-Commerce Lead
An EU-licensed, Central Bank of Ireland-regulated entity (Paysafe Payment Solutions Limited) sits in the chain alongside the UK holding company. But no sovereignty attributes were on record: I found no public information on where payment and cardholder data are processed and stored, on named EU infrastructure, or on a subprocessor list with locations. 2 6
The SaaS Founder
An EU-licensed entity sits in the chain — Paysafe Payment Solutions Limited under the Central Bank of Ireland — but the holding entity is Paysafe Holdings UK Limited and several regulated entities are FCA-authorised. I found no public information on where payment and cardholder data are processed and stored, and no published subprocessor list with locations, so I cannot plan my data flows from the captured pages. 2 6
The Payments Engineer
The independently sourced record carries nothing — no confirmed EU contracting entity, no processing location, no subprocessor list, no DPA. The pages name UK and Irish regulated entities, but the holding entity shown is UK-based, and we found no public information on where transaction or cardholder data is processed or stored. 2 6
The Compliance Officer
The contracting and copyright entity shown is Paysafe Holdings UK Limited, and I found no public information on where transaction and cardholder data are processed, who the subprocessors are, or a data processing agreement separating the provider's processor and controller roles — a disappointment given Irish and UK regulated subsidiaries are clearly named in the imprint. 2 6
The Skeptic
An EU-supervised entity exists in the chain — Paysafe Payment Solutions Limited under the Central Bank of Ireland — but the holding and copyright entity is UK-based Paysafe Holdings UK Limited, and the independently sourced sovereignty attributes show nothing on record. We found no public information on where payment and cardholder data are processed or stored, and no subprocessor list. 2 6
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide 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 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.
The Finance Lead
The captured pages show no price of any kind — no headline percentage, no per-method rate, no chargeback, currency conversion or payout fee. With nothing published, every rate would rest on a sales conversation, and the effective fee for a merchant's own card and country mix is unknowable from public pages alone. 1 2 6
The E-Commerce Lead
Across the captured pages — the homepage, the payment-methods directory and the developer and settlement documentation — we found no public pricing at all: no headline rate, no chargeback, refund, payout or monthly fee, no contract term. The effective fee for my card and country mix is not computable from anything public; every rate is a sales conversation. 1 2 6
The SaaS Founder
The captured pages contain no prices at all — no headline percentage, no per-method rates, no cross-border or currency-conversion markups, no chargeback, refund or payout fees, no monthly minimum. I cannot compute an effective fee for my own card and country mix; every rate would be a sales conversation. 1 2 4
The Payments Engineer
None of the captured pages state a price for any method — no headline rate, no chargeback fee, no payout or monthly fee, nothing to compute an effective fee from. For a merchant sizing this, every number would come from a sales conversation. 1 2
The Compliance Officer
No rates, fees, monthly costs or contract terms appear anywhere in the captured pages, and even the SEPA maximum amount is "set on a per merchant basis" — a merchant cannot compute any effective fee from public information. 3
The Skeptic
Not a single rate, fee or currency-conversion markup appears on any captured page — no percentage, no chargeback fee, no payout fee, no monthly minimum, no blended-versus-interchange-plus statement. A merchant cannot begin to compute an effective fee from public evidence; the effective rate is entirely a sales conversation. 1 2 3 4 5 6
Questions about Paysafe
Is Paysafe European?
Not determined: the vendor’s pages as captured do not say where Paysafe is based.
Where does Paysafe store data?
Not stated on the vendor’s pages as of 20 Oct 2026.
Does Paysafe have a free plan?
Not stated on the vendor’s pages as of 20 Oct 2026.
What are the best alternatives to Paysafe?
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: Paysafe alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 20 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- We found no public information on pricing on the pages we read (paysafe.com, paysafe.com/en/local-payment-methods, developer.paysafe.com/en/api-docs/payments-api/add-payment-methods/sepa-direct-debit, developer.paysafe.com/en/api-docs/paysafe-checkout/configure-3ds, docs.paysafe.com/docs/digital-wallets/quick-checkout/skrill-recurring-billing, docs.paysafe.com/api/paysafecard-paysafecash/settlement-report-api). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 7 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. Know more? Tell us
- 2 legal 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. Know more? Tell us
Sources (6)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.paysafe.com Checked 20 Oct 2026 Details →
- 2 Payment methods & local coverage — found from sitemap www.paysafe.com Checked 20 Oct 2026 Details →
- 3 Payment methods & local coverage — found from sitemap developer.paysafe.com Checked 20 Oct 2026 Details →
- 4 Checkout, SCA & fraud — found from sitemap developer.paysafe.com Checked 20 Oct 2026 Details →
- 5 Subscriptions & recurring payments — found from sitemap docs.paysafe.com Checked 20 Oct 2026 Details →
- 6 Settlement, reconciliation & API — found from sitemap docs.paysafe.com Checked 20 Oct 2026 Details →