MultiSafepay

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

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

by MultiSafepay B.V. · www.multisafepay.com

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

Link to this page

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

MultiSafepay at a glance

Vendor
MultiSafepay B.V.
Headquarters
Incorporated in the Netherlands source, captured 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates MultiSafepay 2.5/5, the mean of 6 judges. MultiSafepay B.V., an Amsterdam payment provider, is strongest where the bench scored highest: payment methods at 6-7 and settlement and reconciliation at 6. how scores are made
As of
Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

MultiSafepay alternatives, European ones first →

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

The panel's verdict

MultiSafepay B.V., an Amsterdam payment provider, is strongest where the bench scored highest: payment methods at 6-7 and settlement and reconciliation at 6. Forty-plus local and international methods run under one contract with each home market named; payouts are daily with a written transfer window of no later than 1 to 7 working days after receipt, backed by CODA, MT940 and CAMT053 exports, SFTP reports and an API into an ERP or data lake. Pricing transparency is weakest at 1-2: the model is published — per transaction, 'No startup or monthly costs', 'Only pay for successful transactions' — but every rate is a custom quote and the chargeback administration fee is only 'as agreed in or based on the Agreement'. Sovereignty scored 3-4 on disclosed transfers to Singapore, the United States, Malaysia and China; the captured pages give different figures for the group parent, Banca Sella as majority owner versus Ant International as the Group, while checkout and SCA and licence and account terms each held at 4. Score variance stayed narrow, and no substantive split was computed.

Report an error

Speaks for it

  • Forty-plus local and international payment methods under one contract, with the home market named for each local method.
  • Daily payouts with a written transfer window of no later than 1 to 7 working days after receipt.
  • Accounting exports in CODA, MT940 and CAMT053, scheduled SFTP reporting, and an API that retrieves all payment data into an ERP or data lake.
  • Recurring billing documented with encrypted tokens from a 0 EUR verification, plans at weekly, monthly or annual frequency, and SEPA Direct Debit mandates converted from Sofort and iDEAL.
  • A named legal structure — MultiSafepay B.V., Chamber of Commerce number 34156361, transaction funds routed to a separate foundation under number 34245794, security deposit returnable no later than 12 months after termination.

Report an error

Held against it

  • No published rate, percentage or markup for any method — every price arrives as a custom quote.
  • We found no public information on 3-D Secure, SCA exemptions or liability shift, and the terms keep PCI DSS responsibility with the merchant.
  • The privacy policy discloses transfers of personal data to Singapore, the United States, Malaysia and China, and we found no public information on where payment and cardholder data are processed and stored.
  • The terms allow unilateral rate changes, payment methods disabled at any time, and a €200-per-day fine for merchants who negotiate rates through third parties.
  • We found no public information on a licence type or supervisor, and the chargeback administration fee is only 'as agreed in or based on the Agreement'.

Report an error

Best for

  • You sell into several European markets and want local methods such as iDEAL, Bancontact, Bizum and Przelewy24 under one contract.
  • Your finance team reconciles bank lines and needs CODA, MT940 or CAMT053 exports plus SFTP and API access into its ERP.
  • You collect recurring payments in euro and can build on SEPA Direct Debit, including mandates converted from Sofort and iDEAL.

Report an error

Avoid if

  • You need published rates to compute an effective fee for your card and country mix before entering a sales conversation.
  • Your data-protection review cannot accept transfers of personal data to Singapore, the United States, Malaysia and China under standard contractual clauses.
  • Your legal review cannot accept unilateral rate changes, payment methods disabled at any time, or a €200-per-day fine for third-party rate negotiation.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

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

Cards, wallets and a genuinely deep European list — iDEAL and Wero, Bancontact, EPS, Multibanco and MB Way, Bizum, Przelewy24, Dankort and Cartes Bancaires — plus SEPA Direct Debit built for recurring collections, all under one contract covering forty-plus methods. It stops short of the top level because each method's country comes from marketing copy rather than a documented matrix, settlement currencies are stated only for SEPA (Euro), and refunds and recurring support are documented for the direct debit flow rather than per method. 5 6 5 6

Report an error

The E-Commerce Lead

