Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Mondu GmbH · mondu.ai

Report an error on this page Is this your product? →

Link to this page

Mondu: AI-assisted analysis on whats-best.ai Mondu: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Mondu at a glance

Vendor
Mondu GmbH
Headquarters
Not stated on the vendor’s pages as of 11 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 11 Nov 2026
Free plan
Not stated on the vendor’s pages as of 11 Nov 2026
Panel verdict
The AI panel rates Mondu 1.5/5, the mean of 6 judges. Mondu GmbH sells buy-now-pay-later terms to B2B merchants: invoice payment with 30 to 90-day terms, instalments over 3 to 12 months, SEPA Direct Debit excluding the UK, a Pay Now instant transfer, a Digital Trade Account and embedded invoice factoring with 12-hour approval and payout within 36 hours. how scores are made
As of
Vendor pages captured 11 Nov 2026; evaluated by the panel 11 Nov 2026. all sources

Mondu alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Mondu GmbH sells buy-now-pay-later terms to B2B merchants: invoice payment with 30 to 90-day terms, instalments over 3 to 12 months, SEPA Direct Debit excluding the UK, a Pay Now instant transfer, a Digital Trade Account and embedded invoice factoring with 12-hour approval and payout within 36 hours. Its clear strength is settlement and reconciliation (scores 4 to 5): processed payouts usually reach the bank within one business day, reports break collective transfers into line items with deductions and VAT as XLSX or CSV, and a payouts API carries per-payout fee fields, payout states and pagination to 1000 items. The weak edges are consistent. Checkout and SCA scores run 0 to 2, with no public information on 3-D Secure, SCA exemptions or fraud screening. Recurring billing runs 0 to 2 — instalments are the buyer's repayment to Mondu, not merchant-initiated charges. Sovereignty runs 0 to 2, with no public information on data residency, subprocessors or a data processing agreement. Payment methods cluster at 4 — named methods, but we found no public information on card or wallet support or per-country coverage.

Report an error

Speaks for it

  • Named buyer methods cover invoice terms of 30 to 90 days, instalments of 3 to 12 months, SEPA Direct Debit excluding the UK, Pay Now and a Digital Trade Account
  • Processed payouts usually reach the bank within one business day, and factoring payouts land within 36 hours of approval
  • Payout reports break collective transfers into line items with deductions and VAT, downloadable as XLSX or CSV
  • A payouts API exposes per-payout MDR and fixed fee fields, payout states, a report link and pagination to 1000 items against a demo endpoint
  • Pay Now account-to-account transfer runs through the same BNPL integration with no separate A2A provider

Report an error

Held against it

  • We found no public information on card or wallet acceptance, nor on which countries and currencies each method serves
  • We found no public information on 3-D Secure, SCA exemption handling or fraud screening for the checkout integration
  • Every documented repetition is on the buyer's side — instalments, SEPA Direct Debit settlement and monthly trade-account billing — with no public information on merchant-initiated recurring charges, dunning or credential export
  • We found no public information on the regulated entity behind the payments, its licence or supervisor, safeguarding of merchant funds, reserves or termination terms
  • We found no public information on data residency, subprocessors or a data processing agreement

Report an error

Best for

  • You sell B2B and want to offer buyers invoice, instalment and SEPA Direct Debit terms from a single checkout integration
  • Your finance team needs granular payout detail — line-item reports with deductions and VAT in XLSX or CSV, and per-payout fee fields through the payouts API
  • Cash speed matters to you — processed payouts usually transfer within one business day, and embedded factoring pays out within 36 hours of approval
  • You run a platform and want to embed invoice factoring for your customers on a single-invoice basis

Report an error

Avoid if

  • Your business bills by subscription or renewal — the documented model is per-order, and instalments are the buyer's repayment to Mondu rather than charges you initiate
  • Your buyers are in the UK and need SEPA Direct Debit settlement — the documentation states it is available excluding the UK
  • You need to know your effective fee before talking to sales — ask the vendor: the public pages we read do not show it
  • Your payout planning cannot absorb deductions — a lost dispute and a buyer payment made to you instead of Mondu are both deducted from the next payout

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Payment methods & local coverage 2 of 5
Checkout, SCA & fraud 1 of 5
Subscriptions & recurring payments 1 of 5
Settlement, reconciliation & API 2.5 of 5
Licence, risk & account terms 1 of 5
European sovereignty 1 of 5

Payment methods & local coverage

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

Report an error

The Finance Lead

Buyer payment methods are documented by name — invoice with 30-90 day terms, installments over three to twelve months, SEPA Direct Debit excluding the UK, a Pay Now account-to-account instant transfer and a Digital Trade Account with collective monthly billing. We found no public information on card or wallet acceptance, however, and no countries or currencies stated per method. 1 2

Report an error

The E-Commerce Lead

The named methods are real conversion levers — invoice with 30-90 day terms, instalments from 3 to 12 months, a Pay Now instant bank transfer, SEPA Direct Debit settlement (excluding the UK) and a Digital Trade Account — but I found no public information on card or wallet support, on which method serves which country or currency, or on refunds and recurring support per method. 1

Report an error

The SaaS Founder

The checkout methods are named and European: BNPL invoice with 30-90 day terms, installments of 3-12 months, SEPA direct debit settlement excluding the UK, and Pay Now instant bank transfer. We found no public information on card or wallet acceptance, and no per-country or per-currency coverage, so I cannot plan a market rollout against it. 1 2

Report an error

The Payments Engineer

Several methods are named — invoice with 30-90 day terms where the customer settles with Mondu by bank transfer, installments over 3 to 12 months, SEPA direct debit with a stated UK exclusion, Pay Now as an A2A instant transfer, and a Digital Trade Account with collective monthly billing. The captured pages name no cards or wallets and no per-country list of countries and currencies per method, so I can plan a BNPL checkout against this but not broader card coverage. 1 2

Report an error

The Compliance Officer

Invoice payment with 30-90 day terms, installments over three to twelve months, SEPA Direct Debit excluding the UK, and an instant account-to-account Pay Now method are each named, which is real named-method coverage. However, the captured pages show no card or wallet acceptance, and no per-country list of which method serves which countries or currencies, so a merchant cannot plan coverage from them. 1 2

Report an error

The Skeptic

The documentation names the methods a buyer can choose: invoice payment with 30 to 90-day terms, instalments of 3 to 12 months, Pay Now instant account-to-account transfer, SEPA Direct Debit settlement of invoices (excluding the UK), a Digital Trade Account with collective monthly billing, plus a section on offline payment methods and embedded invoice factoring. We found no public information on card or wallet acceptance, and no per-country list with the countries and currencies each method serves or refund and recurring support per method. 1 2

Report an error

Checkout, SCA & fraud

n/r Show 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.

Report an error

The Finance Lead not rated — no public information

We found no public information on hosted or embedded checkout options, 3-D Secure, SCA exemption handling or fraud screening. The captured payment-method pages describe what buyers can choose and how the integration is reached, not the path from basket to authorisation. 1 2

Report an error

The E-Commerce Lead

The pages show Mondu sits "in your checkout" and that Pay Now rides the same integration, so a checkout component exists, but I found no public information on hosted versus embedded options, running the payment on my own domain, 3-D Secure or SCA exemption handling, or fraud screening. 1

Report an error

The SaaS Founder

A checkout integration is described ("With Mondu in your checkout…"), but the captured pages show nothing on hosted or embedded checkout options, 3-D Secure, SCA exemption handling or fraud screening. For a BNPL product authorisation is underwriting, and none of that risk path is documented here. 1

Report an error

The Payments Engineer

A checkout integration is shown — 'With Mondu in your checkout, you can offer your customers attractive payment terms (30-90 days)' — and Pay Now is delivered through the same BNPL integration without a separate A2A integration. We found no public information on 3-D Secure, SCA exemption handling, fraud screening, or the PCI scope of each integration type, which is what I need stated before wiring anything in. 1 2

Report an error

The Compliance Officer

A checkout integration is documented — Mondu sits in the merchant's checkout and Pay Now runs through the same integration without a separate bank-transfer provider — but I found no public information on 3-D Secure, strong customer authentication handling, exemptions, or fraud screening. The captured pages never show the path from basket to authorised payment in the PSD2 sense. 1

Report an error

The Skeptic

A checkout integration exists — the pages describe offering these payment terms "with Mondu in your checkout" and an instant bank transfer available through the same integration. We found no public information on hosted versus embedded checkout options, 3-D Secure, SCA exemption handling or fraud screening; the only approval step documented is the 12-hour buyer approval for embedded invoice factoring, which is credit underwriting rather than checkout fraud tooling. 1

Report an error

Subscriptions & recurring payments

n/r Show 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.

Report an error

The Finance Lead not rated — no public information

We found no public information on stored payment credentials under the merchant's control, SEPA mandate management for repeat charges, subscription logic, dunning or token export. The documented installments are the buyer's repayment schedule to Mondu, and the Digital Trade Account aggregates buyer payments, neither of which is a recurring billing capability the merchant bills against. 1 3

Report an error

The E-Commerce Lead

Buyer-side repetition is documented — instalments over 3 to 12 months and the Digital Trade Account's collective monthly billing — but I found no public information on stored credentials for merchant-initiated charges, SEPA mandate management, subscription logic, dunning or token export. 1

Report an error

The SaaS Founder

Everything documented is per-order: invoices, installments, and SEPA direct debit used to settle a single invoice. As a subscription business I see no card-on-file charges I can initiate, no dunning, no plan changes, and no documented process for exporting payment credentials - the model is not built for renewals. 1

Report an error

The Payments Engineer

Buyer-side repeat charging is evidenced — installments over 3 to 12 months with a buyer fee common, and a Digital Trade Account with a collective monthly statement on extended terms — alongside SEPA direct debit settlement of invoices. We found no public information on merchant-initiated subscription billing, mandate management, dunning or retries, or any process for exporting stored payment credentials to another provider. 1

Report an error

The Compliance Officer

Buyers can pay in installments over three to twelve months and settle invoices by SEPA Direct Debit, so scheduled buyer payments exist on the provider's side. I found no public information on stored payment credentials charged again for the merchant, subscription logic, dunning, or any process for exporting payment tokens to another provider. 1

Report an error

The Skeptic

Recurrence is documented on the buyer side only: instalments over 3 to 12 months, invoices settled by SEPA Direct Debit, and a Digital Trade Account billed collectively each month on extended terms. We found no public information on merchant-side recurring charges, subscription logic, retries or dunning, or any process for taking stored payment credentials to another provider. 1

Report an error

Settlement, reconciliation & API

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

Report an error

The Finance Lead

Payout cadence is stated — processed payouts usually transfer within one business day and confirmed by the banking partner, with factoring payouts within 36 hours of approval — and XLSX/CSV payout reports break collective transfers into line items with Transfer Amount, Total Deductions and Net Transfer Amount, including Dispute and Buyer Payment deductions from the next payout. A documented payouts API exposes per-payout MDR and fixed fee amounts in cents with pagination and states, though we found no public information on webhooks, idempotency, accounting integrations or a status page. 2 3 4

Report an error

The E-Commerce Lead

The strongest area: payouts are usually transferred within one business day of being processed, the merchant portal lists every historical payout report for download in CSV or XLSX, reports break collective transfers into line items with deductions and taxes, and a documented payouts API with pagination, fee fields and a demo environment backs it — though I found no public information on webhooks, settlement currencies or accounting exports. 3 4

Report an error

The SaaS Founder

Payout reporting is genuinely worked out: reports break collective transfers into line items with deductions and VAT, percentage and fixed fee amounts are itemised, exports come as XLSX or CSV, a processed payout usually lands within one business day, and there is a payouts API with pagination and a demo environment. What I need for month-end close is missing: webhooks, accounting integrations, configurable payout schedules, and stated reconciliation to bank lines. 3 4

Report an error

The Payments Engineer

