Payment
Paytrail
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Paytrail Oyj · www.paytrail.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.
Paytrail at a glance
- Vendor
- Paytrail Oyj
- 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 Paytrail 1.5/5, the mean of 6 judges. Paytrail Oyj, a Finnish payment provider claiming to be the largest Finnish online payment company, scores highest where its Finnish-market detail is written down: payment methods, recurring billing and settlement and reconciliation each carry a minimum of 4 and maximum of 4, on the strength of nine named Finnish online banks, MobilePay and Siirto, provider-stored card tokens with scheduled charges and seven-day authorization holds, and daily payouts reconciled by order reference and payment stamp. 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
Paytrail Oyj, a Finnish payment provider claiming to be the largest Finnish online payment company, scores highest where its Finnish-market detail is written down: payment methods, recurring billing and settlement and reconciliation each carry a minimum of 4 and maximum of 4, on the strength of nine named Finnish online banks, MobilePay and Siirto, provider-stored card tokens with scheduled charges and seven-day authorization holds, and daily payouts reconciled by order reference and payment stamp. Checkout and SCA scores range 3 to 4, the lower scores reading the PSD2 pages as a regulatory explainer rather than checkout documentation. The weak end is contractual and legal: licence and account terms scores 1 to 3 and sovereignty 1 to 2 — the only supervisory reference is a general note that payment initiation in Finland requires a licence from Finanssivalvonta, and we found no public information on data residency, subprocessors, ownership, reserves or termination notice. Pricing transparency scores 0 to 1 with no prices in the captured pages; that criterion is not counted in the weighted verdicts.
Speaks for it
- All nine Finnish online banks are named one by one, alongside MobilePay, Siirto, the three card schemes, Apple Pay, Google Pay and Click to Pay.
- Card vaulting is documented as provider-stored via a hosted form, with customer- and merchant-initiated transactions and scheduled charges with no technical limits on amounts or billing cycles.
- Payouts default to daily with weekly and per-transaction alternatives, and settlement reports come in XLSX, CSV and PDF with automatic email delivery.
- Reconciliation runs on the order reference and payment stamp, retrievable in real time through the settlement interface.
- Strong customer authentication is stated as already in use on the vendor's card payments with no merchant action required, and the under-30-euro exemption is explained.
Held against it
- International coverage is published as '7 methods for international buyers' with no names, and we found no public information on SEPA Direct Debit or per-method country and currency coverage.
- We found no public information on the vendor's own licence or register number — Finanssivalvonta appears only in a general PSD2 explanation — nor on safeguarding of merchant funds, reserves or termination notice.
- We found no public information on where payment and cardholder data is processed and stored, on subprocessors, on ownership or on a data processing agreement.
- We found no public information on dunning, smart retries, card account updates or any process for exporting stored tokens to another provider.
- The captured pages show no prices, and enabling tokenization starts with a sales contact.
Best for
- You run a Finnish online store and want all nine domestic banks, MobilePay and Siirto plus cards under one agreement.
- You bill subscriptions on stored cards and need scheduled charges with no technical limits on amounts or billing cycles, plus seven-day authorization holds for bookings.
- Your finance team wants daily payouts reconciled by order reference and payment stamp, with reports in XLSX, CSV or PDF.
Avoid if
- You sell mainly beyond Finland and must plan per-method country and currency coverage — the international methods are published only as an unnamed count of seven.
- Your signing process requires the regulated entity's register number and written safeguarding, reserve and termination terms — we found no public information on these, and licence and account terms scored 1 to 3.
- Your compliance review requires published data-residency and subprocessor documentation before contracting — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Payment methods & local coverage | 2 of 5 |
| Checkout, SCA & fraud | 2 of 5 |
| Subscriptions & recurring payments | 2 of 5 |
| Settlement, reconciliation & API | 2 of 5 |
| Licence, risk & account terms | 1 of 5 |
| European sovereignty | 1 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, wallets, every Finnish online bank by name and a deep buy-now-pay-later list are all published, but the whole list points at Finland: I found no public information on SEPA Direct Debit, on any DACH or Benelux method, or on which countries and currencies each method covers. The "seven methods for international buyers" is a count with no names, so a merchant outside Finland cannot plan against it. 1 2
The E-Commerce Lead
The Finnish list is genuinely named — all nine domestic banks plus MobilePay, Siirto, Klarna, OP and Walley invoicing — but for my other seven markets I get "7 methods for international buyers" as a count, and I read counts as counts. I found no public information on SEPA Direct Debit, on the names of the international methods, or on which countries and currencies each one covers, so I cannot plan a market mix from what is published. 1 2
The SaaS Founder
Deep, named coverage of Finland — all nine domestic online banks, MobilePay, Siirto, Klarna and a stack of invoice and instalment services on top of cards, Apple Pay and Google Pay. For the rest of Europe the pages offer only an unnamed "seven methods for international buyers" and a PayPal needing its own direct agreement; we found no public information on SEPA Direct Debit, iDEAL, Bancontact, country-by-currency coverage, or which methods support recurring charges. 1 2
The Payments Engineer
Cards, Apple Pay and Google Pay, all nine Finnish online banks named one by one, MobilePay, Siirto and a deep invoice-and-instalment set give a Finnish merchant a concrete list to plan against. Coverage is Finland-shaped: we found no public information on SEPA Direct Debit or the DACH and Benelux methods, the seven methods for international buyers are an unnamed count, and settlement currencies are unstated. 1 2
The Compliance Officer
Visa, Mastercard and American Express, Apple Pay and Google Pay, every Finnish online bank listed by name, MobilePay, Siirto and a named buy-now-pay-later set make the Finnish coverage unusually concrete. We found no public information on SEPA Direct Debit, on methods for DACH or Benelux markets, or on which countries and currencies the seven international methods serve, and nothing per method on refunds or recurring support. 1 2
The Skeptic
Nine Finnish online banks, MobilePay and Siirto, the three card schemes, the two phone wallets, Click to Pay and a named buy-now-pay-later set give the Finnish market real depth, written down by name. The international story is a headcount — seven methods for international buyers, never named — and we found no public information on SEPA Direct Debit, per-method country and currency coverage, or refund and recurring support per method. A merchant selling beyond Finland cannot plan against this list. 1 2
Checkout, SCA & fraud
Show reasoningHide reasoning
How this is scored
The path from basket to authorised payment under PSD2: hosted and embedded checkout options, 3-D Secure and SCA exemption handling, fraud screening, and what the provider documents about keeping legitimate payments from failing.
0 — A single redirect page with no statement on 3-D Secure, SCA or fraud screening.
3 — Hosted checkout with 3-D Secure 2 mentioned, fraud screening as an unexplained add-on, and no word on exemptions or declined-payment handling.
5 — Hosted and embedded checkout options, 3-D Secure 2 with SCA handled by the provider, configurable fraud rules, and the resulting PCI DSS scope for each integration type stated.
8 — SCA exemptions (low value, transaction risk analysis, merchant-initiated) applied and documented, fraud tooling with rules and risk scores exposed to the merchant, network tokens or account updater, and liability shift explained per flow.
10 — Authorisation is engineered and shown: exemption strategy documented, soft-decline retry handled, authorisation-rate reporting by method and issuer country, and a checkout the merchant can run in their own domain while staying at the lowest PCI scope.
The Finance Lead
Strong customer authentication has been in use on their card payments for some time and the merchant "does not need to do anything", low-value exemptions are acknowledged, and hosted, secure web-interface and native app integrations all appear. What I found no public information on is everything that protects the take rate: fraud screening and configurable rules, declined-payment handling, PCI scope per integration, and liability shift. 4 5
The E-Commerce Lead
Strong authentication is handled for the merchant and the PSD2 page even spells out the under-30-euro exemption, which is the right direction for challenging only when it must, but I found no public information on fraud screening, soft declines, exemption handling in practice, or PCI scope per integration. Card details run through a hosted form with native in-app options, and I found no public information on an embedded checkout that stays on my own domain for the web store. 2 4 5
The SaaS Founder
Strong customer authentication is the provider's problem — the pages say a merchant need not do anything because strong authentication is already in use on card payments, low-value exemptions are acknowledged, and a hosted form plus a native in-app option exist. But we found no public information on fraud screening, configurable risk rules, 3-D Secure specifics, PCI DSS scope per integration or liability shift. 4 5
The Payments Engineer
The vendor states the merchant need not do anything because strong authentication has long been in use on their card payments, exemption categories are explained, and integration modes span a hosted form, web-based in-app interfaces and a native solution. We found no public information on fraud screening, configurable fraud rules, PCI DSS scope per integration type, liability shift or authorisation-rate reporting, which is what separates a documented authorisation path from a compliant redirect. 2 4 5
The Compliance Officer
The PSD2 page states that strong customer authentication is required for cardholder-initiated card payments from September 2019, names exemptions such as payments under 30 euros, and says the merchant need do nothing because strong authentication is already in use on Paytrail's card payments. We found no public information on 3-D Secure by name, fraud screening tools, exemptions applied by the provider, PCI DSS scope per integration, or how declined payments are handled. 4 5
The Skeptic
Strong customer authentication is stated as long in use in card payments and something the merchant need not act on, and the low-value exemption is explained as part of the directive. We found no public information on 3-D Secure by name, fraud screening, web checkout integration options, PCI DSS scope per integration, or how declined payments are handled. What is captured reads as a PSD2 explainer rather than documentation of the checkout itself. 4 5
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
Tokenisation with the provider storing the cards, documented customer- and merchant-initiated transactions, scheduled recurring charges with no limits on amounts or billing cycles, one-click payments and 7-day authorisation holds are all published. For a finance operation the gaps bite: I found no public information on SEPA mandate handling, on retries or dunning for failed charges, or on any process for exporting the stored tokens to another provider. 5
The E-Commerce Lead
Card tokens with both customer- and merchant-initiated transactions documented, scheduled recurring charges with no limits on amounts or billing cycles, and compatible platforms named — that covers my subscription basics, and the seven-day authorization hold with charge-on-confirmation is a nice touch for bookings. But I found no public information on SEPA mandates, dunning or failed-payment notifications, an account updater, or any documented process for taking the tokens to another provider. 1 5
The SaaS Founder
Card vaulting is real — stored cards via the hosted form, customer- and merchant-initiated transactions both explained, scheduled charges with no technical limits on amounts or billing cycles, one-click payments and seven-day authorization holds. But we found no public information on SEPA Direct Debit mandates, dunning or smart retries, proration and plan changes, or a documented process for exporting payment tokens to another provider — the point that decides whether I sign. 1 5
The Payments Engineer
Recurring is real engineering, not a sticker: stored cards via a hosted form, customer- and merchant-initiated transactions both documented, scheduled charges with no technical limits on amounts or cycles, and a seven-day authorisation hold converted only on confirmation. We found no public information on SEPA mandate handling, smart retries or dunning, a card account updater, or any documented way to export stored credentials to another provider. 5
The Compliance Officer
Card-on-file tokenisation through the provider's hosted form, documented customer- and merchant-initiated transaction models, scheduled charges with no limits on amounts or billing cycles, and seven-day authorization holds charged on confirmation are all published. We found no public information on SEPA mandate handling, subscription plan logic such as trials or proration, dunning or retry handling, card account updates, or a process for exporting stored tokens to another provider. 5
The Skeptic
Customer- and merchant-initiated transactions are both defined, cards are vaulted by the provider through a hosted form, and scheduled charges with seven-day authorization holds are written down with compatible platforms named. We found no public information on SEPA mandates, dunning or smart retries, card account updates, or any process for exporting stored tokens to another provider — and getting tokenization switched on starts with the sales team. 5
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
Payout cadence is stated plainly — daily by default, weekly or per transaction on request — and settlement reports come with transaction-specific listings, reconciliation keys (order reference and payment stamp), automatic email delivery and an interface to automate accounting, which is genuinely usable. But payouts are described as "all payments per day as one lump sum", and I found no public information on per-transaction fee itemisation, payout delay, settlement currencies, webhooks, test mode or API versioning. 1 6
The E-Commerce Lead
Daily settlement as the default with weekly and per-transaction alternatives, payment data retrievable in real time through an interface, reports in several formats carrying the order number and a payment identifier for reconciliation, and accounting automation off the settlement interface — that is workable finance plumbing. Fees are not itemised per transaction in anything I found, payout delay and settlement currencies are unstated, and I found no public information on webhooks or a documented API test mode, though a service-availability page and a 99.98 percent availability figure are published. 1 6
The SaaS Founder
Daily settlement is the default with weekly or per-transaction alternatives, reports auto-generate in XLSX, CSV or PDF with transaction-specific listings, email to the accountant, and reconciliation on order number and payment identifier. But payout delay is never stated, and we found no public information on per-transaction fee breakdowns, webhooks, a test mode, or API versioning and rate limits. 6
The Payments Engineer
Payout cadence is stated with alternatives — daily by default, weekly or per transaction — and the finance tooling is concrete: a settlement interface exposing the order reference and payment stamp for reconciliation, XLSX, CSV, PDF and json reports with automatic email delivery, real-time payment data retrieval and accounting automation. We found no public information on payout delay, per-transaction fee breakdown, webhooks, a test mode, API versioning or rate limits, and while a service availability page and a 99.98 percent figure are published, incident history is not evidenced. 1 6
The Compliance Officer
Daily payouts as the default with weekly and per-transaction alternatives, a settlement interface retrieving payment data in real time, transaction-specific settlement listings in XLSX, CSV and PDF, automated email reports, and reconciliation by order number and payment identifier are published, alongside a service availability page. We found no public information on a per-transaction fee breakdown in reports, on webhooks, or on API versioning, idempotency and rate limits. 1 6
The Skeptic
Daily payouts are the default with weekly and per-transaction alternatives, settlement and payment data are retrievable in real time over an interface, reports come in XLSX, CSV and PDF with a transaction-specific listing, and reference and stamp fields tie payouts to orders. We found no public information on payout delay, settlement currencies, per-transaction fee itemisation or webhooks, so the fee side of each payout stays dark. 6 1
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 regulatory fact captured is that payment-initiation activity requires a licence from Finanssivalvonta in Finland; the contracting entity's own licence, register number and safeguarding of merchant funds are not stated anywhere I can see. On the terms I actually buy on — reserves and rolling holds, freezes, termination notice, chargeback fees, dispute route — I found no public information beyond a notice that agreement terms and a price list have changed. 4 7
The E-Commerce Lead
The supervisor is named — Finanssivalvonta, in the context of payment-initiation licensing — and the company presents itself as a Finnish payment firm since 2007. Beyond method-specific American Express rules on cardholder-data use and marketing, I found no public information on the regulated entity's register number, safeguarding of merchant funds, reserve or hold conditions, chargeback fees, or any termination notice period. 3 4
The SaaS Founder
The only licence signal is a PSD2 explainer noting payment initiation requires a licence from a supervisor that in Finland is the Finnish Financial Supervisory Authority — a statement about the law rather than one pinned to the vendor's own entity and register number. We found no public information on safeguarding of merchant funds, reserve or rolling-hold conditions, termination notice, chargeback fees or a dispute route in the captured pages. 4 7
The Payments Engineer
The vendor presents itself as Paytrail Oyj and a PSD2 explainer names the Finnish supervisor for payment initiation licensing, but we found no public information on the licence type, register number or safeguarding of merchant funds. A page about changes to the agreement terms and price list was captured, yet reserve and hold conditions, freeze and termination terms, notice periods, chargeback fees and the dispute process are all unevidenced — the bad day is simply not written down anywhere I was shown. 4 7
The Compliance Officer
The captured pages give no regulated entity named with its supervisor and register number for the merchant relationship; the only supervisory reference is a general PSD2 explanation that payment initiation requires a licence from Finanssivalvonta in Finland. We found no public information on reserves or holds, termination notice, chargeback fees or a dispute process, even though a page on changes to agreement terms and the price list was captured. 4 7
The Skeptic
No licence, register number or supervisor for Paytrail itself appears in the captured pages — the Finnish authority shows up only in a general explanation of what PSD2 requires of payment institutions. We found no public information on reserves, fund freezes, termination notice or chargeback fees; even the captured page announcing changes to agreement terms and the price list yields nothing on the terms. 4 7
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 vendor presents itself as the largest Finnish online payment company under Finnish supervision, which is a start, but every attribute that matters — where payment and cardholder data is processed and stored, who the subprocessors are and where they sit, ownership — is unconfirmed in the captured pages, and partners such as Nets and Liberis appear in the chain with no published locations. With no data-residency statement, no subprocessor list and no data-processing agreement to point at, I cannot treat this as evidenced European processing. 1 2 4
The E-Commerce Lead
The pages point to a Finnish company supervised by Finanssivalvonta with domestic customer service and every Finnish bank on board, which is where I would want a provider to start. But I found no public information on where payment and cardholder data are processed or stored, on ownership, or on any subprocessor list, and for a seller who only ships inside the EU that silence is the whole question. 1 4
The SaaS Founder
Every page reads Finnish — largest Finnish online payment company, domestic multichannel customer service, building Finnish payment infrastructure since 2007 — which is promising for a Europe-first stack. But we found no public information on the contracting entity's jurisdiction, where payment and cardholder data are processed, or a subprocessor list with locations. 1
The Payments Engineer
We found no public information on where transaction and cardholder data are processed or stored, on group ownership, or on any subprocessor list with locations. The only European signals are the vendor's own claim to be the largest Finnish online payment company and a PSD2 explainer naming the Finnish supervisor — marketing context rather than a processing statement. 1 4
The Compliance Officer
Card details are stated to be stored by the provider, but we found no public information on where transaction and cardholder data are processed or stored, on the contracting entity's jurisdiction beyond the company name, on ownership, or on subprocessors and their locations. No data processing agreement splitting processor and controller roles appears in the captured pages. 1 5
The Skeptic
The vendor presents as a Finnish company running Finnish bank payments, but the contracting entity's jurisdiction, ownership, data residency and subprocessors are all unevidenced. We found no public information on where payment or cardholder data is processed and stored, on any subprocessor list, or on a data processing agreement; the European character here is an inference from marketing language, not a published fact. 1 2
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
I found no public prices at all in the captured material — no percentages, no chargeback, refund or payout fees, no monthly fee or contract term — so an effective rate for any card or country mix is not computable. The only trace of pricing is a notice about changes to a price list, and getting features such as tokenisation enabled runs through the sales team. 5 7
The E-Commerce Lead
I found no public information on any price — no headline rate, no per-method fees, no chargeback, payout or monthly costs — and even enabling tokenization is routed through the sales team. There is nothing published that would let me start computing an effective fee for my card and country mix. 1 5
The SaaS Founder
We found no public prices in the captured pages — no headline percentage, no per-method rate, no chargeback, conversion or payout fees — so an effective fee is not computable from anything published here. The only pricing-related capture is a news notice that agreement terms and the price list are changing. 7
The Payments Engineer
We found no public prices at all — no rate, method fee, chargeback, refund, payout or monthly fee is stated in the captured pages, and tokenisation onboarding runs through the sales team, which matches a model where every rate is a sales conversation. A page titled changes to the agreement terms and price list was captured, but no figure from it is stated, so an effective fee cannot be computed from anything public. 5 7
The Compliance Officer
We found no public prices on any captured page, and even the page titled changes to agreement terms and price list yielded no figures. Enabling tokenisation is routed through the sales team, so a merchant has no way to compute an effective fee for their card and country mix from the public pages. 5 7
The Skeptic
The captured pages show no prices at all — no headline percentage, no chargeback fee, no payout or monthly fee, and nothing on currency conversion markups or blended versus interchange++. A page whose address announces changes to the price list shows no figures, and the path to tokenization runs through a sales contact. The effective fee is a conversation, not a computation. 7 5
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about Paytrail
Is Paytrail European?
Not determined: the vendor’s pages as captured do not say where Paytrail is based.
Where does Paytrail store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Paytrail have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Paytrail?
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: Paytrail 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.
- 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.
- 5 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.paytrail.com Checked 13 Oct 2026 Details →
- 2 Payment methods & local coverage — found from sitemap www.paytrail.com Checked 13 Oct 2026 Details →
- 3 Payment methods & local coverage — found from sitemap www.paytrail.com Checked 13 Oct 2026 Details →
- 4 Checkout, SCA & fraud — found from sitemap www.paytrail.com Checked 13 Oct 2026 Details →
- 5 Subscriptions & recurring payments — found from sitemap www.paytrail.com Checked 13 Oct 2026 Details →
- 6 Settlement, reconciliation & API — found from sitemap www.paytrail.com Checked 13 Oct 2026 Details →
- 7 Licence, risk & account terms — found from sitemap www.paytrail.com Checked 13 Oct 2026 Details →