Payment
Worldpay
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Worldpay, LLC · worldpay.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.
Worldpay at a glance
- Vendor
- Worldpay, LLC
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 3 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 3 Nov 2026
- Panel verdict
- The AI panel rates Worldpay 2.5/5, the mean of 6 judges. Worldpay, LLC, now part of Global Payments, earns its best scores on checkout and SCA at 7-8: 3-D Secure 2 with device data collection, exemptions for low value under €30, transaction risk analysis and merchant-initiated transactions, liability shift explained per flow, and a PCI-compliant Checkout SDK with hosted card fields. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 3 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Worldpay, LLC, now part of Global Payments, earns its best scores on checkout and SCA at 7-8: 3-D Secure 2 with device data collection, exemptions for low value under €30, transaction risk analysis and merchant-initiated transactions, liability shift explained per flow, and a PCI-compliant Checkout SDK with hosted card fields. Payment methods score 5-6 on a long named catalogue — cards across the major schemes, Apple Pay and Google Pay, SEPA Direct Debit with 37 countries listed, and Bancontact, Blik, Bizum and Bancomat Pay — though the pages give no per-method view of currencies, refunds or recurring support. Recurring billing scores 5-6 on stored-card tokens, SEPA e-mandates and agreement types, with no public information on dunning or token export. Settlement and reconciliation scores 4-5, licence and account terms 3-4: reserve mechanics are unusually explicit but scoped to partners in the United States and Canada, and enterprise terms defer to the customer's Order. Sovereignty scores are 0-0, with jurisdiction, data residency and processing location unknown; pricing transparency scores 1-2 on quote-only signals. No significant disagreements were recorded.
Speaks for it
- Checkout and SCA scores cluster at 7-8, covering 3-D Secure 2, exemptions under €30, per-flow liability shift and a PCI-compliant Checkout SDK with hosted card fields
- A named catalogue spanning the major card schemes, Apple Pay and Google Pay, SEPA Direct Debit with its 37-country list, and Bancontact, Blik, Bizum and Bancomat Pay
- A recurring core of stored-card tokens with scheme-reference linking, SEPA e-mandates and subscription, installment and unscheduled agreement types, plus an account updater on the Enterprise line
- A versioned RESTful reporting API covering transaction and settlement data, chargebacks, filters, exports and long historical access
- Reserve mechanics documented with percentages, caps and release schedules, an unusually explicit treatment for the category
Held against it
- Sovereignty scored 0-0, with jurisdiction, data residency, hosting options and the data processing agreement all unknown on the captured pages
- We found no public information on payout cadence, settlement currencies, webhooks or per-transaction fee itemisation, leaving the finance lead unable to close a month from these pages alone
- We found no public information on dunning, smart retries, trials, proration or a documented process for exporting payment tokens to another provider
- Licence and account terms score 3-4: no published supervisor, licence, safeguarding statement, chargeback fee or termination notice, and enterprise terms defer to the customer's Order
- No per-method coverage matrix of countries, currencies, refunds and recurring support
Best for
- You sell into European markets and want named local methods — Bancontact for Belgium, Blik for Poland, Bizum for Spain, Bancomat Pay for Italy — alongside cards and SEPA Direct Debit
- You need engineered PSD2 SCA compliance, with documented exemption flows and liability shift stated per transaction flow
- You run card-on-file or SEPA e-mandate subscriptions and value an account updater, which sits on the Enterprise line
- You want a versioned reporting API with filters, exports and test documentation for reconciliation
Avoid if
- Your finance team must close the month from vendor documentation alone — ask the vendor: the public pages we read do not show it
- Your subscription revenue depends on documented dunning, smart retries, trials or proration
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 3 of 5 |
| Checkout, SCA & fraud | 3.5 of 5 |
| Subscriptions & recurring payments | 3 of 5 |
| Settlement, reconciliation & API | 2.5 of 5 |
| Licence, risk & account terms | 2 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 — 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.
The Finance Lead
A long named list spans cards, wallets, buy now pay later and bank transfers, with European local methods named — Bancontact, Bizum, Blik, Bancomat Pay — and SEPA Direct Debit documented with its 37-country list and the four-day CORE settlement delay. What I cannot plan against is a per-method view: the captured pages publish no countries, currencies, or refund and recurring support per method. 2 3 5
The E-Commerce Lead
The named methods give me real local answers for part of Europe — Bancontact for Belgium, Blik for Poland, Bizum for Spain, Bancomat Pay for Italy, Cartes Bancaires for France — alongside cards and SEPA Direct Debit with all 37 SEPA countries listed. There is no per-method matrix of currencies, refunds and recurring support, and iDEAL, EPS, TWINT and Przelewy24 do not appear on the pages I read, which leaves gaps in my Dutch, Austrian and Swiss markets. 2 3 5
The SaaS Founder
Cards from every major scheme, Apple Pay and Google Pay, and SEPA Direct Debit with a 37-country list are all named, alongside the local methods that decide conversion per market: Bancontact, Bizum, Blik and Bancomat Pay. We found no public information on per-method currencies, refund handling or which local methods take recurring charges — recurring is documented for SEPA e-mandates and stored cards. 2 3 5
The Payments Engineer
A large catalogue is named method by method — cards across the major schemes, wallets, Bancontact, BLIK, Bizum, Bancomat Pay, Cartes Bancaires, plus SEPA Direct Debit with a 37-country list — well past the several-local-methods bar. What I cannot plan an integration against is per-method structure: no country and currency matrix per method, no settlement currencies stated, and no per-method statement of refund or recurring support. 2 3 5
The Compliance Officer
Cards across the major schemes plus Apple Pay and Google Pay are documented, SEPA Direct Debit is offered with a named list of 37 countries, and European local methods are listed by name with their home markets — Bancontact, Bizum, Blik and Bancomat Pay. The captured pages do not state settlement currencies or refund and recurring support per method, so a merchant cannot plan against a full coverage matrix from them. 2 3 5
The Skeptic
Cards across the major schemes plus Apple Pay and Google Pay are named, SEPA Direct Debit is documented with its 37 countries listed one by one, and several European local methods appear by name — Bancontact, Blik, Bizum, Bancomat Pay. But the list is a menu, not a matrix: we found no public information on the countries and currencies each method serves, settlement currencies, or refund and recurring support per method. 2 3 5
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 — 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.
The Finance Lead
The 3DS and SCA documentation is genuinely deep: exemptions for low value under €30, transaction risk analysis, whitelisting and merchant-initiated transactions are each explained, and liability shift is spelled out per flow — issuer for 3DS, Worldpay as exemption provider. A PCI-compliant Checkout SDK with hosted card fields plus FraudSight risk outcomes and configurable AVS/CVC cancellation cover the fraud side; the captured pages show nothing on authorisation-rate reporting or soft-decline retry handling. 4 5 6 7
The E-Commerce Lead
Exemptions are engineered and documented — low-value under €30, transaction risk analysis with a fraud threshold, merchant-initiated transactions, whitelisting — and liability shift is explained per flow, to the issuer with 3-D Secure and to the exemption provider otherwise. A PCI-compliant Checkout SDK or direct API, configurable challenge preference, FraudSight outcomes and Account Updater complete the picture; I found no authorisation-rate reporting by issuer country, and the pages do not confirm a checkout running fully on my own domain. 4 5 6 7
The SaaS Founder
The SCA work is genuinely engineered: low-value and transaction-risk-analysis exemptions documented with the €30 low-value limit, merchant-initiated transactions, one-leg-out and whitelisting explained, liability shift stated per flow, and 3-D Secure 2 available inside the payments API or standalone as an external MPI. FraudSight returns a risk outcome that stops a payment and the AVS/CVC decline rule is configurable, but we found no public information on authorisation-rate reporting by issuer country or soft-decline retry handling. 4 5 6
The Payments Engineer
3-D Secure 2 with device data collection and challenge verification, SCA exemptions — low value under €30, transaction risk analysis, merchant-initiated, whitelist — applied automatically in the Payments API or standalone as an external MPI, with liability shift explained per flow and an account updater on the Enterprise line. FraudSight returns a risk outcome to the merchant and the Checkout SDK is described as PCI-compliant hosted card fields, but the PCI scope of the direct-API route is not spelled out, and I found no public information on soft-decline handling, authorisation-rate reporting by issuer, or merchant-configurable fraud rules. 4 5 6 7
The Compliance Officer
3-D Secure with device data collection and challenge handling, SCA exemptions for low-value, transaction risk analysis and merchant-initiated transactions, and liability shift explained per flow are all documented, including who carries liability when an exemption is granted. PCI-compliant hosted card fields are distinguished from direct API card submission, fraud outcomes and AVS/CVC risk factors are exposed to the merchant, and an account updater is offered; we found no public information on authorisation-rate reporting by method or soft-decline retry handling. 4 5 6 7
The Skeptic
The SCA work is documented properly: low-value (under €30) and transaction-risk-analysis exemptions granted with Worldpay as exemption provider, merchant-initiated transactions without SCA, wallet authentication rules, and liability shift explained per flow — issuer under 3DS, Worldpay under exemptions. 3DS 2 with device data collection and challenge handling, a PCI-compliant Checkout SDK with hosted card fields, and FraudSight screening with configurable AVS/CVC cancellation behaviour are all shown. We found no public information on fraud rules or risk scores exposed to the merchant, PCI scope per integration type, or authorisation-rate reporting by issuer country. 4 5 6 7
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 — 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.
The Finance Lead
Subscriptions are real here: stored-card setup with a Worldpay token, merchant-initiated subsequent charges linked by scheme reference, subscription, installment and unscheduled agreement types, an account updater on Enterprise, and SEPA e-mandates with the shopper-facing pre-acceptance information. The captured pages show nothing on dunning, failed-payment notification, plan changes, or a documented process for taking payment tokens to another provider. 3 6 7
The E-Commerce Lead
Cards on file, SEPA e-mandates with shopper-facing pre-acceptance information, merchant-initiated subsequent charges and subscription, installment and unscheduled agreement types are all documented, with Account Updater on the enterprise line. Dunning, smart retries, trials and proration are undocumented, Apple Pay and Google Pay cannot set up a subscription yet, and I found no documented process for exporting payment tokens to another provider. 3 4 6 7
The SaaS Founder
The foundations are here: SEPA e-mandates with the shopper information required before acceptance, merchant-initiated subsequent charges linked by scheme reference, stored-card subscription and installment agreements, a card account updater and Mastercard recurring linkage. We found no public information on trials, proration, plan changes, dunning or measurable recovery — and no documented process for moving my stored tokens to another provider. 3 6 7
The Payments Engineer
Stored cards with consent, Worldpay tokens with scheme-reference linkage for subsequent merchant-initiated charges, subscription, installment and unscheduled agreement types, zero-amount verification at setup, and SEPA e-mandates with the shopper-facing pre-acceptance information — the recurring core is there, plus an account updater on the Enterprise line. I found no public information on dunning, smart retries, failed-payment notification, trials or proration, and the token is stored as a Worldpay token with no documented export process to another provider. 3 6 7
The Compliance Officer
Stored Worldpay tokens, SEPA Direct Debit mandates with shopper-facing e-mandate information before acceptance, merchant-initiated subsequent charges linked by scheme reference and Mastercard transaction identifier, and subscription, installment and unscheduled agreement types are documented, with an account updater at Enterprise level. We found no public information on dunning or notification of failed payments, trials, proration and plan changes, or a documented process for exporting payment tokens to another provider. 3 6 7
The Skeptic
Stored-card tokens with scheme-reference linking, merchant-initiated transactions, SEPA e-mandates with required shopper-facing information, and subscription, installment and unscheduled agreement types are documented, with account updater on Enterprise and a stated rule that Apple Pay and Google Pay are not yet supported when setting up a subscription. We found no public information on dunning, failed-payment notification, trials, proration, or a documented process for exporting payment tokens to another provider — the recovery machinery that makes recurring revenue work stays undocumented. 3 6 7
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 — 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.
The Finance Lead
The Reporting APIs are documented in real depth — RESTful access to transaction and settlement data, settlement batches, chargeback reports, filters, exports and historical archives, with reconciliation and auditing stated as the integration purpose. But the captured pages state no payout cadence and show no fee itemisation per transaction, so I could not close a month from these pages alone. 9 11
The E-Commerce Lead
The RESTful reporting APIs are real: transaction and settlement data, filters by currency and merchant, settlement batches, scheduled extraction, exports, long-term history, a versioned API and a test environment. No payout schedule is stated on the pages I read, the captured pages do not mention webhooks, and fees are not itemised per transaction, so I could not close a month from this data alone. 7 9 11
The SaaS Founder
My finance team gets a real reporting API: RESTful interfaces, filters by currency and merchant ID, pagination, settlement batches, chargeback reports, long historical records, a versioned API and a test endpoint. We found no public information on payout cadence, settlement currencies, per-transaction fee itemisation or webhooks. 9 11 7
The Payments Engineer
RESTful reporting APIs for transaction and settlement data with real-time queries and scheduled extraction, settlement batch records, chargeback reporting with reasons and resolution timelines, pagination and multi-format export, a test API base URL, and a versioned API with a change log. The finance-closing pieces are absent from the captures — no payout cadence and no fee itemisation per transaction — and I found no public information on webhooks, idempotency keys, rate limits or a public status page. 7 9 11
The Compliance Officer
A versioned, RESTful reporting API covers settlement batches, chargebacks and payment activity with filters, scheduled extraction, exports in various formats, pagination and long-period historical access, and testing documentation with a test base URL exists; the SEPA CORE four-day mandated settlement delay gives one stated payout timing. We found no public information on payout currencies and schedules generally, fee itemisation per transaction, webhooks, published rate limits or a public status page. 3 5 7 9
The Skeptic
The reporting side is real: RESTful APIs over transaction and settlement data, settlement batches, chargeback reporting, filters, pagination, export formats, archived history, a versioned API and testing docs. But the money-out side is thin — we found no public information on payout cadence or settlement currencies, webhooks, idempotency and rate limits, or fee itemisation per transaction that would let finance match a bank line. 5 7 9
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 — 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.
The Finance Lead
Reserves are unusually well written down — rolling and accrual reserves with percentage, release interval and an optional cap, hold types with defined release mechanics — though that documentation is flagged for partners in the United States and Canada. The enterprise terms page says only that terms apply as stated in each Order, and we found no public information on the regulated entity's supervisor, safeguarding, termination notice or chargeback fee. 1 9 10 11
The E-Commerce Lead
The entity is named — Worldpay, now part of Global Payments, self-identified as acquirer in the SCA documentation — with dispute management and chargeback reporting covering reasons, statuses and resolution timelines, and reserve mechanics defined with caps and release timelines, though that reserve documentation is scoped to partners in the United States and Canada. I found no supervisor or licence type, no safeguarding statement, no chargeback fee and no termination notice period on the captured legal pages. 1 4 9 10 11
The SaaS Founder
Reserve mechanics are unusually well documented — rolling reserve percentages with release schedules and caps, accrual reserves, and hold types that block payouts — though on a partner page applicable to the United States and Canada. We found no public information on the licence or supervisor behind the payments, safeguarding, termination notice, chargeback fees or an appeal route; the legal page points enterprise merchants to terms stated in their Order. 1 10 11
The Payments Engineer
The captured legal page only tells me the Worldpay Terms and Conditions apply as stated on the customer's Order, and no licensed entity, supervisor, chargeback fee, safeguarding or termination notice appears on these pages. The reserves documentation is unusually concrete — rolling and accrual reserves with percentage, release interval and optional cap, plus defined release routes — though that guide is marked applicable to partners in the United States and Canada, and disputes surface as chargeback reporting rather than published terms. 9 10 11
The Compliance Officer
Reserves and holds are documented in unusual detail — rolling and accrual reserves with percentage, cap, release interval and release endpoints, plus transaction, entity and account holds that block payouts — though this material is marked applicable to partners in the United States and Canada. The enterprise terms are incorporated only by reference to the customer's Order, and we found no public information naming the regulated entity with its supervisor and register number, safeguarding of merchant funds, or freeze, termination and appeal terms; chargeback reporting with resolution timelines is described. 9 10 11
The Skeptic
A dispute process is described via chargeback reporting on reasons, statuses and resolution timelines, and the reserve machinery is unusually explicit — rolling and accrual reserves with percentages, caps and release schedules, hold types that block payouts, and release mechanics. But we found no public information on the supervisor, licence or register number behind the entity holding merchant funds, on safeguarding, on a published chargeback fee, or on freeze, termination and appeal terms; the captured terms defer everything to the customer's Order. 9 10 11
European sovereignty
panel opinion
n/r
n/r
n/r
n/r
n/r
n/r
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 — 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.
The Finance Lead not rated — no public information
We found no public information in the captured pages on the contracting or regulated entity's jurisdiction, or on where payment and cardholder data are processed; no data processing agreement or subprocessor list appears either. 1 10
The E-Commerce Lead not rated — no public information
I found no public information on the contracting entity's jurisdiction, where payment or cardholder data is processed or stored, or any data processing agreement; the captured homepage and legal agreements pages do not state it. 1 10
The SaaS Founder not rated — no public information
We found no public information on the contracting entity's jurisdiction or on where transaction and cardholder data are processed and stored; every sovereignty attribute came back unknown. The captured homepage and legal pages I read name Worldpay, LLC and its parent Global Payments but state no register, licence or processing location. 1 10
The Payments Engineer not rated — no public information
I found no public information on the contracting entity's jurisdiction, where payment or cardholder data is processed or stored, hosting options, or a data processing agreement on any captured page. The pages show SEPA and European local methods offered alongside cards, but nothing that locates the entity, the licence or the data. 1 2 3 4
The Compliance Officer not rated — no public information
We found no public information on the contracting entity's jurisdiction, where transaction and cardholder data are processed or stored, the subprocessor list, or a data processing agreement distinguishing processor from controller roles; the note that Worldpay is now part of Global Payments gives no location or licensing detail. These dimensions remain unknown on the pages captured, and I decline to infer either direction. 1 10
The Skeptic not rated — no public information
Every sovereignty dimension came back unknown: we found no public information on the contracting entity's jurisdiction, where payment or cardholder data is processed, a data processing agreement, transfer safeguards or a subprocessor list in any of the captured pages. 1 10
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 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.
The Finance Lead
No rate of any kind is published on the pages I read — pricing runs through a "get a quote in minutes" flow and a free account creation. I cannot begin to compute an effective fee for a given card and country mix from what is public. 1 9
The E-Commerce Lead
The pages I read show no published rate for any method or card type; small and mid-sized businesses are pointed to a quote in minutes, with a free account creation the only pricing-adjacent item. Every effective rate — cross-border markup, chargeback, payout — would come from a sales conversation rather than a public page. 1 9
The SaaS Founder
Every rate is a sales conversation: the homepage sells "Get a quote in minutes" alongside free account creation, and the captured pages publish no percentage, per-method rate, monthly fee or chargeback cost. I cannot begin to compute an effective fee for my card and country mix from what is public. 1 9
The Payments Engineer
The only pricing signals on the captured pages are that a free account can be created and that small and mid-sized businesses can get a quote in minutes. I found no published rate of any kind — no percentage, no per-method price, no chargeback, payout or conversion fee — so a merchant has nothing to compute an effective fee from. 1 9
The Compliance Officer
No transaction rates, method-level fees, chargeback or payout fees appear on the captured pages; the small-business path is "Get a quote in minutes" and the only price point shown is "Create a free account". A merchant cannot compute an effective fee for their card, country and method mix from the public information reviewed. 1 9
The Skeptic
The only pricing signals in the captured pages are "Get a quote in minutes" and "Create a free account". We found no public information on card rates, domestic versus international distinctions, cross-border or currency-conversion markups, chargeback, refund or payout fees, monthly minimums, contract terms, or whether the model is blended or interchange++ — a merchant cannot compute an effective rate from anything public. 1 9
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| 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 Worldpay
Is Worldpay European?
Not determined: the vendor’s pages as captured do not say where Worldpay is based.
Where does Worldpay store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does Worldpay have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to Worldpay?
As of 3 Nov 2026, the panel rates Adyen (3/5), Mollie (3/5) and Novalnet (3/5) highest among the other 35 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: Worldpay alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 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 could not confirm any compliance information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 24 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
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page worldpay.com Checked 3 Nov 2026 Details →
- 2 Payment methods & local coverage — found from sitemap www.worldpay.com Checked 3 Nov 2026 Details →
- 3 Payment methods & local coverage — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
- 4 Checkout, SCA & fraud — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
- 5 Checkout, SCA & fraud — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
- 6 Subscriptions & recurring payments — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
- 7 Subscriptions & recurring payments — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
- 8 Settlement, reconciliation & API — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
- 9 Settlement, reconciliation & API — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
- 10 Licence, risk & account terms — found from sitemap www.worldpay.com Checked 3 Nov 2026 Details →
- 11 Licence, risk & account terms — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →