Payment
Stripe
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Stripe, Inc. · stripe.com
Compare with Adyen → Compare with Mollie → Compare with PayPal → 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
Stripe's pricing transparency scores at 7, its clearest strength: card rates are printed by origin (1,5 % + 0,25 € for standard EWR cards, 3,15 % + 0,25 € for foreign cards), SEPA Direct Debit costs 0,35 €, disputes cost 20,00 € each, and standard payments carry no monthly fee. The weakest columns are sovereignty, at 0 to 1, and checkout and SCA at 2, where judges found no public information on 3-D Secure, SCA exemptions, checkout integration types or where payment and cardholder data is processed; the captured legal notice names Stripe, Inc. of Delaware as service provider, while the provenance notes an Irish contracting entity for EEA merchants — Stripe Payments Europe Ltd, Dublin — which the vendor's own captured pages do not state. Recurring billing is the split, at 4 to 6: subscriptions are evidenced at scale with billing priced at 0,7 % of billing volume, but we found no public information on dunning, SEPA mandate management or exporting payment tokens to another provider. Licence and account terms sit at 2 on terms permitting termination at any time.
Speaks for it
- Card pricing is published by origin — 1,5 % + 0,25 € for standard EWR cards, 2,8 % + 0,25 € premium, 2,5 % + 0,25 € UK, 3,15 % + 0,25 € foreign — with a stated 2 % currency-conversion markup
- Local methods carry printed prices: SEPA Direct Debit at 0,35 € and Klarna from 2,99 % + 0,35 €, with Girocard support on the Stripe Reader S700
- Subscription billing is evidenced at scale, with more than 200 million active subscriptions managed through Stripe Billing and billing priced at 0,7 % of billing volume
- Standard payments are stated to carry no setup, monthly or hidden fees
- Developer tooling is documented — SDKs, APIs, developer documentation and an app marketplace, with 500 million-plus API requests daily claimed
Held against it
- We found no public information on 3-D Secure, SCA exemption handling, hosted versus embedded checkout or PCI scope per integration; checkout and SCA scores 2
- Sovereignty scores 0 to 1: the captured legal notice names Stripe, Inc. of Delaware as service provider, and we found no public information on where payment or cardholder data is processed or on a subprocessor list
- We found no public information on payout schedule, settlement currencies, per-transaction fee itemisation or reconciliation reports that match bank lines; settlement and reconciliation scores 2 to 3
- The terms let Stripe terminate the agreement or close the account at any time, with individual binding arbitration and liability capped at fees paid in the prior 12 months; licence and account terms scores 2
- We found no public information on dunning, smart retries, SEPA mandate management or a process for exporting payment tokens to another provider
Best for
- You sell mainly on cards and want a published price list by card origin to benchmark against acquirer quotes
- You run subscription or usage-based billing and value priced models — 0,7 % of billing volume, 0,4 % per paid invoice — with evidence of scale
- You have in-house engineers who can build on the documented SDKs, APIs and developer documentation without vendor-led onboarding
Avoid if
- You must verify an EU licensed entity or EU processing of payment data from the vendor's own public pages before signing; sovereignty scored 0 to 1 and we found no public information on processing locations or a subprocessor list
- Your conversion depends on a documented 3-D Secure and SCA exemption flow; checkout and SCA scored 2 and we found no public information on the challenge flow or declined-payment handling
- Your finance team needs published payout schedules and reconciliation reporting to close the month; settlement and reconciliation scored 2 to 3
- You cannot accept terms permitting termination or account closure at any time, with disputes routed to individual binding arbitration
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
The pricing page names SEPA-Lastschrift at 0,35 €, Klarna from 2,99 % + 0,35 €, Girocard on the German terminal reader, and card rates split into EWR standard, EWR premium, UK and foreign cards — real local methods with real prices. But "Über 100 Zahlungsmethoden" is a count, not a coverage statement: we found no public information on which methods serve which countries, and no named wallets or method-level refund and recurring support. 1 2
The E-Commerce Lead
The pages give me a count — "über 100 Zahlungsmethoden" — and pricing names SEPA Direct Debit (0,35 €), Klarna (ab 2,99 % + 0,35 €) and Girocard on the German reader, which is more than a vague "many local methods". But no wallets like Apple Pay or Google Pay are named, there is no per-country list of methods, and we found no public information on which methods support refunds or recurring charges — I cannot plan a launch in my eight markets on a count. 1 2
The SaaS Founder
SEPA Direct Debit at 0,35 € and Klarna at ab 2,99 % + 0,35 € are named and priced, Girocard is supported on the S700 reader, and the headline claims "Über 100 Zahlungsmethoden" across 135+ currencies. But the pages never say which countries each method serves, and we found no public information on wallets like Apple Pay or Google Pay, on iDEAL, Bancontact, BLIK, TWINT or EPS, or on refund and recurring support per method — so a merchant cannot plan per market from this. 1 2
The Payments Engineer
Over a hundred payment methods and 135+ supported currencies are claimed, SEPA Direct Debit is priced at 0,35 €, Klarna from 2,99 % + 0,35 €, and Girocard support is shown for the German terminal reader — but the captured pages never say which countries and currencies each method serves, and we found no public information on wallets or on refund and recurring support per method. That is a count, not a coverage matrix a merchant can plan against. 1 2
The Compliance Officer
The captured pages price cards by origin (1,5 % + 0,25 € für Standardkarten aus dem EWR, 3,15 % + 0,25 € für ausländische Karten), name SEPA Direct Debit at 0,35 € and Klarna, and mention Girocard on the German terminal reader. Beyond "Über 100 Zahlungsmethoden" we found no public information on which countries and currencies each method covers, on wallets such as Apple Pay and Google Pay, or on Benelux methods such as iDEAL or Bancontact. 1 2
The Skeptic
The captured pages price SEPA Direct Debit at 0,35 €, Klarna from 2,99 % + 0,35 € and cards by origin, and Girocard is named on the terminal reader — but the only statement of breadth is the count 'Über 100 Zahlungsmethoden', and we found no public information on iDEAL, Bancontact, BLIK, TWINT or Wero coverage, on the countries each method serves, or on which methods support refunds and recurring charges. 1 2
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
Stripe Radar is named as the fraud product and PCI-Konformität is claimed, with no-code payment links and SDKs as integration paths, but that is all the captured pages show. We found no public information on 3-D Secure, SCA exemption handling, liability shift, or declined-payment handling — the PSD2 authorisation path is undocumented here. 1 2 3
The E-Commerce Lead
Fraud prevention is evidenced — Stripe Radar and the platform compliance modules are named, and PCI compliance is stated — but we found no public information on hosted versus embedded checkout, on 3-D Secure or SCA exemption handling, or on declined-payment handling. For a merchant measured on conversion, nothing on these pages shows the challenge flow at all, let alone one that challenges only when it must. 1 2 3
The SaaS Founder
Stripe Radar is named as the fraud product that shares attempted transactions for risk assessment and "PCI-Konformität" is claimed, but we found no public information on checkout integration types, 3-D Secure, SCA exemption handling, soft-decline handling or authorisation-rate reporting. For a European basket under PSD2, which is where my conversions live, this is the part the pages say nothing about. 1 2 3
The Payments Engineer
We found no public information on 3-D Secure, SCA exemption handling, hosted versus embedded checkout options, or the PCI scope of each integration — only a bare PCI-conformity label, fraud prevention via Stripe Radar, and no-code payment links. Fraud screening is named but unexplained, and nothing is evidenced on keeping legitimate payments from failing. 1 2 3
The Compliance Officer
Fraud prevention appears as named products (Stripe Radar, and Betrugsprävention among the platform compliance tools) and PCI conformity is asserted as a bare label on the pricing page, but we found no public information on hosted versus embedded checkout, 3-D Secure or SCA exemption handling. For a regulated merchant the PCI scope attached to each integration type is the first thing I look for, and it is not stated anywhere we were shown. 1 2 3
The Skeptic
Stripe Radar is named as the fraud product and PCI conformity is claimed, but we found no public information on 3-D Secure, SCA exemptions, hosted versus embedded checkout options, PCI scope per integration, or liability shift. A fraud product's name and a compliance badge are not a documented authorisation path. 2 3
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
Subscriptions are clearly a first-class product — 200 Mio.+ aktive Abos managed through Stripe Billing, with usage-based and invoice-based billing priced publicly and SEPA-Lastschrift at 0,35 € alongside stored payment information via Link. But the operational mechanics are silent: we found no public information on merchant-initiated transactions, dunning or smart retries, card account updater, mandate pre-notification, or any process for exporting payment tokens. 1 2 3
The E-Commerce Lead
Stripe Billing is clearly a serious product — 200 million-plus active subscriptions, usage-based and invoice-based billing priced (0,7 % of billing volume, 0,4 % per paid invoice) and Link storing payment details for repeat purchases. But we found no public information on SEPA mandate management, merchant-initiated transactions, retries and dunning, an account updater, or exporting tokens to another provider. 1 2
The SaaS Founder
Stripe Billing is evidenced at scale — "200 Mio.+ aktive Abos, die über Stripe Billing verwaltet werden" — with usage-based and invoice-based models priced and SEPA Direct Debit at 0,35 €. But we found no public information on dunning, smart retries, card account updater, mandate pre-notification, merchant-initiated transaction handling, or a process for exporting payment tokens to another provider, and the terms grant only a revocable technology licence with no data-retention obligation after the contract ends — the hostage problem I care most about is not addressed anywhere I can see. 1 2 5
The Payments Engineer
Subscription billing is evidently a real product — over 200 million active subscriptions managed via Stripe Billing, a billing fee of 0,7 % of billing volume, invoicing at 0,4 % per paid invoice, usage-based pricing examples, and SEPA Direct Debit priced. But we found no public information on dunning or smart retries, mandate pre-notification, a card account updater, merchant-initiated transaction documentation, or any process for exporting payment tokens to another provider. 1 2
The Compliance Officer
Subscription billing is evidently a core product — "200 Mio.+ aktive Abos, die über Stripe Billing verwaltet werden", selectable billing models and usage-based pricing at 0,01 € pro 1.000 Einheiten — while Link stores payment details for repeat use and SEPA Direct Debit is priced. We found no public information on merchant-initiated transaction handling, SEPA mandate management, dunning or smart retries, or a process for exporting stored credentials to another provider. 1 2 3
The Skeptic
A subscription product is evidenced — '200 Mio.+ aktive Abos, die über Stripe Billing verwaltet werden', configurable billing models and usage-based pricing at 'Token 0,01 € pro 1.000 Einheiten'. But we found no public information on SEPA mandate management, dunning or smart retries, card account updater, or a documented process for exporting payment tokens to another provider. 1 2 3
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
For a platform claiming 500 Mio.+ API-Anfragen täglich with SDKs and a dashboard, the captured pages give a finance team nothing to close the month on: no payout schedule or settlement currencies, no per-transaction fee breakdown, no reconciliation reports, and no webhooks or test mode. The terms also state Stripe is not obligated to retain data after the term, so historical continuity is not promised. 1 5
The E-Commerce Lead
The developer side is evidently substantial — 500 million-plus API requests daily, SDKs, developer documentation and an app marketplace — and payouts are named as a capability, but we found no public information on payout cadence or settlement currencies. Nothing on fee itemisation per transaction, reports that match bank lines, webhooks or a test mode, so my finance team gets scale numbers and no reconciliation story. 1 3 5
The SaaS Founder
The developer side is genuinely evidenced — SDKs, APIs, developer documentation, the app marketplace, 500 Mio.+ API requests daily — but we found no public information on payout frequency or settlement currencies, per-transaction fee itemisation, reconciliation reports that match bank lines, webhooks, or a status page with incident history. My finance team cannot close a month from what these pages show. 1 3 5
The Payments Engineer
SDKs, APIs, developer documentation, a dashboard and serious throughput figures are published, yet we found no public information on payout schedule or settlement currencies, per-transaction fee itemisation, reconciliation reports that match bank lines, webhooks, a test mode, idempotency, or a status page with incident history. The 99,999 % availability figure is a marketing claim, not an incident record I could plan an on-call rotation around. 1 5
The Compliance Officer
Engineering scale is documented — "500 Mio.+ API-Anfragen täglich", SDKs and APIs, an app marketplace, developer documentation and "99,999 % historische Verfügbarkeit" — and payouts are mentioned as part of the financial infrastructure offering. We found no public information on payout cadence or settlement currencies, per-transaction fee itemisation, webhooks, or reconciliation reports that tie a payout to its transactions. 1 3
The Skeptic
SDKs, APIs, an app marketplace and developer documentation are evidenced with stated throughput, but we found no public information on payout schedule or delay, settlement currencies, per-transaction fee breakdowns in reports, webhooks, or reconciliation exports that match bank lines. The 99,999 % historical availability figure is an uptime claim, not an incident-history status page. 1 3 5
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 terms let Stripe terminate or close the account "at any time" with no reason or timeline stated, and we found no public information on any regulated payments entity, licence, safeguarding of merchant funds, or reserve and hold conditions — my rolling-reserve question is simply unanswered. The published 20,00 € dispute fee and 30 days' notice on fee increases are the only merchant-facing protections evidenced; the imprint names Stripe, Inc. of Delaware. 2 4 5
The E-Commerce Lead
The imprint names Stripe, Inc. of Delaware with a register number, and the terms publish a 20,00 € dispute fee and at least 30 days notice of fee increases. But the terms state Stripe may terminate the agreement or close the account at any time, and we found no public information on a financial licence or supervisor, safeguarding of merchant funds, reserves or holds, or a dispute process. 2 4 5
The SaaS Founder
The imprint names Stripe, Inc. of South San Francisco, California with a Delaware register number, the pricing page lists 20,00 € per payment dispute, and the terms give me 30 days notice of fee increases — but we found no public information on a European regulated entity with its supervisor, licence type, register number or a safeguarding statement. And the terms say Stripe "may terminate this Agreement or close User's Stripe Account at any time", with no stated notice period, reason, reserve limits, release timeline or appeal route. 2 4 5
The Payments Engineer
The imprint names Stripe, Inc., a Delaware corporation with a company register number, but no payments licence, supervisor or safeguarding statement appears on the captured pages, and the terms let Stripe terminate or close the account at any time with no stated reason or timeline. A 20,00 € dispute fee is published and fee increases carry 30 days' notice, which is the only daylight between this and the floor. 2 4 5
The Compliance Officer
The German imprint names Stripe, Inc., a Delaware corporation with register number 4675506, as the service provider — a company register entry, not a payment licence — and we found no public information on the EEA regulated entity, its supervisor, licence type or safeguarding of merchant funds. The terms are blunt on the bad day: "Stripe may terminate this Agreement or close User's Stripe Account at any time", with individual binding arbitration and a class action waiver; the published 20,00 € dispute fee and the 30-day fee-increase notice are the most buyer-protective items we found. 2 4 5
The Skeptic
The only entity the captured pages name is Stripe, Inc., a Delaware corporation with a corporate register number — we found no public information on a payment licence, supervisor, safeguarding of merchant funds, or reserve and hold conditions. The terms state Stripe 'may terminate this Agreement or close User's Stripe Account at any time', route disputes to individual binding arbitration in English with liability capped at the prior twelve months' fees, and the one protective number published is the '20,00 € für jede Zahlungsanfechtung' dispute fee. 2 4 5
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
The imprint names Stripe, Inc. of Delaware at a South San Francisco address as the service provider, and the vendor's captured pages confirm no EU contracting or licensed entity. The privacy policy carries an international data transfer section and the agreement incorporates a Data Transfers Addendum, and we found no public information on where payment or cardholder data is processed or which subprocessors are used. 3 4 5
The E-Commerce Lead
The captured pages name a California service provider and a Delaware corporation as the legal entity, and we found no public information on where payment or cardholder data is processed, on a published subprocessor list with locations, or on European ownership — the independent sovereignty pipeline likewise scores this at zero. A data-transfers section and an incorporated DPA exist in the terms, but nothing captured states EU processing; the provenance notes an Irish contracting entity for EEA merchants, which the vendor's own captured pages do not state. 3 4 5
The SaaS Founder
The service provider named in the legal notice is Stripe, Inc., South San Francisco, California, and we found no public information on where payment and cardholder data is processed or stored, or on any subprocessor with its location. The privacy policy references international data transfers without naming safeguards or processing locations, so there is nothing here a European buyer can rely on for EU processing. 3 4
The Payments Engineer
The captured pages name Stripe, Inc. of South San Francisco as the service provider, and we found no public information confirming an EU contracting or licensed entity, where payment data is processed and stored, or any subprocessor list. An international data transfer section and an incorporated DPA with a Data Transfers Addendum exist, but nothing evidences EU processing of payment or cardholder data. 3 4 5
The Compliance Officer
The service provider on the captured legal notice is Stripe, Inc. of South San Francisco, California, while the privacy notice says the responsible Stripe entity varies by jurisdiction — and we found no public information on where transaction and cardholder data are processed or stored, and no subprocessor list. The privacy notice does state that Stripe acts as controller and/or processor depending on the activity, and a DPA with a Data Transfers Addendum is incorporated into the agreement; those are the only sovereignty-relevant disclosures on the captured pages. 3 4 5
The Skeptic
The contracting entity named on the captured pages is Stripe, Inc. of Delaware with its service address in South San Francisco, and we found no public information on where payment or cardholder data is processed, on processing locations for any subprocessor, or on an EU licence for the European contracting chain. The privacy policy confirms international data transfers and machine-learning training on the data, and a data transfers addendum is incorporated without a stated location safeguard. 3 4 5
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
A genuinely detailed public price list: 1,5 % + 0,25 € for EWR standard cards, 2,8 % + 0,25 € premium, 3,15 % + 0,25 € foreign cards, 2,5 % + 0,25 € UK plus 2 % currency conversion, SEPA at 0,35 €, Klarna from 2,99 % + 0,35 €, disputes at 20,00 €, no monthly or setup fees, and IC+ pricing named with volume discounts for larger merchants. Two common costs are missing from the captured pages — payout fees and refund handling — and with over 100 payment methods claimed but only a handful priced, the effective fee for a mixed-method business is not fully computable. 2 5
The E-Commerce Lead
This is the strongest part: standard and premium EWR cards (1,5 % + 0,25 € and 2,8 % + 0,25 €), UK and foreign cards, a 2 % currency conversion markup, 20,00 € disputes, 0,35 € SEPA Direct Debit and Klarna ab 2,99 % + 0,35 € are all public, with interchange-plus named for custom tiers and no setup or monthly fees stated for the standard plan. But most of the "100+" methods carry no published price, and we found no public information on refund or payout fees or on published volume tiers, so my effective rate is computable for cards only. 2 5
The SaaS Founder
Card pricing is unusually precise — 1,5 % + 0,25 € for standard EWR cards, 2,8 % + 0,25 € premium, 2,5 % + 0,25 € UK, 3,15 % + 0,25 € foreign — with a 2 % currency-conversion markup, 20,00 € dispute fee, SEPA at 0,35 €, "IC+-Preisgestaltung" named for custom tiers, and no setup, monthly or hidden fees. We found no public information on refund or payout fees, and the methods behind the "Über 100 Zahlungsmethoden" headline are unpriced on the captured pages, so the effective fee is close to computable but not fully. 2
The Payments Engineer
This is a genuinely public price list: EWR standard cards at 1,5 % + 0,25 € and premium at 2,8 % + 0,25 €, UK at 2,5 % + 0,25 € and foreign cards at 3,15 % + 0,25 €, a stated +2 % currency conversion, SEPA Direct Debit at 0,35 €, Klarna from 2,99 % + 0,35 €, a 20,00 € dispute fee, and no setup or monthly fees. What keeps it short of the top of the scale: we found no public information on refund or payout fees or the contract term, and interchange++ pricing appears only as a named custom-tier feature rather than a plainly stated model. 2 5
The Compliance Officer
Card pricing is differentiated publicly — 1,5 % + 0,25 € für Standardkarten aus dem EWR, 2,8 % + 0,25 € for premium EWR cards, 3,15 % + 0,25 € für ausländische Karten, a 2 % currency conversion markup and a 20,00 € dispute fee — alongside "Keine Einrichtungsgebühren, monatlichen Gebühren oder versteckten Gebühren" and IC+-Preisgestaltung named for custom tiers. We found no public information on payout fees, refund fees, or prices for the rest of the claimed "Über 100 Zahlungsmethoden" beyond SEPA-Lastschrift and Klarna. 1 2
The Skeptic
This is the rare pricing page that shows its markups: '1,5 % + 0,25 €' for standard EWR cards against '2,8 % + 0,25 €' for premium EWR and '3,15 % + 0,25 €' for foreign cards, plus a stated 2 % currency conversion, a '20,00 €' chargeback fee, no monthly fee for standard payments, and interchange-plus named as an available model. We found no public information on refund or payout fees, and volume tiers and country-specific pricing sit in a custom tier rather than as published numbers. 1 2 5
European sovereignty — proven facts
1 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 US ⚠ unverified | 0/3 pts | 4 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited 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 — Legal entity. The imprint names only the US website operator; the Stripe Services Agreement designates the applicable contracting Stripe entity by the user's Stripe Account Country (Sections 12–13), so business users in other regions may contract with a different Stripe entity.
- 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.
- 22 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
- 13 pricing 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 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
- 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
- 3 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
- 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 integrations 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
- 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
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage stripe.com Checked 22 Sep 2026 Details →
- 2 Pricing page stripe.com Checked 22 Sep 2026 Details →
- 3 Privacy policy stripe.com Checked 22 Sep 2026 Details →
- 4 Legal notice stripe.com Checked 22 Sep 2026 Details →
- 5 Terms of service stripe.com Checked 22 Sep 2026 Details →
- 6 Payment methods & local coverage — found from sitemap stripe.com Checked 1 Oct 2026 Details →
- 7 Payment methods & local coverage — found from sitemap stripe.com Checked 1 Oct 2026 Details →
- 8 Checkout, SCA & fraud — found from sitemap docs.stripe.com Checked 1 Oct 2026 Details →
- 9 Checkout, SCA & fraud — found from sitemap docs.stripe.com Checked 1 Oct 2026 Details →
- 10 Subscriptions & recurring payments — found from sitemap docs.stripe.com Checked 1 Oct 2026 Details →
- 11 Subscriptions & recurring payments — found from sitemap docs.stripe.com Checked 1 Oct 2026 Details →
- 12 Settlement, reconciliation & API — found from sitemap docs.stripe.com Checked 1 Oct 2026 Details →
- 13 Settlement, reconciliation & API — found from sitemap docs.stripe.com Checked 1 Oct 2026 Details →
- 14 Licence, risk & account terms — found from sitemap stripe.com Checked 1 Oct 2026 Details →
- 15 Licence, risk & account terms — found from sitemap support.stripe.com Checked 1 Oct 2026 Details →