Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

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

by IXOPAY GmbH · www.ixopay.com

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

Link to this page

IXOPAY: AI-assisted analysis on whats-best.ai IXOPAY: 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.

IXOPAY at a glance

Vendor
IXOPAY GmbH
Headquarters
Not stated on the vendor’s pages as of 11 Nov 2026
Data hosting
In the EU by default source, captured 11 Nov 2026
Free plan
Not stated on the vendor’s pages as of 11 Nov 2026
Panel verdict
The AI panel rates IXOPAY 2/5, the mean of 6 judges. IXOPAY, a payment orchestration platform from IXOPAY GmbH, is strongest on payment methods, scores clustering at 6-7 — a country-labelled catalogue spanning iDEAL, Bancontact, BLIK, Przelewy24, eps, Multibanco, SEPA Direct Debit and Klarna variants across 250+ acquirer adapters and 300+ methods — and on recurring billing at 5-6, with automated retries, card data updates and portable merchant-owned tokenization claimed. how scores are made
As of
Vendor pages captured 11 Nov 2026; evaluated by the panel 11 Nov 2026. all sources

IXOPAY alternatives, European ones first →

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

The panel's verdict

IXOPAY, a payment orchestration platform from IXOPAY GmbH, is strongest on payment methods, scores clustering at 6-7 — a country-labelled catalogue spanning iDEAL, Bancontact, BLIK, Przelewy24, eps, Multibanco, SEPA Direct Debit and Klarna variants across 250+ acquirer adapters and 300+ methods — and on recurring billing at 5-6, with automated retries, card data updates and portable merchant-owned tokenization claimed. Weakest among the weighted criteria is licence and account terms, scored 2-3: the imprint gives IXOPAY GmbH, Vienna Commercial Court FN 451099g, states the business purpose as IT-Service provider, and the captured pages name no payment licence, supervisor or regulated partner. Checkout and SCA, settlement and reconciliation and sovereignty each scored 4 — hosted pages and 3-D Secure without public detail on SCA exemptions or PCI scope, reconciliation without payout schedules or fee itemisation, and an EU Data Act statement placing orchestration operations in Austria while standalone modules and the Card Account Updater run in the USA. Pricing transparency, not counted in these verdicts, scored lowest at 1-2; the only pricing statement is usage-based commercial packages. Score ranges stayed within a point.

Report an error

Speaks for it

  • A country-labelled catalogue of local payment methods — iDEAL, Bancontact, BLIK, Przelewy24, eps, Multibanco, SEPA Direct Debit, Klarna variants — across 250+ acquirer adapters and 300+ methods
  • Automated retries and card data updates documented for recurring charges, with SEPA Direct Debit described for subscriptions and a recurring-payments guide in the documentation
  • Merchant-owned universal tokenization with portability across channels claimed on the homepage
  • A transparent Austrian imprint: IXOPAY GmbH, Vorgartenstrasse 206c, 1020 Vienna, FN 451099g at the Vienna Commercial Court, EU VAT ID ATU 71998225
  • Automated reconciliation named as a core capability, backed by a reconciliation API and provider-settlement documentation

Report an error

Held against it

  • The imprint states the business purpose as IT-Service provider and names IXOPAY GmbH while the copyright line names IXOPAY, INC., with no public information naming a payment licence, supervisor or regulated partner
  • We found no public information on chargeback fees, dispute processes, safeguarding or termination terms, with a rolling-reserve documentation page stating no limits or release timelines
  • The checkout evidence stops at hosted payment pages and 3-D Secure, with no public information on SCA exemptions, configurable fraud rules or PCI DSS scope
  • We found no public information on payout schedules, settlement currencies, per-transaction fee itemisation or reports matching payouts to bank lines
  • Standalone payment modules and the Card Account Updater are stated to run in USA jurisdiction, with USA transfers disclosed in cookie consent and no public information on a data processing agreement or subprocessor list

Report an error

