Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

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

by TinTel B.V. · www.pay.nl

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

Link to this page

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

Pay. at a glance

Vendor
TinTel B.V.
Headquarters
Not stated on the vendor’s pages as of 16 Nov 2026
Data hosting
In the EU source, captured 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates Pay. 3/5, the mean of 6 judges. Pay. how scores are made
As of
Vendor pages captured 1 Nov 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

Pay. alternatives, European ones first →

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

The panel's verdict

Pay. is TinTel B.V. of Spijkenisse, a Dutch payment institution licensed by De Nederlandsche Bank since 29 July 2013, and its paperwork is the strongest part of this file: licence and account terms score 6-7, with trade register number 24283498, merchant funds segregated at Stichting Derdengelden Pay. (register number 50152769) at a Wft-licensed credit institution, and PCI DSS Level 1 audited annually since 2014. Settlement and reconciliation also scores 6-7 on MT940 and Coda XML statement files delivered by e-mail, SFTP or API and direct accounting integrations into Exact Online, e-Boekhouden.nl, Twinfield and Yuki; pricing transparency scores 6-7 on per-method rates published to the cent. The clear weak spot is recurring billing, scored 4: periodic debits and batch upload are documented, but we found no public information on dunning, failed-payment handling or token export. Sovereignty sits at 5 — 'Our data is stored in Dutch data centres' is marketing copy without exclusivity, and we found no public information on a subprocessor list with locations. Score ranges span at most one point; no meaningful split was recorded.

Report an error

Speaks for it

  • Licence and safeguarding chain written down in checkable detail — TinTel B.V. under trade register number 24283498, a De Nederlandsche Bank licence granted 29 July 2013, and merchant funds at Stichting Derdengelden Pay. (register number 50152769)
  • MT940 and Coda XML bank statement files delivered by e-mail, SFTP or API push, with direct integrations into Exact Online (xCore), e-Boekhouden.nl, Twinfield and Yuki
  • Card rates published to the cent per tier — Visa and Mastercard at €0,12 + 1,30% on Business and €0,15 + 1,50% on Professional — with a currency conversion fee of €0.03 per payment and 2.75% of the transaction value stated in the terms
  • 3-D Secure 2 documented with frictionless and challenge flows, plus a published exemption for payments up to 30 euros with the fraud-chargeback liability spelled out
  • Benelux methods named and priced per market — iDEAL, Bancontact, an iDEAL-to-Wero incentive, Klarna, Riverty and Billink — under an acquiring licence for iDEAL, Bancontact, American Express, Mastercard and Visa

Report an error

Held against it

  • Recurring billing scores 4 — periodic debits and admin-panel batch upload are documented, but we found no public information on dunning, failed-payment notification, SEPA mandate management or exporting stored payment credentials to another provider
  • Wallets sit behind 'Specialistic Fees - On request' (Apple Pay, Google Wallet, 3-D Secure), the Premium plan carries no published price, and interchange++ opens only above €1,000,000 in online card payments via Sales
  • The captured pages give different figures for contract duration — 'No contract duration' in marketing against a one-year initial term with tacit renewal in the terms — and we found no published chargeback, refund or payout fee
  • Sovereignty scores 5 — the Dutch data-centre sentence carries no exclusivity, the processor agreement is confirmed to exist but not published, and we found no public information on subprocessor locations or hosting infrastructure
  • Method coverage is named, not matrixed — we found no public information on settlement currencies, on refund or recurring support per method, or on SEPA Direct Debit as a checkout method

Report an error

Best for

  • You sell into the Netherlands, Belgium, Poland or France and want local methods named and priced per market under a Dutch acquirer licence
  • Your finance team closes the month in Exact Online, e-Boekhouden.nl, Twinfield or Yuki, or matches MT940 and Coda XML statements — settlement and reconciliation scored 6-7
  • You want per-method rates published up front — cards, pay-later, gift cards and terminal pricing across Business and Professional tiers, with conversion and fair-use costs disclosed in the terms
  • You need a checkable licence chain for vendor review — entity, register numbers, licence date, safeguarding foundation and PCI DSS Level 1 since 2014 are public

