Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

by Satispay S.p.A. · satispay.com

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

Link to this page

Satispay: AI-assisted analysis on whats-best.ai Satispay: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Satispay at a glance

Vendor
Satispay S.p.A.
Headquarters
Not stated on the vendor’s pages as of 17 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 17 Nov 2026
Free plan
Not stated on the vendor’s pages as of 17 Nov 2026
Panel verdict
The AI panel rates Satispay 1.5/5, the mean of 6 judges. The payment vendor Satispay S.p.A. how scores are made
As of
Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Satispay alternatives, European ones first →

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

The panel's verdict

The payment vendor Satispay S.p.A. shows narrow public evidence; the scores follow. Settlement and reconciliation is the strength, scores clustered at 4 on a documented report API: CSV or XLS output carrying the fee amount per transaction in cents, customisable columns, an idempotency key and signature-based authentication — though the captured pages state no payout schedule, webhooks or test mode, and reports are merchant-level only. Payment methods sits at 2: payments to business and refunds to business are documented transaction types, with Meal Voucher, Fringe Benefit and Buy Now Pay Later as report columns, but the captured pages name no cards, wallets or local methods per country. Checkout and SCA, recurring billing and sovereignty all sit at 0, reflecting no public information on the checkout path, subscriptions or mandates. Two criteria show score splits: licence and account terms spans 0-2, the finance lead crediting the named contracting entity, the others nothing beyond the name; pricing transparency spans 0-1, some judges counting the 20 euro consumer welcome code and after-the-fact fee fields as partial evidence, others nothing to rate.

Report an error

Speaks for it

  • A documented report API generates CSV or XLS reports with the total amount and fee amount per transaction in cents, plus a group id
  • Report columns are customisable, with additional columns for activated Meal Voucher, Fringe Benefit and Buy Now Pay Later products
  • Authentication is signature-based via a dedicated RSA key pair, and report creation carries an idempotency key header
  • Payments to business and refunds to business are both documented transaction types, queried by payment date interval

Report an error

Held against it

  • We found no published merchant pricing on the captured pages — no rates per method, monthly fees, or chargeback, refund, payout or conversion fees
  • We found no public information on the checkout path, hosted or embedded options, 3-D Secure, SCA exemptions or fraud screening
  • We found no public information on stored payment methods, SEPA mandates, subscription logic or dunning — only payments and refunds to business are documented
  • The captured pages state no payout schedule, settlement currencies, webhooks or test mode, leaving a finance team unable to close the month on the reports alone
  • No sovereignty attributes are on record, and we found no public information on where data are processed, on subprocessors, or on the licence or supervisor behind the payments

Report an error

Best for

  • You already accept payments through Satispay and need itemised per-transaction fee reports in CSV or XLS for reconciliation
  • You have activated Meal Voucher, Fringe Benefit or Buy Now Pay Later products and need them broken out in your reporting
  • You need refunds reported alongside payments at merchant level, queried by payment date interval

Report an error

Avoid if

  • You need to compute an effective fee before signing — ask the vendor: the public pages we read do not show it
  • You charge customers on a recurring basis — the only documented transaction types are payments to business and refunds to business
  • You need shop-level reporting — extraction is merchant-level only, with shop-level extraction stated as not available
  • You need timely or automated reporting — previous-day reports must be generated at least 4 hours after midnight and report access is activated manually by the vendor's IT team

Report an error

The scores

Payment methods & local coverage

Show reasoning
How this is scored

Which methods a European customer can actually pay with — cards and wallets, SEPA Direct Debit, and the local methods that decide conversion per country — judged on the named list per market rather than on a method count.

0 — Not a payment acceptance product; customers cannot pay through it.

3 — Card payments with the major schemes, plus wallets such as Apple Pay or Google Pay.

5 — Cards and wallets plus SEPA Direct Debit and several European local methods (for example iDEAL or Wero, Bancontact, Klarna, EPS) listed by name.