Best for

  • You sell across many European markets at once and need local methods named per country, from iDEAL and Bancontact to BLIK, eps and Multibanco
  • You run a subscription business and want automated retries, card data updates, SEPA Direct Debit and a merchant-owned tokenization layer with portability
  • You already hold PSP and acquirer relationships of your own and want an orchestration, routing and reconciliation layer on top of them

Report an error

Avoid if

  • You must verify a payment licence, a financial supervisor or safeguarding arrangements from public pages before shortlisting a provider
  • Your finance team closes the month from vendor reporting and needs payout schedules, fee itemisation and payout-to-bank-line matching documented
  • You need every component of the stack, including the Card Account Updater, running under EU jurisdiction
  • You need SCA exemption handling, configurable fraud rules and PCI DSS scope documented before committing to a checkout

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Payment methods & local coverage 3 of 5
Checkout, SCA & fraud 2 of 5
Subscriptions & recurring payments 3 of 5
Settlement, reconciliation & API 2 of 5
Licence, risk & account terms 1 of 5
European sovereignty 2 of 5

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

The payment methods catalogue names each method with its countries — iDEAL, Bancontact, BLIK, Przelewy24, eps, giropay, Multibanco and SEPA Direct Debit among them — a list a merchant can genuinely plan against. We found no public information on currencies per method, settlement currencies, or refund and recurring support per method, so it stops short of a full planning matrix. 4 1 8

Report an error

The E-Commerce Lead

The named list is genuinely useful for a multi-market EU shop: iDEAL for the Netherlands, Bancontact for Belgium, BLIK and Przelewy24 for Poland, eps for Austria, Multibanco for Portugal, Satispay and Bancomat Pay for Italy, giropay and Sofort for Germany, plus SEPA Direct Debit and Klarna variants. I found no French or Spanish local method named, cards and wallets appear only generically, and no currencies, refund or recurring support are documented per method — so I can plan most markets but not against a full matrix. 4 8

Report an error

The SaaS Founder

The payment methods hub names a broad list with country coverage — SEPA Direct Debit, iDEAL, Bancontact, BLIK and BLIK One Click, eps, giropay, Przelewy24, Multibanco and Klarna variants — with cards and wallets claimed across 300+ methods. We found no public information on currencies per method, settlement currencies, or per-method refund and recurring support, so I cannot plan a market entry against it, only be reassured the breadth is there. 1 4 8

Report an error

The Payments Engineer

The payment methods knowledge hub names a genuinely broad catalog per country — iDEAL, Bancontact, BLIK and BLIK One Click, eps, giropay, Przelewy24, Multibanco, Satispay, Paysera, TrustPay, SEPA Direct Debit and more — alongside pre-built adapters for over 250 acquirers and 300+ payment methods. What I cannot plan against is the matrix detail: currencies and settlement per method, and which methods support refunds and recurring charges, are not documented on the captured pages. 4 1 8

Report an error

The Compliance Officer

A long catalogue of local methods is published with the country each serves — iDEAL for the Netherlands, BLIK and Przelewy24 for Poland, eps for Austria, Bancontact for Belgium, Multibanco for Portugal, SEPA Direct Debit for the SEPA area, plus Klarna, Sofort and Trustly for selected European countries — well beyond a card-and-wallet list. Cards themselves are described only generically as credit, debit and wallet acceptance across 300+ methods routed through 250+ acquirer adapters, and no currency, refund or recurring support is stated for any method, so a merchant cannot yet plan against a full matrix. 4 8 1

Report an error

The Skeptic

Three hundred plus payment methods across 250+ acquirer adapters, and the knowledge hub names local methods per country — BLIK and Przelewy24 in Poland, eps in Austria, iDEAL, Bancontact, SEPA Direct Debit and Klarna variants. We found no public information on settlement currencies per method or on which methods support refunds and recurring charges, and nothing separating the provider's own acquiring from third-party routing. 1 4

Report an error

Checkout, SCA & fraud

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