This is a named list, not a count, and that is what I plan merchandising against: iDEAL with Wero for the Netherlands, Bancontact, Belfius and KBC/CBC for Belgium, Bizum for Spain, Cartes Bancaires for France, EPS for Austria, Przelewy24 for Poland, Dankort for Denmark, Multibanco and MB Way for Portugal, MyBank and Postepay for Italy, plus cards, wallets, Klarna, Riverty, in3 and Billink, and SEPA Direct Debit with recurring support. What keeps it below the top anchors is that countries are attributed in one-line descriptions rather than a matrix with currencies, refund and recurring support per method — SEPA is the only method with that detail — and I found no public information on BLIK or TWINT, which I would need for Poland and Switzerland. 5 5 6 6

Report an error

The SaaS Founder

A genuinely broad named menu — iDEAL|Wero, Bancontact, KBC/CBC, Belfius, Multibanco, MB Way, Bizum, Cartes Bancaires, EPS, Przelewy24, Dankort, Postepay and MyBank alongside cards, wallets and buy-now-pay-later — with the lead country named for each local method, and SEPA Direct Debit documented with recurring support, split payments and full and partial refunds. Currency is stated only as Euro for SEPA and we found no public per-method matrix of currencies, refunds or recurring support, which is what I would plan a market rollout against. 5 6 5 6

Report an error

The Payments Engineer

Forty-plus methods are named with their home markets — iDEAL and Wero, Bancontact, Belfius and KBC/CBC for Belgium, Multibanco and MB Way for Portugal, Bizum for Spain, EPS for Austria, Przelewy24 for Poland, Dankort for Denmark — alongside cards, the major wallets and SEPA Direct Debit with recurring collection. What keeps this short of a matrix a merchant can plan against is that currencies per method, settlement currencies, and refund and recurring support beyond SEPA are not laid out; we found no public information on those details. 5 5 6 6

Report an error

The Compliance Officer

iDEAL | Wero, Bancontact, EPS, Przelewy24, Multibanco, MB Way, Bizum, Dankort and Cartes Bancaires are each named with the market they serve, alongside cards, wallets and Chinese wallets, and SEPA Direct Debit is documented as covering the SEPA region in euro with recurring charges, split payments and full and partial refunds; cross-border direct debits reach almost anywhere in Europe and multi-currency acceptance is offered. We found no public information on the settlement currency per method or on refund and recurring support stated per method, so a merchant planning per country has the names but not the full picture. 5 6 6 7

Report an error

The Skeptic

Forty-plus methods are listed by name with the country each serves — Bancontact for Belgium, EPS for Austria, Przelewy24 for Poland, Multibanco and MB Way for Portugal, iDEAL with Wero for the Netherlands — alongside cards, wallets and SEPA Direct Debit with recurring support. What holds this below the top level is per-method documentation: refund and recurring support is spelled out only for SEPA, and multi-currency acceptance is claimed while settlement currencies are stated only as Euro on the direct debit page. 5 5 6 6 7

Report an error

Checkout, SCA & fraud

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

Hosted and embedded checkouts are both documented, with express checkout buttons and Second Chance emails to recover abandoned payments, plus in-house risk and fraud monitoring. I found no public information on 3-D Secure or SCA exemption handling, on configurable fraud rules, or on PCI scope per integration type — the terms only place the merchant's own PCI DSS responsibility on the merchant — so it sits above a plain hosted page but well short of a documented SCA flow. 2 6 8 4 6

Report an error

The E-Commerce Lead

The checkout path I care about is there: hosted redirect, an embedded option that keeps payment inside my own checkout, ready-made CMS plugins, express checkout buttons for Apple Pay, Google Pay, PayPal, Klarna and Amazon Pay with profile prefill, plus Second Chance recovery emails, one-click repeat payments and encrypted tokenisation. But the SCA story I actually need before signing is missing — I found no public information on 3-D Secure handling, SCA exemptions, soft declines or authorisation-rate reporting — fraud monitoring is a single in-house claim, and the terms put PCI DSS responsibility squarely on me as the merchant. 1 6 7 8 9 4 2

Report an error

The SaaS Founder

