Payment
Worldline Online Payments
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Worldline SA · worldline.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.
Worldline Online Payments at a glance
- Vendor
- Worldline SA
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Worldline Online Payments 0/5, the mean of 6 judges. Worldline Online Payments, a payment offering from Worldline SA, publishes product-level marketing — an "all-in-one online payment solution", acquiring processing for all channels, omnichannel and cross-border payments — plus scale figures of 1.2M+ merchants and financial institutions and 48bn transactions processed. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Worldline Online Payments alternatives, European ones first →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Worldline Online Payments, a payment offering from Worldline SA, publishes product-level marketing — an "all-in-one online payment solution", acquiring processing for all channels, omnichannel and cross-border payments — plus scale figures of 1.2M+ merchants and financial institutions and 48bn transactions processed. The bench found the record weakest on payment methods, checkout and SCA, recurring billing, and settlement and reconciliation, where scores cluster at 0: the captured pages name no payment method, and we found no public information on checkout integration, 3-D Secure, SCA exemptions, SEPA mandates, dunning, payout cadence, fee itemisation or API documentation. Its strongest ground is only relative: licence and account terms (scores range 0 to 1, credited to the published corporate name) and sovereignty (0 to 2), where judges genuinely split — several counted selection for the Eurosystem's digital euro pilot as a European signal, while others called it a group-level fact evidencing nothing about where payment data is processed; the independently collected record shows no sovereignty attributes for this vendor. No price of any kind appears in the captured pages.
Speaks for it
- The captured pages publish the contracting entity, Worldline SA, giving merchants a named vendor.
- Selection for the Eurosystem's digital euro pilot is on record as a European signal.
- Published scale figures — 1.2M+ merchants and financial institutions, 48bn transactions processed, 128 M cards managed — document the group's volume.
- Named solution areas span in-store, online, omnichannel, cross-border and payments for platforms, sketching the breadth of the offering.
Held against it
- Payment methods scores cluster at 0 — the captured pages name no method, country or currency a merchant can plan coverage against.
- We found no public information on hosted or embedded checkout, 3-D Secure, SCA exemption handling or fraud screening.
- We found no public information on stored credentials, SEPA mandate handling, subscription logic or dunning.
- We found no public information on payout cadence, settlement currencies, per-transaction fee itemisation, reconciliation reports or a documented API.
- We found no public information on a licence type, supervisor or register number, on reserves or termination terms, or on where payment and cardholder data is processed and which subprocessors are involved.
Best for
- You run a large retail, marketplace or platform business and plan a sales-led procurement in which method coverage, rates and account terms are negotiated in writing during an RFP.
- You want a provider selected for the Eurosystem's digital euro pilot and are willing to verify processing locations, subprocessors and licences through direct diligence.
- Your shortlisting weighs published scale — 1.2M+ merchants and financial institutions and 48bn transactions processed — and you defer all detail to vendor answers.
Avoid if
- You need to compare payment method coverage per country or currency before talking to sales — ask the vendor: the public pages we read do not show it
- Your engineering team must evaluate checkout integration, 3-D Secure behaviour and fraud screening from documentation before committing build time.
- Your finance team needs published payout schedules, fee itemisation and reconciliation reporting to plan month-end close.
- You run subscriptions and need documented SEPA mandate handling, merchant-initiated transactions and dunning.
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 0 of 5 |
| Checkout, SCA & fraud | 0 of 5 |
| Subscriptions & recurring payments | 0 of 5 |
| Settlement, reconciliation & API | 0 of 5 |
| Licence, risk & account terms | 0.5 of 5 |
| European sovereignty | 0.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
The capture markets an all-in-one online solution and cross-border payments without naming a single method, country or currency; we found no public information on SEPA Direct Debit or any of the local European methods that decide conversion per market. 1
The E-Commerce Lead
The page names product lines like 'acquiring processing for all channels' and an 'all-in-one online payment solution' but no actual method — not a card scheme, not SEPA Direct Debit, not iDEAL, Bancontact or BLIK for any of my eight markets. Counts like '1.2M+ merchants' and '48bn transactions processed' tell me scale, not which local method converts in each country, and I found no public information on per-country coverage. 1
The SaaS Founder
The captured page markets an "all-in-one online payment solution" and cross-border payments without naming a single payment method, and we found no public information on which local methods, countries or currencies are covered. A subscription business that lives on SEPA Direct Debit mandates has nothing here to plan conversion against. 1
The Payments Engineer
The captured page markets an "all-in-one online payment solution" and cross-border payments without naming a single method, country or currency it serves. The Eurosystem digital euro pilot selection is the closest thing to a local-rail fact, and it is not a method list a merchant can plan acceptance against. 1
The Compliance Officer
The captured page names solution areas such as cross-border, omnichannel and account payments, but we found no public information on which payment methods a European customer can actually use, or the countries and currencies each one covers; no method — card, wallet, SEPA Direct Debit or any local scheme — is named anywhere on it. With no named list per market, the lowest score is the honest one. 1
The Skeptic
The captured pages name no payment method at all — not even which cards, let alone SEPA Direct Debit or a per-country local method list — just an "all-in-one online payment solution" and cross-border marketing copy. We found no public information on which methods serve which countries or currencies, so a merchant cannot plan coverage from this. 1
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
We found no public information on checkout integration options, 3-D Secure, SCA exemptions, fraud screening or PCI scope — the captured material stays entirely at the level of product marketing. 1
The E-Commerce Lead
I found no public information on hosted or embedded checkout, 3-D Secure, SCA exemptions, declined-payment handling or fraud screening; the closest item is an 'Authentication & Security' line in a solutions list aimed at financial institutions. I cannot tell whether the checkout stays on my domain or how challenges are triggered, so I have nothing usable about the payment path. 1
The SaaS Founder
We found no public information on hosted or embedded checkout, 3-D Secure, SCA exemption handling or fraud screening in the captured material; the only adjacent mention is "Authentication & Security" inside a solution set aimed at financial institutions. That is not a checkout path a merchant can evaluate for authorisation rates. 1
The Payments Engineer
We found no public information on hosted or embedded checkout options, 3-D Secure, SCA exemption handling, fraud screening or the PCI scope of any integration. As the engineer who wires the provider in and gets paged when things break, there is nothing captured here I could design a checkout against. 1
The Compliance Officer
We found no public information on hosted or embedded checkout options, 3-D Secure or SCA exemption handling, or any fraud screening offered to merchants. An Authentication & Security solution is listed among services aimed at financial institutions, which does not evidence what happens on a merchant's checkout path. 1
The Skeptic
We found no public information on checkout integration options, 3-D Secure or SCA exemption handling, fraud screening, or how legitimate payments are kept from failing. Every question this criterion asks is unanswered in the captured pages, which I score as complete absence. 1
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
We found no public information on stored payment credentials, SEPA mandate handling, subscription plans, smart retries or dunning; the captured pages do not address charging the same customer again at all. 1
The E-Commerce Lead
I found no public information on stored payment credentials, merchant-initiated transactions, SEPA mandate handling, subscription logic or dunning. For charging the same customer again there is nothing published to plan on. 1
The SaaS Founder
We found no public information on stored payment methods, SEPA mandate handling, merchant-initiated transactions, subscription logic, dunning or any process for exporting payment tokens to another provider. For a business where every failed renewal is churn nobody chose, nothing published here evidences the capability at all. 1
The Payments Engineer
We found no public information on stored credentials, merchant-initiated transactions, SEPA mandates, subscription logic, retries and dunning, or token export. Repeat charging is not evidenced on the captured page at all. 1
The Compliance Officer
We found no public information on stored payment credentials, card-on-file or merchant-initiated transactions, SEPA mandate handling, subscription plans, retries or dunning. Account payments processing appears as a product line but with no statement about charging the same customer again. 1
The Skeptic
The published material says nothing about stored payment methods, merchant-initiated transactions, SEPA mandates, subscription logic or dunning. We found no public information on whether stored credentials can be exported to another provider either. 1
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
I close the month on payout schedules, per-transaction fee lines and reports that tie to the bank statement, and we found no public information on payout cadence, settlement currencies, fee itemisation, reconciliation exports or a documented API with webhooks. The only developer-adjacent item captured is a Universal Commerce Protocol announcement for agentic commerce, which is not finance tooling. 1
The E-Commerce Lead
Payout cadence and currencies, per-transaction fee breakdowns, reconciliation reports, and any API or webhook documentation are all things I found no public information on; the only figures are marketing scale numbers like '48bn transactions processed'. Finance has nothing here to match a payout to its transactions. 1
The SaaS Founder
The capture states no payout schedule or settlement currency, no per-transaction fee breakdown, and no API, webhook or reconciliation reporting; we found no public information on any of it. Scale claims like 48 billion transactions processed say nothing about whether finance can close the month from the provider's data. 1
The Payments Engineer
We found no public information on payout cadence or currencies, per-transaction fee breakdown, reports that match a bank statement, a REST API, webhooks, idempotency, a test mode or a status page. Neither a finance team nor an integration team can build anything from what is captured. 1
The Compliance Officer
We found no public information on payout cadence or settlement currencies, per-transaction fee itemisation, reports that tie to a bank statement, or any documented API, webhooks or test mode. Nothing on this evidence lets a finance team assess reconciliation. 1
The Skeptic
Payout cadence and currencies, per-transaction fee breakdown, reconciliation reports and API documentation are all missing from the captured pages; we found no public information on any of them. There is nothing here a finance team could match against a bank statement or build a process on. 1
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 company is identified, but we found no public information on the supervisor, licence type or register number of the regulated entity, nor on safeguarding of merchant funds, chargeback fees, reserve or hold limits, or termination notice — the bad-day terms I need written down are not in the capture. 1
The E-Commerce Lead
I found no public information naming the regulated entity, its supervisor or a register number, or stating safeguarding of merchant funds, and nothing on reserves, freezes, termination, chargeback fees or a dispute process. Judged on what the published terms state, there is nothing to judge. 1
The SaaS Founder
No regulated entity, supervisor or register number appears in the captured page, and we found no public information on reserve, rolling-hold, freeze, termination or chargeback terms. On a bad day the contract is what protects my money, and none of it is visible in what was published. 1
The Payments Engineer
The corporate name Worldline SA is published, but we found no public information on a licence, supervisor or register number, safeguarding of merchant funds, chargeback fees, reserves, or freeze and termination terms. One point above the bottom only because a named contracting entity exists. 1
The Compliance Officer
The vendor is identified as Worldline SA, but we found no public information on the regulated entity that would hold merchant funds, its supervisor, its register number or any licence type, and equally none on reserve, freeze, termination, chargeback or safeguarding terms. A corporate name is not a licence identification, and the terms side is entirely unevidenced. 1
The Skeptic
The vendor's legal name appears, but we found no licence type, supervisor or register number, no safeguarding statement, no chargeback fees and no account terms captured at all. To my eye a missing licence number is itself an answer, and nothing published bounds reserves, holds or termination. 1
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
The independent record shows no sovereignty attributes at all; selection for the Eurosystem's digital euro pilot points to European activity, but we found no public information on the contracting entity's licence or domicile, on where payment and cardholder data is processed, or on any subprocessor list. 1
The E-Commerce Lead
No sovereignty attributes are on record: I found no public information on where the contracting entity sits, where payment data is processed and stored, or which subprocessors are used. The single European signal is that Worldline was 'selected for the Eurosystem's digital euro pilot', which alone lifts this just above nothing. 1
The SaaS Founder
No sovereignty attributes are on record: the capture states nothing about the contracting entity's location, where payment and cardholder data are processed, or any subprocessors. The one European signal is selection for the Eurosystem's digital euro pilot, which is not a substitute for documented EU processing on named infrastructure. 1
The Payments Engineer
The independently collected sovereignty attributes are all empty: no contracting entity detail, no processing or storage locations, no subprocessor list, no DPA. For a European merchant asking where cardholder data lives, we found no public information on the captured pages. 1
The Compliance Officer
The capture records no sovereignty attributes at all: we found no public information on the contracting entity, where transaction and cardholder data are processed or stored, the subprocessor chain and its locations, or where the provider acts as controller rather than processor. Selection for the Eurosystem's digital euro pilot is a group-level fact that does not evidence any of the controls a regulated merchant would rely on. 1
The Skeptic
The independently sourced record shows no sovereignty attributes for this vendor, and the captured pages state nothing about the contracting entity's regulatory footing, where payment and cardholder data are processed, or which subprocessors are involved. We found no public information on processing locations or a subprocessor list. 1
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
We found no public prices of any kind — no method rates, no cross-border or currency conversion markups, no chargeback, payout or monthly fees — so an effective fee for a given mix of cards and countries cannot be computed from what was captured. 1
The E-Commerce Lead
No rate of any kind appears — no headline percentage, no chargeback, refund, payout or monthly fee — so the effective fee for my card, country and method mix is not computable from public pages. I found no public pricing at all. 1
The SaaS Founder
We found no public prices in the captured material — no headline percentage, no per-method rates, no chargeback, payout or monthly fees, and no indication of blended versus interchange-plus. A merchant cannot begin to compute an effective fee from what is published. 1
The Payments Engineer
We found no public pricing on the captured page — no headline percentage, no per-method rate, and no word on cross-border, currency conversion, chargeback, refund, payout or monthly fees. Every rate would be a sales conversation. 1
The Compliance Officer
We found no public prices at all — no per-method rates, domestic versus international distinctions, cross-border or currency conversion markups, chargeback or payout fees, monthly fees or contract terms. On this evidence every rate is a sales conversation. 1
The Skeptic
The captured pages contain no price of any kind — no headline percentage, no rates per method, no currency conversion markup, no chargeback, refund, payout or monthly fee. Every rate is evidently a sales conversation, which is the bottom of this scale exactly. 1
Questions about Worldline Online Payments
Is Worldline Online Payments European?
Not determined: the vendor’s pages as captured do not say where Worldline Online Payments is based.
Where does Worldline Online Payments store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Worldline Online Payments have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Worldline Online Payments?
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: Worldline Online Payments alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 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 (worldline.com). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- We found no public information on compliance on the pages we read (worldline.com). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 4 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
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (1)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page worldline.com Checked 13 Oct 2026 Details →