Hosted payment pages and 3-D Secure are documented, and fraud prevention is described as real-time transaction monitoring, machine learning and 3-D Secure authentication. We found no public information on embedded checkout, SCA exemption handling, or configurable fraud rules, so I cannot verify from the captured pages how legitimate payments are kept from failing. 8 6 7

Report an error

The E-Commerce Lead

The documentation covers hosted payment pages and a 3-D Secure feature, and the captured pages describe real-time transaction monitoring and machine-learning fraud screening with 3DS authentication. I found no public information on an embedded or merchant-domain checkout, SCA exemption handling, configurable fraud rules, or PCI scope — exactly the details that decide whether my legitimate payments pass. 6 7 8

Report an error

The SaaS Founder

3-D Secure authentication, real-time transaction monitoring and machine-learning fraud prevention are named, and documentation pages exist for 3-D Secure and hosted payment pages. We found no public information on SCA exemption handling, configurable fraud rules or authorisation-rate reporting, so this reads as a hosted checkout with 3DS rather than an engineered-authorisation story. 6 7 8

Report an error

The Payments Engineer

Hosted payment pages and 3-D Secure are documented — there is a dedicated documentation page for hosted payment pages, and 3DS is listed alongside real-time transaction monitoring and machine learning fraud prevention. I found no public information on SCA exemption handling, embedded checkout options, configurable fraud rules with risk scores, or the PCI DSS scope of each integration type, so I cannot place it above the hosted-page-plus-3DS level. 7 6 8

Report an error

The Compliance Officer

Three-D Secure authentication, machine learning and real-time transaction monitoring are documented as fraud tooling, and the vendor's documentation includes hosted payment pages. We found no public information on SCA exemption handling, the PCI DSS scope of each integration type, or liability shift, so the path to authorisation is only partly evidenced. 8 7

Report an error

The Skeptic

Hosted payment pages and a 3-D Secure feature are documented, and real-time transaction monitoring, machine learning and 3DS authentication are named. We found no public information on SCA exemptions, configurable fraud rules, PCI DSS scope or liability shift — the checkout story stops at 3-D Secure existing. 6 7 8

Report an error

Subscriptions & recurring payments

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

For subscription services they document automated retries and card data updates across multiple gateways, a recurring-payments guide, and SEPA Direct Debit described for recurring charges — and the merchant-owned tokenization layer with stated portability matters to me, because tokens that can leave keep my options open. We found no public information on trials, proration, plan changes, mandate pre-notification, or a documented token export process with a timeline. 8 9 4 1

Report an error

The E-Commerce Lead

For subscriptions there is real substance: automated retries and card data updates, a recurring-payments guide in the documentation, SEPA Direct Debit described for recurring charges, and a merchant-owned tokenization layer with portability claimed. I found no public information on mandate management with pre-notification, dunning, trials and plan changes, or a documented token migration process with a stated timeline and format. 8 9 4 1

Report an error

The SaaS Founder

The pieces I live on are named: automated retries, card data updates, SEPA Direct Debit for subscriptions, and a merchant-owned tokenization layer described as giving portability — an ownership claim on the tokens, which is the part most providers keep hostage. We found no public information on dunning with recovery measurement, proration, trials and plan changes, mandate pre-notification, or a documented token export process with a stated timeline, so it stops short of the level I would move a subscriber base onto. 1 2 4 8 9

Report an error

The Payments Engineer

Automated retries, card data updates (a Card Account Updater module exists, stated to run under US jurisdiction), SEPA Direct Debit for recurring charges, and merchant-owned universal tokenization with portability — that token ownership is exactly what I want, since stored credentials are not captive to the platform. Subscription mechanics like trials, proration and plan changes, dunning with measurable recovery, mandate pre-notification and a documented token migration timeline are not documented on the captured pages. 8 4 1 2 9

Report an error

The Compliance Officer