Hosted and embedded checkout, ready-made CMS integrations, express checkout buttons that prefill profiles, Fastcheckout with stored shipping and payment methods, and in-house risk and fraud monitoring are all on the captured pages. We found no public information on 3-D Secure, SCA exemption handling, PCI scope per integration type or liability shift, so I cannot see how they keep legitimate payments from failing under PSD2. 1 2 8 8

Report an error

The Payments Engineer

Hosted, embedded and ready-made CMS routes are all documented, plus express checkout buttons for Apple Pay, Google Pay, PayPal and Klarna, in-house risk and fraud monitoring, and tokenisation with a zero-euro card verification. We found no public information on 3-D Secure, SCA exemption handling or liability shift, and on PCI DSS the terms only say the merchant remains responsible for its own compliance — the integration options are shown but the authorisation machinery underneath them is not. 6 1 2 9 4 8

Report an error

The Compliance Officer

Hosted, embedded and API checkout paths are all documented, with express checkout buttons for Apple Pay, Google Pay, PayPal and Klarna, encrypted tokens seeded by a 0 EUR card verification, and in-house risk and fraud monitoring. We found no public information on 3-D Secure, SCA exemption strategy or liability shift, and the terms put PCI DSS responsibility for cardholder data on the merchant without stating the provider's own attestation level. 6 8 9 2 4

Report an error

The Skeptic

Hosted and embedded checkout, payment links, express checkout buttons and in-house risk and fraud monitoring are documented, and card details can be stored as an encrypted token after a 0 EUR verification transaction. But we found no public information on 3-D Secure handling, SCA exemptions or the PCI scope of each integration type — the terms only state that the CVV code must never be stored and that the merchant stays responsible for PCI DSS compliance. 1 2 9 8 4

Report an error

Subscriptions & recurring payments

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

Encrypted tokens with a zero-euro verification before the first charge, SEPA Direct Debit explicitly positioned for recurring collections on the back of Sofort and iDEAL, and subscription schedules at weekly, monthly or annual frequency for B2B and B2C. I found no public information on dunning, retries, an account updater or a process for exporting tokens to another provider, which caps it at the middle level. 6 9 5

Report an error

The E-Commerce Lead

Recurring is real, not an afterthought: card details stored as an encrypted token from an initial transaction, a zero-euro verification transaction before the first charge, subscription plans at weekly, monthly or annual frequency for both B2B and B2C, and SEPA Direct Debit for recurring collections including Sofort and iDEAL conversions, with e-invoicing that chases customers through email, letters, text or WhatsApp. I found no public information on dunning or smart retries, an account updater, or any process for exporting my stored payment tokens to another provider. 9 6 6 5 2

Report an error

The SaaS Founder

The pieces I need to run subscriptions are evidenced: encrypted payment tokens from an initial transaction, a 0 EUR card verification before the first charge, SEPA Direct Debit recurring collection, and automated payment plans at weekly, monthly or annual frequency for B2B and B2C. We found no public information on dunning, retries, failed-payment notification, proration, or any process for exporting tokens to another provider — and with no documented exit, whoever holds the tokens holds my customer base. 9 5 6

Report an error

The Payments Engineer

Stored payment details as encrypted tokens, SEPA Direct Debit built for recurring collection — it converts Sofort and iDEAL payments into mandates — and subscription plans at weekly, monthly or annual frequency for B2B and B2C, managed from the dashboard with an in-house e-invoicing timeline. We found no public information on smart retries, dunning, card account updater, or any process for exporting payment tokens to another provider. 9 6 5 6

Report an error

The Compliance Officer

Card details stored as encrypted tokens after a 0 EUR verification, recurring payment plans at weekly, monthly or annual frequency, and SEPA Direct Debit marketed as excellent for subscriptions cover card-on-file and mandate-based recurring alike. We found no public information on dunning or smart retries, an account updater, or a documented route for exporting payment tokens to another provider. 9 5 6 2

Report an error

The Skeptic

Stored cards as encrypted tokens, SEPA Direct Debit recurring — including mandates built from Sofort and iDEAL — and subscription plans weekly, monthly or annually for B2B and B2C are all documented. We found no public information on dunning or smart retries, account updater, proration and trials, or a documented process for exporting payment tokens to another provider. 9 5 6 6

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

