SlimPay
Provenance unknown Report an errorPanel 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 SlimPay SAS · slimpay.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
SlimPay at a glance
- Vendor
- SlimPay SAS
- Headquarters
- Not stated on the vendor’s pages as of 2 Nov 2026
- Data hosting
- In the EU by default source, captured 2 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 2 Nov 2026
- Panel verdict
- The AI panel rates SlimPay 2.5/5, the mean of 6 judges. how scores are made
- As of
- Vendor pages captured 29 Sep 2026 to 2 Nov 2026; evaluated by the panel 3 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
No written verdict for this product
The panel scored SlimPay, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 2 of 5 |
| Checkout, SCA & fraud | 2 of 5 |
| Subscriptions & recurring payments | 3.5 of 5 |
| Settlement, reconciliation & API | 3 of 5 |
| Licence, risk & account terms | 2 of 5 |
| European sovereignty | 3.5 of 5 |
Payment methods & local coverage
Show reasoningHide reasoning
How this is scored
Which methods a European customer can actually pay with — cards and wallets, SEPA Direct Debit, and the local methods that decide conversion per country — judged on the named list per market rather than on a method count.
0 — Not a payment acceptance product; customers cannot pay through it.
3 — Card payments with the major schemes, plus wallets such as Apple Pay or Google Pay.
5 — Cards and wallets plus SEPA Direct Debit and several European local methods (for example iDEAL or Wero, Bancontact, Klarna, EPS) listed by name.
8 — Broad EU coverage named per country with the countries and currencies each method serves — including methods such as BLIK, TWINT, Przelewy24, EPS and Wero — multi-currency acceptance with settlement currencies stated, and which methods support refunds and recurring charges documented per method.
10 — Coverage is documented as a matrix a merchant can plan against: every method with its countries, currencies, refund, partial-capture and recurring support, and the provider's own acquiring versus third-party routing stated per method.
The Finance Lead
SEPA Direct Debit Core and B2B, SEPA Credit Transfers and open banking payments are named and processed in euros across the euro zone (36 countries), which is a genuinely deep single rail. We found no public information on cards, wallets, or other local methods such as iDEAL or BLIK, and settlement is euro only. 3 4 1
The E-Commerce Lead
Customers can genuinely pay through this — SEPA Direct Debit (Core and B2B), SEPA Credit Transfers and open banking across the euro zone in euros only, with the local names of direct debit given for France, Spain, Belgium and Germany, which I appreciate even if the captured pages give different figures for the country count (36 versus 34). For my eight markets, though, we found no public information on cards or wallets, and no per-country matrix naming methods with their currencies, refunds and recurring support. This is a single-rail account-to-account product, not the local-method coverage I plan per market against. 1 3
The SaaS Founder
The vendor's own pages describe a single currency — euros — processed as SEPA Direct Debit (Core and B2B), SEPA Credit Transfers and open banking across the euro zone, with SEPA's local names given for France, Spain, Belgium and Germany; we found no public information on cards, wallets, or country-specific methods such as iDEAL or BLIK. For my SEPA renewals that rail is deep, but a checkout with no card option anywhere in the captures is a conversion question I cannot ignore. 3 4 1
The Payments Engineer
SEPA Direct Debit Core and B2B, SEPA Credit Transfer and open-banking collection are named with their per-country local names, and mandate signing plus one-off or recurring debit flows are documented in detail. Everything settles in euros, and the captured pages give different figures for the covered country count (36 on the vendor page, 34 in the SEPA overview). We found no public information on cards, wallets, or other local methods such as iDEAL, Bancontact or BLIK. 3 4 5 1
The Compliance Officer
The documented methods are SEPA Direct Debit Core and B2B, SEPA Credit Transfers and open-banking payment initiation, all denominated in euros across the euro area, with direct debit's local names given for France, Spain, Belgium and Germany. We found no public information on card or wallet acceptance or on a per-country coverage matrix, and the captured pages give different figures for the number of countries covered (34 and 36). 3 4 1
The Skeptic
Customers pay by SEPA Direct Debit (Core and B2B), SEPA Credit Transfer and open banking, all in euros across the 36-country euro zone, with the local names for direct debit given for France, Spain, Belgium and Germany. We found no public information on card or wallet acceptance or a per-country matrix of which method serves which market — this is one rail family, deep rather than broad. 3 4 1
Checkout, SCA & fraud
Show reasoningHide reasoning
How this is scored
The path from basket to authorised payment under PSD2: hosted and embedded checkout options, 3-D Secure and SCA exemption handling, fraud screening, and what the provider documents about keeping legitimate payments from failing.
0 — No checkout or payment form; the product does not take a payment to authorisation itself.
3 — A hosted payment page or payment links with 3-D Secure.
5 — Hosted and embedded checkout options, 3-D Secure 2 with SCA handled by the provider, and fraud screening with configurable rules.
8 — SCA exemptions (low value, transaction risk analysis, merchant-initiated) applied and documented, the PCI DSS scope of each integration type stated, fraud tooling with rules and risk scores exposed to the merchant, network tokens or account updater, and liability shift explained per flow.
10 — Authorisation is engineered and shown: exemption strategy documented, soft-decline retry handled, authorisation-rate reporting by method and issuer country, and a checkout the merchant can run in their own domain while staying at the lowest PCI scope.
The Finance Lead
A hosted checkout documented in pop-in, iframe, redirect and API modes plus payment links, with mandate and document signature flows and mobile optimisation, which is real flexibility. We found no public information on 3-D Secure or SCA exemption handling, and the only fraud measure described is legally mandated transaction monitoring rather than merchant-configurable screening. 5 6 2
The E-Commerce Lead
The checkout options are genuinely good for my funnel: pop-in, an iFrame that sits inside my own page, a redirect that can be merchant-hosted under a white-label option, and an API mode where I build the UI myself — plus payment links and mandate-with-document signature combinations. But it is a direct-debit checkout, and we found no public information on 3-D Secure, SCA exemptions or fraud rules I could configure; the transaction monitoring described is a legal anti-money-laundering obligation, not merchant-tunable screening. Strong on staying near my domain, silent on everything PSD2-card-side that decides my authorisation rates. 2 5 6
The SaaS Founder
Four integration modes are documented — pop-in, iframe, redirect and a full API where the merchant builds their own interface — plus payment links, mobile optimisation, and mandate signing combined with document e-signature and an initial debit or payment plan. We found no public information on SCA exemption handling, merchant-configurable fraud rules, or liability shift; the transaction monitoring described is the legally mandated kind rather than a fraud product for merchants. 5 6 1 2
The Payments Engineer
Checkout is documented in four integration modes — pop-in, iframe, redirect, and an API mode where I build my own interface and submit the mandate signature or payment order myself — with a mobile-optimised flow and payment links among the features. We found no public information on 3-D Secure or SCA exemption handling, and none on the PCI scope of each integration type. The only anti-fraud statement is transaction monitoring performed under French anti-money-laundering law, a legal obligation rather than rules I can configure. 2 5 6 1
The Compliance Officer
Four checkout integration modes are documented — pop-in, iFrame, redirect and an API mode where the merchant builds its own interface — covering mandate signature alone or combined with document signature, an initial direct debit or a payment plan. We found no public information on 3-D Secure or SCA exemption handling, PCI scope by integration type, or fraud rules a merchant could configure; the fraud evidence captured is transaction monitoring performed under a French anti-money-laundering legal obligation. 2 5 6
The Skeptic
Four checkout integration modes are documented in detail — pop-in, iFrame, redirect and a build-your-own API mode — plus payment links and a mobile-optimised flow. We found no public information on SCA exemption handling, 3-D Secure, PCI scope, or fraud screening a merchant could configure; the only fraud measure described is transaction monitoring the provider runs to satisfy a French anti-money-laundering obligation. 2 5 6 1
Subscriptions & recurring payments
Show reasoningHide reasoning
How this is scored
Charging the same customer again: card-on-file and merchant-initiated transactions, SEPA mandates, subscription logic and dunning — and whether the stored payment credentials can leave with the merchant.
0 — One-off payments only; the product stores no payment method for a later charge.
3 — Saved cards (card-on-file) charged again for repeat or recurring payments.
5 — Stored cards and SEPA Direct Debit mandates for recurring charges, merchant-initiated transactions, and subscriptions or scheduled payments with notification of failed payments.
8 — Subscription billing with trials, proration and plan changes, smart retries and dunning, card account updater, mandate management with pre-notification, and a documented process for exporting payment tokens to another provider.
10 — Recurring revenue is a first-class product: usage-based and invoice-based billing, dunning with measurable recovery, token migration in and out documented with a stated timeline and format, and recurring support stated for every local method that allows it.
The Finance Lead
Mandates for one-off and recurring direct debits and payment plans, automatic resubmission of failed payments, and a full mandate lifecycle from bulk import through IBAN change with history to revocation, with downloadable exports carrying the mandate reference and IBAN. We found no public information on subscription plan logic such as trials or proration, dunning recovery, or a documented process for moving mandates to another provider. 3 5 8 1
The E-Commerce Lead
This is the heart of the product and it shows: mandate signing by link, delegation or import with compliance validation, custom PDF templates, revocation, IBAN changes with history, a signed copy emailed to the debtor, payment plans, automatic retry, and a downloadable mandate export carrying the mandate reference, IBAN and status. We found no public information on subscription logic such as trials, proration and plan changes, or on dunning recovery, and the export is not framed as a documented migration of credentials to another provider. 1 5 7 8
The SaaS Founder
This is the heart of the product: the SEPA mandate lifecycle end to end — signing by link, by delegation or by importing existing mandates in bulk, revocation, IBAN changes with history, custom templates, signed copies emailed to debtors — plus automatic resubmission of failed payments and a downloadable mandate export carrying the mandate reference and IBAN, which is what portability means for SEPA credentials. What I miss is billing logic: we found no public information on trials, proration, plan changes or dunning communication beyond automatic retry, and the pages point to partners for subscription management. 5 7 8 1
The Payments Engineer
Recurring collection is the product's centre of gravity: electronic mandate signature standalone or bundled with an initial debit and payment plan, bulk mandate import behind compliance validation, IBAN updates with history, revocation, and a mandate export carrying the unique mandate reference and IBAN. Failed payments are recovered by automatic resubmission, and R-transaction files report rejects and returns. We found no public information on retry scheduling or dunning depth, pre-notification of debits, or subscription logic such as trials, proration and plan changes. 5 7 8 10 1
The Compliance Officer
The SEPA mandate lifecycle is managed end to end — electronic signature, import of existing mandates after compliance validation, bulk import, revocation, debtor notification with a signed copy, and export files carrying the mandate reference and IBAN — and failed payments are resubmitted automatically under a stated retry capability. Payment plans and recurring direct debits are the product's core; we found no public information on trials, proration or plan changes, on dunning with measurable recovery, or on a stated timeline and format for migrating mandates to another provider. 5 8 10 1
The Skeptic
This is the product's centre: a full SEPA mandate lifecycle — electronic signature, import, IBAN change with history, revocation, and exports carrying the unique mandate reference and IBAN — plus payment plans and automatic resubmission of failed payments. We found no public information on dunning workflows, trials or proration, or a documented timeline for migrating mandates to another provider. 5 8 10 1
Settlement, reconciliation & API
Show reasoningHide reasoning
How this is scored
Getting the money and knowing what it was: payout cadence and currencies, fee itemisation per transaction, reports that match a bank statement, and an API and webhooks a team can build finance processes on.
0 — No merchant reporting: the product is a payment button or link with no dashboard, report or API.
3 — A dashboard of transactions and payouts, a stated payout schedule, and CSV export.
5 — The payout schedule stated, reports or exports that link each payout to its transactions and fees, and a documented API with webhooks and a test mode.
8 — Configurable payout schedules and settlement currencies, reconciliation reports that match bank lines, accounting integrations or exports named, a versioned API with idempotency and published rate limits, and a public status page with incident history.
10 — Finance can close the month from the provider's data: interchange and scheme fees itemised per transaction, automated reconciliation to the ledger, a deprecation policy for the API, and full historical data exportable after the contract ends.
The Finance Lead
A stated average payout time of 24 hours, CSV account-statement reports listing every operation with execution and value dates, credits, debits and fee lines by nature, a balance summary separating the reserve from pending transfers, monthly invoicing by email, and a documented developer centre for reporting. We found no public information on webhooks, a test mode, or API versioning and rate limits. 9 10 1 8
The E-Commerce Lead
The reporting pages are concrete: an account-statement report in.csv listing every direct debit, transfer and fee line with transaction IDs, a funds formula of balance minus reserve minus pending transfers and fees, distinct fee categories for direct debits, rejections, returns, refunds and fund transfers, a monthly invoice, report automation on request, and a stated '24h Average payout time'. A public Dev Center and dashboard-or-API reporting are referenced; we found no public information on webhooks, a test mode, idempotency, rate limits or a status page. 1 8 9 10
The SaaS Founder
A 24-hour average payout time is stated, and the CSV reporting is a detailed account-statement equivalent with per-transaction fee lines for direct debits, rejects, returns, refunds and fund transfers, invoice references, initial-transaction links and a balance-to-available-funds breakdown that nets out the €300 coverage; an API with a developer centre is referenced and report automation is available on request. We found no public information on webhooks, a test mode, configurable payout schedules, or accounting exports named by product. 8 9 10 1
The Payments Engineer
Reporting is genuine reconciliation material: CSV account statements described as the equivalent of a detailed bank statement, with execution and value dates, credit and debit values, invoice reference and a fee line per nature (direct debits, rejects, returns, refunds, fund transfers), plus a balance view separating reserve from available funds; payout is stated as a 24-hour average. A developer centre documents the mandate and reporting APIs. We found no public information on webhooks, a test mode, API versioning, idempotency keys, rate limits or a public status page — exactly the pieces I need before wiring finance processes to a provider. 8 9 10 1
The Compliance Officer
Reporting is documented in practical depth: account-statement-equivalent CSV files listing every operation with its nature and fee category, balance and available-funds arithmetic that nets out reserves and pending transfers, mandate reports and R-transaction files, automatable by frequency, plus a documented API and developer centre. An average payout time of 24 hours is stated; we found no public information on webhooks, a test mode, API versioning or rate limits, configurable payout schedules or settlement currencies, or a public status page. 8 9 10 1
The Skeptic
The reporting is reconciliation-grade in outline: a CSV account statement with named columns for value date, credit and debit amounts and an invoice reference, fees itemised by type (direct debits, rejects, returns, refunds, fund transfers), a stated funds formula of balance minus reserve minus pending transfers, and a 24h average payout time. We found no public information on configurable payout schedules, webhooks and a test mode, a public status page, or API versioning and idempotency. 8 9 10 1
Licence, risk & account terms
Show reasoningHide reasoning
How this is scored
Who holds the merchant's money under which licence, and what the contract lets the provider do on a bad day: freezes, reserves, termination, chargebacks. Scored on what the terms and the imprint state, not on reputation.
0 — The terms let the provider freeze funds or close the account at any time with no notice, reason or timeline.
3 — The regulated entity or the licensed partner behind the payments named, and a chargeback or dispute process described.
5 — The regulated entity named with its supervisor or licence type, the dispute process and chargeback fee published, and either safeguarding of merchant funds or a notice period for ordinary termination stated.
8 — Entity, supervisor, register number and passporting stated per country; safeguarding stated; reserve and rolling-hold conditions defined with limits and release timelines; freeze and termination terms with reasons and a route to appeal; PCI DSS level and attestation published.
10 — The bad day is written down: every regulated entity in the chain named with register links, reserve calculation disclosed, funds release timelines after termination committed, a documented complaint route to the supervisor, and exit terms that include handing back payment tokens and transaction history.
The Finance Lead
A named French company with an RCS register number, authorised and supervised by the ACPR as a payment institution acting as both processor and acquirer, and the payment-account coverage actually written down: a 300 euro minimum balance made of a fixed plus variable reserve, with no fixed reserve for SDD B2B. We found no public information on safeguarding of merchant funds, a dispute or chargeback process with fees, or freeze and termination terms. 1 2 3 10
The E-Commerce Lead
The chain is named: SlimPay SAS, registered office 12 rue Godot de Mauroy 75009 Paris, RCS 518 991 336, an authorised payment institution supervised by ACPR acting as both technical payment provider and acquirer, with a 'Minimum balance: €300 coverage' reserve defined and no fixed reserve for business-to-business direct debit. Debtor return and refund windows (8 weeks and 13 months) are described; we found no public information on safeguarding of merchant funds, termination notice, freeze conditions, an appeal route or the amounts of dispute-related fees. 1 2 3 10
The SaaS Founder
The regulated entity is named and concrete — SlimPay SAS, registered office in Paris, RCS 518 991 336, authorised and supervised by the ACPR as a payment institution acting as both technical payment provider and acquirer — and the pages publish SEPA dispute mechanics (returns within 8 weeks and 13 months) plus a €300 minimum balance defined as a fixed plus variable reserve, with no fixed reserve for B2B direct debits. We found no public information on safeguarding of merchant funds, ordinary termination notice, freeze conditions or a route to appeal. 2 3 10 1
The Payments Engineer
The regulated entity is named and supervised: a French payment institution authorised by the ACPR acting as both technical payment provider and acquirer, registered in Paris. The SEPA dispute framework is spelled out — return and reject deadlines of 8 weeks and 13 months, a 3-day B2B unpaid window, and a minimum balance of €300 defined as fixed plus variable reserve, with no fixed reserve on B2B. We found no public information on termination notice, freeze conditions, a route to appeal, safeguarding of merchant funds, or the amounts of reject and return fees. 1 2 3 9 10
The Compliance Officer
The regulated entity is properly identified — a French limited company registered at RCS Paris 518 991 336, authorised and supervised by the ACPR as a payment institution acting as both technical payment provider and acquirer — and reserve mechanics are defined, with a minimum balance of €300 as fixed plus variable coverage and no fixed reserve for SDD B2B. SEPA return and reject deadlines are published with fees identified by category; we found no public information on the amounts of those fees, safeguarding of merchant funds, notice periods, or freeze and termination terms with a route to appeal. 1 2 3 10
The Skeptic
The regulated entity is named down to its Paris trade register number 518 991 336, authorised and supervised by the ACPR as a payment institution — though the ACPR's own register number and passporting are not stated. The risk terms stop at a €300 minimum balance made of a fixed and variable reserve held against rejected payments, with no release timeline; we found no public information on chargeback fees, safeguarding of merchant funds, freeze or termination notice, or an appeal route. 1 2 3 9 10
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting and regulated entity is, and where transaction and cardholder data are processed and stored. Independently sourced by the sovereignty pipeline. The card schemes are US-based for every provider, so the scheme layer is not held against any one vendor; the part the vendor controls is.
0 — Contracting entity and processing of payment data both shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; the processing location of payment data not stated or partly outside the EU.
5 — An EU contracting or regulated entity, with EU processing of core payment data stated or a subprocessor list published, and a data processing agreement offered.
8 — EU entity and EU licence, payment and cardholder data processed and stored in the EU on named infrastructure, subprocessor list published with locations, and a DPA covering the processing the provider does as processor versus as controller.
10 — Sovereign end to end and evidenced: European ownership, EU entity and licence, every processing location and subprocessor European, European rails (SEPA, Wero or national schemes) offered alongside cards, and certifications published.
The Finance Lead
A French regulated entity under the ACPR, servers stated to be located entirely within the European Union on Amazon Web Services, a published data processor list with GDPR processor contracts, transfers outside the EU only under adequacy decisions or standard contractual clauses, and a Swedish parent in Trustly. We found no public information on a merchant data processing agreement or the locations of every processor on the list. 1 2 1
The E-Commerce Lead
European on its face: a Paris-registered company supervised by ACPR, a privacy policy stating servers 'located entirely within the European Union' via Amazon Web Services, a published list of data processors with GDPR processor contracts promised, BNP Paribas named in the chain, and transfers outside the EU covered by adequacy decisions or Standard Contractual Clauses. Hosting rests with a US-headquartered provider, and we found no public information on the locations of each subprocessor or on a data processing agreement splitting controller and processor roles; SlimPay declares itself Data Controller. 1 2
The SaaS Founder
The chain the vendor controls is European and named: a Paris-registered company supervised by the French ACPR, servers located entirely within the EU on Amazon Web Services, transfers outside the EU only under adequacy decisions or standard contractual clauses, a published processor list with GDPR processor contracts, and BNP Paribas plus Stockholm-based Trustly Group named in controller roles under a parent company in Trustly. We found no public information on the locations of individual subprocessors or a merchant-facing data processing agreement, so I stop short of the top of the scale. 1 2 1
The Payments Engineer
A French payment institution under the ACPR with a Paris registered office, servers stated to be located entirely within the EU on Amazon Web Services, and any extra-EU transfer covered by an adequacy decision or standard contractual clauses. A data-processor list is published with processor contracts undertaken, and the parent is Trustly Group AB of Stockholm, named as joint controller for open-banking mandate services. We found no public information on per-subprocessor locations, a merchant-facing data processing agreement distinguishing processor from controller roles, or certifications. 1 2
The Compliance Officer
The contracting and regulated entity is French and ACPR-supervised, owned by Sweden's Trustly, and the privacy policy states that servers sit entirely within the European Union on Amazon Web Services, with adequacy decisions or standard contractual clauses required for any transfer outside the EU/EEA; partners BNP Paribas and Trustly Group AB are disclosed with their controller roles and, for Trustly, its Swedish register number. The independently sourced sovereignty attributes leave processing location unconfirmed, and the captured pages do not show the processor list with each processor's location or a merchant-facing data processing agreement, which holds this below the top of the range. 1 2 1
The Skeptic
The chain is European as documented: a Paris-registered company supervised by the ACPR, servers located entirely within the European Union on Amazon Web Services, a published processor list, standard contractual clauses or adequacy decisions for any transfer out, and Swedish parent Trustly Group AB named as joint data controller. We found no public information on a data processing agreement offered to merchants, processor locations, or certifications. 1 2 1
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the effective fee for their own mix of cards, countries and methods — including cross-border and currency conversion markups, chargebacks, refunds, payouts and monthly fees — from public pages alone.
0 — No public prices at all; every rate is a sales conversation.
3 — A headline rate published for one method or card type, or a "from" percentage.
5 — Rates published per main method with domestic and international cards distinguished, and any monthly or plan fee stated with its billing period; ancillary fees (currency conversion, chargeback, payout) may still be missing or "on request".
8 — Every method priced publicly, cross-border and currency conversion markups stated, chargeback, refund and payout fees listed, minimum monthly fees and contract term given, and whether the model is blended or interchange++ said plainly.
10 — Complete fee computability: the effective rate derivable for a given volume, card mix and country mix — interchange++ with the markup published or a blended rate with every exception listed — plus volume tiers, reserves and every ancillary fee on a public page.
The Finance Lead
The fee taxonomy is public — fees taken on direct debits, rejections, returns, refunds and fund transfers, applied to the payment account and shown on a monthly invoice, alongside a 300 euro minimum balance — so I know what I will be charged for. No rate or percentage appears anywhere on the captured pages, so an effective fee for our transaction mix cannot be computed. 9 10
The E-Commerce Lead
We found no public information on rates: no percentage or fixed fee appears anywhere, so I cannot compute an effective cost per direct debit even roughly before a sales conversation. What is public is the shape of the bill — fees for direct debits, rejections, returns, refunds and fund transfers applied to the SlimPay payment account and invoiced monthly, plus the 'Minimum balance: €300 coverage' reserve. 1 9 10
The SaaS Founder
The public pages show the fee taxonomy — fees applied to the SlimPay payment account on a monthly invoice, fee lines for direct debits, rejects, returns, refunds and fund transfers, and the €300 minimum balance — but we found no public rates of any kind: no per-transaction price, no monthly fee, no 'from' percentage. For a mid-market and enterprise sales motion that may be normal; for a buyer computing effective cost per mandate, nothing here is computable. 9 10
The Payments Engineer
The captured pages name the fee categories — direct debits, rejects, returns, refunds and fund transfers — applied to the payment account and communicated on a monthly emailed invoice, but no rate, percentage or fixed fee appears anywhere. The only figure published is the €300 minimum balance, and that is a reserve rather than a price, so a merchant cannot compute an effective fee from public pages. 9 10
The Compliance Officer
Fee mechanics are public — transaction fees are applied to the SlimPay payment account and set out on a monthly invoice sent by email, with categories for direct debits, rejects, returns, refunds and fund transfers, and a minimum balance of €300 stated — but we found no public information on any rate, percentage or amount for these fees, so a merchant cannot compute an effective cost from the captured pages. 9 10
The Skeptic
The captured pages publish no processing rate of any kind — no headline percentage and no per-transaction fee — only the fee categories (direct debits, rejects, returns, refunds, fund transfers) that appear on a monthly invoice, and a €300 minimum balance. A merchant cannot compute what they will pay from public pages; the amounts arrive on the invoice. 9 10
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?Servers are entirely in the EU, but the policy explicitly allows transfers/processing outside the EU/EEA by subprocessors and Trustly Group affiliates, so this is not eu_only. |
2/4 pts | 2 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 SlimPay
Is SlimPay European?
Not determined: the vendor’s pages as captured do not say where SlimPay is based.
Where does SlimPay store data?
SlimPay stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 2 Nov 2026.
Does SlimPay have a free plan?
Not stated on the vendor’s pages as of 2 Nov 2026.
What are the best alternatives to SlimPay?
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: SlimPay alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 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 — Hosting location. Servers are entirely in the EU, but the policy explicitly allows transfers/processing outside the EU/EEA by subprocessors and Trustly Group affiliates, so this is not EU only.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 5 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
- 2 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
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
- The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. 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 page slimpay.com Checked 2 Nov 2026 +1 earlier capture: 29 Sep 2026 Details →
- 2 Privacy policy — found from the homepage www.slimpay.com Checked 2 Nov 2026 Details →
- 3 Payment methods & local coverage — found from sitemap support.slimpay.com Checked 2 Nov 2026 Details →
- 4 Payment methods & local coverage — found from sitemap support.slimpay.com Checked 2 Nov 2026 Details →
- 5 Checkout, SCA & fraud — found from sitemap support.slimpay.com Checked 2 Nov 2026 Details →
- 6 Checkout, SCA & fraud — found from sitemap support.slimpay.com Checked 2 Nov 2026 Details →
- 7 Subscriptions & recurring payments — found from sitemap support.slimpay.com Checked 2 Nov 2026 Details →
- 8 Subscriptions & recurring payments — found from sitemap support.slimpay.com Checked 2 Nov 2026 Details →
- 9 Settlement, reconciliation & API — found from sitemap support.slimpay.com Checked 2 Nov 2026 Details →
- 10 Settlement, reconciliation & API — found from sitemap support.slimpay.com Checked 2 Nov 2026 Details →