whats-best.ai
Search Sign in

Payment

Worldpay

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

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

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

Worldpay 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 3 of 5
Settlement, reconciliation & API 2.5 of 5 2.5 of 5
Licence, risk & account terms 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

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

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

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

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

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

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

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

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

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

Report an error

Pricing transparency not rated — the vendor publishes no price

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

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

Report an error

European sovereignty — proven facts

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

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.

Do you know more about Worldpay? Tell us Report an error on this page

Sources (11)

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

  1. 1 Vendor page worldpay.com Checked 3 Nov 2026 Details →
  2. 2 Payment methods & local coverage — found from sitemap www.worldpay.com Checked 3 Nov 2026 Details →
  3. 3 Payment methods & local coverage — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
  4. 4 Checkout, SCA & fraud — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
  5. 5 Checkout, SCA & fraud — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
  6. 6 Subscriptions & recurring payments — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
  7. 7 Subscriptions & recurring payments — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
  8. 8 Settlement, reconciliation & API — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
  9. 9 Settlement, reconciliation & API — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →
  10. 10 Licence, risk & account terms — found from sitemap www.worldpay.com Checked 3 Nov 2026 Details →
  11. 11 Licence, risk & account terms — found from sitemap docs.worldpay.com Checked 3 Nov 2026 Details →