Recurring optimisation is described with automated retries, card data updates and multi-gateway management, SEPA Direct Debit is listed as enabling recurring charges across the SEPA area, and a merchant-owned tokenization layer with portability of payment data is claimed. We found no public information on subscription plan logic such as trials or proration, dunning, mandate pre-notification, or the format and timeline for exporting tokens to another provider. 8 4 1

Report an error

The Skeptic

Automated retries and card data updates are promised, a Card Account Updater product exists (its ICT jurisdiction stated as the USA), and SEPA Direct Debit is described as covering recurring payments for subscriptions. Merchant-owned, portable tokenization is claimed on the homepage, but we found no public information on a token-export process, dunning, trials or proration. 1 2 4 8

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

Automated reconciliation is a headline capability, and a reconciliation API plus provider settlement documentation exist — the right bones for a month-end close. But we found no public information on payout schedules, fee itemisation per transaction, webhooks, or reports tying each payout to its bank line, which is what I actually close the month on. 1 10 11

Report an error

The E-Commerce Lead

Automated reconciliation is claimed on the homepage and the documentation includes a reconciliation API and provider settlement processing pages, which is promising for finance. But payout schedules, fee itemisation, webhooks, a test mode and accounting exports are not shown on any captured page, so I cannot tell whether my finance team could close the month from this data. 1 10 11

Report an error

The SaaS Founder

Automated reconciliation is claimed on the homepage and documentation pages exist for a reconciliation API and for provider settlements, so finance tooling is clearly real. We found no public information on payout schedules, fee itemisation per transaction, bank-statement matching, webhooks or a test mode, so I cannot confirm month-end close from the public pages. 1 10 11

Report an error

The Payments Engineer

Automated reconciliation is named as a core capability, and dedicated documentation exists for a reconciliation API and for provider settlements, which suggests a real finance data path. But nothing captured states payout schedules or settlement currencies, fee itemisation per transaction, or an API with versioning, idempotency, rate limits, test mode and a public status page — as the person paged when webhooks stop arriving, I have no documented incident surface to point at. 1 10 11

Report an error

The Compliance Officer

Automated reconciliation is named as a core capability, and the vendor's documentation includes provider settlement and reconciliation API pages, so reporting and settlement are clearly part of the product. The captured pages show no payout schedule or settlement currencies, no fee itemisation per transaction, and no webhook or test-mode detail, so a finance team closing the month from this data is not evidenced. 1 11 10

Report an error

The Skeptic

Automated reconciliation is a homepage promise, with a reconciliation API, provider-settlement documentation and a public code repository behind it. We found no public information on payout schedules, settlement currencies, fee itemisation or exports that match a bank line — for an orchestrator the money still comes from the PSPs behind the adapters, and those questions stay open. 1 3 10 11

Report an error

Licence, risk & account terms

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 imprint is proper — IXOPAY GmbH, Vienna, register number FN 451099g at the Vienna Commercial Court, EU VAT ATU 71998225 — but the stated business purpose is IT service provider, and we found no public information on a payment licence, a regulated partner behind the funds, safeguarding, or a chargeback and dispute process. Documentation on rolling reserve post-processing exists, but we found no public information on limits or release timelines. 2 12

Report an error

The E-Commerce Lead

The legal notice names IXOPAY GmbH in Vienna with commercial register number FN 451099g, an EU VAT ID and Austrian chamber membership, so the contracting entity is transparent. But the licensed partner behind the money movement is not named, and I found no public information on a dispute process, chargeback fees, safeguarding, reserve conditions, or termination and freeze terms — only a rolling-reserve page in the platform documentation. 2 12

Report an error

The SaaS Founder

The imprint is thorough — IXOPAY GmbH, Vienna Commercial Court register number FN 451099g, EU VAT ID, WKO membership under Austrian law — and a rolling-reserve documentation page exists. But we found no public information on a payments licence or regulated partners behind the transactions, chargeback or dispute processes, safeguarding of merchant funds, or freeze and termination terms; also the site copyright names IXOPAY, INC. while the legal notice names IXOPAY GmbH, and the captured pages give no explanation of how the two relate. 1 2 12