Report an error

Avoid if

  • Your model depends on subscription operations — recurring billing scores 4, and after termination the terms grant only limited access for thirty-five days to retrieve transaction information
  • You plan to take card payments on your own domain — the terms require the merchant to be PCI DSS compliant and provide proof of this to Pay.
  • You lean on the low-value exemption for conversion — a merchant choosing the up-to-30-euros route is liable for the costs of a chargeback with fraud as the reason
  • Your volume is quiet for two consecutive months or longer — a minimum invoice of 75% of average fees applies, and fair-use surcharges of 10.0% on fees or 1.0% on volume can follow chargeback-ratio breaches

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

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

Named methods go well past cards: iDEAL, Bancontact, Wero, Klarna, Riverty, Billink, Przelewy24 and Cartes Bancaires are each priced or described with their market, alongside Visa, Mastercard, American Express and the wallets Apple Pay, Google Wallet, PayPal and Amazon Pay, with dedicated country pages for Poland and France. What keeps this short of full coverage is that settlement currencies and the refund and recurring support of each method are not documented, and we found no public information on SEPA Direct Debit acceptance as a checkout method. 2 5 6 13

Report an error

The E-Commerce Lead

Methods are named per market where it counts: the licence names iDEAL and Bancontact, the Poland page names Przelewy24 and Apple Pay, the France page walks through Cartes Bancaires and PayPal, and Klarna, Riverty and Billink are priced for the Netherlands and Belgium. But "Access to more than 50 payment methods" is a count, not a list, and we found no public information showing the countries and currencies each method serves, or which methods support refunds and recurring charges. 2 5 6 13

Report an error

The SaaS Founder

The certifications page states an acquiring licence for iDEAL, Bancontact, American Express, Mastercard and Visa, and the captured pages name methods per market — Wero, Klarna, Riverty and Billink for the Netherlands and Belgium, Przelewy24 and Apple Pay for Poland, Cartes Bancaires for France, plus PayPal and Amazon Pay, with pricing for "more than 50 payment methods". What I could not find is SEPA Direct Debit named anywhere we read, nor a per-method statement of refund or recurring support or settlement currencies, so coverage is named but not yet a matrix a merchant can plan against. 2 5 6 13

Report an error

The Payments Engineer

Named methods run well past the Benelux core — iDEAL, Bancontact, Wero, Klarna, Billink and Riverty in the Netherlands and Belgium, Przelewy24, Apple Pay and PayPal in Poland, Cartes Bancaires in France — with cards under Pay.'s own acquiring licence for Visa, Mastercard and American Express, plus terminals, SoftPOS and Tap to Pay on iPhone. What I cannot plan against is a per-country matrix: the captured pages cover two country pages, and we found no public information on settlement currencies, on refund and recurring support documented per method, or on SEPA Direct Debit as a named method. 2 5 6 13

Report an error

The Compliance Officer

Local methods are named per market — iDEAL, Bancontact and a Wero incentive for the Benelux, Klarna, Billink and Riverty for pay-later, Przelewy24 on the Poland page and Cartes Bancaires on the France page, with cards acquired under Pay.'s own licence for iDEAL, Bancontact, American Express, Mastercard and Visa. I found no public information on SEPA Direct Debit, on the settlement currencies each method serves, or on which methods support refunds and recurring charges, so the planning matrix a merchant needs is not there. 2 5 6 14

Report an error

The Skeptic

The named list runs deep for Benelux and beyond: iDEAL, Bancontact, Klarna, Riverty and Billink priced per country, a Wero incentive for the Netherlands, Przelewy24 and Apple Pay for Poland, Cartes Bancaires for France, and an acquiring licence covering iDEAL, Bancontact, American Express, Mastercard and Visa. Coverage comes as country pages and price lines rather than a planning matrix — we found no public information on which methods support refunds or recurring charges, on settlement currencies, or on SEPA Direct Debit. 2 5 6 13

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