The payout schedule is written into the terms — funds transferred by the foundation no later than 1 to 7 working days after receipt — with daily payouts claimed and accounting exports in CODA, MT940 and CAMT053, exactly the formats a finance team reconciles bank lines with, automatable through SFTP push or pull and the API into our own ERP. I found no public information on webhooks, per-transaction fee itemisation, settlement currencies or a public status page, so I cannot plan a full month-end close on the documented evidence. 2 10 4 5

Report an error

The E-Commerce Lead

Finance gets more than a basic dashboard here: daily payouts with transfer no later than one to seven working days after funds are received, accounting exports in CODA, MT940 and CAMT053 formats, reports automated over SFTP by push or pull, an API for transaction retrieval, payment matching and reconciliation into my own ERP, and a test account to build against. I found no public information on webhooks, itemised interchange and scheme fees per transaction, published rate limits, or a public status page with incident history, which is what the top level turns on. 10 4 2 5

Report an error

The SaaS Founder

Daily payouts, funds transferred to the merchant's bank account no later than 1 to 7 working days after receipt, accounting exports in CODA, MT940 and CAMT053, automated reconciliation, scheduled reports over SFTP, and an API to pull all payment data into our own ERP — this is a workable month-end. We found no public information on webhooks, interchange or scheme fee itemisation per transaction, configurable settlement currencies, or API versioning and rate limits. 2 10 4

Report an error

The Payments Engineer

The payout cadence is written down — funds transferred no later than one to seven working days after receipt, with daily payouts advertised — and the finance tooling is real: CODA, MT940 and CAMT053 exports, accounting plugins, scheduled reports over SFTP, and an API that automates payment matching and can feed an ERP or data lake. But the captured pages give no webhooks, no idempotency keys, no API versioning policy and no public status page with incident history, which is exactly the layer I would be paged on. 4 2 10 9

Report an error

The Compliance Officer

The terms commit the Foundation to transfer merchant funds no later than 1 to 7 working days after receipt, daily payouts are advertised, and the reporting suite is real finance tooling — scheduled reports over SFTP push or pull, accounting exports in CODA, MT940 and CAMT053, accounting plugins, and all payment data retrievable via the API into an ERP or data lake, with a test account. We found no public information on webhooks, configurable settlement currencies, or a public status page with incident history. 4 2 10

Report an error

The Skeptic

Daily payouts, a stated transfer window of no later than 1 to 7 working days, accounting exports in CODA, MT940 and CAMT053, automated SFTP reports in push or pull, and an API for payment matching and reconciliation with a test account give a finance team real material to build on. We found no public information on webhooks, configurable payout schedules or settlement currencies, API versioning and idempotency, or a public status page. 10 2 4 5

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

The contracting entity is named with its Chamber of Commerce number, transaction funds are received by a separate foundation, ordinary termination needs two months' notice, chargebacks carry a twelve-month reclaim window, and the security deposit is committed back no later than twelve months after termination without interest. I found no licence type or supervisor stated, the chargeback administration fee is only "as agreed in or based on the Agreement", and I found no public information on how a reserve is calculated or capped — the number I want before signing. 4 4

Report an error

The E-Commerce Lead

The terms name the contracting entity with a Chamber of Commerce registration and a separate foundation that receives transaction funds, give ordinary termination at two months' written notice, and put a timeline on the bad day — a security deposit returned no later than twelve months after termination, a dispute process with two working days to contact the customer and fourteen days to resolve, and chargebacks reclaimable up to a year. The chargeback administration fee is only given as whatever is agreed in the agreement, and I found no public information naming a licence type or supervisor for the entity behind the payments, so I cannot place this higher. 4 4 3

Report an error

The SaaS Founder

The terms name MultiSafepay B.V. in Amsterdam with Chamber of Commerce number 34156361, route transaction funds through a separate Foundation registered under number 34245794, commit to two months' notice for termination, and promise return of a security deposit no later than 12 months after termination, without interest. The chargeback administration fee is stated as agreed in the Agreement rather than as a published figure, and we found no public statement of licence type, supervisor or PCI DSS level. 4 4

