Payment
Nuvei
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Nuvei Corporation · nuvei.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.
Nuvei at a glance
- Vendor
- Nuvei Corporation
- 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 Nuvei 3/5, the mean of 6 judges. Nuvei is a payments platform whose public documentation is strongest where card acceptance gets technical: checkout and SCA scores sit at 7, with the judges crediting 3-D Secure coverage that enumerates fifteen challenge-preference reasons, per-transaction exemption control, soft-decline resubmission and a plainly stated liability shift. 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
Nuvei is a payments platform whose public documentation is strongest where card acceptance gets technical: checkout and SCA scores sit at 7, with the judges crediting 3-D Secure coverage that enumerates fifteen challenge-preference reasons, per-transaction exemption control, soft-decline resubmission and a plainly stated liability shift. Recurring billing follows at 6-7, a documented rebilling product with plan and subscription management through the control panel and REST API, free trials, card updater and three retries at 72-hour intervals. Weakest are payment methods and sovereignty, both at 4: the pages state 720+ methods while the named list is short, with no public information naming SEPA Direct Debit or iDEAL per market, and while EU regulated entities are evidenced, we found no public information on where data is processed, on subprocessors or on a data processing agreement, with headquarters stated as Montreal. Licence and account terms span 4-6 — the e-commerce lead's 4 weighs bad-day terms, with no public information on chargeback fees or safeguarding of merchant funds, against the licence disclosure others credit. Settlement and reconciliation spans 5-6, and no rate or fee appears on the public pages.
Speaks for it
- Checkout and SCA documentation enumerates fifteen 3-D Secure challenge-preference reasons, with per-transaction exemption control, soft-decline resubmission and a stated liability shift.
- Recurring billing is a documented product, with plan and subscription management via control panel and REST API, free trials, card updater and three retries at 72-hour intervals.
- Licence disclosure names regulated entities in Cyprus, Lithuania, the Netherlands and the UK with supervisors and register numbers, plus PCI DSS Level 1 held since 2007.
- The Settlement Summary Report drills from payout ID to movement details, filters by acquirer bank and settlement currency, and exports to Excel or CSV with scheduling by email or SFTP.
Held against it
- Payment method coverage is a 720+ figure beside a short named list, with no public information naming SEPA Direct Debit, iDEAL or Bancontact per market.
- Sovereignty disclosure stops at the licence layer, with no public information on where payment data is processed, on subprocessors or on a data processing agreement, and headquarters stated as Montreal.
- We found no public information on safeguarding of merchant funds, reserve limits and release timelines, chargeback fees, or freeze and termination terms.
- No payout cadence is stated — scheduling defers to the merchant settlement agreement — and we found no public information on per-transaction fee itemisation, API idempotency, a test mode or a public status page.
Best for
- You run card-first checkout in Europe and need documented 3-D Secure exemption control with liability shift to the issuer.
- You bill subscriptions on cards or the named recurring wallets (Google Pay, Apple Pay, PayPal) and want retries, card updater and plan management in one product.
- Your procurement requires named, register-numbered EU regulated entities and long-held PCI DSS Level 1 certification.
Avoid if
- You sell into European markets and need local methods such as iDEAL or SEPA Direct Debit named per country before you can plan a rollout.
- Your compliance review requires published data-residency and subprocessor terms before contracting.
- Your finance close depends on a stated payout cadence and itemised per-transaction fees from the provider.
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 2 of 5 |
| Checkout, SCA & fraud | 3.5 of 5 |
| Subscriptions & recurring payments | 3.5 of 5 |
| Settlement, reconciliation & API | 2.5 of 5 |
| Licence, risk & account terms | 3 of 5 |
| European sovereignty | 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
Marketing claims 720+ methods across 200 markets with local acquiring in 50, but the named list is short — PayPal, Apple Pay, Klarna, WeChat, Skrill and crypto — with cards, bank transfers and BNPL described only as categories. I found no SEPA Direct Debit named and no country-by-country breakdown, so I cannot plan a per-market rollout from what is published. 3 11 6
The E-Commerce Lead
The pages count 720+ payment methods but the ones actually named are PayPal, Apple Pay, Google Pay, Klarna, WeChat, Skrill and crypto, alongside cards through principal membership of Mastercard and Visa. For my EU markets I found no public information naming iDEAL, Bancontact, BLIK, Przelewy24, EPS, Wero or SEPA Direct Debit per country, and no per-method refund or recurring flags beyond Google Pay, Apple Pay and PayPal. Cards and wallets are clearly named and Klarna appears by name, which puts this partway between basics and real named-per-market coverage. 1 2 3 6 11
The SaaS Founder
Cards and wallets including Apple Pay, Google Pay and PayPal are named, alongside Klarna, WeChat and Skrill inside a claimed 720+ methods across 200 markets and 150 currencies. We found no public information on SEPA Direct Debit or country-level European methods such as iDEAL or Bancontact, so the breadth is a headline count rather than a named list per market I can plan a subscription launch against. 1 3 6 11
The Payments Engineer
Cards, wallets and a European BNPL are named by brand — PayPal, Apple Pay, Klarna, Skrill, plus UnionPay and Amex connections — against headline counts of 720+ methods across 200 markets and 150 currencies. The local methods that decide conversion per European country go unnamed: we found no public information naming SEPA Direct Debit, iDEAL, Bancontact, EPS, BLIK or Wero, and no per-country list with refund or recurring support. Counts without names are nothing I can plan an integration against. 3 11 2
The Compliance Officer
Cards are well evidenced — principal membership of Mastercard and Visa for settlement in Europe, Amex and UnionPay connections, and named wallets including Apple Pay, Google Pay and PayPal, with Klarna the one European local method named. The pages count 720-plus methods across more than 200 markets, but we found no public information naming SEPA Direct Debit, iDEAL, Bancontact or EPS, or stating the countries and currencies each method serves, so a European merchant cannot plan per market from what is captured. 2 3 6 11
The Skeptic
The named list stops at PayPal, Apple Pay, Klarna, WeChat, Skrill and crypto alongside the card schemes, with recurring support named only for Google Pay, Apple Pay and PayPal; the "720+ payment methods, 150 currencies, 50 local acquiring markets" figures are counts, not a list a merchant can plan a market entry on. We found no public information on SEPA Direct Debit or per-country local methods such as iDEAL, Bancontact, EPS or BLIK. That sits above a cards-and-wallets processor and below the per-country coverage a European merchant needs. 3 6 11 2
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 3-D Secure documentation is genuinely deep: low-value, transaction-risk-analysis and merchant-initiated exemptions are enumerated with reason codes, soft-decline resubmission is documented, liability shift to the issuer is explained, and both a hosted Payment Page and Web SDKs are offered, with card updater features in the rebilling service. What I did not find is the PCI scope stated per integration type or authorisation-rate reporting by method and issuer country. 4 5 6 1
The E-Commerce Lead
3-D Secure handling is genuinely engineered for conversion: challenge-versus-exemption is documented for low-value, transaction-risk-analysis, merchant-initiated, recurring and wallet-delegated payments, I can request an exemption or insist on a challenge by preference, soft declines are resubmitted automatically with a challenge request, and the liability shift is explained. Both the hosted payment page and the web SDKs run 3-D Secure end to end, on top of PCI DSS Level 1 held since 2007. We found no public information on fraud rules or risk scores exposed to the merchant, authorisation-rate reporting by method and issuer country, or the PCI scope of each integration type. 4 5 1 2
The SaaS Founder
Hosted Payment Page and Web SDKs run 3DS2 end to end, the exemption catalogue is genuinely detailed — low value, transaction risk analysis, merchant-initiated and recurring exemptions with challenge-preference control — and liability shift and soft-decline re-submission are both explained. We found no public information on PCI scope per integration type, fraud rules exposed to the merchant, or authorisation-rate reporting by method and issuer country. 1 4 5
The Payments Engineer
The 3DS documentation is the real thing: hosted Payment Page and Web SDK checkout options, 3DS2 with exemptions driven by acquirer decision and merchant preference — low value, transaction risk analysis, merchant-initiated, delegation and trusted beneficiaries all enumerated — plus 3RI, soft-decline resubmission and an explicit liability-shift statement. Missing for my purposes is the PCI DSS scope stated per integration type, since the Level 1 badge is the company's certification rather than my SAQ level, and any authorisation-rate reporting by method or issuer country. That lands it just under the top band. 4 5 2 1
The Compliance Officer
The exemption machinery is documented in depth: Nuvei as acquirer requests or declines 3-D Secure challenges with fifteen named preference reasons including low-value, transaction risk analysis and merchant-initiated transactions, and PSD2 SCA exemption handling, issuer liability shift after successful authentication, and automated soft-decline resubmission are all described. A hosted payment page and Web SDKs, scheme card-updater features and continuously learning fraud models are stated, but we found no public information on the PCI DSS scope of each integration type or on fraud rules and risk scores exposed to the merchant. 1 4 5 6
The Skeptic
The 3-D Secure documentation is unusually deep: challenge versus exemption decided per transaction type, low-value and transaction-risk-analysis exemptions with a fifteen-entry reason table, soft-decline resubmission with a challenge, liability shift stated in plain words, and 3RI for merchant-initiated payments, over hosted payment page and Web SDK checkout options. We found no public information on fraud rules or risk scores exposed to the merchant or the PCI DSS scope of each integration type, which keeps it off the top anchors. 4 5 2
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
The Rebilling Service is a real product: stored payment methods as user payment options, merchant-initiated transactions without CVV, free trials, plan and subscription management through the control panel and REST API, automatic retries 72 hours apart with cancellation after the third failure, and card updater features. Missing for my taste: SEPA mandate handling with pre-notification, proration, dunning beyond the retry cycle, and any documented process for exporting payment tokens to another provider. 6 7
The E-Commerce Lead
Rebilling is a real product: stored payment methods in user payment option records, automatic subsequent charges without CVV, a defined retry schedule of three attempts at 72-hour intervals, card updater, free trial periods, setup fees, end dates, and create, edit and cancel through both the control panel and the REST API, with signed notifications on every subscription event. Recurring charges are also documented for Google Pay, Apple Pay and PayPal. We found no public information on proration, customer dunning, SEPA mandate management, or a process for exporting payment tokens to another provider. 6 7 5
The SaaS Founder
The rebilling engine is real: stored payment methods, merchant-initiated transactions, automated subsequent charges, free trials, plan and subscription editing by API and control panel, card updater, and a retry ladder documented at three retries every 72 hours before the subscription goes inactive. For a business like mine the missing parts decide it — we found no public information on SEPA mandate management with pre-notification, proration, dunning beyond the fixed retry schedule, or any documented process for exporting stored payment tokens to another provider. 6 7
The Payments Engineer
Rebilling is a first-class product: payment methods stored as user payment options, merchant-initiated server-to-server charges, plan and subscription lifecycle through REST methods and the Control Panel, free trials, setup fees, card account updater, failed-payment notifications with checksums, and three retries at 72-hour intervals before the subscription goes inactive. We found no public information on SEPA mandate management, proration, dunning beyond the retry schedule, or exporting stored tokens to another provider — the exit question I ask every vendor. 6 7
The Compliance Officer
The rebilling service stores customer payment methods as user payment options, automates subsequent merchant-initiated charges without requiring CVV2, includes scheme card-updater features, free trial periods, plan and subscription editing through the control panel and REST API, and a documented retry schedule of three attempts at 72-hour intervals before the subscription turns inactive. We found no public information on SEPA Direct Debit mandate management or pre-notification, dunning, proration, or a documented process for exporting payment tokens to another provider. 5 6 7
The Skeptic
Subscriptions are a real product: plan templates with free trial periods, create/edit/delete from the control panel or REST API, a retry mechanism on a fixed 72-hour schedule with cancellation after the final failure, scheme card-updater, and server-to-server recurring on Google Pay, Apple Pay and PayPal. We found no public information on SEPA mandate management, dunning, or a documented process for exporting stored payment tokens to another provider. 6 7 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 — 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 Settlement Summary Report drills from a Payout ID down to movement details with CSV/Excel export, filters by acquirer bank and settlement currency, scheduled delivery by email or SFTP, and there is a documented REST API with signed notifications. But no payout cadence is stated anywhere — the documentation defers to the merchant settlement agreement as defined by the Finance Team — fees are not shown itemised per transaction, and reports stop at 14 months back, so I could not close the month from this data alone. 8 9 10 6
The E-Commerce Lead
The settlement summary report filters by acquirer bank and settlement currency, drills from a payout ID into its movement details, exports to Excel or CSV, schedules delivery by email or SFTP, and reaches back 14 months, with downloadable sample reports and an API reference with checksummed notification callbacks. No payout cadence is stated on these pages, and we found no public information on per-transaction fee itemisation. We also found no public information on accounting integrations, API idempotency, rate limits or a status page. 8 9 10 11 6
The SaaS Founder
The Settlement Summary Report drills from payout ID to individual movements, exports to Excel or CSV, schedules via email or SFTP and runs 14 months back, with a reserve-balance report showing capture and release, plus full API reference documentation and signed notification callbacks with SHA-256 checksums. We found no public information on payout cadence, per-transaction fee itemisation, a test mode, or API versioning and idempotency. 6 8 9 10 11
The Payments Engineer
The Settlement Summary Report links payouts to their underlying movements, filters by acquirer bank and settlement currency, exports to Excel or CSV, schedules delivery by email or SFTP and reaches back fourteen months, with checksummed notifications and documented REST methods alongside it. The engineering plumbing I get paged on is absent from the captured pages: no API versioning or idempotency keys, no test mode, no published rate limits, no public status page, and neither a payout cadence nor fee itemisation per transaction stated. 8 9 10 3 6
The Compliance Officer
The Settlement Summary Report filters by acquirer bank and settlement currency, drills from payout IDs into movement details, exports to Excel and CSV, and can be scheduled by email or SFTP, with financial reports available up to 14 months back; a documented REST API and merchant notifications with SHA-256 checksums support finance processes. We found no public information on the payout cadence, a test mode, itemised fees per transaction, or accounting integrations. 1 6 8 9 10
The Skeptic
The Settlement Summary Report drills from payout ID down to settlements and movements, filters by acquirer bank and settlement currency, exports to Excel or CSV and can be scheduled by email or SFTP, with sample reports downloadable. But the payout schedule itself is left to "the merchant settlement agreement as defined by the Finance Team", and we found no public information on fee itemisation per transaction, API idempotency and rate limits, or a public status page. 8 9 10
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
This is the strong suit: three EU regulated entities named with supervisors and licence numbers (e-money institutions in Cyprus and Lithuania, a payment service provider in the Netherlands), plus FCA and FinCEN registrations and PCI DSS Level 1 held since 2007. There is even a Reserve Balance report with capture and release lines, but the reserve conditions, limits and release timelines are not published, and I found no safeguarding statement, chargeback fee, termination notice period or appeal route. 2 10 11
The E-Commerce Lead
Licence disclosure is unusually complete: Electronic Money Institutions with the Central Bank of Cyprus and the Central Bank of Lithuania, a Dutch payment service provider under DNB, an FCA-authorised UK entity and a US FinCEN registration, each with register numbers, plus PCI DSS Level 1 held since 2007 and a reserve balance report that surfaces reserve captures and releases. We found no public information on the chargeback fee, safeguarding of merchant funds, notice periods for termination, or reserve limits and release timelines. 2 10 1 11
The SaaS Founder
Licence disclosure is unusually thorough: EU electronic money and payment institutions in Cyprus, Lithuania and the Netherlands with supervisors and register numbers, UK FCA authorisation, US money-transmitter registration across 39 jurisdictions, MiCAR passporting, and PCI DSS Level 1 held since 2007. The bad-day terms are what I could not find — we found no public information on safeguarding of merchant funds, reserve limits and release timelines, termination notice and appeal routes, or a published chargeback fee. 1 2 10 11
The Payments Engineer
The licences page names every regulated entity with supervisor, licence type and register number — Cyprus and Lithuania electronic money institutions, a Dutch payment service provider, a UK FCA-registered firm, a US money services business and five ISO partner banks — plus PCI DSS Level 1 held since 2007 and a MiCAR licence passported across the EU. The bad-day text is what the pages do not show: we found no public information on safeguarding of merchant funds, a dispute process or chargeback fees, reserve conditions with limits and release timelines, or freeze, termination and appeal terms beyond a report exposing reserve capture and release fields. 2 11 10 1
The Compliance Officer
The regulated entities are named with supervisors and register numbers — Cyprus, Lithuania, Netherlands and UK licences, US FinCEN registration, PCI DSS Level 1 since 2007, and MiCAR authorisation passported across EU member states — which is more disclosure than most providers publish. The bad-day terms are thinner: a reserve balance report with capture and release fields and a rule that no payout is made on a negative daily balance exist, but we found no public information on safeguarding of merchant funds, chargeback fees, reserve limits with release timelines, or freeze and termination terms with a route to appeal. 1 2 10 11
The Skeptic
Credit where due: the licences page names five regulated entities with supervisors and register numbers — electronic money institutions in Cyprus and Lithuania, a Dutch payment service provider, an FCA-authorised UK firm — plus PCI DSS Level 1 since 2007 and MiCAR passporting. The bad day is the gap: a reserve report with capture and release fields proves reserves exist, but we found no public information on reserve limits or release timelines, safeguarding of merchant funds, chargeback fees, or freeze and termination terms. 2 11 10 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 — 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
The licences page proves EU regulated entities with register numbers, and the MiCAR announcement states EU passporting of the crypto licence, with European principal membership of Mastercard and Visa. Nothing on the captured pages states where payment or cardholder data is processed, no subprocessor list is published, no data processing agreement is evidenced, and headquarters is stated as Montreal. 2 11
The E-Commerce Lead
The captured pages prove European regulated entities in Cyprus, Lithuania and the Netherlands with licence and register numbers, EU-wide passporting under the MiCAR licence, and principal membership of Mastercard and Visa for European settlement. We found no public information on where transaction and cardholder data are processed or stored, on subprocessor locations, or on a data processing agreement. European entities and licences are evidenced; the data-residency side stays unknown. 2 11
The SaaS Founder
Nuvei holds EU licences through named entities in Cyprus, Lithuania and the Netherlands and received EU MiCAR authorisation with passporting across member states, which is more than most non-EU processors can show. But the press dateline places headquarters in Montreal, and we found no public information on where payment and cardholder data are processed, subprocessor locations, or a data processing agreement. 2 11
The Payments Engineer
European regulated entities are named and real: electronic money institutions in Cyprus and Lithuania, a payment service provider in the Netherlands under DNB, Visa and Mastercard principal membership for Europe, and an EU MiCAR authorisation with passporting. No captured page states where payment or cardholder data is processed or stored, publishes a subprocessor list, or offers a data processing agreement, and the headquarters are in Montreal. EU entity proven, data residency not. 2 11
The Compliance Officer
European regulated entities are proven — Electronic Money Institution licences in Cyprus and Lithuania and a Dutch payment service provider licence, each with a register number — so the entity layer is European. But we found no public information on where transaction and cardholder data are processed or stored, on subprocessors and their locations, or on a data processing agreement distinguishing where Nuvei acts as processor versus controller, so the data layer is unproven rather than European. 2 11
The Skeptic
EU-regulated entities are properly documented — electronic money institutions licensed by the Central Bank of Cyprus and the Central Bank of Lithuania, and a Dutch payment service provider — which is more licence substance than most processors publish. Everything below the licence is dark: we found no public information on where payment and cardholder data is processed, no subprocessor list, no data processing agreement, and the group's headquarters is Montreal. 2 11
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 not rated — no public information
We found no public information on pricing: none of the captured pages, including the homepage and the payment methods page, carries a rate, fee, plan price or monthly minimum. A merchant cannot begin to compute an effective rate from what we captured. 1 3 11
The E-Commerce Lead not rated — no public information
We found no public information on pricing in anything we read — no card rate, per-method rate, monthly fee, chargeback fee or conversion markup appears on the homepage, the payment-methods pages or the announcements we captured. Computing an effective fee for my card and country mix from public pages alone is not possible; every rate would come from a sales conversation. 1 3 11
The SaaS Founder not rated — no public information
We found no public information on pricing — no headline rate, monthly or plan fee, chargeback or payout fee, or a blended versus interchange-plus model appears on the captured homepage, payment-methods page, documentation pages or licence pages I read. 1 2 3 8
The Payments Engineer not rated — no public information
We found no public information on pricing: no headline or per-method rate, monthly or plan fee, chargeback, refund, payout or currency conversion fee appears on any page we read, so a merchant cannot begin to compute an effective rate from public pages alone. 1 3 11
The Compliance Officer not rated — no public information
We found no public information on pricing transparency in the captured pages — no transaction rates, monthly or plan fees, currency conversion markups, or chargeback, refund and payout charges appear on the homepage, offers page or legal notice. 1 2 3
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 Nuvei
Is Nuvei European?
Not determined: the vendor’s pages as captured do not say where Nuvei is based.
Where does Nuvei store data?
Not stated on the vendor’s pages as of 3 Nov 2026.
Does Nuvei have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to Nuvei?
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: Nuvei 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 found no public information on pricing on the pages we read (nuvei.com, nuvei.com/legal/licences-and-certifications, nuvei.com/offers/global-payment-methods, docs.nuvei.com/documentation/features/3d-secure/3ds-implementations/challenges-and-exemptions, docs.nuvei.com/documentation/features/3d-secure, docs.nuvei.com/documentation/features/subscription-rebilling and 5 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 6 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
- 3 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 (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page nuvei.com Checked 3 Nov 2026 Details →
- 2 Legal notice — found from the homepage www.nuvei.com Checked 3 Nov 2026 Details →
- 3 Payment methods & local coverage — found from sitemap www.nuvei.com Checked 3 Nov 2026 Details →
- 4 Checkout, SCA & fraud — found from sitemap docs.nuvei.com Checked 3 Nov 2026 Details →
- 5 Checkout, SCA & fraud — found from sitemap docs.nuvei.com Checked 3 Nov 2026 Details →
- 6 Subscriptions & recurring payments — found from sitemap docs.nuvei.com Checked 3 Nov 2026 Details →
- 7 Subscriptions & recurring payments — found from sitemap docs.nuvei.com Checked 3 Nov 2026 Details →
- 8 Settlement, reconciliation & API — found from sitemap docs.nuvei.com Checked 3 Nov 2026 Details →
- 9 Settlement, reconciliation & API — found from sitemap docs.nuvei.com Checked 3 Nov 2026 Details →
- 10 Licence, risk & account terms — found from sitemap docs.nuvei.com Checked 3 Nov 2026 Details →
- 11 Licence, risk & account terms — found from sitemap www.nuvei.com Checked 3 Nov 2026 Details →