8 — Broad EU coverage named per country with the countries and currencies each method serves — including methods such as BLIK, TWINT, Przelewy24, EPS and Wero — multi-currency acceptance with settlement currencies stated, and which methods support refunds and recurring charges documented per method.

10 — Coverage is documented as a matrix a merchant can plan against: every method with its countries, currencies, refund, partial-capture and recurring support, and the provider's own acquiring versus third-party routing stated per method.

Report an error

The Finance Lead

Payments clearly reach merchants — the report API distinguishes payments to business and refunds to business — and the report columns name Buy Now Pay Later, Meal Voucher and Fringe Benefit as active products. Beyond that we found no public information on card acceptance, wallets, SEPA Direct Debit or a per-country method list, so I cannot plan coverage against what is published. 1 2

Report an error

The E-Commerce Lead

I need the local methods my eight markets actually use, named per country, and we found no public information on per-market method coverage — no cards, wallets, SEPA Direct Debit or local methods appear on the captured pages. What the evidence does show is real payment flow, with payments to business and refunds as documented transaction types, plus an activatable Buy Now Pay Later product that adds its own report columns. That is far short of a coverage list I can plan conversion against. 1 2

Report an error

The SaaS Founder

Payments and refunds clearly flow through this product — the transaction reporting covers payments to business and refunds, with Buy Now Pay Later, Meal Voucher and Fringe Benefit products named — but the captured pages never list cards, wallets or SEPA Direct Debit, which is the mandate coverage I look for first as a subscription operator. 2

Report an error

The Payments Engineer

The reporting API proves customers pay through it — payment and refund transaction types flow to businesses, with add-on products like Buy Now Pay Later, meal vouchers and fringe benefit reported — but the captured pages name no card schemes, wallets or local methods per market, so I cannot plan acceptance coverage from them. 1 2

Report an error

The Compliance Officer

The reporting API confirms customers pay businesses through the product, with refunds and optional Meal Voucher, Fringe Benefit and Buy Now Pay Later products. We found no public information on card acceptance, wallets, SEPA Direct Debit, or any per-country list of methods on the captured pages. 1 2

Report an error

The Skeptic

The report documentation proves real acceptance — payments to business and refunds to business, with additional report columns for Buy Now Pay Later, meal-voucher and fringe-benefit products — but the captured pages never name a card scheme, wallet, SEPA Direct Debit or any local method. We found no public information on which methods a customer in a given country can actually pay with. 2

Report an error

Checkout, SCA & fraud

n/r n/r n/r n/r n/r n/r Show reasoning
How this is scored

The path from basket to authorised payment under PSD2: hosted and embedded checkout options, 3-D Secure and SCA exemption handling, fraud screening, and what the provider documents about keeping legitimate payments from failing.

0 — No checkout or payment form; the product does not take a payment to authorisation itself.

3 — A hosted payment page or payment links with 3-D Secure.

5 — Hosted and embedded checkout options, 3-D Secure 2 with SCA handled by the provider, and fraud screening with configurable rules.

8 — SCA exemptions (low value, transaction risk analysis, merchant-initiated) applied and documented, the PCI DSS scope of each integration type stated, fraud tooling with rules and risk scores exposed to the merchant, network tokens or account updater, and liability shift explained per flow.

10 — Authorisation is engineered and shown: exemption strategy documented, soft-decline retry handled, authorisation-rate reporting by method and issuer country, and a checkout the merchant can run in their own domain while staying at the lowest PCI scope.

Report an error

The Finance Lead not rated — no public information

We found no public information on the checkout path, hosted or embedded, on 3-D Secure or SCA exemptions, or on fraud screening. The pages I read are the consumer homepage and the developer documentation for generating reports, and neither describes how a payment is authorised. 1 2

Report an error

The E-Commerce Lead not rated — no public information

