Sources before conclusions
A statement is published only with the instrument, article or document it rests on. Where we interpret, we say that we are interpreting.
About the publication
Veridexaa Analytics is operated by Veridexaa Analytics Group from Espoo, Finland. We document how open-banking payments work in practice, for the teams that have to build, audit and operate them.
Veridexaa Analytics started from a recurring observation: organisations choosing an open-banking payment method were asked to decide on the basis of sales material, while the factors that actually determined their outcomes were written in regulatory technical standards, scheme rulebooks and bank interface specifications that few people outside payments engineering read.
The gap was not a lack of information but a lack of structure. Each regime explained itself in its own vocabulary. The PSD2 RTS spoke of authentication codes and dedicated interfaces; the European Payments Council spoke of schemes, participants and timelines; providers spoke of conversion and coverage. A product manager trying to understand why a payment succeeded in one bank and failed in another had to translate between all three.
Our response is to publish that translation openly. The whitepaper sets out the regulatory boundaries as precisely as the texts allow. The infrastructure ledger records what can be verified about individual providers and states plainly what cannot. Every page shows its sources and its last review date, so readers can decide how far to rely on it.
We write for an audience that includes treasury and finance teams, product owners, integration engineers and compliance officers in the Nordic countries and Poland. That audience is served best by documents that are precise, dated and modest about what is known. We therefore avoid rankings, scores and unattributed performance figures.
The publication is financed by its operator. It contains no affiliate links, and inclusion in the ledger cannot be purchased. Organisations that want an analysis of their own flows can request a technical audit through the inquiry form; the scope of any such work is agreed in writing before it begins and is kept separate from editorial content.
A statement is published only with the instrument, article or document it rests on. Where we interpret, we say that we are interpreting.
We do not publish latency, conversion or uptime figures unless they come from a reproducible measurement or a contractual commitment.
Providers cannot pay for inclusion or placement. Corrections are accepted only with a public source.
Every module carries a review date. Errors are corrected in the next revision and the correction is recorded.
The publication is produced by a small analyst team organised around four functions. We list functions rather than personal profiles; correspondence is handled through the shared desks listed on the contact page.
Reviews scheme rulebooks, clearing arrangements and settlement timelines, and maintains the infrastructure ledger.
Tracks PSD2, the RTS, Regulation (EU) 2024/886 and related supervisory guidance, and drafts the whitepaper modules.
Reads bank and provider interface documentation and checks factual claims against public registers before publication.
Edits all modules, manages the six language editions and handles corrections and reader correspondence.
Veridexaa Analytics is operated as an independent analytical publication by Veridexaa Analytics Group at Linnoitustie 6–9, 02600 Espoo, Finland.
Describe your markets, bank coverage and payment flows, and we will reply by email.
Cookies and local storage
We use strictly necessary local storage to remember your consent choice. Optional analytics is off by default and is only activated if you allow it.