Report an error

The Payments Engineer

MultiSafepay B.V. is named with its Chamber of Commerce number, transaction funds are routed to a named Dutch Foundation, and the terms state a two-month termination notice, a security deposit returned within twelve months of termination, and a defined dispute-handling window of fourteen days. We found no public information on licence type or supervisor, the chargeback administration fee is only "as agreed in the Agreement", and the terms allow MultiSafepay to change rates unilaterally and disable payment methods at any time. 4 4

Report an error

The Compliance Officer

MultiSafepay B.V. of Amsterdam is named with Chamber of Commerce number 34156361, transaction funds are routed to a separate Foundation registered under number 34245794, ordinary termination carries two months' notice, and a security deposit is returned within twelve months after termination — a structure a risk officer can at least read. We found no public information on the supervisor or licence type behind the payments; the chargeback administration fee is payable "as agreed in or based on the Agreement", payment methods may be disabled at any time, and no appeal route against suspension is described. 4 4

Report an error

The Skeptic

MultiSafepay B.V. is named with Chamber of Commerce number 34156361, transaction funds flow to a Dutch foundation, ordinary termination carries a two-month notice, and a chargeback can be reclaimed up to a year after payment — but the captured terms state no licence or supervisor for the payments, the chargeback administration fee is only as agreed in the Agreement, and a security deposit may be returned no later than 12 months after termination with no interest. The bad-day terms also include unilateral rate changes on two months' notice, payment methods that can be disabled at any time for risk or complaint reasons, and a fine of €200 per day of violation for merchants who negotiate rates with third parties. 4 4

Report an error

European sovereignty panel opinion

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

The contracting entity is MultiSafepay B.V. in Amsterdam, and the privacy policy publishes a subprocessor list with standard contractual clauses for transfers outside the EEA. Those transfers are disclosed as reaching Singapore, the United States, Malaysia and China for the technical infrastructure and business structure, the processing location of payment data itself is not stated, and I found no public information on a data processing agreement. 3 3 4

Report an error

The E-Commerce Lead

The contracting entity is Dutch with a Chamber of Commerce number, the privacy notice publishes a subprocessor list and appoints a DPO, and transfers to third countries are said to run under EU standard contractual clauses. But the same notice states personal data is transferred to Singapore, the United States, Malaysia and China to accommodate the technical infrastructure, I found no public information on where payment and cardholder data is processed or stored, and the captured pages give different figures for the group's ownership, so European ownership cannot be confirmed from them. 4 3 3

Report an error

The SaaS Founder

The contracting entity is a Dutch company with a published Chamber of Commerce number, a privacy policy and a published subprocessor list, and third-country transfers run on standard contractual clauses. The privacy policy states transfers of personal data to Singapore, the United States, Malaysia and China for technical infrastructure, the processing location of payment data is not stated, and we found no public information on a data processing agreement. 3 3 4

Report an error

The Payments Engineer

The contracting entity is MultiSafepay B.V. in Amsterdam under Dutch terms, and a list of agents and service providers is published, which is worth a mid score. But the privacy policy discloses international transfers of personal data to Singapore, the United States, Malaysia and China for technical infrastructure under standard contractual clauses, and we found no public information on where payment or cardholder data itself is processed and stored. 4 3 3

Report an error

The Compliance Officer

The contracting entity is the Dutch MultiSafepay B.V. and a list of subprocessors is stated to be published, but the privacy policy contemplates transfers of personal information to Singapore, the United States, Malaysia and China to accommodate the technical infrastructure, relying on standard contractual clauses, and refers to the group as Ant International. We found no public information on where transaction and cardholder data are processed and stored, on subprocessor locations, or on a data processing agreement separating the provider's controller and processor roles. 3 4 3

Report an error

The Skeptic

MultiSafepay B.V. is a Dutch contracting entity and a subprocessor list is published, but the privacy policy discloses transfers of personal data to Singapore, the United States, Malaysia and China to accommodate technical infrastructure, under standard contractual clauses. We found no public information on where payment and cardholder data are processed or stored, or on a data processing agreement. The vendor descriptor names Italy's Banca Sella as majority owner while the privacy policy defines the Group as Ant International — different figures for the group parent. 4 3 3