We found no public information on checkout options, 3-D Secure, SCA exemption handling or fraud screening on the two captured pages. The consumer homepage and the developer report documentation leave the path from basket to authorised payment undocumented, so as a merchant measured on conversion I cannot assess it. 1 2

Report an error

The SaaS Founder not rated — no public information

We found no public information on checkout options, 3-D Secure handling, SCA exemptions or fraud screening; the pages captured cover a consumer welcome offer and report generation only. 1 2

Report an error

The Payments Engineer not rated — no public information

We found no public information on checkout or payment form options, 3-D Secure, SCA exemption handling or fraud screening in the captured pages. 1 2

Report an error

The Compliance Officer not rated — no public information

We found no public information on the checkout path — hosted or embedded options, 3-D Secure, SCA exemption handling, or fraud screening. The captured pages document back-office reporting only and say nothing about how a payment is taken to authorisation. 1 2

Report an error

The Skeptic not rated — no public information

We found no public information on hosted or embedded checkout, 3-D Secure, strong customer authentication exemptions, PCI scope or fraud screening. The captured pages cover report generation, signature-based authentication for API keys, and a consumer welcome bonus — nothing on the path from basket to authorised payment. 1 2

Report an error

Subscriptions & recurring payments

n/r n/r n/r n/r n/r n/r Show reasoning
How this is scored

Charging the same customer again: card-on-file and merchant-initiated transactions, SEPA mandates, subscription logic and dunning — and whether the stored payment credentials can leave with the merchant.

0 — One-off payments only; the product stores no payment method for a later charge.

3 — Saved cards (card-on-file) charged again for repeat or recurring payments.

5 — Stored cards and SEPA Direct Debit mandates for recurring charges, merchant-initiated transactions, and subscriptions or scheduled payments with notification of failed payments.

8 — Subscription billing with trials, proration and plan changes, smart retries and dunning, card account updater, mandate management with pre-notification, and a documented process for exporting payment tokens to another provider.

10 — Recurring revenue is a first-class product: usage-based and invoice-based billing, dunning with measurable recovery, token migration in and out documented with a stated timeline and format, and recurring support stated for every local method that allows it.

Report an error

The Finance Lead not rated — no public information

We found no public information on stored cards, SEPA mandates, subscription billing or dunning. The only transaction types the reports distinguish are payments to business and refunds to business, with nothing documented on repeat or scheduled charges. 1 2

Report an error

The E-Commerce Lead not rated — no public information

We found no public information on subscriptions, card-on-file or merchant-initiated transactions, SEPA mandates or dunning on the captured pages. The only payment documentation captured is the settlement report, covering payments to business and refunds, which says nothing either way about recurring charges. 1 2

Report an error

The SaaS Founder not rated — no public information

We found no public information on stored payment methods, SEPA mandates, subscription logic, dunning or any process for exporting payment tokens to another provider — nothing on the captured pages describes charging the same customer again. 1 2

Report an error

The Payments Engineer not rated — no public information

We found no public information on stored payment credentials, SEPA mandates, merchant-initiated transactions, subscriptions or dunning in the captured pages. 1 2

Report an error

The Compliance Officer not rated — no public information

We found no public information on stored payment methods, SEPA mandates, merchant-initiated transactions, subscription logic or dunning. The reporting API distinguishes only payments and refunds, which gives no basis to judge recurring capability either way. 1 2

Report an error

The Skeptic not rated — no public information

The only transaction types documented are payments to business and refunds to business — one-off flows. We found no public information on stored cards, SEPA mandates, merchant-initiated transactions, subscription logic, dunning or any export of payment tokens. 1 2

Report an error

Settlement, reconciliation & API

Show reasoning
How this is scored

Getting the money and knowing what it was: payout cadence and currencies, fee itemisation per transaction, reports that match a bank statement, and an API and webhooks a team can build finance processes on.

0 — No merchant reporting: the product is a payment button or link with no dashboard, report or API.