3-D Secure 2 is documented with frictionless and challenge flows, the low-value exemption up to 30 euros is published with the fraud liability stated plainly, chargeback protection under 3D Secure is explained, and there is a brandable checkout where credit card payments complete inside the webshop plus payment links. The PCI DSS burden is stated for card acceptance on the merchant's own domain and an anti-fraud product called VERIFY exists. We found no public information on configurable fraud rules, risk scores exposed to the merchant, or authorisation-rate reporting. 7 8 11 4

Report an error

The E-Commerce Lead

The 3-D Secure 2.0 documentation is what I want for conversion: frictionless first with a challenge only when that fails, an exemption for payments up to 30 euros with the fraud liability spelled out, and the promise that 3-D Secure card payments cannot be reversed on the basis of "it wasn't me". The custom checkout keeps card payments inside my webshop environment with my own logo and colours, though accepting cards on my own domain requires my own PCI-DSS compliance, and the VERIFY anti-fraud software is named without its rules or risk scores being shown. 3 4 7 8 11

Report an error

The SaaS Founder

3-D Secure 2 with frictionless and challenge flows is documented, a low-value exemption up to 30 euros is published with the fraud chargeback liability landing on the merchant, and the liability shift for authenticated card payments is spelled out — that is real SCA engineering on paper. An embedded card checkout inside the webshop and no-code customisation are described, the terms state the merchant must prove PCI DSS compliance to take cards on its own domain while Pay. carries Level 1, and the VERIFY anti-fraud product is named. What we found no public information on is configurable fraud rules or risk scores exposed to the merchant, network tokens or an account updater, and authorisation-rate reporting by method or issuer. 3 4 7 8 11

Report an error

The Payments Engineer

3-D Secure 2 is documented down to frictionless versus challenge flows, a low-value exemption up to 30 euros with the fraud-chargeback liability written out, and the statement that 3DS card payments can never be reversed through a chargeback on the reason 'it wasn't me' — real SCA engineering copy. PCI scope is stated per integration (Pay. declares responsibility for the platform and secure storage; the merchant must prove PCI DSS compliance to take cards on its own domain), and an anti-fraud product named VERIFY exists with PCI-3DS certification behind it. I stop short of more because we found no public information on transaction-risk-analysis or merchant-initiated exemptions, on configurable fraud rules or exposed risk scores, or on network tokens and authorisation-rate reporting. 4 7 8 11 14

Report an error

The Compliance Officer

Hosted checkout and card payments completed inside the webshop environment are both shown, with 3-D Secure 2 frictionless and challenge flows, a documented low-value route for payments up to 30 euros without mandatory authentication, and the liability consequences of each stated plainly. The terms also place card acceptance on the merchant's own domain into the merchant's PCI DSS scope; I found no public information on merchant-configurable fraud rules or risk scores, network tokens or an account updater. 4 7 8 11

Report an error

The Skeptic

3-D Secure 2 is documented with frictionless and challenge flows, and the low-value route is honest: payments up to 30 euros may skip authentication, with the merchant liable for fraud chargebacks if they take that option. On-site card acceptance is offered, with the merchant required to be PCI DSS compliant on their own domain, and 3-D Secure chargebacks based on 'it wasn't me' are stated as never reversible. The fraud tool called VERIFY is a name on the reports page; we found no public information on configurable rules, risk scores, exemption strategy beyond the 30-euro rule, soft-decline retry or authorisation-rate reporting. 4 7 8 11

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

Subscriptions and memberships are supported with fixed or variable amounts debited per week, month or year, batch upload of payment orders from the admin panel, and an API to link repeat payments to your own financial system — variable, usage-style debits are covered. We found no public information on dunning, failed-payment notification, smart retries, SEPA mandate management, or any process for exporting payment tokens to another provider. 9 10 12