Report an error

Pricing transparency

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 pricing page states the model — payment per successful transaction, no startup or monthly fees, prices exclusive of VAT — but publishes no rate of any kind: every figure comes as a custom quote after telling them about your business, the chargeback administration fee is "as agreed in or based on the Agreement", and currency conversion costs are passed through without a stated markup. I cannot compute an effective fee for my card and country mix from these pages. 2 4 4

Report an error

The E-Commerce Lead

The pricing page sells the model but publishes no rates: pay only for successful transactions, no startup or monthly fees, and a custom quote — give us information about your business and we will come back with an offer — which means every rate is a sales conversation. The terms add honest structure around it, with currency conversion costs passed through, prices exclusive of VAT, two months' notice before new fees take effect, and no interest paid on balances or the security deposit, but nothing on these pages lets me compute an effective fee for my card and country mix. 2 4 6

Report an error

The SaaS Founder

The captured pricing pages say transparent per-transaction pricing, no startup or monthly costs, and charges only for successful transactions, then invite you to describe your business for a custom pricing offer — we found no public rate, percentage or per-method figure to compute an effective fee from, while the terms add that currency conversion costs are passed on and a chargeback fee is as agreed. The €200 per day of violation fine for rate negotiation through a third party is a term any CFO should see before signing. 2 4 4

Report an error

The Payments Engineer

The pricing page publishes the model — pay per successful transaction, no startup or monthly costs, prices exclusive of VAT — and the terms commit to two months' notice before rate changes and pass currency-conversion costs through. But every actual rate is a quote ("we'll get back to you with a pricing offer made for you"): we found no public percentage for any method or card type, and the chargeback fee is only "as agreed in the Agreement". 2 4 4

Report an error

The Compliance Officer

The public pricing pages give the model but not the money: per-transaction billing, no startup or monthly costs, "Only pay for successful transactions", and a bespoke offer ("we'll get back to you with a pricing offer made for you"). We found no published rate, percentage or markup for any method, and the ancillary costs surface only in the terms — chargeback administration "as agreed in or based on the Agreement", currency conversion costs passed through, no interest on balances or deposits, prices exclusive of VAT. 2 4 4

Report an error

The Skeptic

Every actual rate is a sales conversation: the pricing pages invite a business to request a custom quote, and while they state "No startup or monthly costs" and "Only pay for successful transactions", we found no public information on any published rate for any method, domestic or international. The terms say conversion costs "will be passed on to Merchant" without a markup figure, and the chargeback administration fee is whatever is agreed in the Agreement — a merchant cannot compute an effective fee from public pages. 2 4 2

Report an error

European sovereignty — proven facts

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

Is MultiSafepay European?

Yes. whats-best.ai classifies MultiSafepay as EU-Made. Its vendor, MultiSafepay B.V., is incorporated in the Netherlands, per the vendor’s page captured 16 Nov 2026.

Where does MultiSafepay store data?

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

Does MultiSafepay have a free plan?

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

What are the best alternatives to MultiSafepay?

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: MultiSafepay 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 (10)

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

  1. 1 Vendor homepage www.multisafepay.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 22 Sep 2026 Details →
  2. 2 Pricing page www.multisafepay.com Checked 16 Nov 2026 +1 earlier capture: 22 Sep 2026 Details →
  3. 3 Privacy policy www.multisafepay.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  4. 4 Terms of service www.multisafepay.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  5. 5 Payment methods & local coverage — found from sitemap www.multisafepay.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  6. 6 Payment methods & local coverage — found from sitemap www.multisafepay.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  7. 7 Checkout, SCA & fraud — found from sitemap www.multisafepay.com Checked 16 Nov 2026 Details →
  8. 8 Checkout, SCA & fraud — found from sitemap www.multisafepay.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  9. 9 Subscriptions & recurring payments — found from sitemap www.multisafepay.com Checked 16 Nov 2026 Details →
  10. 10 Settlement, reconciliation & API — found from sitemap www.multisafepay.com Checked 16 Nov 2026 Details →