3 — A dashboard of transactions and payouts, a stated payout schedule, and CSV export.

5 — The payout schedule stated, reports or exports that link each payout to its transactions and fees, and a documented API with webhooks and a test mode.

8 — Configurable payout schedules and settlement currencies, reconciliation reports that match bank lines, accounting integrations or exports named, a versioned API with idempotency and published rate limits, and a public status page with incident history.

10 — Finance can close the month from the provider's data: interchange and scheme fees itemised per transaction, automated reconciliation to the ledger, a deprecation policy for the API, and full historical data exportable after the contract ends.

Report an error

The Finance Lead

The report API is genuinely useful to me: it produces CSV or XLS with the fee for each transaction plus a group id, customisable columns, and an idempotency key on report creation. But we found no public information on payout schedule, settlement currencies, webhooks or a test mode; reports are merchant-level only (shop-level extraction is unavailable), previous-day reports must be generated at least 4 hours after midnight, and the report API requires a dedicated key activated manually by the vendor's IT team. 2

Report an error

The E-Commerce Lead

The settlement side has a genuinely documented API: a report endpoint that returns the fee amount per transaction, CSV and XLS output, customisable columns and an idempotency key on requests. But no payout cadence, settlement currency, webhook or test-mode documentation appears on the captured pages, reports are merchant-level only with shop-level extraction unavailable, previous-day reports must wait at least four hours after midnight, and report access is activated manually by the vendor's IT team. 2

Report an error

The SaaS Founder

The report API is real and workable: merchant-level reports with per-transaction fee amounts in cents, CSV or XLS output, customisable columns, an Idempotency-Key header and payment-date-interval queries. But the only supported query type is a date interval, shop-level extraction is not available, and the captured pages state no payout schedule, webhooks or test mode, so I could not yet run a full finance process on it. 2

Report an error

The Payments Engineer

The report API is genuinely buildable — an idempotency key header, signature-based authentication, CSV or XLS output with per-transaction fee amounts in cents and customizable columns — though the captured pages state no payout schedule, webhook delivery or test mode, and reporting is constrained to merchant-level date intervals only, with a four-hour data delay and a separate RSA key pair required just for reports. 2

Report an error

The Compliance Officer

The reporting API is documented in workable detail: signature authentication with a dedicated key pair, an idempotency key, a versioned endpoint, and customisable CSV and XLS exports carrying the fee amount and refunds per transaction at merchant level, with shop-level extraction stated as not available. The captured pages state no payout schedule, no linkage of payouts to their transactions, and no webhooks or test mode, so a finance team cannot run on this alone. 2

Report an error

The Skeptic

A documented report API generates CSV or XLS reports with the total amount and the fee amount per transaction in cents, customisable columns, merchant-level aggregation, an idempotency key and a four-hour wait before previous-day payments can be reported. That is per-transaction fee itemisation and a start on reconciliation — but we found no public information on payout schedules or settlement currencies, webhooks, a test mode, accounting exports or a status page, so a finance team cannot close the month from it. 2

Report an error

Licence, risk & account terms

n/r n/r n/r n/r n/r Show reasoning
How this is scored

Who holds the merchant's money under which licence, and what the contract lets the provider do on a bad day: freezes, reserves, termination, chargebacks. Scored on what the terms and the imprint state, not on reputation.

0 — The terms let the provider freeze funds or close the account at any time with no notice, reason or timeline.

3 — The regulated entity or the licensed partner behind the payments named, and a chargeback or dispute process described.

5 — The regulated entity named with its supervisor or licence type, the dispute process and chargeback fee published, and either safeguarding of merchant funds or a notice period for ordinary termination stated.

8 — Entity, supervisor, register number and passporting stated per country; safeguarding stated; reserve and rolling-hold conditions defined with limits and release timelines; freeze and termination terms with reasons and a route to appeal; PCI DSS level and attestation published.

