Use Cases
Confirm payee identity before every wire.
Your ERP has name + IBAN. That's not proof the company is real. sikker.me checks the official registry — before the payment leaves.
What we verify
One API call. Every field that matters.
- Legal name — current, from the official registry
- Registration status — active, dissolved, suspended, in liquidation
- Registration number — HRB, KvK, MBS, or jurisdiction equivalent
- Director(s) — current names and appointment dates
- Registered address — matches invoice address
- IBAN correlation — confirmed via open banking where available
- Historical changes — name drift, ownership events, entity substitution
Verdicts
No scores. No thresholds. No interpretation needed.
Entity verified. Payment proceeds. Source cited. Audit trail created.
Registry contradicts payee data. Payment held. Named discrepancy. Recommended action.
Data incomplete. Manual review queued with specific guidance.
Every outcome is:
- · Actionable in one step
- · Backed by a named authoritative source
- · Logged with timestamp and audit ID
- · Explainable to a compliance officer or court
vs. VoP
VoP checks the bank's record. We check the company.
Verification of Payee (mandatory since October 2025) matches the payee name against what the bank has on file for that account.
It cannot check:
- Whether the company is still registered and active
- Whether a director was replaced last month
- Whether the company was acquired by new owners
- Whether the IBAN was recently changed in the registry
sikker.me goes to the source. The government registry of the company's jurisdiction holds all of this — and we query it before every payment.
Coverage
Every major Western European jurisdiction. Direct.
RCS (France) · Registro delle Imprese (Italy) · KvK (Netherlands) · Handelsregister (Germany) · Bolagsverket (Sweden) · CVR (Denmark) · Firmenbuch (Austria) · CBE (Belgium) · Zefix (Switzerland)
Verify before the next wire leaves.
First 10 verifications free. No integration required to start.