Payout cadence is stated (a processed payout usually transfers within one business day), payout reports break collective transfers into line items with deductions and taxes and download as XLSX or CSV, and a versioned payouts API exposes per-payout fee fields, pagination up to 1000 items and a demo host. We found no public information on webhooks, idempotency keys or rate limits — without webhooks finance processes end up polling, and polling rots. 3 4

Report an error

The Compliance Officer

Payout cadence is stated — initiated transfers are usually expected within one business day and confirmed by the banking partner — and payout reports break collective transfers into line items with deductions and VAT, downloadable as XLSX or CSV, with a documented payouts API including pagination and a demo endpoint. Webhooks are not documented in anything I captured, which is what keeps this below the fuller integration level. 3 4

Report an error

The Skeptic

The merchant portal lists all current and historical payout reports, downloadable as XLSX or CSV, breaking collective transfers into line items with deductions and VAT on the discount, and processing is stated to reach the bank usually within one business day. A payouts API is documented against a demo endpoint, with pagination, per-payout fee fields for the MDR and fixed fee, a report link and payout states. We found no public information on webhooks, configurable payout schedules or settlement currencies, idempotency and rate limits, or a status page. 3 4

Report an error

Licence, risk & account terms

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

Report an error

The Finance Lead

A dispute process is described — when the merchant loses a dispute, the disputed amount may be deducted from the next payout, and buyer payments made to the merchant instead of Mondu have a reporting route — but we found no public information on the licence or supervisor behind the payments, safeguarding of merchant funds, reserve conditions with limits, or termination notice. 3

Report an error

The E-Commerce Lead

The docs describe a dispute flow — a lost dispute can be deducted from the next payout — and buyer payments can likewise be netted from payouts, but I found no public information naming the regulated entity or its supervisor, safeguarding of merchant funds, reserve and rolling-hold conditions, or termination and appeal terms. 3

Report an error

The SaaS Founder

Dispute mechanics are written down - losing a dispute or a buyer paying me directly is deducted from the next payout - and payouts are "confirmed by our banking partner", though no partner is named in the pages. I found no public information on licence, supervisor, safeguarding, reserves, freezes or termination terms. 3

Report an error

The Payments Engineer

The only account terms captured are offset mechanics: a lost dispute's amount may be deducted from the next payout, and a customer payment reported to the merchant portal is likewise deducted. We found no public information on the regulated entity behind the payments, its licence or supervisor, safeguarding of merchant funds, reserves, or termination notice and appeal. 3

Report an error

The Compliance Officer

The vendor is presented as Mondu GmbH and the payout documentation does describe one bad-day scenario: a lost dispute has its amount deducted from the next payout. Beyond that I found no public information on the licence or supervisor behind the payment services, safeguarding of merchant funds, reserves and rolling holds, or termination and appeal terms. 3

Report an error

The Skeptic

One edge of the risk terms is visible: a lost dispute is deducted from the next payout via a Dispute Note, and buyer payments made to the merchant are likewise deducted when reported. We found no public information on the regulated entity behind the payments, its licence, supervisor or register number, safeguarding of merchant funds, reserve conditions, or freeze and termination terms in the pages captured. 3

Report an error

European sovereignty panel opinion

n/r n/r n/r n/r n/r Show 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.

Report an error

The Finance Lead not rated — no public information

We found no public information on the contracting or regulated entity's jurisdiction, where payment and cardholder data are processed, subprocessors, or a data processing agreement. Every captured page — payment methods, factoring and payouts — is silent on these dimensions. 1 2 3 4

Report an error

The E-Commerce Lead not rated — no public information

I found no public information on the contracting entity's jurisdiction, where payment data is processed or hosted, subprocessors or a data processing agreement; the captured pages cover payment methods and payouts only, and the only European signal is that payouts carry a SEPA identifier. 1 2 3 4

Report an error

The SaaS Founder not rated — no public information

We found no public information on where transaction or buyer data is processed or stored, on a data processing agreement, or on subprocessors; every sovereignty dimension is unrecorded. I read the payment methods page, the e-commerce payment methods page, the payouts documentation and the payouts API reference. 1 2 3 4

Report an error

The Payments Engineer not rated — no public information