Report an error

The Payments Engineer

The legal notice gives a proper Austrian imprint — IXOPAY GmbH of Vienna, commercial register number FN 451099g at the Vienna Commercial Court, business purpose 'IT-Service provider' — while the copyright line names IXOPAY, INC., so the captured pages give different names for the entity. Either way, I found no public information naming a licensed payments entity or supervisor behind the funds, safeguarding of merchant money, a dispute or chargeback process, or freeze, reserve and termination terms with reasons and appeal. A rolling-reserve documentation page exists, but no reserve conditions, limits or release timelines are captured. 2 12 1

Report an error

The Compliance Officer

The contracting entity is properly identified — IXOPAY GmbH, Vorgartenstrasse 206c, 1020 Vienna, registered at the Vienna Commercial Court under FN 451099g, WKO member, with the district municipal authority named as competent under the Austrian trade and e-commerce acts — which is a trade registration, not a payment licence. We found no public information on any payment-services licence or financial supervisor, safeguarding of merchant funds, a dispute or chargeback process, or termination terms; a rolling-reserve page exists in the documentation but the captured pages state no limits or release timelines. 2 12

Report an error

The Skeptic

The imprint gives clean corporate transparency — IXOPAY GmbH, register number FN 451099g at the Vienna Commercial Court, Austrian VAT ID — but states the business purpose as IT-Service provider and names no payment licence, supervisor or regulated partner behind the payments. We found no public information on chargeback fees, safeguarding, reserve conditions or termination terms; a rolling-reserve document title is the only risk-related capture. 1 2 12

Report an error

European sovereignty panel opinion

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

The EU Data Act statement places Payment Orchestration Operations in Austria, while standalone payment modules and the Card Account Updater sit in the USA — core processing is European, part of the stack is not. We found no public information on a data processing agreement, subprocessor locations, or hosting options, and the US corporate presence plus consent-based Google Analytics transfers to the USA temper the picture. 2 1

Report an error

The E-Commerce Lead

Core payment orchestration operations are stated as subject to Austria, which is what I want to hear for my EU sales, and the publishing entity is a Vienna-registered GmbH. However, standalone payment modules and the card account updater sit under US jurisdiction, the copyright and trademark are held by IXOPAY, Inc., and I found no public information on a data processing agreement or a subprocessor list. 2 8

Report an error

The SaaS Founder

The contracting entity is Austrian and a Data Act statement puts payment orchestration operations in Austria — core payment processing in the EU, stated. Standalone payment modules and the Card Account Updater are stated to run in the USA, cookie consent relies on consent-based transfers to the USA, and we found no public information on a data processing agreement, subprocessor list or named hosting infrastructure — and the updater sitting outside the EU is exactly the piece a subscription business like mine cares about. 2 6

Report an error

The Payments Engineer

The EU Data Act statement puts payment orchestration operations under Austrian jurisdiction, and the publisher is IXOPAY GmbH of Vienna, so the core orchestration layer in the EU is stated. However, standalone payment modules and the Card Account Updater are stated to run in the USA, cookie consent includes USA transfers under Article 49, and I found no public information on a data processing agreement or a subprocessor list with locations. 2 6 1

Report an error

The Compliance Officer

The publisher is an Austrian company with a commercial register number, and the Data Act statement places payment orchestration operations in Austria — but the same statement places the standalone payment modules and the Card Account Updater under United States jurisdiction, and the site copyright is attributed to IXOPAY, INC., so part of the chain is American. No subprocessor list, data processing agreement, or controller-versus-processor split appears in the captured pages, and the cookie consent itself discloses personal data transfers to the USA under Article 49 consent for Google Analytics. 2 6

Report an error

The Skeptic

The contracting entity is Austrian and the EU Data Act statement puts payment orchestration operations in Austria — but standalone payment modules and the Card Account Updater are stated as USA-jurisdiction, and the site's own cookie consent covers USA transfers under Art 49 GDPR. We found no public information on a data processing agreement, a subprocessor list or hosting options. 2 6 9

