Payment
MultiSafepay
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 4 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? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
MultiSafepay B.V., a collecting payments provider in Amsterdam, scores best on payment methods at 6-7: 40+ methods — iDEAL|Wero for the Netherlands, Bancontact for Belgium, Multibanco, Bizum, EPS, Przelewy24 — with SEPA Direct Debit and cross-border collection under one contract. Settlement and reconciliation follows at 5-6 on written payout timing (daily payouts, no later than 1 to 7 working days after receipt) and exports (CODA, MT940, CAMT053, SFTP, API matching). Pricing transparency is weakest at 1-2: every rate arrives as a custom quote — "we'll get back to you with a pricing offer made for you" — conversion costs are passed on at an unstated markup, and rates can change on two months' notice. Checkout and SCA spans 2-4: express checkouts are documented, but we found no public information on 3-D Secure, SCA exemptions or PCI scope per integration. Licence and account terms sit at 4; sovereignty at 3-4, the privacy policy naming transfers to Singapore, the United States, Malaysia and China, and the group parent differing between the bench's provenance note (Banca Sella, majority owner since 2020) and the captured privacy policy (Ant International).
Speaks for it
- Named list of 40+ payment methods with markets attached — iDEAL|Wero for the Netherlands, Bancontact for Belgium, Multibanco, Bizum, EPS, Przelewy24 — plus SEPA Direct Debit with cross-border collection under one contract
- Payout timing written down: daily payouts, transfer no later than 1 to 7 working days after receipt of funds
- Concrete reconciliation tooling: CODA, MT940 and CAMT053 exports, accounting plugins, SFTP push or pull, and API payment matching into your own ERP
- Recurring core evidenced: encrypted card tokens with a 0 EUR verification, MDES network tokenisation, weekly-to-annual plans, and SEPA mandates created from iDEAL and Sofort
- Express-checkout buttons with profile prefill documented for Amazon Pay, Apple Pay, Google Pay, Klarna and PayPal
Held against it
- Every actual rate arrives as a custom quote; we found no public information on rate amounts, chargeback fees or the currency-conversion markup
- We found no public information on 3-D Secure, SCA exemptions, liability shift or PCI DSS scope per integration type, and the terms place PCI DSS responsibility on the merchant
- We found no public information on dunning, smart retries, a card account updater, or any process for exporting payment tokens to another provider
- The privacy policy names international 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
- The terms permit unilateral rate changes on two months' notice, payment methods to be disabled at any time, and a security deposit returned no later than 12 months after termination without interest; we found no public information on a payment licence or supervisor
Best for
- You sell into the Netherlands, Belgium and wider European markets and want a broad, named set of local methods under one contract
- Your finance team needs bank-format reconciliation — CODA, MT940 or CAMT053 exports with SFTP and API matching — flowing into its own ERP
- You run basic weekly, monthly or annual subscriptions on card tokens and SEPA Direct Debit without needing advanced dunning or plan changes
Avoid if
- You must compute an effective fee before signing, since actual rates are quoted only after a sales conversation
- Your data-transfer policy bars transfers of personal data to Singapore, the United States, Malaysia or China
- You need rate stability, since the terms permit unilateral rate changes on two months' notice and payment methods can be disabled at any time
- You cannot budget around a security deposit returned no later than 12 months after termination with no interest paid
The scores
Payment methods & local coverage
Show reasoningHide reasoning
How this is scored
Which methods a European customer can actually pay with — cards and wallets, SEPA Direct Debit, and the local methods that decide conversion per country — judged on the named list per market rather than on a method count.
0 — Cards only, or a method list with no statement of which countries and currencies each one covers.
3 — Major cards and wallets plus one or two European methods, with local coverage stated vaguely ("many local methods") and no SEPA Direct Debit.
5 — Cards, Apple Pay and Google Pay, SEPA Direct Debit, and the main local methods for DACH and Benelux (iDEAL or Wero, Bancontact, Klarna or invoice) listed by name with the countries they serve.
8 — Broad EU coverage named per country — including methods such as BLIK, TWINT, Przelewy24, EPS and Wero — multi-currency acceptance with settlement currencies stated, and which methods support refunds and recurring charges documented per method.
10 — Coverage is documented as a matrix a merchant can plan against: every method with its countries, currencies, refund, partial-capture and recurring support, and the provider's own acquiring versus third-party routing stated per method.
The Finance Lead
Cards, Apple Pay, Google Pay, SEPA Direct Debit and the Benelux names are all there — iDEAL|Wero for the Netherlands, Bancontact for Belgium, Klarna and the in3/Billink instalment options — and the reach beyond is genuinely broad, with EPS, Przelewy24, Multibanco, MB Way, Bizum and Cartes Bancaires listed. But countries are stated for only some methods, and we found no public information on settlement currencies or on refund and recurring support per method outside the SEPA page, so I cannot plan a market entry against it. 5 6 8
The E-Commerce Lead
This is a named list, not just a count: iDEAL with Wero for the Netherlands, Bancontact for Belgium, Multibanco for Portugal, plus Cartes Bancaires, EPS, Przelewy24, Dankort, Bizum, MyBank, cards, Apple Pay, Google Pay, Klarna and SEPA Direct Debit — most of what my eight markets ask for. What holds it back from the top band: I found no public information on BLIK or TWINT, settlement currencies behind the multi-currency claim, or refund and recurring support documented per method (it is spelled out for SEPA only). 5 6 7 8
The SaaS Founder
The method list is named per market — iDEAL|Wero for the Netherlands, Bancontact for Belgium, plus EPS, Przelewy24, Cartes Bancaires, Multibanco, Bizum and more, with SEPA Direct Debit handling recurring collection and mandates created from iDEAL and Sofort. Multi-currency is claimed without settlement currencies being stated, and recurring and refund support is documented only for SEPA, with no per-method matrix; we found no public information on BLIK or TWINT. 1 5 6 7
The Payments Engineer
iDEAL | Wero, Bancontact, Klarna and a long named per-country list (EPS, Przelewy24, Multibanco, Dankort, Cartes Bancaires and more) plus SEPA Direct Debit with recurring and full and partial refunds means a merchant can plan most of Europe from these pages. It stops short of a full matrix: settlement currencies under the multi-currency feature are never stated, and refund and recurring support is documented for SEPA rather than per method. 5 6 7
The Compliance Officer
Cards, the major wallets, iDEAL|Wero, Bancontact, Klarna and a long named list of European methods are published with the market attached to the headline ones, alongside SEPA Direct Debit with cross-border collection and Sofort and iDEAL recurrence. We found no public information on settlement currencies, on BLIK or TWINT, or on refund and recurring support documented per method. 5 6 7
The Skeptic
A long, named list with markets attached — iDEAL|Wero for the Netherlands, Bancontact, Multibanco, Bizum, EPS, Przelewy24, plus SEPA Direct Debit with cross-border collection — is something a buyer can plan against. But the multi-currency claim names no settlement currencies, and we found no public information on which methods support refunds or recurring charges beyond SEPA and card tokens; no BLIK or TWINT appears on the captured pages. 5 6 7
Checkout, SCA & fraud
Show reasoningHide reasoning
How this is scored
The path from basket to authorised payment under PSD2: hosted and embedded checkout options, 3-D Secure and SCA exemption handling, fraud screening, and what the provider documents about keeping legitimate payments from failing.
0 — A single redirect page with no statement on 3-D Secure, SCA or fraud screening.
3 — Hosted checkout with 3-D Secure 2 mentioned, fraud screening as an unexplained add-on, and no word on exemptions or declined-payment handling.
5 — Hosted and embedded checkout options, 3-D Secure 2 with SCA handled by the provider, configurable fraud rules, and the resulting PCI DSS scope for each integration type stated.
8 — SCA exemptions (low value, transaction risk analysis, merchant-initiated) applied and documented, fraud tooling with rules and risk scores exposed to the merchant, network tokens or account updater, and liability shift explained per flow.
10 — Authorisation is engineered and shown: exemption strategy documented, soft-decline retry handled, authorisation-rate reporting by method and issuer country, and a checkout the merchant can run in their own domain while staying at the lowest PCI scope.
The Finance Lead
Hosted and embedded checkout plus express buttons for Apple Pay, Google Pay, PayPal and Klarna are documented, but fraud screening appears only as "in-house risk and fraud monitoring" with nothing behind it. We found no public information on 3-D Secure, SCA exemptions, PCI DSS scope per integration type or liability shift, and that silence is exactly what I would need settled before trusting the authorisation path. 2 6 7 8
The E-Commerce Lead
Hosted and embedded checkout both exist, and the express-checkout work (Amazon Pay, Apple Pay, Google Pay, Klarna, PayPal with profile prefill) is exactly the conversion kit I look for, with Click to Pay and iDEAL express flagged as coming soon for the Dutch market. But I found no public information on 3-D Secure, SCA exemption strategy, declined-payment handling or fraud rules I could configure — fraud appears only as an in-house monitoring service — and the terms put PCI DSS responsibility on the merchant rather than stating scope per integration type. 2 4 6 8
The SaaS Founder
Hosted and embedded checkouts plus express buttons with data prefill are all present, and fraud screening appears only as an unexplained "in-house risk and fraud monitoring" line. But the captured pages never mention 3-D Secure, SCA, exemptions or PCI scope per integration — under PSD2 I would be authorising blind. 2 5 6 8
The Payments Engineer
Hosted, embedded and a decent set of express checkout buttons with prefill exist, but I found no public information on 3-D Secure, SCA exemptions, liability shift or declined-payment handling beyond one unexplained in-house risk and fraud monitoring mention. The terms push PCI DSS responsibility onto the merchant without stating the scope of each integration type, and there is no word on fraud rules or risk scores exposed to the merchant. 2 4 6 8
The Compliance Officer
Hosted, embedded and express checkout routes are documented, and in-house risk and fraud monitoring is stated as a single item on the pricing page. We found no public information on 3-D Secure, SCA exemptions, fraud rules exposed to the merchant, or the PCI DSS scope of each integration type. 2 6 8
The Skeptic
Hosted, embedded and express checkouts are all documented, but the PSD2 machinery is invisible: we found no public information on 3-D Secure, SCA exemption handling or liability shift, and fraud screening is one unexplained line — "In-house risk and fraud monitoring". The terms also put PCI DSS responsibility squarely on the merchant rather than stating scope per integration type. 2 4 6 8
Subscriptions & recurring payments
Show reasoningHide reasoning
How this is scored
Charging the same customer again: card-on-file and merchant-initiated transactions, SEPA mandates, subscription logic and dunning — and whether the stored payment credentials can leave with the merchant.
0 — No stored payment methods; every charge needs the customer to pay again.
3 — Card-on-file tokens for repeat charges, but no SEPA mandate handling, no subscription logic, and failed-payment handling left entirely to the merchant.
5 — Stored cards and SEPA Direct Debit mandates, merchant-initiated transactions documented, and basic subscription plans with scheduled charges and failed-payment notifications.
8 — Subscription billing with trials, proration and plan changes, smart retries and dunning, card account updater, mandate management with pre-notification, and a documented process for exporting payment tokens to another provider.
10 — Recurring revenue is a first-class product: usage-based and invoice-based billing, dunning with measurable recovery, token migration in and out documented with a stated timeline and format, and recurring support stated for every local method that allows it.
The Finance Lead
Encrypted card tokens, a zero-euro verification to set them up, and SEPA Direct Debit that "makes recurring payments easy to process" with Sofort and iDEAL support make a workable recurring base, with weekly, monthly and annual plans and in-house e-invoicing on top. We found no public information on dunning, smart retries, a card account updater, or a process for exporting the stored tokens to another provider, so both the recovery rate and the exit path are unproven. 5 6 9
The E-Commerce Lead
The basics are in place for my DACH and Benelux subscribers: encrypted card tokens with a 0 EUR verification before the first charge, automated payment plans weekly, monthly or annually, SEPA Direct Debit with recurring including iDEAL and Sofort, and automated invoice chasing by email, letter, SMS and WhatsApp. I found no public information on trials, proration, plan changes, smart retries or dunning, an account updater, mandate pre-notification, or any process for exporting tokens to another provider. 5 6 9
The SaaS Founder
Encrypted tokens with a zero-euro verification charge, SEPA Direct Debit mandates, and weekly, monthly and annual plans cover the basics of subscription billing for B2B and B2C. But this is where my churn lives, and the pages show no proration, no retries or dunning, no account updater and — the deal-breaker for me — we found no public information on any process for exporting payment tokens to another provider. 2 5 6 9
The Payments Engineer
The recurring core is real: encrypted tokens, a 0 EUR pre-authorisation to verify cards, MDES network tokenisation, automated weekly/monthly/annual plans and SEPA mandates with conversion from Sofort and iDEAL. I found no public information on smart retries, dunning recovery, mandate pre-notification, or any documented process for exporting tokens to another provider. 5 6 9
The Compliance Officer
Encrypted card tokens with a zero-euro verification, automated recurring plans at weekly to annual frequencies, and SEPA Direct Debit collection are documented for subscriptions. We found no public information on mandate pre-notification, dunning or failed-payment handling, account updater, or a process for exporting tokens to another provider. 6 9
The Skeptic
Encrypted card tokens with a 0 EUR verification, SEPA Direct Debit recurring across Europe, and weekly-to-annual subscription plans are evidenced. But we found no public information on dunning, smart retries, card account updater, mandate pre-notification, or any process to export payment tokens to another provider — nothing shows the stored credentials can leave. 6 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 — Payouts on an unstated schedule, one net amount per payout, and no API or report beyond an on-screen list.
3 — A stated payout schedule and CSV exports, but fees netted invisibly into payouts and an API with thin documentation.
5 — Payout frequency and delay stated, per-transaction fee breakdown in reports, a documented REST API with webhooks and a test mode, and exports that link each payout to its transactions.
8 — Configurable payout schedules and settlement currencies, reconciliation reports that match bank lines, accounting integrations or exports named, a versioned API with idempotency and published rate limits, and a public status page with incident history.
10 — Finance can close the month from the provider's data: interchange and scheme fees itemised per transaction, automated reconciliation to the ledger, a deprecation policy for the API, and full historical data exportable after the contract ends.
The Finance Lead
Payout terms are written down — daily payouts, transfer no later than 1 to 7 working days after receipt of funds, to a European bank account only — and the accounting side is unusually strong, with CODA, MT940 and CAMT053 exports, SFTP push or pull, automated reconciliation and an API for payment matching into my own ERP. What I miss is the itemisation: we found no public information on a per-transaction fee breakdown in reports, webhooks, published rate limits or a status page, so I still cannot tie every payout line to its fees. 2 4 10
The E-Commerce Lead
Payout timing is written down (within 1 to 7 working days after receipt of funds, daily payouts claimed), and reconciliation is treated as a product: CODA, MT940 and CAMT053 exports, automated payment matching through the API, SFTP push and pull, scheduled reports, a test account and a published API reference. I found no public information on a per-transaction fee breakdown in reports, webhooks, configurable payout schedules or settlement currencies, or a public status page with incident history. 2 4 9 10
The SaaS Founder
Payout timing is stated (daily payouts, funds transferred within 1 to 7 working days) and the reconciliation material is real: CODA, MT940 and CAMT053 exports, SFTP push and pull, scheduled reports and API retrieval into our own ERP or data lake. But we found no public information on per-transaction fee itemisation, webhooks, API versioning or a status page, so month-end still needs stitching together. 2 4 10
The Payments Engineer
Payout timing is stated in the terms, daily payouts are offered, a free test account exists, and the CODA, MT940 and CAMT.053 exports with SFTP push and pull are exactly what a finance team needs to match bank lines — but no per-transaction fee breakdown is shown anywhere. I found no public information on webhooks, API versioning, idempotency, rate limits or a public status page with incident history, and the terms only say 24/7 availability is strived for and cannot be guaranteed. 2 4 6 10
The Compliance Officer
Payout cadence and delay are written down — daily payouts, funds transferred within one to seven working days — and reconciliation is concrete with CODA, MT940 and CAMT053 exports, accounting plugins, scheduled SFTP reports and API retrieval for payment matching. We found no public information on per-transaction fee itemisation, webhooks, API idempotency and rate limits, or a public status page with incident history. 2 4 10
The Skeptic
The payout delay is written down honestly — no later than 1 to 7 working days after receipt of the funds — and the reconciliation tooling is real: CODA, MT940 and CAMT053 exports, accounting plugins, an API for automated matching and SFTP push or pull. We found no public information on a per-transaction fee breakdown, webhooks, or a public status page with incident history. 2 4 10
Licence, risk & account terms
Show reasoningHide reasoning
How this is scored
Who holds the merchant's money under which licence, and what the contract lets the provider do on a bad day: freezes, reserves, termination, chargebacks. Scored on what the terms and the imprint state, not on reputation.
0 — No regulated entity named; terms allow freezing funds and terminating the account at any time with no notice, reason or timeline.
3 — A licence mentioned without the entity, supervisor or register number, and terms that permit reserves and holds with no stated limits.
5 — The regulated entity named with its supervisor and licence type, safeguarding of merchant funds stated, chargeback fees and dispute process published, and a notice period for ordinary termination.
8 — Entity, supervisor, register number and passporting stated per country; reserve and rolling-hold conditions defined with limits and release timelines; freeze and termination terms with reasons and a route to appeal; PCI DSS level and attestation published.
10 — The bad day is written down: every regulated entity in the chain named with register links, reserve calculation disclosed, funds release timelines after termination committed, a documented complaint route to the supervisor, and exit terms that include handing back payment tokens and transaction history.
The Finance Lead
The contracting entity is named to the digit — MultiSafepay B.V. of Amsterdam, Chamber of Commerce 34156361, with a Foundation at 34245794 — and ordinary termination carries two months' notice, with the security deposit returnable no later than 12 months after termination and no interest paid. But we found no public information on the licence or supervisor, safeguarding of merchant funds, a chargeback fee, or any limit or calculation for when a security deposit is taken — a reserve I cannot size is a reserve I cannot budget. 3 4
The E-Commerce Lead
MultiSafepay B.V. of Amsterdam is named with Chamber of Commerce number 34156361, ordinary termination carries a two-month notice, a security deposit is committed back within twelve months of termination without interest, and there is a 14-day dispute window with chargeback reclaim possible up to a year after payment. I found no public information on the supervisor or licence type, chargeback fee amounts, or PCI DSS level; the terms also allow payment methods to be disabled at any time and rates to be changed unilaterally with two months' notice. 4
The SaaS Founder
Chamber of Commerce numbers are published for both MultiSafepay B.V. and the Amsterdam Foundation through which funds flow, with a two-month termination notice, a 14-day dispute window and the security deposit returned no later than 12 months after termination without interest. But we found no public information on licence type, supervisor or licence register number, and the terms still allow unilateral rate changes, payment methods disabled at any time, and a fine of €200 per day of violation for negotiating rates with third parties. 3 4
The Payments Engineer
MultiSafepay B.V. is named with its Amsterdam address and Chamber of Commerce number 34156361, and a separate Foundation (34245794) sits in the payout chain — but no licence type, supervisor or passporting is stated anywhere I can see, which a PSP's terms should say in line one. On the bad day there are defined timelines (two months' notice for termination and rate changes, a twelve-month cap on returning the security deposit with no interest, a 14-day dispute window), yet reserves can be withheld without a disclosed calculation, payment methods can be disabled at any time, and no chargeback fee or appeal route is published. 3 4
The Compliance Officer
MultiSafepay B.V. is named with its Amsterdam address and Chamber of Commerce number 34156361, and the terms show real discipline: two months' notice for termination and rate changes, a security deposit returned within twelve months of termination, and a fourteen-day dispute window. We found no public information on the financial licence, the supervisor, safeguarding of merchant funds, or chargeback fees — the Chamber of Commerce number is a company register, not a licence register, and payment methods may be disabled at any time. 4
The Skeptic
The contracting entity and its collecting Foundation are named with Chamber of Commerce numbers, but we found no public information on a payment licence, supervisor or licence register number — for a collecting provider, that is the number I look for first. The terms allow unilateral rate changes on two months' notice, immediate termination for GDPR violations, and a security deposit held up to 12 months interest-free; no chargeback fee appears on the captured pages, though a 12-month chargeback reclaim window and a 14-day dispute window are stated. 3 4
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting and regulated entity is, and where transaction and cardholder data are processed and stored. Independently sourced by the sovereignty pipeline. The card schemes are US-based for every provider, so the scheme layer is not held against any one vendor; the part the vendor controls is.
0 — Non-EU contracting entity, no statement on where payment data is processed, and subprocessors unnamed.
3 — An EU licensed entity contracts, but payment and customer data is processed outside the EU by default without an explained safeguard, or the subprocessor list is absent.
5 — EU contracting and regulated entity, EU processing stated for core payment data, but the group parent or significant parts of the chain (fraud scoring, support, analytics) are non-EU without a stated safeguard.
8 — EU entity and EU licence, payment and cardholder data processed and stored in the EU on named infrastructure, subprocessor list published with locations, and a DPA covering the processing the provider does as processor versus as controller.
10 — Sovereign end to end and evidenced: European ownership, EU entity and licence, every processing location and subprocessor European, European rails (SEPA, Wero or national schemes) offered alongside cards, and certifications published.
The Finance Lead
A Dutch entity contracts under Dutch law, a subprocessor list is published, and transfers outside the EEA are covered by standard contractual clauses. But the privacy notice names Singapore, the United States, Malaysia and China as transfer destinations for the technical infrastructure, the group parent is named as Ant International with no domicile stated on the page, and we found no public information stating where payment and cardholder data themselves are processed. 3 4
The E-Commerce Lead
An Amsterdam entity contracts, a subprocessor list is published, and international transfers are disclosed rather than hidden — Singapore, the United States, Malaysia and China are named for technical infrastructure and business structure, with standard contractual clauses given as the mechanism. But nothing on the captured pages states where payment and cardholder data is processed by default, subprocessor locations are not given, and the group parent is named as Ant International. 3 4
The SaaS Founder
MultiSafepay B.V. in Amsterdam contracts, but the privacy policy discloses transfers to Singapore, Malaysia, China, the United States and the United Kingdom "to accommodate our technical infrastructure", covered by standard contractual clauses, with the parent named as Ant International. We found no public information on where payment and cardholder data are processed or stored by default, or on subprocessor locations. 3 4
The Payments Engineer
An Amsterdam entity contracts, and transfers outside the EEA carry Standard Contractual Clauses with a published subprocessor list, which lifts this above the floor. But I found no public information stating where payment and cardholder data is processed or stored, and the privacy notice names Ant International as the group parent while international transfers run to Singapore, the United States, Malaysia and China for technical infrastructure and business structure. 3 4
The Compliance Officer
A Dutch entity contracts, Standard Contractual Clauses cover third-country transfers, and a DPO and GDPR rights are published, yet the privacy policy itself lists Singapore, the United States, Malaysia and China among transfer destinations for its technical infrastructure. We found no public information on where transaction and cardholder data are processed and stored, and the subprocessor list is referenced without names or locations captured; the group parent also differs between the provenance summary and the captured privacy policy. 3 4
The Skeptic
A Dutch entity contracts, but the privacy policy names international transfers of personal data to Singapore, the United States, Malaysia and China "to accommodate our technical infrastructure", with Standard Contractual Clauses as the only stated safeguard. We found no public information on where payment and cardholder data are processed or stored, and the group parent is Ant International. 3 4
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the effective fee for their own mix of cards, countries and methods — including cross-border and currency conversion markups, chargebacks, refunds, payouts and monthly fees — from public pages alone.
0 — No public prices at all; every rate is a sales conversation.
3 — A headline percentage exists, but it is unclear which cards and countries it covers, and cross-border, currency conversion or chargeback fees are unstated — the effective fee is unknowable.
5 — Rates published per main method with domestic and international cards distinguished, but at least one commonly incurred cost (currency conversion markup, chargeback fee, payout or monthly fee) is missing or "on request".
8 — Every method priced publicly, cross-border and currency conversion markups stated, chargeback, refund and payout fees listed, minimum monthly fees and contract term given, and whether the model is blended or interchange++ said plainly.
10 — Complete fee computability: the effective rate derivable for a given volume, card mix and country mix — interchange++ with the markup published or a blended rate with every exception listed — plus volume tiers, reserves and every ancillary fee on a public page.
The Finance Lead
The pricing page confirms you only pay for successful transactions with no startup or monthly fees, but every actual rate arrives as a custom quote after telling them about your business — there is no public percentage to compute anything from. The terms add that currency conversion costs are passed on to the merchant, prices are exclusive of VAT, and rates can change unilaterally on two months' notice, while we found no public information on chargeback, refund or payout fees or whether the model is blended or interchange-plus-plus; the effective fee is unknowable in advance. 2 4 6
The E-Commerce Lead
Pricing is quote-based — "Provide us with some information about your business, and we'll get back to you with a pricing offer made for you" — so I cannot compute an effective fee for my card and country mix from public pages at all. The structure is at least stated plainly (per-transaction billing, no startup or monthly fees, "Only pay for successful transactions", prices exclusive of VAT, currency conversion costs passed on to the merchant), but I found no public information on rate amounts, cross-border markups or chargeback fees. 2 4
The SaaS Founder
The public pages publish no rates at all — "Transparent pricing per transaction" resolves to a form: "we'll get back to you with a pricing offer made for you." What is public is structural: no startup or monthly fees, payment only for successful transactions, currency conversion costs "passed on to Merchant" at an unstated rate, and no chargeback fee; the effective fee for my SEPA-heavy renewal mix is not computable from these pages. 2 4 6
The Payments Engineer
The pricing page confirms no startup or monthly fees and that merchants are charged per transaction, but the rate itself is a sales conversation — the offer is made for you after you provide business information — so no merchant can compute an effective fee for their card or country mix. Currency conversion costs are passed on to the merchant without figures, chargeback fees are unstated, prices are exclusive of VAT, and rates can be changed unilaterally with two months' notice. 2 4 6
The Compliance Officer
The pricing page describes the model — per transaction, no startup or monthly costs, only successful transactions charged — but every actual rate arrives as a custom quote after a sales conversation. Currency conversion costs are said to be passed on without any rate, and we found no public information on chargeback fees, cross-border fees or the security deposit amount. 2 4 6
The Skeptic
No rate appears on any captured page — pricing is a quote ("we'll get back to you with a pricing offer made for you"), so the effective fee is unknowable before a sales conversation. The model is public (per transaction, no startup or monthly fees, VAT excluded), and the terms admit currency conversion costs are "passed on to Merchant" without stating the markup. We found no public information on chargeback, refund or payout fees, and the terms permit unilateral rate changes on two months' notice plus a €200-per-day fine if the merchant negotiates rates through a third party. 2 4 6
European sovereignty — proven facts
2 of 4 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 NL | 3/3 pts | 4 Report an error |
|---|---|---|---|
| Ownership | Foreign-controlled ⚠ unverified | 0/2 pts | 3 Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Ownership. The page names Ant International as parent but does not state its domicile or shareholder structure, so the foreign (non-EU, Singapore-based Ant Group affiliate) classification is inferred from the group's identity rather than stated on the page.
- 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.
- 29 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
- 12 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
- 8 support 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
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.multisafepay.com Checked 22 Sep 2026 Details →
- 2 Pricing page www.multisafepay.com Checked 22 Sep 2026 Details →
- 3 Privacy policy www.multisafepay.com Checked 22 Sep 2026 Details →
- 4 Terms of service www.multisafepay.com Checked 22 Sep 2026 Details →
- 5 Payment methods & local coverage — found from sitemap www.multisafepay.com Checked 1 Oct 2026 Details →
- 6 Payment methods & local coverage — found from sitemap www.multisafepay.com Checked 1 Oct 2026 Details →
- 7 Checkout, SCA & fraud — found from sitemap www.multisafepay.com Checked 1 Oct 2026 Details →
- 8 Checkout, SCA & fraud — found from sitemap www.multisafepay.com Checked 1 Oct 2026 Details →
- 9 Subscriptions & recurring payments — found from sitemap www.multisafepay.com Checked 1 Oct 2026 Details →
- 10 Settlement, reconciliation & API — found from sitemap www.multisafepay.com Checked 1 Oct 2026 Details →