Industries
Your bank checks the name. We check the company.
VoP tells you whether a name matches the bank's own record. It cannot tell you whether the company is legitimately registered, actively trading, or structurally unchanged since you last verified. The bank knows the account. The registry knows the company. sikker.me queries the registry.
VoP data
One in three payments needs resolution. Banks have no tool.
VoP went live October 2025. Live statistics (Natixis CIB, March 2026, based on STET Sepamail data, 180M transactions, French market):
19%
no-match
13%
close-match
2%
unable to verify
34% of French-market VoP transactions in a grey zone. No standard resolution tool. Every unresolved case requires documented decision-making for audit defensibility.
The EBA Practitioners Group (September 2025):
"There is no market-wide standard specifying which data should be used for the VoP check."
sikker.me is the resolution standard.
CDD RTS timeline
AMLA submits the CDD RTS in July 2026. Requirements apply July 2027.
July 10, 2026
AMLA submits CDD RTS to the European Commission
Formally codifies government registries — RCS, Registro delle Imprese, KvK, Handelsregister, Bolagsverket — as 'reliable, independent sources' under Article 22(6)(a).
Oct 2026 – Jan 2027
Procurement window closes
Verification infrastructure procurement runs 6–9 months. Entities starting in July 2026 are on track. Entities waiting for final text will scramble.
July 10, 2027
Requirements apply
sikker.me's registry-primary architecture meets the RTS standard from day one.
Registry coverage
The registries that matter for European B2B payments.
Western Europe
Nordics
DACH
Benelux
Capabilities
The registry layer your VoP check is missing.
VoP resolution
Close-match and unable-to-verify resolved against registry
Entity status
Registration status in real time
Director & UBO
Verified against official registries
IBAN correlation
Open banking + registry
AMLR 22(6)(a)
Registry-sourced, audit-defensible records
Continuous monitoring
Alerts on entity changes
Full audit trail
Source-cited, timestamped, exportable
API-first
POST /v1/verify — integrates into existing flow
DORA
DORA applies to you. It doesn't apply to us.
Banks and systemically important financial institutions are subject to DORA ICT third-party risk requirements — including formal vendor onboarding processes that can take 12–18 months. sikker.me is designed to work through your existing API procurement process. We provide the documentation, SLAs, and security posture required for DORA vendor onboarding. Talk to us about enterprise onboarding timelines.