Report an error

The E-Commerce Lead

Recurring payments are real: weekly, monthly or yearly debits, fixed or variable amounts, usage-based cases like shared mobility, batch upload in the admin panel, and an API to link repeat payments to my own finance systems. But we found no public information on stored cards or SEPA mandates as the funding instrument, or on dunning and failed-payment handling, and after termination I keep only limited access for thirty-five days to retrieve transaction information. 4 9 10 12

Report an error

The SaaS Founder

Recurring payments are a real feature: fixed or variable amounts per week, month or year, variable usage-based debits like shared mobility, batch upload from the admin panel without technical knowledge, and an API to link repeat payments to your own financial IT solution. As a subscription operator the gaps that matter: we found no public information on SEPA mandate management with pre-notification, on dunning, smart retries or failed-payment handling, and the terms give only thirty-five days of limited access after termination to retrieve transaction information — nothing about exporting payment tokens to another provider. 4 9 10 12

Report an error

The Payments Engineer

Recurring is real and flexible: subscriptions and memberships, fixed or variable amounts per week, month or year, usage-based models like shared mobility, batch upload of payment orders from the admin panel with no technical knowledge, and an API to link repeat payments to your own financial IT solution. The instrument layer stays vague though — we found no public information naming card-on-file, SEPA mandate management or merchant-initiated transactions — and no public information on dunning, smart retries, failed-payment notification, an account updater, or exporting stored payment credentials to another provider. One-off planned payments are marked as coming soon. 9 10 12

Report an error

The Compliance Officer

Subscriptions and memberships with periodic debits per week, month or year, fixed or variable amounts, batch upload from the admin panel and an API link to the merchant's own financial system are all documented. I found no public information on SEPA mandate management, smart retries or dunning, a card account updater, or any documented process for exporting stored payment credentials to another provider — the token exit question I always ask is unanswered. 9 10 12

Report an error

The Skeptic

Recurring charging is real: periodic debits per week, month or year with fixed or variable amounts, batch upload from the admin panel without technical knowledge, and an API to link repeat payments to the merchant's own financial systems; one-off planned payments are stated as 'coming soon'. We found no public information on SEPA mandate management, notification of failed payments, dunning, a card account updater, or a process for exporting payment tokens to another provider. 9 10 12

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

This is where the evidence is strongest: statements give access to invoices, payouts and the current balance, reports slice by webshop, payment method and period in real time, and exports come in PDF, CSV, MT940 and Coda XML — bank statement formats — pushed by email, SFTP or API in a custom format and frequency, with named direct integrations into Exact Online, e-Boekhouden.nl, Twinfield and Yuki for automatic import and reconciliation. What holds it back for a finance team closing the month: no stated payout cadence beyond revenue being "frequently paid out", no per-transaction itemisation of interchange and scheme fees, and we found no public information on a versioned API with idempotency or a public status page. 4 11 12 6

Report an error

The E-Commerce Lead

The reconciliation half is strong: MT940 and Coda XML bank statement files delivered by e-mail, SFTP or API in a custom format and frequency, direct integrations with Exact Online, e-Boekhouden.nl, Twinfield and Yuki, and statements covering invoices, payouts and balance. Payout speed is stated as within 15 minutes, but we found no public information on webhooks, a versioned API with idempotency, per-transaction fee itemisation, or a public status page. 2 4 10 11 12

Report an error

The SaaS Founder

Statements cover invoices, payouts and the current balance, real-time reports run with per-webshop, payment-method and period dimensions, and exports go to PDF or CSV; the accounting side is genuinely strong — named direct integrations with Exact Online, e-Boekhouden.nl, Twinfield and Yuki, and MT940 and Coda XML bank-statement files delivered by email, SFTP or API in a custom format and frequency. That gets a finance team most of the way to a bank-line match, but we found no public information on the payout schedule, webhooks, a versioned API with idempotency, or a public status page with incident history. 6 11 12