Report an error

Pricing transparency not rated — the vendor publishes no price

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 one pricing statement on the captured pages is "Usage-based commercial packages, pay for capabilities and usage needed" — a commercial model, not a rate. We found no public information on any percentage, monthly fee, chargeback fee, or payout fee, so I cannot compute an effective rate for my own card and country mix. 1

Report an error

The E-Commerce Lead

The only pricing signal is a qualitative statement about usage-based commercial packages where you pay for the capabilities and usage you need; I found no public rates, plan fees, or ancillary fees on any captured page. As a merchant I could not begin to compute my effective fee from this. 1

Report an error

The SaaS Founder

We found no public prices on any page captured — the only pricing signal is usage-based commercial packages where you pay for the capabilities and usage you need, with no rate, percentage, fee or tier published. A merchant cannot compute even a headline cost from this, let alone an effective rate for their card and country mix. 1

Report an error

The Payments Engineer

The only pricing statement captured is 'usage-based commercial packages' — pay for the capabilities and usage you need — which describes a model without a single figure. I found no public information on any rate, 'from' percentage, monthly fee or ancillary charge, so a merchant can compute nothing from the public pages. 1

Report an error

The Compliance Officer

The only public pricing statement is that commercial packages are usage-based — pay for the capabilities and usage you need as your business grows. We found no published rate, fee, plan price, monthly minimum or contract term anywhere in the captured pages, so a merchant can compute nothing for their own card and country mix. 1

Report an error

The Skeptic

The only public pricing statement is 'Usage-based commercial packages, pay for capabilities and usage needed' — a model, not a number. We found no published rate, monthly fee, chargeback fee, currency-conversion markup or payout fee on the captured pages, so a merchant cannot compute any effective cost before the sales conversation. 1

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location EU by default unverified
Why unverified?

This is an EU Data Act statement on where the ICT infrastructure is subject, split by service rather than a default storage claim — the core payment orchestration runs in Austria (EU) but standalone payment modules and the Card Account Updater run in the USA, so data is not stored only in the EU.

2/4 pts 2 Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about IXOPAY

Is IXOPAY European?

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

Where does IXOPAY store data?

IXOPAY stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 11 Nov 2026.

Does IXOPAY have a free plan?

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

What are the best alternatives to IXOPAY?

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: IXOPAY 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 (12)

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

  1. 1 Vendor page www.ixopay.com Checked 11 Nov 2026 Details →
  2. 2 Legal notice — found from the homepage www.ixopay.com Checked 11 Nov 2026 Details →
  3. 3 Code repository (open-source licence) — found from the homepage github.com Checked 11 Nov 2026 Details →
  4. 4 Payment methods & local coverage — found from sitemap www.ixopay.com Checked 11 Nov 2026 Details →
  5. 5 Payment methods & local coverage — found from sitemap documentation.ixopay.com Checked 11 Nov 2026 Details →
  6. 6 Checkout, SCA & fraud — found from sitemap documentation.ixopay.com Checked 11 Nov 2026 Details →
  7. 7 Checkout, SCA & fraud — found from sitemap documentation.ixopay.com Checked 11 Nov 2026 Details →
  8. 8 Subscriptions & recurring payments — found from sitemap www.ixopay.com Checked 11 Nov 2026 Details →
  9. 9 Subscriptions & recurring payments — found from sitemap documentation.ixopay.com Checked 11 Nov 2026 Details →
  10. 10 Settlement, reconciliation & API — found from sitemap documentation.ixopay.com Checked 11 Nov 2026 Details →
  11. 11 Settlement, reconciliation & API — found from sitemap documentation.ixopay.com Checked 11 Nov 2026 Details →
  12. 12 Licence, risk & account terms — found from sitemap documentation.ixopay.com Checked 11 Nov 2026 Details →