Payment
Ecommpay
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Ecommpay Ltd · www.ecommpay.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.
Ecommpay at a glance
- Vendor
- Ecommpay Ltd
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Ecommpay 1.5/5, the mean of 6 judges. Ecommpay is a payment provider whose evidence is strongest where subscriptions live and thinnest where regulated checkout and finance demand detail. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Ecommpay is a payment provider whose evidence is strongest where subscriptions live and thinnest where regulated checkout and finance demand detail. Recurring billing is the high point at 6 across the bench: scheduled and unscheduled charges, API-configurable trials, smart retries and a dashboard-managed retry queue are documented across cards, wallets and SEPA/Bacs Direct Debit. Payment methods hold at 4 — the major wallets, open banking across Europe and direct debit are named, but the '100+ alternative payment methods' figure is a count, not a list. Checkout and SCA is the genuine split, 2 to 4: higher scores credit the documented redirect, iframe and three-field microframe modes with network tokens; lower scores found no public information on 3-D Secure, SCA exemptions or PCI scope. Settlement and reconciliation scored 2 for five of six judges, licence and account terms run 1 to 2, and sovereignty sits at 0 to 1 with jurisdiction, ownership, data residency and subprocessors unknown — a UK ombudsman route is the only territorial signal, not a licence or residency statement. No prices are published; every rate is a sales conversation.
Speaks for it
- Recurring billing is the strongest criterion at 6 across the bench — scheduled and unscheduled charges, API-configurable trials and dashboard-managed smart retries are all documented across cards, wallets and SEPA/Bacs Direct Debit.
- Three checkout modes are published — redirect, iframe and a three-field microframe — with one-click payments and bring-your-own network tokens.
- Payouts are documented across 70 countries and 40 currencies, with SEPA Instant and Faster Payments, initiated by API, manually or through a payout page.
- Cards, the major wallets (PayPal, Apple Pay, Google Pay, Skrill, Neteller, Trustly), open banking across Europe and SEPA/Bacs Direct Debit are all named.
- Smart retries and cascading between payment accounts are documented, alongside a claimed payout approval rate of up to 98%.
Held against it
- We found no public information on 3-D Secure, SCA exemption handling, fraud screening detail or PCI DSS scope per integration type (checkout and SCA scored 2 to 4).
- The '100+ alternative payment methods' figure is a count — we found no public information naming iDEAL, Bancontact or Klarna, or a country-by-country coverage list.
- We found no public information on payout frequency or delay, per-transaction fee itemisation, or reports tying payouts to bank statement lines (settlement and reconciliation scored 2 to 4).
- We found no public information naming a regulated entity, supervisor, licence type or register number — the only terms signal is a complaint route to the UK's Financial Ombudsman Service (licence and account terms scored 1 to 2).
- Sovereignty scored 0 to 1 — the legal entity's jurisdiction, ownership, data residency and subprocessor exposure are all recorded as unknown.
Best for
- You run a subscription or recurring-revenue business — trials, configurable retries and a dashboard-managed retry queue are the best-documented capabilities in the scoring.
- You sell across Europe on cards, the major wallets and SEPA/Bacs Direct Debit and want checkout modes that keep payment on your own page.
- You want to lift approval rates on an existing billing stack — the vendor states it works alongside existing infrastructure without replacing it, and smart routing, cascading and retries are documented.
Avoid if
- You need documented PSD2 checkout handling — 3-D Secure, SCA exemptions, PCI scope per integration — before wiring a checkout; we found no public information on any of these.
- You must plan a country-by-country local-method launch — ask the vendor: the public pages we read do not show it
- Your compliance review requires a named regulated entity, register number, safeguarding terms and a subprocessor list — all are recorded as unknown.
- Your finance team must close the month from provider data — we found no public information on payout schedules, per-transaction fee itemisation or payout-to-bank-line reconciliation.
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 2 of 5 |
| Checkout, SCA & fraud | 1.5 of 5 |
| Subscriptions & recurring payments | 3 of 5 |
| Settlement, reconciliation & API | 1 of 5 |
| Licence, risk & account terms | 1 of 5 |
| European sovereignty | 0 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
Cards, the major wallets, SEPA Direct Debit, open banking and Skrill, Neteller and Trustly are all named for Europe, which clears the bar above cards-only. But I found no public information naming the local methods for the Dutch, Belgian or German markets, and no statement of which countries and currencies each method serves — the "100+ alternative payment methods" figure is a count, not a list I can plan a market launch against. 1 2 3 4
The E-Commerce Lead
The Europe page names SEPA Direct Debit, open banking and the global wallets, but for my eight markets I need methods named per country and "100+ alternative payment methods" is a count, not a list. I found no public information naming iDEAL, Bancontact, Klarna, BLIK or TWINT with the countries they serve, and the payment method finder is a self-service tool rather than a published matrix. SEPA Direct Debit being named keeps this above the basic tier, but nothing here lets me plan a country-by-country mix. 1 2 3
The SaaS Founder
Cards, the three big wallets, open banking across Europe and SEPA Direct Debit (with Bacs for the UK) are all named, which is the floor a European subscription business needs. But the per-market methods that decide conversion — I found no public information naming iDEAL, Bancontact or Klarna with the countries they serve; coverage reads as methods "popular across much of Europe" plus a count of 100+ alternative payment methods. Good bones, but no per-country matrix to plan a launch against. 2 3 1
The Payments Engineer
Cards, Apple Pay, Google Pay and SEPA Direct Debit are on the page alongside a handful of named European methods — Skrill, Neteller, Trustly, open banking, Bacs — and a claim of 100+ alternative payment methods as a count with no per-country list. I found no public information naming iDEAL, Bancontact, BLIK or similar conversion-deciding local methods with the countries they serve, and nothing per method on refunds or recurring support. 1 2 3
The Compliance Officer
Cards, the major wallets, open banking and SEPA and Bacs Direct Debit are named for Europe, but we found no public information naming the country-level local methods an EU roll-out needs, such as iDEAL, Bancontact or Klarna, or a per-country list of what the claimed one-hundred-plus alternative methods cover. The payment finder is a self-service tool, not a published coverage list. 1 2 3 4
The Skeptic
Cards, the global wallets PayPal, Apple Pay, Google Pay, Skrill, Neteller and Trustly, SEPA and Bacs direct debit and open banking across Europe are all confirmed, but the local-method story stops at "100+ alternative payment methods" and a payment-finder tool. We found no public information naming iDEAL, Bancontact, Klarna or any country-by-country list with the countries each method serves, or refund and recurring support per method. 1 2 3
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
Redirect, iframe and microframe checkout modes, one-click payments and network tokens are real integration choices, and routing plus cascading are pitched squarely at approval rates. But I found no public information on 3-D Secure handling, SCA exemptions, configurable fraud rules or PCI scope per integration type, which is the regulatory heart of getting a payment authorised. 1 4 6 8
The E-Commerce Lead
Redirect, iframe and a three-field microframe give me a checkout that stays on my page, and one-click, Click to Pay, smart routing and cascading are the conversion machinery I care about. But I found no public information on 3-D Secure handling, SCA exemptions, fraud rules or PCI scope per integration — the exact part that decides whether a legitimate EU payment fails at the challenge. 4 5 6 8
The SaaS Founder
Redirect, iframe and microframe checkout modes with one-click payments and network tokenization — bring-your-own tokens included — is a genuine authorisation story. On the PSD2 core, though, I found no public information on 3-D Secure, SCA exemptions, configurable fraud rules, or PCI scope per integration type; risk management appears only as an unexplained line among the core functionalities. The checkout options are published, the SCA and fraud disclosure is not. 4 6 1
The Payments Engineer
Redirect, iframe and a three-field microframe are documented, plus one-click payments, Click to Pay and network tokens — a genuine checkout toolkit. But I found no public information on 3-D Secure, SCA exemption handling, fraud rules exposed to the merchant, or the PCI scope of each integration mode, which is exactly what I need before wiring a checkout into PSD2 Europe. 4 5 6
The Compliance Officer
Redirect, iframe and microframe checkout modes are documented, but we found no public information on 3-D Secure, SCA exemption handling, PCI scope per integration type, or how fraud screening actually works beyond "risk management" named as a core functionality. Authorisation routing and cascading are described for payment performance, not for the PSD2 checkout path. 1 4 6 8
The Skeptic
Redirect, iframe and a three-field microframe checkout are documented alongside real authorisation work — cascading between payment accounts, smart retries and network tokens. But we found no public information on 3-D Secure, SCA exemption handling, fraud screening detail or the PCI DSS scope of any integration type, which is the core of the PSD2 checkout question. 4 6 8
Subscriptions & recurring payments
Show reasoningHide reasoning
How this is scored
Charging the same customer again: card-on-file and merchant-initiated transactions, SEPA mandates, subscription logic and dunning — and whether the stored payment credentials can leave with the merchant.
0 — No stored payment methods; every charge needs the customer to pay again.
3 — Card-on-file tokens for repeat charges, but no SEPA mandate handling, no subscription logic, and failed-payment handling left entirely to the merchant.
5 — Stored cards and SEPA Direct Debit mandates, merchant-initiated transactions documented, and basic subscription plans with scheduled charges and failed-payment notifications.
8 — Subscription billing with trials, proration and plan changes, smart retries and dunning, card account updater, mandate management with pre-notification, and a documented process for exporting payment tokens to another provider.
10 — Recurring revenue is a first-class product: usage-based and invoice-based billing, dunning with measurable recovery, token migration in and out documented with a stated timeline and format, and recurring support stated for every local method that allows it.
The Finance Lead
Scheduled and unscheduled merchant-initiated charges, API-configurable trial periods, smart retries with a configurable queue managed in the dashboard, and recurring across cards, wallets, PayPal and Direct Debit — that is a credible subscription stack. Missing for a finance operation: I found no public information on SEPA mandate management or pre-notification, dunning communications, a card account updater, or any documented process for exporting tokens to another provider. 1 2 5 6 7
The E-Commerce Lead
Recurring is a real product: a scheduled and unscheduled API, trial periods, configurable smart retries with a dashboard-managed retry queue, network tokens I can bring myself, and subscriptions across cards, wallets and Direct Debit including PayPal. What holds it below the top tier is that I found no public information on proration, plan changes outside the PayPal dashboard, SEPA mandate pre-notification, an account updater, or a documented process for taking my tokens to another provider. 2 5 6 7
The SaaS Founder
This is my world: scheduled and unscheduled recurring across cards, wallets and SEPA Direct Debit, API-configurable trial periods, and smart retries with a configurable sequence and a retry queue I can manage from the dashboard — involuntary churn is clearly a design target, and bring-your-own network tokens means my credentials arrive portable. What keeps it from the top band: we found no public information on proration, customer-facing dunning, a card account updater, SEPA mandate pre-notification, or a documented process for exporting tokens out to another provider. 6 2 5 7
The Payments Engineer
Scheduled and unscheduled recurring, API-configurable trial periods, tokenization, and smart retries with a configurable queue managed in the dashboard make a real recurring product across cards, wallets and Direct Debit. I found no public information on proration, a card account updater, SEPA mandate pre-notification, or any documented process for exporting tokens to another provider — bring-your-own network tokens covers bringing credentials in, not taking them out. 5 6 7
The Compliance Officer
Scheduled and unscheduled recurring charges, configurable trials, smart retries with a dashboard-managed queue, and network tokenisation are documented, and Direct Debit and PayPal subscriptions extend beyond cards. We found no public information on mandate pre-notification, an account updater, proration, or a documented process for exporting payment tokens to another provider. 2 5 6 7
The Skeptic
Scheduled and unscheduled merchant-initiated charges, card and direct-debit subscriptions, API-configured trial periods, configurable smart retries and dashboard monitoring of the retry queue are all documented. We found no public information on proration and plan changes, dunning recovery, a card account updater, SEPA mandate pre-notification or a process for exporting payment tokens to another provider — "bring your own network tokens" covers bringing them in, not getting them out. 5 6 7
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
Payouts are described by method and reach — API, manual and a payout page, 70 countries and 40 currencies, SEPA Instant — but I found no public information on payout frequency, per-transaction fee itemisation, or reports tying a payout to its transactions. An API with documentation and a dashboard with reports exist, yet nothing published here would let me reconcile a payout to the bank statement or close a month from the provider's data. 4 5 6 8
The E-Commerce Lead
Payouts come with methods and reach — API, manual and a payout page across 70 countries and 40 currencies, with SEPA Instant — plus a dashboard with reports and documented APIs and SDKs. But I found no public information on payout frequency or delay, per-transaction fee breakdowns, webhooks or a test mode, or exports that tie each payout to its transactions, so finance cannot plan a close on this. 4 6 8
The SaaS Founder
Payouts are the documented half: 70 countries, 40 currencies, SEPA Instant and Faster Payments, initiated by API, manually or through a payout page. On the finance half I found no public information on payout frequency or delay, per-transaction fee itemisation, reconciliation reports that match bank lines, or webhooks and a test mode for the API — my finance team could not close a month on what is published. 8 6 4
The Payments Engineer
Payout coverage is stated plainly — 70 countries, 40 currencies, SEPA Instant and Faster Payments, via API, manual or a payout page — but I found no payout schedule or delay, no per-transaction fee breakdown, and no word on webhooks, a test mode, API versioning, idempotency keys or rate limits. The dashboard promises "detailed analytics and insightful reports" with nothing shown that would back a month-end close, and I found no public information on a status page with incident history. 4 6 8
The Compliance Officer
Payouts across seventy countries and forty currencies with several payout methods and SEPA Instant are described, but we found no public information on payout frequency or delay, per-transaction fee breakdown, or reports that tie each payout to its transactions. A documented API and SDKs exist, though webhook and test-mode details are not shown. 4 6 8
The Skeptic
Payout reach is stated — 70 countries, 40 currencies, SEPA Instant and Faster Payments, via API, manual or a payout page — and a dashboard with analytics and reports exists. We found no public information on payout schedule or delay, per-transaction fee itemisation, webhooks, a test mode, or reports that reconcile payouts to bank lines; the fee story is invisible to the merchant. 8 4 6
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 only terms-level evidence is a complaints route that ends at the UK Financial Ombudsman Service, which at least implies a regulated context and an escalation path with a final response. I found no public information naming the regulated entity, its licence or register number, safeguarding of merchant funds, chargeback fees, or notice periods and reserve limits — the bad-day terms I want written into a contract are not in evidence. 9
The E-Commerce Lead
The one hard fact is a published complaint route to the Financial Ombudsman Service with a stated reply window of 1-3 business days, which is more than nothing. Beyond that I found no public information naming the regulated entity, its supervisor or register number, safeguarding of merchant funds, chargeback fees, or the freeze, reserve and termination terms a merchant signs up to. 9
The SaaS Founder
The published regulatory notice gives merchants a complaint route to the Financial Ombudsman Service with a stated 1-3 business day response window, which is more than nothing on a bad day. Beyond that, we found no public information naming the regulated entity, its supervisor, licence type or register number, safeguarding of merchant funds, chargeback fees, or the terms governing reserves, freezes, notice periods and termination. 9
The Payments Engineer
The regulatory notice gives a complaints escalation route to the Financial Ombudsman Service, which is the only account-terms signal captured. I found no public information naming the regulated entity, its supervisor or register number, safeguarding of merchant funds, chargeback fees and dispute process, or termination, reserve and hold conditions. 9
The Compliance Officer
The regulatory notice gives a complaint escalation route to the Financial Ombudsman Service, but we found no public information naming the regulated entity, its supervisor or its register number, and no published terms on reserves, freezes, termination or chargeback handling. For an acquirer holding merchant funds, that silence is itself the outsourcing risk. 9
The Skeptic
The regulatory notice publishes a complaint escalation route to the Financial Ombudsman Service, which is more than nothing. Yet no regulated entity, supervisor, licence type or register number appears anywhere in the captures, and we found no public information on chargeback fees, reserve and rolling-hold conditions, fund-freeze grounds or ordinary termination notice. 9
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 independently gathered attributes carry no information on the contracting entity's jurisdiction, ownership, data residency or subprocessors; the only regulatory signal on the captured pages is a UK ombudsman referral. With nothing evidenced on where payment and cardholder data are processed or stored, this sits at the bottom of the scale. 9
The E-Commerce Lead
Everything I need to judge this is missing: the captured pages give no contracting entity jurisdiction, no ownership, no statement of where payment and cardholder data are processed, and no subprocessor list. The only regulatory signal anywhere is a complaint route to the UK's Financial Ombudsman Service, which is a UK framework rather than an EU one. 9
The SaaS Founder
Every sovereignty fact a payments buyer needs is missing: we found no public information on the contracting entity's jurisdiction or ownership, on where payment and cardholder data are processed and stored, or on a subprocessor list with locations. The only regulatory signal in the captured pages is a UK ombudsman referral route, which does not evidence an EU entity, an EU licence or EU processing. 9
The Payments Engineer
Nothing captured names the contracting entity's jurisdiction, where payment and cardholder data are processed and stored, or a single subprocessor with a location. The only territorial signal anywhere in the captured pages is the Financial Ombudsman referral, which points at a UK nexus rather than an EU one. 9
The Compliance Officer
We found no public information on the contracting entity's jurisdiction, ownership, where transaction and cardholder data are processed, or who the subprocessors are; the ombudsman referral hints at a UK nexus but nothing is confirmed on the vendor's own captured pages. There is nothing here a regulated merchant could place in an outsourcing file. 9
The Skeptic
The contracting entity's jurisdiction, the ownership, where payment and cardholder data are processed and stored, and the subprocessor list are all unconfirmed on the captured pages. The only territorial signal is a UK ombudsman route, which is neither a licence nor a data-residency statement. 1 9
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
No public prices appear on the captured pages at all — no headline rate, no chargeback, refund or payout fees, no monthly minimums — and the vendor's own positioning funnels toward a conversation about bespoke solutions. As a buyer I cannot compute even a rough effective fee from what is published, so every rate is a sales negotiation. 1
The E-Commerce Lead
No rate appears anywhere in the captured pages — no headline percentage, no per-method pricing, no cross-border or currency-conversion markups, no chargeback or payout fees — so an effective fee for my card and country mix is not computable from public pages. The only path shown is a contact form promising a reply in 1-3 business days and an invitation to chat about bespoke solutions. 1 9
The SaaS Founder
The captured pages show no prices at all — no headline percentage, nothing per method, and nothing on cross-border fees, currency conversion, chargebacks, payouts or monthly minimums. The only pricing-adjacent signal is an invitation to chat about bespoke solutions, so the effective fee for my card and country mix is a sales conversation, not a computation. 1
The Payments Engineer
No public price appears on any captured page — not a headline percentage, not a chargeback fee, not a payout or monthly fee. With the vendor inviting visitors to chat about bespoke solutions, every rate is a sales conversation and the effective fee is unknowable. 1 2 6
The Compliance Officer
The captured pages publish no prices at all, not even a headline rate, with the vendor steering to "bespoke solutions" and a contact form that answers in one to three business days. The effective fee for any merchant mix is a sales conversation. 1 9
The Skeptic
No public price of any kind was captured — no headline rate, no currency-conversion markup, no chargeback or payout fee, no monthly minimum or contract term — and the pages steer the reader to "Let's chat about our bespoke solutions". The effective fee for any card, country and method mix is unknowable from these pages. 1 3
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 ⚠ unverified | — | uncited 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 |
Questions about Ecommpay
Is Ecommpay European?
Not determined: the vendor’s pages as captured do not say where Ecommpay is based.
Where does Ecommpay store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Ecommpay have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Ecommpay?
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: Ecommpay alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 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 — Legal entity. 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.
- We found no public information on pricing on the pages we read (ecommpay.com, ecommpay.com/payment-methods/europe, ecommpay.com/payment-methods, ecommpay.com/core-functionalities/integrations/hosted-payment-page, ecommpay.com/solutions/payment-links, ecommpay.com/solutions/subscriptions and 3 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 55 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
- 5 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
- 4 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 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. 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 (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.ecommpay.com Checked 13 Oct 2026 Details →
- 2 Payment methods & local coverage — found from sitemap ecommpay.com Checked 13 Oct 2026 Details →
- 3 Payment methods & local coverage — found from sitemap ecommpay.com Checked 13 Oct 2026 Details →
- 4 Checkout, SCA & fraud — found from sitemap ecommpay.com Checked 13 Oct 2026 Details →
- 5 Checkout, SCA & fraud — found from sitemap ecommpay.com Checked 13 Oct 2026 Details →
- 6 Subscriptions & recurring payments — found from sitemap ecommpay.com Checked 13 Oct 2026 Details →
- 7 Subscriptions & recurring payments — found from sitemap ecommpay.com Checked 13 Oct 2026 Details →
- 8 Settlement, reconciliation & API — found from sitemap ecommpay.com Checked 13 Oct 2026 Details →
- 9 Licence, risk & account terms — found from sitemap ecommpay.com Checked 13 Oct 2026 Details →