10 — The bad day is written down: every regulated entity in the chain named with register links, reserve calculation disclosed, funds release timelines after termination committed, a documented complaint route to the supervisor, and exit terms that include handing back payment tokens and transaction history.

Report an error

The Finance Lead

The contracting entity is named — Satispay S.p.A. — and that is where the published information I can see stops. We found no public information on the licence or supervisor behind the payments, safeguarding of merchant funds, the dispute and chargeback process, reserve conditions, or termination notice. 1 2

Report an error

The E-Commerce Lead not rated — no public information

We found no public information on the regulated entity behind the payments, its supervisor or licence, chargeback or dispute process, safeguarding of merchant funds, or account termination terms on the captured pages. Neither the homepage nor the developer documentation captured touches contract or risk terms. 1 2

Report an error

The SaaS Founder not rated — no public information

We found no public information on the regulated entity behind the payments, safeguarding of merchant funds, reserve or freeze conditions, or a dispute and chargeback process on the captured pages — for a business whose renewals depend on payouts arriving, that is the first thing I would demand before signing. 1 2

Report an error

The Payments Engineer not rated — no public information

We found no public information on the regulated entity and its supervisor, safeguarding of merchant funds, dispute and chargeback terms, or freeze, reserve and termination conditions in the captured pages. 1 2

Report an error

The Compliance Officer not rated — no public information

We found no public information on the regulated entity behind the payments — no supervisor, licence type or register number — nor on safeguarding of merchant funds, reserves, freezes, termination, or a chargeback and dispute process. Neither captured page carries terms, an imprint or a licence statement. 1 2

Report an error

The Skeptic not rated — no public information

We found no public information on the regulated entity or licensed partner behind the payments, its supervisor or register number, safeguarding of merchant funds, reserves, chargeback fees, dispute handling or termination notice. The terms on a bad day are exactly what I read first, and the captured pages gave me nothing to read. 1 2

Report an error

European sovereignty panel opinion

n/r n/r n/r n/r n/r n/r Show reasoning
How this is scored

Who the contracting and regulated entity is, and where transaction and cardholder data are processed and stored. Independently sourced by the sovereignty pipeline. The card schemes are US-based for every provider, so the scheme layer is not held against any one vendor; the part the vendor controls is.

0 — Contracting entity and processing of payment data both shown to be outside the EU, with no transfer safeguard stated.

3 — A named contracting entity and a privacy policy or data processing agreement; the processing location of payment data not stated or partly outside the EU.

5 — An EU contracting or regulated entity, with EU processing of core payment data stated or a subprocessor list published, and a data processing agreement offered.

8 — EU entity and EU licence, payment and cardholder data processed and stored in the EU on named infrastructure, subprocessor list published with locations, and a DPA covering the processing the provider does as processor versus as controller.

10 — Sovereign end to end and evidenced: European ownership, EU entity and licence, every processing location and subprocessor European, European rails (SEPA, Wero or national schemes) offered alongside cards, and certifications published.

Report an error

The Finance Lead not rated — no public information

We found no public information on where the contracting or regulated entity is licensed or where payment and cardholder data are processed and stored; no sovereignty attributes were on record for this vendor. Neither page I read — the consumer homepage nor the developer report API — states a processing location, a subprocessor list or a data processing agreement. 1 2

Report an error

The E-Commerce Lead not rated — no public information

The sovereignty pipeline has no attributes on record, and we found no public information on where payment or cardholder data are processed, on the contracting entity's licence, or on any subprocessor list. Neither captured page states a processing location or data transfer safeguard. 1 2

Report an error

The SaaS Founder not rated — no public information

We found no public information on the contracting entity or where payment and cardholder data are processed; no sovereignty attributes are on record, and the only infrastructure named anywhere is the report API endpoint domain. 1 2

Report an error

The Payments Engineer not rated — no public information