Report an error

The Payments Engineer

The reconciliation story is the strongest part of this file: MT940 and Coda XML bank statement files plus minimal and customer-data CSV, generated automatically in a custom format and frequency, delivered by email, SFTP or API push, with named direct accounting integrations (Exact Online (xCore), e-Boekhouden.nl, Twinfield, Yuki), statements covering invoices, payouts and balance, and free testing included. What holds it back for me: we found no public information on webhooks, on API versioning, idempotency keys or published rate limits, or on a public status page — the only uptime commitment is a contractual 99.9% availability promise with fee discounts when it slips. The payout cadence is also never pinned down; the 15-minute figure on these pages is about receiving payments after registration, and the terms say only that revenue is 'frequently paid out'. 2 4 6 11 12

Report an error

The Compliance Officer

Real-time reporting across online and in-store channels, statements covering invoices, payouts and current balance, exports in PDF, CSV, MT940 and Coda XML, and named accounting integrations with Exact Online, e-Boekhouden.nl, Twinfield and Yuki plus automatic reconciliation and free testing give a finance team real material. The payout schedule is only loosely stated — revenue is frequently paid out, and a 15-minute claim that reads as onboarding — and I found no public information on webhooks, idempotency, rate limits or a status page. 4 6 11 12

Report an error

The Skeptic

The reconciliation side is solid: real-time reports by webshop, method and period, statements covering invoices, payouts and balance, exports to PDF or CSV, bank-statement formats MT940 and Coda XML delivered by e-mail, SFTP or API push, and named integrations into Exact Online, Twinfield, Yuki and e-Boekhouden.nl. On the payout side the captured pages advertise payments within 15 minutes of registration and the terms say revenue 'is frequently paid out'; we found no public information on a payout schedule, settlement currencies, API versioning, idempotency or a public status page. 4 6 11 12

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 chain is written down: TinTel B.V. in the trade register under number 24283498, a De Nederlandsche Bank payment institution licence since 29 July 2013, an acquiring licence for iDEAL, Bancontact, American Express, Mastercard and Visa, and merchant funds segregated at a DNB-supervised foundation holding its account at a Wft-licensed credit institution. I particularly credit that the deposit is contractually capped at up to six months after termination, with a three-month termination notice after the initial term, thirty-day change notice, and PCI DSS Level 1 published. We found no public information on passporting per country, an appeal route against suspension, or a published chargeback fee, and there is a suspension right with a €2,500 per-claim fine on the provider's side. 4 3 14 13

Report an error

The E-Commerce Lead

The chain is written down: TinTel B.V. in Spijkenisse with Trade Register number 24283498, a De Nederlandsche Bank payment institution licence since 29 July 2013, merchant funds segregated at Stichting Derdengelden Pay. (register number 50152769) at a Wft-licensed credit institution, and PCI DSS Level 1 audited annually since 2014. The harder terms are partly defined — a one-year initial term with three-month notice after it, a deposit held up to six months after termination, suspension rights with fines — but we found no published passporting per country or a route to appeal. 3 4 14

Report an error

The SaaS Founder

The bad day is largely written down: TinTel B.V. with trade register number, a De Nederlandsche Bank payment institution licence granted 29 July 2013, and merchant funds safeguarded in a separate Stichting Derdengelden Pay. with its own register number at a Wft-licensed credit institution — plus a deposit held at most six months after termination, three-month notice after the initial year, and PCI DSS Level 1 audited annually since 2014. The terms also publish chargeback-ratio bands with surcharges of 10.0% and 1.0%, a 15% administration surcharge on network claims, and defined noncompliance fees. We found no public information on passporting per country, an appeal route against freezes, or a published chargeback fee per dispute. 3 4 14

Report an error

The Payments Engineer

