Payment
Ratepay
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Ratepay GmbH · www.ratepay.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.
Ratepay at a glance
- Vendor
- Ratepay GmbH
- Headquarters
- Not stated on the vendor’s pages as of 20 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 20 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 20 Oct 2026
- Panel verdict
- The AI panel rates Ratepay 2/5, the mean of 6 judges. Ratepay is a Berlin-based buy-now-pay-later provider offering invoice, SEPA direct debit, interest-free pay-in-3 instalments and prepayment through a hosted, white-label payment page. how scores are made
- As of
- Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Ratepay is a Berlin-based buy-now-pay-later provider offering invoice, SEPA direct debit, interest-free pay-in-3 instalments and prepayment through a hosted, white-label payment page. It scores strongest on settlement and reconciliation (4 to 6) and recurring billing (4 to 6), where judges credit a CSV settlement file per payout itemising eight fee types per transaction, and dunning blocks with defined durations per reason. Weakest is payment methods (2 to 4): we found no public information on card or wallet acceptance, or on which countries and currencies each method serves — the only market signal is 15+ years of experience in DACH payments. Checkout and SCA and licence and account terms both land at 4 to 4. The genuine split is sovereignty (3 to 6): higher scores credit the Berlin entity, BaFin regulation and a payment page developed and hosted in Germany, while the lowest score weighs unconfirmed checks on ownership and data residency, a password-gated data processing agreement, and named safeguards for third-country transfers. We found no public price; the commercial page ends in a demo booking.
Speaks for it
- CSV settlement files arrive with every payout via the ORCA portal or SFTP, itemising eight fee types per transaction with chargeback reason codes and an ERP accounting reference
- Dunning blocks are per-invoice with durations fixed per reason from two to six weeks, extendable once, with automatic resumption
- Recurring SEPA direct debit is documented in depth — payer authorisation, pre-notification rules, a single notice covering follow-on debits, and B2B mandate confirmation
- The strong customer authentication position is published and reasoned: SCA does not apply to SEPA direct debit as Ratepay offers it, a view stated as supported by BaFin
- The checkout is a hosted, white-label page with no redirects or third-party sign-ups and OTP verification on high-value purchases
Held against it
- We found no public information on card or wallet acceptance, or a per-method statement of which countries and currencies are covered
- We found no public price of any kind — the pricing path is a demo booking
- We found no public information on webhooks, idempotency, a test mode, rate limits or a status page
- We found no public information on payout delay, settlement currencies, or exporting stored payment credentials to another provider
- We found no public information on the licence type or register number, safeguarding of merchant funds, chargeback fees, or termination notice periods
Best for
- You sell into DACH markets and want invoice, SEPA direct debit and interest-free pay-in-3 instalments as the core rails
- Your finance team needs reconciliation-grade settlement data: a CSV per payout with fee types itemised per transaction and an ERP accounting reference
- You collect by recurring SEPA direct debit and want mandate handling and dunning run and documented by the provider
Avoid if
- You need cards, wallets or local methods beyond the named set of invoice, direct debit, pay-in-3 and prepayment
- You run card-based subscriptions with trials and proration — the documented recurring machinery is SEPA direct debit mandates and dunning
- You must verify the regulated counterparty by register number and licence type up front — the pages state BaFin regulation and point to a licence page without them
- Your procurement requires a published subprocessor list and openly accessible contract text — the data processing agreement sits behind a password from sales
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 1.5 of 5 |
| Checkout, SCA & fraud | 2 of 5 |
| Subscriptions & recurring payments | 2 of 5 |
| Settlement, reconciliation & API | 2.5 of 5 |
| Licence, risk & account terms | 2 of 5 |
| European sovereignty | 3 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 — 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
The named methods are invoice, direct debit, installments and prepayment — a buy-now-pay-later catalogue rather than a full acquirer's, and we found no public information on cards, wallets, or local methods outside Germany such as iDEAL or Bancontact. SEPA direct debit itself is documented in depth and the positioning is firmly DACH, but the pages give no statement of which countries and currencies each method serves. 5 3 9
The E-Commerce Lead
The named list is invoice, SEPA direct debit, interest-free pay-in-3 and prepayment, with the SEPA scheme documented in real depth, but we found no public information on which countries and currencies each method covers, and the captured pages name no cards, wallets or market-local methods such as iDEAL or Bancontact. Fifteen-plus years in DACH payments is the only market hint I get, so for my eight EU markets this reads as a specialist add-on rather than coverage I can plan against. 2 3 5 9
The SaaS Founder
The captured product pages name Invoice and Direct Debit, Pay in 3 installments and prepayment, backed by genuinely deep SEPA Direct Debit scheme documentation — but I found no public information on card or wallet acceptance, and no per-method statement of countries and currencies beyond "15+ years of experience in DACH payments". For a merchant mixing card-paying customers with SEPA payers, this is a specialist method set, not a coverage plan I can architect conversion around. 3 5
The Payments Engineer
The named methods are the core DACH staples — invoice with thirty-day terms, SEPA Direct Debit, interest-free three-instalment payments and prepayment — with SEPA Direct Debit documented right down to mandate and pre-notification rules. We found no public information on cards or wallets, and no per-method statement of the countries and currencies each method covers, so I cannot plan cross-market coverage from these pages. 5 3 9
The Compliance Officer
The offer is named — invoice purchase, SEPA Direct Debit, interest-free installments, prepayment — and the SEPA mandate rules are documented in depth, which is genuine German local coverage. But we found no public information on cards, wallets, or which countries and currencies each method serves beyond a claim of 15+ years of experience in DACH payments. 3 5 9
The Skeptic
The named methods are invoice, direct debit, instalments and prepayment, and we found no public information on card or wallet acceptance. The SEPA direct-debit scheme is documented in real depth, but beyond a fifteen-year DACH experience claim we found no per-method statement of which countries and currencies are covered, so there is no coverage list a merchant could plan against. 5 2 3 9
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
The hosted payment page is documented — branded, white label, no redirects — with risk scoring, fraud prevention and frictionless OTP verification for high-value purchases, and the strong customer authentication position on SEPA direct debit is argued out with BaFin and EBA references rather than glossed. What I cannot see: fraud rules exposed to the merchant, PCI scope per integration, and we found no public information on an embedded checkout option or declined-payment handling. 5 4
The E-Commerce Lead
A branded, white-label hosted payment page with no third-party redirects or sign-ups, OTP only on high-value purchases, and a genuinely documented SCA position — arguing, with a BaFin view and an EBA clarification, that SCA does not apply to their SEPA direct debit — is close to the challenge-only-when-needed behaviour I want for that rail. We found no public information on configurable fraud rules, declined-payment handling or authorisation-rate reporting, and no 3-D Secure appears because the captured pages show no card acceptance. 4 5
The SaaS Founder
The hosted payment page is documented as branded, white-label and built with no redirects, strong customer authentication is argued substantively — the documentation states SCA does not apply to SEPA Direct Debit as Ratepay offers it, citing a BaFin-supported view — and OTP verification covers high-value purchases alongside named risk scoring and fraud prevention. I found no public information on an embedded checkout option, merchant-configurable fraud rules, declined-payment handling, or authorisation-rate reporting. 4 5
The Payments Engineer
There is a hosted, white-label payment page with "frictionless OTP verification for high-value purchases", and the provider publishes real regulatory reasoning that SCA does not apply to its SEPA Direct Debit flows, backed by a BaFin-endorsed EBA clarification. Fraud screening appears only as marketing claims of risk scoring, and we found no public information on PCI DSS scope per integration type, merchant-configurable fraud rules, or an embedded checkout option. 4 5
The Compliance Officer
A hosted, white-label checkout with no redirects, OTP verification for high-value purchases and stated PSD2 compliance is documented, and the position that SCA does not apply to their SEPA Direct Debit is argued with BaFin and EBA references. We found no public information on 3-D Secure, an embedded option, exemption handling for other flows, or the resulting PCI scope. 4 5
The Skeptic
A hosted, white-label payment page with no redirects is documented, and the SCA position is genuinely published — strong customer authentication does not apply to their SEPA direct debit as offered, backed by a BaFin question in the EBA rulebook tool. The fraud story, however, is two marketing phrases with no rules or risk scores exposed, and we found no public information on declined-payment handling, 3-D Secure or PCI scope per integration. 5 4
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
Recurring SEPA direct debits are properly documented — mandate handling, pre-notification rules, a single notice covering follow-on debits — and the dunning side is genuinely written down, with dunning blocks of defined duration per reason, one extension, and per-invoice granularity. But there are no stored cards in the picture, no subscription plan or trial logic, and we found no public information on moving stored mandates or tokens to another provider. 3 6 7
The E-Commerce Lead
Recurring SEPA direct debit authorisation, single-use mandate rules and pre-notification duties are documented, and dunning is run by the provider with per-invoice dunning blocks of defined length and reason codes — real receivables machinery. We found no public information on subscription plans, trials, proration, an account updater, or a process for exporting stored mandates or tokens to another provider. 3 6 7 9
The SaaS Founder
SEPA mandate mechanics are the strong suit: recurring direct-debit authorisation, pre-notification rules down to re-issue obligations, and a dunning system with defined block reasons, fixed durations and automatic resumption — dunning that is engineered rather than hand-waved. I found no public information on card-on-file charges, subscription logic like trials, proration or plan changes, and above all on exporting stored payment credentials to another provider — the hostage question is unanswered. 3 6 7
The Payments Engineer
Mandate handling and dunning are documented with genuine operational depth: recurring SEPA authorisations, pre-notification rules, and dunning blocks with defined durations per reason that are visible in the merchant portal and extendable once, plus instalment direct debit as a product type. We found no public information on subscription plans with trials or proration, an account updater, smart retries, or any process for exporting stored payment credentials to another provider. 3 6 7 9
The Compliance Officer
Recurring SEPA Direct Debit is handled properly — recurring authorisation, pre-notification duties and a single notice covering follow-on debits — and installment products give scheduled charges with a managed dunning process including defined block reasons and durations. We found no public information on stored cards, subscription plan logic, account updater, or any process for taking payment credentials to another provider. 3 6 7 9
The Skeptic
Recurring SEPA direct debits are properly documented — payer authorisation for creditor-initiated regular debits, a single pre-notification covering recurring collections, B2B mandate confirmation — and the dunning machinery is real, with per-invoice dunning blocks in the merchant portal and defined durations per reason from two to six weeks. We found no public information on subscription plans, trials or proration, no card account updater, and nothing on exporting stored payment credentials to another provider. 3 6 7 11
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
This is the part I can work with: settlement files generated with every payout, a CSV line per transaction with fee types itemised — Disagio, transaction fee, service charge, VAT, interest cost, chargeback reason codes — plus a merchant accounting reference field that ties each line back to an ERP order. Payout cadence is stated as each working day a payout is generated, but the payout delay and settlement currencies are not, and we found no public information on webhooks, a test mode, or a public status page. 8 9
The E-Commerce Lead
Every payout is accompanied by a CSV settlement file itemising Ratepay fees per transaction across eight fee types, with chargeback reason codes and an ERP accounting reference field, delivered each working day via the ORCA portal or SFTP. We found no public information on payout delay, webhooks, a test mode or a status page, and the payment API surfaces only as version-tagged field mappings for Payment API 1.8 and Payment API 2.0. 8 9
The SaaS Founder
This is the best-documented area: a CSV settlement report generated with every payout, delivered each working day via the ORCA portal or SFTP, itemising per transaction the fee types (disagio, transaction fee, service charge, VAT, interest cost, chargeback) and carrying merchant order, invoice and ERP reference numbers through to the payout line. I found no public information on payout delay or settlement currencies, webhooks, a test mode, or a public status page. 8 9
The Payments Engineer
The settlement reporting is finance-grade: a CSV on each payout day via the merchant portal or SFTP, itemised fee types per transaction including disagio, transaction fee, service charge, VAT, interest cost and chargeback retransfer with reason codes, an ERP accounting reference field, and settlement fields mapped across two named API versions. But we found no public information on webhooks, idempotency keys, a test mode, published rate limits or a status page with incident history — the pieces my pager depends on. 8 9
The Compliance Officer
Settlement files arrive with every payout and itemise eight fee types per transaction, including chargeback reason codes and a merchant ERP accounting reference, which is genuinely usable reconciliation data. We found no public information on payout delay or settlement currencies, and beyond references to Payment API 1.8 and 2.0 field names, no public information on API documentation, webhooks, test mode or a status page. 8 9
The Skeptic
Settlement reporting is the strongest thing here: a CSV on each working day a payout is generated, delivered via the merchant portal and SFTP, itemising per transaction an eight-way fee taxonomy from disagio and transaction fees to VAT, interest cost and chargeback reason codes, with an ERP accounting reference that maps into their payment API. We found no public information on payout delay, accounting integrations, API documentation with webhooks, idempotency or rate limits, a status page, or historical export after the contract ends. 8 9
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
Ratepay GmbH in Berlin is named as the BaFin-regulated entity, backed by Nexi Group, with a licence page and an EBA Q&A citation behind its SCA position. But we found no public information on the register number, licence type, safeguarding of merchant funds, reserve or freeze conditions, chargeback fees, or the notice period for termination — and a receivables purchaser holding my payout schedule has to write the bad day down in the contract, not on a Tuesday. 2 5 10 4
The E-Commerce Lead
Ratepay GmbH at a Berlin address is named as a BaFin-regulated financial company, a licence page exists, an Art. 28 GDPR data processing agreement is published in versioned form, and Nexi Group backing is stated. We found no public information on the register number or licence type, safeguarding of merchant funds, chargeback fees, reserves, or termination notice and an appeal route. 2 4 5 11
The SaaS Founder
Ratepay GmbH of Berlin is the named contracting entity, BaFin regulation is stated with a licence page and an EBA Q&A reference, and a data processing agreement under GDPR Article 28 is published — more than a bare licence claim. I found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions, chargeback fees, or termination notice and exit terms — the clauses that decide what happens on a bad day. 2 4 10 11
The Payments Engineer
The regulated entity is named — Ratepay GmbH, Berlin — with BaFin regulation affirmed, a dedicated licence page, and a versioned data processing agreement concluded under Article 28 GDPR. That agreement text is available only behind a password from sales, and we found no public information on the licence type or register number, safeguarding of merchant funds, reserve or rolling-hold limits, termination notice periods, or a dispute and appeal route. 2 4 11
The Compliance Officer
Ratepay GmbH of Ritterstrasse 12-14, Berlin is named and BaFin is named as its supervisor, with a licence page published, but the register number and licence type never appear, which is exactly what I need to verify a regulated chain. We found no public information on safeguarding of merchant funds, chargeback fees, reserves, or termination notice periods, and the data processing agreement text sits behind a password obtainable from sales. 2 4 5 10 11
The Skeptic
The entity is named — Ratepay GmbH, Ritterstr. 12-14, Berlin, described as BaFin-regulated with a licence page in the docs — but we found no register number, no licence type, no safeguarding statement for merchant funds, and no published chargeback fees, dispute process or termination notice period. The data-processing agreement exists with version control, yet its text sits behind a password issued by sales, and the pages themselves disclaim being legal advice. 5 4 2 11
European sovereignty
panel opinion
panel disagrees
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
The contracting and regulated entity is German, the hosted payment page is developed and hosted in Germany, and the privacy policy names standard safeguards for third-country transfers — so some data does leave the EU, with standard contractual clauses and the EU-US framework cited. But we found no published subprocessor list with locations, and the data processing agreement text sits behind a password obtained from sales. 2 5 11
The E-Commerce Lead
The contracting entity is Berlin-based Ratepay GmbH under BaFin supervision, the payment page is developed and hosted in Germany to PSD2 and GDPR standards, and third-country transfers cite standard contractual clauses and EU adequacy decisions. The independently sourced attributes could not confirm ownership or data residency, and we found no public information on a subprocessor list with locations or the named infrastructure the processing runs on. 2 5 11
The SaaS Founder
The European core is real: a German company in Berlin, BaFin regulation, a payment page developed and hosted in Germany meeting PSD2 and GDPR, and named safeguards for any third-country transfers. I found no public information on a subprocessor list, the infrastructure behind the German hosting, or the role of the Nexi Group parent in the chain — and the data processing agreement text itself sits behind a password obtainable from sales. 2 5 11
The Payments Engineer
This is a German company in Berlin under BaFin supervision, with a payment page "developed and hosted in Germany" meeting PSD2 and GDPR, Nexi Group backing, and named safeguards such as standard contractual clauses, adequacy decisions and binding internal rules for third-country transfers. We found no published subprocessor list with locations, no named hosting infrastructure, and the data processing agreement text itself sits behind a password. 2 5 11
The Compliance Officer
The contracting entity Ratepay GmbH sits in Berlin, the payment page is stated as developed and hosted in Germany, third-country transfers are covered by named safeguards, and the backer is Nexi Group. But we found no public information on a subprocessor list with locations, on named infrastructure rather than just the country, or on where the provider acts as controller versus processor beyond a password-restricted Article 28 agreement for the regular-customer concept. 2 5 11
The Skeptic
The contracting entity is a German GmbH with a Berlin address and the payment page is claimed as developed and hosted in Germany, but the privacy policy lists third-country transfer safeguards such as standard contractual clauses and the EU-US Data Privacy Framework, so some processing outside the EU appears contemplated. We found no public subprocessor list, the data-processing agreement text is password-gated, and the independent checks on jurisdiction, ownership and data residency came back unconfirmed. 2 5 11
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 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 solutions page offers a demo booking and nothing else — we found no public price of any kind. The settlement documentation at least names which fee categories will appear on the statement (Disagio, transaction fee, service charge, VAT, interest cost, chargebacks), but without a single number a merchant cannot begin to compute an effective cost for their own mix. 5 9
The E-Commerce Lead
The solutions page offers a Book a Demo and we found no public prices at all; the settlement documentation names fee categories — disagio, transaction fee, service charge, VAT, interest cost, chargeback retransfer — but not one rate or amount is published. My effective cost per market is unknowable without a sales conversation. 5 9
The SaaS Founder
The captured pages show no public prices — the pricing path is "Book a Demo" — so an effective fee for any method or country is a sales conversation. The settlement documentation does publish the fee categories a merchant would later see itemised per transaction, which is one shard of structure, though we found no public information on the rates themselves. 5 9
The Payments Engineer
The product page offers only "Book a Demo" — we found no public prices at all, so the effective fee for any mix is unknowable before a sales conversation. The settlement documentation does name the fee categories a merchant will meet (disagio, transaction fee, service charge, interest cost), but no rate is attached to any of them. 5 9
The Compliance Officer
No public price appears in the captured pages — the commercial page ends in a call to book a demo — and the only pricing-adjacent information is a taxonomy of fee types in the settlement file specification. A merchant cannot compute any effective fee from what is published. 5 9
The Skeptic
No rate is public anywhere; the pricing page is a 'Book a Demo' button, and even the data-processing agreement needs a password from sales. The settlement file taxonomy at least tells a merchant which fee categories exist — disagio, transaction fee, service charge, interest cost, chargeback — but every amount is a sales conversation, so the effective fee cannot even be estimated. 5 9
European sovereignty — proven facts
0 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 | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about Ratepay
Is Ratepay European?
Not determined: the vendor’s pages as captured do not say where Ratepay is based.
Where does Ratepay store data?
Not stated on the vendor’s pages as of 20 Oct 2026.
Does Ratepay have a free plan?
Not stated on the vendor’s pages as of 20 Oct 2026.
What are the best alternatives to Ratepay?
As of 21 Oct 2026, the panel rates Adyen (3/5), Mollie (3/5) and Checkout.com (3/5) highest among the other 30 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 Adyen (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Ratepay alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 20 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Subprocessors. Not confirmed on the vendor’s own pages as captured.
- 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.
- 6 legal 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 subprocessors 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
- 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
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.ratepay.com Checked 20 Oct 2026 Details →
- 2 Privacy policy — found from the homepage www.ratepay.com Checked 20 Oct 2026 Details →
- 3 Payment methods & local coverage — found from sitemap docs.ratepay.com Checked 20 Oct 2026 Details →
- 4 Checkout, SCA & fraud — found from sitemap docs.ratepay.com Checked 20 Oct 2026 Details →
- 5 Checkout, SCA & fraud — found from sitemap www.ratepay.com Checked 20 Oct 2026 Details →
- 6 Subscriptions & recurring payments — found from sitemap docs.ratepay.com Checked 20 Oct 2026 Details →
- 7 Subscriptions & recurring payments — found from sitemap docs.ratepay.com Checked 20 Oct 2026 Details →
- 8 Settlement, reconciliation & API — found from sitemap docs.ratepay.com Checked 20 Oct 2026 Details →
- 9 Settlement, reconciliation & API — found from sitemap docs.ratepay.com Checked 20 Oct 2026 Details →
- 10 Licence, risk & account terms — found from sitemap docs.ratepay.com Checked 20 Oct 2026 Details →
- 11 Licence, risk & account terms — found from sitemap docs.ratepay.com Checked 20 Oct 2026 Details →