No sovereignty information is on record, and the captured pages state nothing about the contracting entity's location, any EU licence, or where payment and cardholder data are processed. 1 2

Report an error

The Compliance Officer not rated — no public information

We found no public information on where transaction and cardholder data are processed or stored, who the subprocessors are, whether a data processing agreement is offered, or where the provider acts as controller rather than processor. The operator appears only by vendor name, with no supervisor or register number anywhere in the captured material. 1 2

Report an error

The Skeptic not rated — no public information

We found no public information on the contracting entity's seat, any licence, or where transaction and cardholder data are processed and stored. The captured pages address none of this, and no data processing agreement or subprocessor list appears on them. 1 2

Report an error

Pricing transparency

n/r n/r Show reasoning
How this is scored

Whether a merchant can compute the effective fee for their own mix of cards, countries and methods — including cross-border and currency conversion markups, chargebacks, refunds, payouts and monthly fees — from public pages alone.

0 — No public prices at all; every rate is a sales conversation.

3 — A headline rate published for one method or card type, or a "from" percentage.

5 — Rates published per main method with domestic and international cards distinguished, and any monthly or plan fee stated with its billing period; ancillary fees (currency conversion, chargeback, payout) may still be missing or "on request".

8 — Every method priced publicly, cross-border and currency conversion markups stated, chargeback, refund and payout fees listed, minimum monthly fees and contract term given, and whether the model is blended or interchange++ said plainly.

10 — Complete fee computability: the effective rate derivable for a given volume, card mix and country mix — interchange++ with the markup published or a blended rate with every exception listed — plus volume tiers, reserves and every ancillary fee on a public page.

Report an error

The Finance Lead

The only published figure in the captured pages is a 20€ welcome bonus for consumers with code CONTO20; we found no public information on merchant rates, monthly fees, or ancillary fees such as currency conversion, chargebacks or payouts. The reports do itemise the fee on each transaction after the fact — visibility into what I was charged, not a price I could compute beforehand. 1 2

Report an error

The E-Commerce Lead

We found no published merchant rate on the captured pages — no headline percentage, no per-method pricing, nothing I could compute an effective fee from before signing. The only fee-related facts are the per-transaction fee amount that appears inside settlement reports once live, and a '20€ di benvenuto' consumer welcome bonus on the homepage. 1 2

Report an error

The SaaS Founder

The only prices visible on the captured pages are a 20€ consumer welcome code and fee amounts per transaction inside generated reports; no merchant rate card, monthly fee or chargeback price is published, so I could not begin to compute an effective fee for my own card and country mix. 1 2

Report an error

The Payments Engineer not rated — no public information

We found no public merchant pricing in the captured pages — the only price-adjacent item is a twenty-euro consumer welcome bonus, and fee amounts appear as report columns without any published rates a merchant could compute from. 1 2

Report an error

The Compliance Officer not rated — no public information

We found no public merchant pricing on the captured pages — no rates per method, monthly fees, or chargeback, refund, payout or currency-conversion fees. The only pricing-adjacent fact is that the reporting API records a fee amount in cents per transaction, which is no basis for computing an effective rate. 1 2

Report an error

The Skeptic

The captured pages publish a 20 euro welcome bonus for consumers and confirm through the report fields that fees are collected per transaction, but we found no public merchant rate of any kind — no card percentage, currency conversion markup, chargeback, refund or payout fee, and no monthly fee or contract term. A merchant cannot begin to compute an effective rate from what we read. 1 2

Report an error

Questions about Satispay

Is Satispay European?

Not determined: the vendor’s pages as captured do not say where Satispay is based.

Where does Satispay store data?

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

Does Satispay have a free plan?

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

What are the best alternatives to Satispay?

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: Satispay alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (2)

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

  1. 1 Vendor page satispay.com Checked 17 Nov 2026 Details →
  2. 2 Settlement, reconciliation & API — found from sitemap developers.satispay.com Checked 17 Nov 2026 Details →