The sovereignty review returned unknown for every dimension — legal entity jurisdiction, data residency, hosting options, data processing agreement and transfer impact assessment — so I found no public information on who the contracting and regulated entity is or where transaction data is processed and stored. The pages I read were the payment methods, e-commerce payment methods, payouts and payout API documentation. 1 2 3 4

Report an error

The Compliance Officer

The vendor presents as Mondu GmbH and the rails are European — payouts carry a SEPA identifier and SEPA Direct Debit is offered excluding the UK — but I found no public information on where transaction and cardholder data are processed, who the subprocessors are, or a data processing agreement. Every sovereignty dimension that matters to me as a regulated buyer is simply not documented on these pages. 1 4

Report an error

The Skeptic not rated — no public information

We found no public information on the contracting entity, its jurisdiction or licence, or where payment and customer data are processed; the sovereignty assessment marks every one of these dimensions unknown. The only European signal in the pages read is that buyers settle invoices by SEPA Direct Debit and payouts carry a SEPA reference, which says nothing about who holds the merchant's money or where data is stored. 1 2 3 4

Report an error

Pricing transparency not rated — the vendor publishes no price

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

Report an error

The Finance Lead

The fee model is public — a contract-set MDR percentage plus a fixed per-order transaction fee applied once to the first invoice, with the discount and VAT on the discount shown as deductions in payout reports — but every rate itself is set in the contract, so a merchant cannot compute an effective fee from public pages. Installments carry a buyer fee of unstated amount, and no chargeback, payout or monthly fees are published. 1 3

Report an error

The E-Commerce Lead

The fee model's shape is published — a contract-set MDR percentage plus a fixed per-order transaction fee applied once to the first invoice, with the discount and VAT-on-discount deductions shown in payout reports — but every actual rate is set in the contract and no figure is given anywhere, so I cannot compute an effective fee for my card and country mix from public pages alone. 1 3

Report an error

The SaaS Founder

The fee model is public but no number is: an MDR percentage and a fixed per-order transaction fee, both "set in the contract", with the fixed fee applied once to the first invoice. A merchant cannot compute an effective rate for their own mix from anything published. 3

Report an error

The Payments Engineer

The fee model is documented — a contract-set MDR percentage plus a fixed per-order transaction fee applied once to the first invoice, with discounts and VAT on discounts deducted from payouts — but no rate is published: both components are 'set in the contract', and the installment buyer fee is described as common with no figure. I cannot compute an effective fee for any volume or mix from public pages; every number is a sales conversation. 1 3

Report an error

The Compliance Officer

The payout documentation publishes the fee structure — a percentage described as MDR plus a fixed per-order transaction fee applied to the first invoice — but states both are "set in the contract", so no rate a merchant could compute against is public. Installment buyers commonly pay a fee, yet I found no public figure for it, nor for chargebacks, refunds or payouts. 3 1

Report an error

The Skeptic

The published detail is the shape of the fee, not the numbers: a contract-set MDR percentage plus a contract-set fixed transaction fee charged once per order on the first invoice. We found no published rate for any method in the pages captured, and the buyer fee that commonly applies to instalments appears without an amount. 1 3

Report an error

European sovereignty — proven facts

0 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Mondu

Is Mondu European?

Not determined: the vendor’s pages as captured do not say where Mondu is based.

Where does Mondu store data?

Not stated on the vendor’s pages as of 11 Nov 2026.

Does Mondu have a free plan?

Not stated on the vendor’s pages as of 11 Nov 2026.

What are the best alternatives to Mondu?

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: Mondu alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (4)

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

  1. 1 Payment methods & local coverage — found from sitemap docs.mondu.ai Checked 11 Nov 2026 Details →
  2. 2 Payment methods & local coverage — found from sitemap docs.mondu.ai Checked 11 Nov 2026 Details →
  3. 3 Settlement, reconciliation & API — found from sitemap docs.mondu.ai Checked 11 Nov 2026 Details →
  4. 4 Settlement, reconciliation & API — found from sitemap docs.mondu.ai Checked 11 Nov 2026 Details →