The bad day is partly written down: TinTel B.V. named with Chamber of Commerce number, a De Nederlandsche Bank payment institution licence since 2013, client money segregated at a DNB-supervised stichting derdengelden whose account sits at a Wft-licensed credit institution, PCI DSS Level 1 audited annually since 2014, three months' written notice after a one-year initial term, a deposit held for up to six months after termination, an annual audit right, and 35 days of post-termination access to retrieve transaction information. Short of the top: we found no public information on passporting per country, on reserve or rolling-hold calculation, or on an appeal route against suspension — and the terms also carry a € 2,500 per-claim fine and fair-use surcharges up to 1.0% of volume, disclosed but numbers a merchant should model. 3 4 13 14

Report an error

The Compliance Officer

This is the discipline I want to see: TinTel B.V. named with Trade Register number 24283498, supervised by De Nederlandsche Bank under a payment institution licence granted 29 July 2013, a third-party funds foundation under its own register number 50152769 and DNB supervision, and PCI DSS Level 1 audited annually since 2014. The terms define a three-month notice period, a deposit held up to six months after termination, 35 days of post-termination access and chargeback-ratio bands with fee consequences; I found no public information on passporting per country, a published dispute or chargeback fee, or a route to appeal suspension. 3 4 13 14

Report an error

The Skeptic

The chain is written down: TinTel B.V. with trade register number 24283498 holds a payment-institution licence from De Nederlandsche Bank granted on 29 July 2013, merchant funds sit in Stichting Derdengelden Pay. at a licensed credit institution, PCI DSS Level 1 has been audited annually since 2014, a deposit is held up to six months after termination, and three months' notice applies after the one-year initial term. For the bad day we found no public information on a chargeback fee, a merchant dispute process, passporting per country or a route to appeal — the terms provide a suspension right with a fine of € 2,500 per claim and fair-use surcharges tied to chargeback ratios. 3 4 13 14

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 contracting and regulated entity is Dutch and DNB-supervised, processing is stated as "Our data is stored in Dutch data centres" on the certifications page, and a processor agreement exists with the controller-versus-processor position published. That statement sits in marketing copy without naming infrastructure, we found no public information on a subprocessor list or hosting options, and the agreement text itself is not published. 13 3 4 14

Report an error

The E-Commerce Lead

The contracting entity is Dutch and licensed by De Nederlandsche Bank, and the certifications page states "Our data is stored in Dutch data centres". A processor agreement exists and the privacy statement sets out where Pay. acts as controller versus processor, but the residency sentence is marketing copy that does not say "only", the same privacy statement notes data is released to third parties to facilitate payments, and we found no public information on a subprocessor list with locations. 3 4 13 14

Report an error

The SaaS Founder

The contracting entity is Dutch with a Dutch supervisor, and the certifications page states "Our data is stored in Dutch data centres" — though that sentence sits in marketing copy without the word "only", while the privacy statement notes data is released to third parties to facilitate payments. A processor agreement is confirmed to exist and the controller-versus-processor position is stated, but the text is not published, and we found no public information on a subprocessor list, hosting options, or named infrastructure. Certified EU entity, EU licence and stated EU storage, with the processing chain left dark. 3 4 13

Report an error

The Payments Engineer

Dutch on paper: TinTel B.V. in Spijkenisse contracts, a DNB licence, and the certifications page states 'Our data is stored in Dutch data centres'. The processor agreement is confirmed to exist for merchants, and Pay. states it acts as both controller and processor for end-user transactions — but the agreement text is not published, the data-centre sentence sits in marketing copy without the word 'only', and the privacy statement separately notes data is released to third parties to facilitate payments. We found no public information on subprocessor locations, hosting options or named infrastructure. 3 4 13 14

Report an error

The Compliance Officer

A Dutch contracting entity with a register number, a DNB licence and a statement that data is stored in Dutch data centres establish an EU entity, an EU licence and an EU processing claim, and I credit the privacy statement for saying plainly that Pay. is both controller and processor for end-user transactions with a processor agreement for merchants. But the Dutch data-centre line sits in marketing copy without exclusivity while the privacy statement notes data is released to third parties to facilitate payments, no subprocessor list with locations is published, the infrastructure is not named, and the processor agreement is only said to exist rather than offered publicly. 3 4 13 14

