Question 1

Is sikker.me a fraud prevention tool?

Accepted Answer

Not exactly. sikker.me is a continuous verification layer — not a rule-based fraud screener. It tells you, before a payment executes, whether the payee relationship is verified against the official government registry of their jurisdiction. Prevention is the outcome. Verification is the mechanism.

Question 2

What does "silent by default" mean?

Accepted Answer

The API does not emit alerts unless a state change occurs — if nothing changes, nothing fires. Confirmed results are logged and auditable but do not trigger a notification or webhook. Your operations team sees nothing on a clean payment — only the exception that requires a decision.

Question 3

What are the three outcomes?

Accepted Answer

Confirmed — entity verified, payment proceeds automatically. Mismatch — graph state contradicts payee data, payment held with specific reason attached. Unverifiable — registry data incomplete or unavailable. An honest signal, not a false positive. No scores. No other states.

Question 4

What does a single API call return?

Accepted Answer

One of three outcomes, a confidence signal, the sources traversed, and — on Mismatch — the specific reason the graph state contradicts the payee data. Every response is timestamped and auditable.

Question 5

How wide is the coverage?

Accepted Answer

sikker.me integrates directly with authoritative government registries across Western Europe, with coverage expanding. Where coverage is incomplete, we return Unverifiable — never a false confirmation.

Question 6

How is Unverifiable different from a false positive?

Accepted Answer

Unverifiable means registry data is incomplete or unavailable for this entity at this moment — not that the entity is suspicious. Treating absence of data as fraud would generate false positives. sikker.me does not do that.

Question 7

Does this require workflow changes?

Accepted Answer

No. sikker.me runs as infrastructure between identity and execution. Zero workflow change for your team. No human action required unless a Mismatch is returned.

Question 8

How does it integrate?

Accepted Answer

One POST request to /v1/verify with payee name, account number, and jurisdiction. Result in under three seconds. Integrates into any payment pipeline via REST API.

Question 9

What does API access include?

Accepted Answer

The /v1/verify endpoint, full graph traversal across covered jurisdictions, structured JSON responses, Mismatch reason codes, and a complete audit log of every verification call.

Question 10

How do we audit a Mismatch decision?

Accepted Answer

Every verification call is logged with the payee input, sources traversed, outcome, confidence signal, and — on Mismatch — the specific graph state contradiction that triggered the hold. The record is immutable and available for regulatory review.

Question 11

Is our payment data stored?

Accepted Answer

No. Account numbers are stored as cryptographic hashes. Payment amounts and payer identity are never stored. Network signals are derived, anonymized outputs — not raw transaction data. Designed for GDPR and EU privacy frameworks from day one.

Capability	VoP	sikker.me
Data source	Bank's internal name record	Official government registry
Returns close-match result	Requires manual resolution
Detects company dissolution
Director / ownership changes
Post-onboarding monitoring
Regulator-grade audit trail
Verdict traceable to named source

Capability	KYB / AML vendors	sikker.me
Continuous monitoring
Registry-authoritative data	Partial (often scraped / indirect)
Verdict, not a risk score	Score outputs
Resolves VoP grey-zone results
No workflow change
Verdict traceable to named registry	Partial

Verify every wire.
Before it leaves.

Fraud lives in the gap between onboarding and today's wire.

Most tools verify
at onboarding.
Nobody watches after.

The market is every B2B payment in Europe.

Not a replacement. A missing layer in your payment stack.

VoP tells you the IBAN matches.
We tell you the company is real.

KYB vendors verify at onboarding.
We watch continuously.

Every major Western European registry.
Direct.

The cost of an unverified
payment flow.

Common questions.

Verify every wire.Before it leaves.

Fraud lives in the gap between onboarding and today's wire.

Most tools verifyat onboarding.Nobody watches after.

The market is every B2B payment in Europe.

Not a replacement. A missing layer in your payment stack.

VoP tells you the IBAN matches.We tell you the company is real.

KYB vendors verify at onboarding.We watch continuously.

Every major Western European registry.Direct.

The cost of an unverifiedpayment flow.