Mangopay
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by MangoPay SAS · www.mangopay.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.
Mangopay at a glance
- Vendor
- MangoPay SAS
- Headquarters
- Incorporated in Luxembourg source, captured 11 Nov 2026
- Data hosting
- In the EU by default; pages mention Ireland and Germany source, captured 11 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 11 Nov 2026
- Panel verdict
- The AI panel rates Mangopay 3/5, the mean of 6 judges. Mangopay is a payment provider for platforms, contracted through Mangopay S.A., a Luxembourg société anonyme and CSSF-licensed electronic money institution, register B173459. how scores are made
- As of
- Vendor pages captured 11 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Mangopay is a payment provider for platforms, contracted through Mangopay S.A., a Luxembourg société anonyme and CSSF-licensed electronic money institution, register B173459. Checkout and SCA scored highest, clustered at 7, with the low-value exemption under €30, its five-transaction and €100 cumulative caps written down, and 3-D Secure handled by the Checkout SDK. Payment methods scored 6-7: twenty-three methods named by region, but per-method currency, refund and recurring detail documented for Bancontact only. Recurring billing and settlement and reconciliation scored 5-6 — a documented card-on-file model and a real reporting layer, but we found no public information on payout schedule or settlement currencies. Licence and account terms and sovereignty sit at 4-5 — we found no public information on safeguarding of merchant funds, chargeback fees, reserves, termination terms, subprocessor locations or a data processing agreement — while personal data is stated to be stored on cloud servers in Ireland (Dublin) and Germany (Frankfurt) and the privacy statement acknowledges occasional transfers outside the EU/EEA. Ranges were narrow; no material disagreements were flagged; the pricing page reads 'Pricing Documentation Contact sales', with no rate stated.
Speaks for it
- SCA written down in depth — the low-value exemption under €30 with its five-transaction and €100 cumulative caps, plus low-risk exemption fraud-rate bands by amount
- Twenty-three payment methods listed by name with regions, from Bancontact for Belgium and BLIK for Poland to TWINT for Switzerland and SEPA Direct Debit for the eurozone
- Recurring card payments fully modelled — a first charge authenticated within 24 hours of card registration, merchant-initiated follow-ups without SCA, free initial cycles and custom schedules with no fixed amount or end date
- The regulated entity is on the record — Mangopay S.A., a Luxembourg société anonyme approved as an electronic money institution by the CSSF, register number B173459
- Reports available via API or Dashboard with CSV export and daily-to-quarterly scheduling, plus the Echo flow matching incoming partner-PSP funds against declared intents
Held against it
- Per-method currency, refund and recurring detail is documented for Bancontact only, and payment methods require contract amendments and activation in all cases
- We found no public information on safeguarding of merchant funds, chargeback fees, reserve or rolling-hold conditions, or freeze and termination terms
- Recurring is documented only for registered CB, Visa, Mastercard and Amex cards, capped at 99 pay-ins per registration before the 100th fails with error 205001, with no public information on SEPA mandate recurring, dunning or smart retries
- We found no public information on payout schedule, settlement currencies, interchange or scheme fee itemisation, or a public status page
- We found no public information on subprocessor locations or a data processing agreement, while the privacy statement acknowledges occasional transfers of personal data outside the EU/EEA
Best for
- You run an EU platform or marketplace that needs local methods by market — Bancontact, BLIK, Bizum, TWINT, Swish — on a CSSF-licensed Luxembourg entity
- You sell card-based subscriptions and need engineered SCA: an authenticated first charge, merchant-initiated charges without SCA, and free initial cycles via FreeCycles
- Your finance team needs schedulable reports with CSV export plus a reconciliation flow that matches incoming partner-PSP funds against declared transactions
Avoid if
- You need to see rates before talking to sales — the public pricing page shows only 'Pricing Documentation Contact sales'.
- Your recurring billing runs on SEPA Direct Debit mandates — recurring is documented as available only for registered CB, Visa, Mastercard and Amex cards, capped at 99 pay-ins per registration.
- You plan market by market from documentation alone — the per-method currency, refund and recurring matrix is documented for Bancontact only, and methods require contract amendments and activation before they work.
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 3.5 of 5 |
| Checkout, SCA & fraud | 3.5 of 5 |
| Subscriptions & recurring payments | 3 of 5 |
| Settlement, reconciliation & API | 3 of 5 |
| Licence, risk & account terms | 2 of 5 |
| European sovereignty | 2.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 — 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
The documented method list is genuinely broad — cards, Apple Pay and Google Pay, SEPA Direct Debit, and local methods named per market including Bancontact for Belgium, BLIK for Poland, Bizum for Spain, TWINT for Switzerland and Swish for Sweden — but only Bancontact carries the detail I would plan against, with its currency, 180-day refund window and recurring support stated; the rest are listed with a region label and little else. 4 5 6
The E-Commerce Lead
The per-market list is named, not just counted: Bancontact for Belgium, Bizum for Spain, BLIK for Poland, CB for France, Swish for Sweden, TWINT for Switzerland, SEPA Direct Debit for the eurozone, plus iDEAL | Wero, with cards and wallets behind them — but the currencies, refund window and recurring support I plan against are documented only for Bancontact (EUR, refunds within 180 days, recurring planned), and settlement currencies per method are not stated. Good enough to plan most of my markets, short of a per-method matrix. 4 5 6
The SaaS Founder
The payment-methods page names a long list with regions per method — SEPA Direct Debit for the Eurozone, BLIK for Poland, TWINT for Switzerland, Bizum for Spain, CB for France, Swish for Sweden, Bancontact for Belgium, iDEAL|Wero — so my SEPA and local-method needs are on the map. But only Bancontact gets the full treatment, with currency, refunds within 180 days and recurring support documented; currencies and refund or recurring support per method for the rest are not stated on the captured pages. 4 5
The Payments Engineer
A named method list with region per method — Bancontact for Belgium, BLIK for Poland, Bizum for Spain, TWINT for Switzerland, Swish for Sweden, CB for France, SEPA Direct Debit for the eurozone, iDEAL | Wero, Klarna, PayPal, plus cards and wallets — and the Bancontact page goes as far as currencies, a 180-day refund window and recurring status. The per-method refund and recurring matrix is documented for one method only, and settlement currencies are not stated anywhere I read, so a merchant still cannot plan against it market by market. 4 5 6
The Compliance Officer
The payment methods documentation names over twenty methods with their regions — cards, Apple Pay and Google Pay, SEPA Direct Debit, and local methods including iDEAL/Wero, BLIK, TWINT, Bizum, Swish, Multibanco and MB WAY — and the Bancontact guide goes further, documenting currency, refunds within 180 days, disputes and recurring support for that one method. We found no public information on currencies, refund or recurring support for the remaining methods, or on settlement currencies, so a merchant cannot yet plan per market from these pages alone. 4 5
The Skeptic
Twenty-three methods are listed by name with their regions — Bancontact, BLIK, TWINT, Bizum, Swish, MB WAY, Multibanco, iDEAL with Wero, SEPA Direct Debit — so the European coverage is real, not a logo wall. But the per-method detail stops at Bancontact: refunds within 180 days, disputes supported, recurring marked only as planned, EUR only; we found no public information on currencies, refund or recurring support for the other methods. Every method also requires a contract amendment and activation before it works, which a merchant planning per country cannot price or schedule against. 4 5 6
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 checkout SDK embeds a customizable payment page with integrated 3-D Secure 2 handled by the provider, and the exemption machinery is properly written down — a low-value exemption under €30 with consecutive and cumulative limits, low-risk exemption fraud-rate bands, frictionless versus challenge flows, and liability shift to the issuer when SCA applies, with MOTO liability explicitly left with the platform. We found no public information on merchant-facing fraud rules or risk scores, per-integration PCI scope, or an account updater. 6 7 8
The E-Commerce Lead
The Checkout SDK powers the payment page of my own website or app with integrated 3-D Secure and customisable design, and the SCA detail is exactly what I sell on: challenge versus frictionless flow, the low-value exemption under €30 with the five-transaction and €100 cumulative caps, low-risk exemption rates by amount band, a Maximum Frictionless Amount, and the issuer making the final decision — plus liability shift with SCA and platform liability for MOTO. We found no public information on PCI DSS scope per integration type, merchant-facing risk scores, network tokens or account updater, or authorisation-rate reporting. 6 7 8
The SaaS Founder
Authentication is genuinely engineered: challenge and frictionless flows, low-value exemptions under €30 with cumulative caps, low-risk exemption rates, issuer final say, and liability shift explained for both SCA and MOTO. The Checkout SDK is an embedded, customizable payment page with integrated 3DS and PCI-DSS-compliant tokenization. We found no public information on fraud rules or risk scores exposed to the merchant, an account updater, or a hosted checkout option, which keeps it below the top of the scale. 6 7
The Payments Engineer
3-D Secure 2 is handled by the provider with challenge and frictionless flows, the low-value exemption thresholds and low-risk fraud-rate exemptions are written down, no exemption is possible on a recurring customer-initiated payment, and liability shift is explained — including MOTO liability staying with the platform. The Checkout SDK is embeddable and customisable with PCI-DSS-compliant tokenisation claimed. What I did not find: the PCI scope of each integration type, fraud rules or risk scores exposed to the merchant, an account updater, or authorisation-rate reporting. 6 7 8
The Compliance Officer
The Checkout SDK powers a customisable payment page with integrated 3DS handling and PCI DSS-compliant tokenization, and the 3DS guide documents SCA in real depth: challenge and frictionless flows, low-value exemption thresholds and issuer fraud-rate criteria, exemptions capped at once per transaction, and liability shift to the issuer with SCA while MOTO chargeback liability stays with the platform. We found no public information on fraud rules or risk scores exposed to the merchant, account updater or network tokens, or the PCI DSS scope of each integration type. 6 7
The Skeptic
The exemptions are actually written down — the low-value rule under €30 with its five-transaction and €100 cumulative caps, low-risk exemption fraud rates by amount band, once per transaction, and MOTO liability resting squarely with the platform — and the Checkout SDK handles 3DS with configurable SecureMode and a platform-set Maximum Frictionless Amount. We found no public information on PCI DSS scope per integration type, network tokens or account updater, or authorisation-rate reporting, which is what separates a documented flow from an engineered one. 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
Card-on-file recurring is engineered properly: a registration object, a customer-initiated first charge under SCA within 24 hours of card registration, merchant-initiated charges without SCA afterwards, custom schedules with no fixed amount or end date, and a FreeCycles parameter that passes the initial cycles at zero — my trial mechanism. The documentation covers cards only; we found no public information on SEPA mandate management for recurring charges, dunning or smart retries, a card account updater, or exporting the stored credentials to another provider. 8 9 5
The E-Commerce Lead
Recurring is properly modelled on cards: a cardholder-authenticated first charge within 24 hours of registration, merchant-initiated follow-ups without SCA, up to 99 charges per registration, free initial cycles via FreeCycles, custom schedules with no fixed amount or end date, and failed-payment hooks on the Bancontact flow. We found no public information on dunning or smart retries, a card account updater, SEPA mandate management, or taking stored credentials to another provider. 8 9 5
The SaaS Founder
Recurring card payments are properly built: an initial customer-initiated payment with mandatory SCA within 24 hours of card registration, subsequent merchant-initiated payments without SCA, custom recurring with no fixed amount or end date, and a FreeCycles parameter that runs initial cycles at zero — trial behaviour I can actually use. It is cards only (CB, Visa, Mastercard, AMEX) with a maximum of 99 pay-ins per registration, and we found no public information on SEPA mandates for recurring charges, dunning, smart retries, proration, or a documented process for exporting payment tokens to another provider. 9 8 5
The Payments Engineer
Recurring is card-based and properly engineered on paper: a registration object, a first customer-initiated payment with SCA within 24 hours of card registration, merchant-initiated payments without SCA, a documented cap of 99 pay-ins per registration with the restart flow, free initial cycles, and no fixed amount or end date. Recurring is limited to registered cards on CB, Visa, Mastercard and AMEX; SEPA mandates for recurring charges, dunning and smart retries, an account updater, and any process for exporting tokens to another provider are not in the pages I read. 5 8 9
The Compliance Officer
Recurring card payments are documented as a proper CIT/MIT architecture: the first charge authenticated by 3DS within 24 hours of card registration, subsequent charges without the cardholder present and outside SCA, free initial cycles for trials, and custom schedules with no fixed amount or end date, capped at 99 charges per registration. We found no public information on SEPA Direct Debit mandate management, smart retries or dunning, card account updater, or a process for exporting payment tokens to another provider. 8 9 5
The Skeptic
Recurring card payments are properly modelled — a first customer-initiated payment under mandatory SCA within 24 hours of card registration, then merchant-initiated payments with no SCA, FreeCycles for initial zero-value cycles, custom schedules with no fixed amount or end date, and a re-authentication trigger when the card changes. The cap is 99 pay-ins per registration before the 100th fails with error 205001 and a fresh customer authentication is needed, and recurring is limited to registered CB, Visa, Mastercard and Amex cards; we found no public information on SEPA mandate recurring, dunning, smart retries, account updater or a process for exporting payment tokens. 8 9
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
Reporting is the strong suit: eight report types covering wallets, collected fees, splits and settlements, schedulable daily through quarterly, exportable as CSV and available via API, plus the Echo product which matches incoming funds line-by-line against declared transactions and tracks them through matched, partially matched and unmatched states. As the one who closes the month, I note we found no public information on payout cadence, settlement currencies, or itemisation of interchange and scheme fees per transaction. 10 11 5
The E-Commerce Lead
Reports run via API and Dashboard with CSV export and daily-to-quarterly scheduling — wallets, user wallet transactions including chargeback repudiations, splits, and a collected-fees report — and the Echo reconciliation flow matches incoming partner-PSP funds against declared transactions through matched, partially matched, unmatched and insufficient-funds states with validation-error endpoints, with webhooks on the payment flows. We found no public information on payout schedules, settlement currencies, accounting integrations, idempotency and rate limits, or a public status page. 10 11 5
The SaaS Founder
Reporting is real: eight report types available via API and Dashboard, scheduling from daily to quarterly, CSV export, a collected-fees report itemising Fees Wallet movements, and the Echo flow that matches incoming funds on a dedicated virtual account to declared intents with explicit partially-matched and unmatched statuses. Webhook events for pay-in success and failure are documented. We found no public information on payout schedules, settlement currencies, idempotency, rate limits, or accounting integrations. 10 11 5
The Payments Engineer
The reporting layer is real finance tooling: reports by API or dashboard, scheduled daily to quarterly, CSV export, a collected-fees report, wallet transaction reports, and the Echo reconciliation product that matches an uploaded settlement file against declared intents and tracks matched, partially matched and unmatched states with retries on insufficient funds. What I did not find: a stated payout schedule or settlement currencies, a test mode, idempotency keys or published rate limits, or a public status page — semantic versioning is claimed for the Checkout SDK package only. 5 6 10 11
The Compliance Officer
Nine report types — wallet transactions, collected fees, settlements, intents and splits among them — are available via API or Dashboard with CSV export, daily-to-quarterly scheduling and access control, and the Echo reconciliation flow matches partner-PSP funds received into a dedicated virtual account against declared intents, with matched, partially matched and unmatched states plus error-monitoring endpoints. We found no public information on payout cadence and settlement currencies, accounting integrations, idempotency and published rate limits, or a public status page. 10 11 5
The Skeptic
The reporting side is real: eight named reports including collected fees, splits and settlements, schedulable daily to quarterly, CSV export, via API or Dashboard with hook notifications, plus the Echo reconciliation product that matches funds arriving on a dedicated virtual account to declared intents through matched, partially matched, unmatched and insufficient-funds states. What we found no public information on is the money itself: payout schedule, settlement currencies, interchange or scheme fee itemisation, API idempotency and rate limits, or a public status page. 5 10 11
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
The entity is properly on the record — Mangopay S.A., a Luxembourg public limited company approved as an electronic money institution by the CSSF and registered in the Luxembourg Trade and Company Register under B173459, with a UK sister entity and its ICO registration also named. The bad-day terms are what I could not find: no published chargeback fee, no safeguarding statement, and we found no public information on reserve or rolling-hold conditions, freeze and termination terms, or appeal routes. 2 3 5
The E-Commerce Lead
The paper trail on who holds the money is solid: Mangopay S.A., a Luxembourg société anonyme, approved as an electronic money institution by the CSSF, registered B173459 with VAT LU25939145, PSD2 referenced and a complaint route to the CNPD; disputes are marked available for Bancontact, chargeback repudiations surface in the wallet-transaction report, and MOTO chargeback liability is explicitly on the platform. We found no public information on the chargeback fee, safeguarding of merchant funds, reserve or rolling-hold conditions, or freeze, termination and appeal terms. 2 3 5 10
The SaaS Founder
The entity is properly named: Mangopay S.A., a Luxembourg public limited company, register number B173459, approved as an electronic money institution by the CSSF, with share capital and VAT number published. Beyond that the terms are thin — we found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions, freeze and termination terms, or chargeback fees. On a bad day I do not know what this contract lets them do with my funds. 2 3
The Payments Engineer
The regulated entity is properly named: Mangopay S.A., a Luxembourg public limited company, register number B173459 on the Luxembourg Trade and Company Register, approved as an electronic money institution by the CSSF, with a UK entity registered with the ICO and a documented right to complain to the CNPD. The captured terms publish no safeguarding statement, no chargeback fee, and no reserve, freeze, termination or appeal conditions — the bad-day rules are not written down anywhere I read. 2 3 5
The Compliance Officer
The legal notice does what I demand of any provider: Mangopay S.A. is named as a Luxembourg société anonyme with its supervisor (the CSSF), its licence type (electronic money institution), register number B173459, share capital of 27.201.000 euros and PSD2 reference, and the privacy statement adds an ICO registration and the right to complain to the CNPD. We found no public information on safeguarding of merchant funds, published chargeback fees, reserve or rolling-hold conditions, or freeze and termination terms with reasons, notice or appeal. 2 3
The Skeptic
The licence layer is properly published: Mangopay S.A., a Luxembourg société anonyme, register number B173459, approved as an Electronic money institution by the CSSF, with a UK entity and ICO registration named alongside. The bad-day terms are not: we found no public information on chargeback fees, safeguarding of merchant funds, reserve or rolling-hold conditions, or freeze and termination notice, and the dispute trail amounts to a single "Disputes Yes" on the Bancontact page. 2 3 5
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 contracting and regulated entity is Luxembourg — an electronic money institution under the CSSF — and personal data is stored on cloud servers in Ireland (Dublin) and Germany (Frankfurt), with the same section acknowledging occasional transfers outside the EEA under adequacy decisions or standard contractual clauses. Subprocessors such as Mastercard, Visa, American Express, Entrust and Trulioo are named in the privacy statement, but without locations, and we found no public information on a data processing agreement or named infrastructure. 2 3
The E-Commerce Lead
The contracting and regulated entity is European — Mangopay S.A. in Luxembourg, a CSSF-licensed e-money institution — with personal data stated to be stored on cloud servers in Ireland and Frankfurt and named processors such as American Express, Mastercard, Visa, Entrust and Trulioo bound by strict contractual obligations, while transfers outside the EEA are acknowledged and covered by adequacy decisions or standard contractual clauses. We found no public information on a data processing agreement, subprocessor locations, or hosting options, so this sits mid-table rather than sovereign end to end. 2 3
The SaaS Founder
Mangopay S.A. is a Luxembourg entity holding a CSSF e-money licence, and the privacy statement says personal data is stored on cloud servers in Ireland (Dublin) and Germany (Frankfurt), with subprocessors named — Mastercard, Visa, American Express, Entrust, Trulioo — though without locations. The same statement acknowledges transfers of personal data outside the EU/EEA under adequacy decisions or standard contractual clauses, and we found no public information on a data processing agreement for merchant data. 2 3
The Payments Engineer
The contracting and regulated entity is Luxembourg, licensed by the CSSF, and the privacy statement says personal data is stored on cloud servers in Ireland (Dublin) and Germany (Frankfurt), with subprocessors such as American Express, Mastercard, Visa, Entrust and Trulioo named and bound by strict contractual obligations. The same section acknowledges occasional transfers outside the EEA under adequacy decisions or standard contractual clauses, and I found no data processing agreement offered, no subprocessor locations, and no statement of which processing Mangopay does as processor versus controller. 2 3
The Compliance Officer
The contracting and regulated entity is Luxembourg-domiciled and CSSF-licensed, personal data is stored on cloud servers in Ireland (Dublin) and Germany (Frankfurt), and the privacy statement names subprocessors — Entrust and Trulioo for KYC, American Express as payment facilitator, Mastercard and Visa — though it also acknowledges occasional transfers outside the EEA under adequacy decisions or standard contractual clauses. We found no public information on a data processing agreement offered to merchants, the locations of those subprocessors, the infrastructure provider, or a processor-versus-controller breakdown beyond naming Mangopay S.A. and Mangopay UK Ltd as controllers. 2 3
The Skeptic
An EU contracting and regulated entity (Luxembourg, CSSF-licensed e-money institution) with personal data stored on cloud servers in Ireland and Frankfurt, subprocessors named — American Express, Mastercard, Visa, Entrust, Trulioo — and transfers outside the EEA covered by adequacy decisions or standard contractual clauses. It stays below the higher marks because subprocessor locations are not published, no data processing agreement is evidenced, occasional transfers outside the EU are acknowledged in the same breath as EU storage, and the vendor's own site is served by Netlify Inc. of San Francisco. 2 3
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
A pricing destination exists publicly but carries no rates at all — the captured text reads "Pricing Documentation Contact sales" — so a merchant cannot compute an effective fee for any mix of cards, countries or methods from public pages. Every rate is a sales conversation. 1
The E-Commerce Lead
The public pricing page shows only "Pricing Documentation Contact sales" — no rate for any method, card type or country appears on the pages we read, so I cannot compute an effective fee for my mix of cards, countries and methods and every rate is a sales conversation. 1
The SaaS Founder
The pricing page publishes nothing — the captured text is just "Pricing Documentation Contact sales" — so every rate is a sales conversation. As a subscription operator I cannot begin to compute my effective card fee, let alone cross-border or chargeback costs, from public pages. 1
The Payments Engineer
The captured pricing content reads "Pricing Documentation Contact sales" — no headline rate, no "from" percentage, no monthly fee, nothing a merchant can compute with. Every rate is a sales conversation, and a live demo link is not a price. 1
The Compliance Officer
The pricing page carries only the words 'Pricing', 'Documentation' and 'Contact sales', with prices explicitly not stated on the page and no rate published for any method or card type. We found no public information on currency conversion markups, chargeback, refund or payout fees, monthly minimums or contract terms; every rate is a sales conversation. 1
The Skeptic
A pricing page exists and reads "Pricing Documentation Contact sales" — no rates for any method, no monthly fee, and we found no public information on chargeback, currency conversion, refund or payout fees anywhere in the captured pages. Every rate is a sales conversation, so a merchant cannot compute an effective fee for their own card and country mix from public pages alone. 1
European sovereignty — proven facts
2 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 |
Incorporated in LU
unverified
Why unverified?The privacy statement also names Mangopay UK Ltd as a separate controller for UK-based partners, but the legal notice names Mangopay S.A. as the single publishing company and no parent company is mentioned. |
2/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?Storage is EU-based, but the same section acknowledges occasional transfers of personal data to companies outside the EU/EEA, so it is not strictly EU-only. |
2/4 pts | 3 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 Mangopay
Is Mangopay European?
Not determined: the vendor’s pages as captured do not say where Mangopay is based. Its vendor, MangoPay SAS, is incorporated in Luxembourg, per the vendor’s page captured 11 Nov 2026.
Where does Mangopay store data?
Mangopay stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 11 Nov 2026. The vendor’s pages mention Ireland and Germany as hosting locations, per the vendor’s page captured 11 Nov 2026.
Does Mangopay have a free plan?
Not stated on the vendor’s pages as of 11 Nov 2026.
What are the best alternatives to Mangopay?
As of 18 Nov 2026, the panel rates Novalnet (3.5/5), PayPal (3.5/5) and Mollie (3/5) highest among the other 45 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 Novalnet (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Mangopay alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 11 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. The privacy statement also names Mangopay UK Ltd as a separate controller for UK-based partners, but the legal notice names Mangopay S.A. as the single publishing company and no parent company is mentioned.
- Weak sourcing — Hosting location. Storage is EU-based, but the same section acknowledges occasional transfers of personal data to companies outside the EU/EEA, so it is not strictly EU-only.
- 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.
- 20 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 compliance 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 integrations 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 www.mangopay.com Checked 11 Nov 2026 Details →
- 2 Legal notice — found from the homepage mangopay.com Checked 11 Nov 2026 Details →
- 3 Privacy policy — found from the homepage mangopay.com Checked 11 Nov 2026 Details →
- 4 Payment methods & local coverage — found from sitemap docs.mangopay.com Checked 11 Nov 2026 Details →
- 5 Payment methods & local coverage — found from sitemap docs.mangopay.com Checked 11 Nov 2026 Details →
- 6 Checkout, SCA & fraud — found from sitemap docs.mangopay.com Checked 11 Nov 2026 Details →
- 7 Checkout, SCA & fraud — found from sitemap docs.mangopay.com Checked 11 Nov 2026 Details →
- 8 Subscriptions & recurring payments — found from sitemap docs.mangopay.com Checked 11 Nov 2026 Details →
- 9 Subscriptions & recurring payments — found from sitemap docs.mangopay.com Checked 11 Nov 2026 Details →
- 10 Settlement, reconciliation & API — found from sitemap docs.mangopay.com Checked 11 Nov 2026 Details →
- 11 Settlement, reconciliation & API — found from sitemap docs.mangopay.com Checked 11 Nov 2026 Details →