Report an error

The Skeptic

The good half is documented: a Dutch contracting entity (TinTel B.V., Spijkenisse) under a De Nederlandsche Bank payment-institution licence. The residency claim is one marketing sentence — 'Our data is stored in Dutch data centres' — sitting on the certifications page, while the privacy statement separately notes data is released to third parties to facilitate payments. The processor agreement is confirmed to exist but its text is not published; we found no public information on hosting infrastructure, a subprocessor list with locations, or transfer safeguards. 3 4 13

Report an error

Pricing transparency

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

Rates are published per method — Visa and Mastercard online at €0,15 + 1,50% professional or €0,12 + 1,30% business, Klarna for Netherlands and Belgium at €0,45 + 2,95%, Billink, Riverty, the iDEAL-to-Wero incentive, gift cards and terminal rates — and the terms disclose real ancillary costs a merchant needs: a currency conversion fee of €0.03 per payment and 2.75% of the transaction value, a minimum bill of 75% of average fees, fair-use surcharges of 10.0% on fees or 1.0% on volume, onboarding, review and risk investigation fees. Wallets and 3-D Secure are priced on request, interchange++ is only available above €1,000,000 in online card payments via Sales, and we found no published chargeback, refund or payout fee. The captured pages give different figures for contract duration — the pricing page states "No contract duration" while the terms set a twelve-month initial term with tacit renewal. 2 4

Report an error

The E-Commerce Lead

Card and buy-now-pay-later rates are published per method across two plan tiers — Visa and Mastercard at €0,12 + 1,30% on Business, Klarna Netherlands and Belgium Pay later at €0,45 + 2,95% on Professional — with an exact currency conversion fee of €0.03 per payment and 2.75% of the transaction value, a minimum bill of 75% of average fees in quiet months, and an IC++ calculation available above €1,000,000 in online card payments. But Apple Pay, Google Wallet and 3-D Secure fall under "Specialistic Fees - On request", we found no public chargeback, refund or payout fee, and the captured pages give different figures for contract duration — "No contract duration" on the pricing page against a twelve-month initial term with tacit renewal in the terms. 2 4 13

Report an error

The SaaS Founder

Per-method rates are public — Visa and Mastercard at €0,15 + 1,50% (€0,12 + 1,30% on Business), Klarna Netherlands and Belgium at €0,45 + 2,95%, Riverty, Billink, gift cards and an iDEAL-to-Wero incentive — with no monthly plan fee and no contract duration, and the terms add a currency-conversion fee of €0.03 per payment and 2.75% of the transaction value, a minimum invoice of 75% of average fees, onboarding and risk-investigation fees, and fair-use surcharges. But specialistic fees including Apple Pay, Google Wallet and 3-D Secure are on request, an IC++ calculation is only offered above €1,000,000 in online card payments via Sales, and domestic versus international card pricing and a per-dispute chargeback fee are not distinguished, so I cannot compute my own effective rate end to end. 2 4

Report an error

The Payments Engineer

Rates are published per method with plan tiers spelled out — Visa and Mastercard at €0,15 + 1,50% professional versus €0,12 + 1,30% business, Klarna, Billink and Riverty itemised, gift cards, terminal and SoftPOS rates, a currency conversion fee of €0.03 per payment and 2.75% of the transaction value when the payment currency differs from the settlement currency, VAT-exclusive billing, and the 75% minimum invoice rule all public. Apple Pay, Google Wallet and 3dSecure sit under specialistic fees on request, the Premium plan price is not published, IC++ is a sales conversation above €1,000,000 in card volume, and we found no public information on refund or payout fees. The captured pages also give different figures for contract duration: 'No contract duration' on the pricing pages versus a one-year initial term with tacit renewal and three months' notice in the terms. 2 4

Report an error

The Compliance Officer

Per-method rates are public for cards, debit, pay-later, gift cards and vouchers, and the terms disclose more than most: an exchange rate fee of €0.03 per payment and 2.75% of the transaction value, onboarding and risk-investigation fee schedules, fair-use surcharges of 10.0% on fees and 1.0% on volume, and a minimum invoice of 75% of average fees. Apple Pay, Google Wallet and 3-D Secure sit behind "on request", interchange++ only opens above €1,000,000 in online card payments through Sales, I found no public information on refund or payout fees, and the captured pages give different figures for contract duration — "No cure, no pay. No contract duration" in marketing against a one-year initial term with tacit renewal in the terms. 2 3 4

Report an error

The Skeptic

Card rates are published to the cent — Mastercard and Visa at €0,12 + 1,30% for Business and €0,15 + 1,50% for Professional, Maestro terminal payments in NL at €0,07 and €0,065 — and, unusually, the conversion cost is public: €0.03 per payment and 2.75% of the transaction value when the payment currency differs from the settlement currency. But the edges leak: Apple Pay, Google Wallet and 3-D Secure pricing is 'on request', the Premium plan carries no price at all, interchange++ appears only above €1,000,000 in online card payments via Sales, and the captured pages give different figures for the contract term — 'No contract duration' in the marketing against a one-year initial term with tacit renewal in the terms. We found no public information on a chargeback, refund or payout fee. 2 4

Report an error

European sovereignty — proven facts

2 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 only unverified
Why unverified?

The sentence sits in marketing copy on the certifications page and does not use the word "only", while the privacy statement separately notes data is released to third parties to facilitate payments.

4/4 pts 13 Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement On request unverified
Why unverified?

The privacy statement only confirms the agreement exists; it neither publishes the text nor explains how a merchant obtains or concludes it.

0/1 pts 3 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Pay.

Is Pay. European?

Yes. whats-best.ai classifies Pay. as EU-Made.

Where does Pay. store data?

Pay. stores customer data in the EU, per the vendor’s page captured 16 Nov 2026.

Does Pay. have a free plan?

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

What are the best alternatives to Pay.?

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: Pay. 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 (16)

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

  1. 1 Vendor homepage www.pay.nl Checked 16 Nov 2026 Details →
  2. 2 Pricing page www.pay.nl Checked 16 Nov 2026 Details →
  3. 3 Privacy policy www.pay.nl Checked 16 Nov 2026 Details →
  4. 4 Terms of service www.pay.nl Checked 16 Nov 2026 Details →
  5. 5 Payment methods & local coverage — found from sitemap www.pay.nl Checked 16 Nov 2026 Details →
  6. 6 Payment methods & local coverage — found from sitemap www.pay.nl Checked 16 Nov 2026 Details →
  7. 7 Checkout, SCA & fraud — found from sitemap www.pay.nl Checked 16 Nov 2026 Details →
  8. 8 Checkout, SCA & fraud — found from sitemap www.pay.nl Checked 16 Nov 2026 Details →
  9. 9 Subscriptions & recurring payments — found from sitemap www.pay.nl Checked 16 Nov 2026 Details →
  10. 10 Subscriptions & recurring payments — found from sitemap www.pay.nl Checked 16 Nov 2026 Details →
  11. 11 Settlement, reconciliation & API — found from sitemap www.pay.nl Checked 16 Nov 2026 Details →
  12. 12 Settlement, reconciliation & API — found from sitemap www.pay.nl Checked 16 Nov 2026 Details →
  13. 13 Licence, risk & account terms — found from sitemap www.pay.nl Checked 16 Nov 2026 Details →
  14. 14 Licence, risk & account terms — found from sitemap www.pay.nl Checked 16 Nov 2026 Details →
  15. 15 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →
  16. 16 Structured-data backfill: markup only, no text or screenshot www.pay.nl Checked 8 Nov 2026 Details →