Use Cases
Every verdict. Source cited. Timestamped. Immutable.
When a regulator asks what you did before the payment left — this is the answer. sikker.me creates a compliance-grade record for every verification, automatically. No reconstruction required.
The record
The full record. Nothing left out.
{
"audit_id": "vrf_20260505_a3f9c2",
"timestamp": "2026-05-05T09:14:22Z",
"payee": {
"name_queried": "Meridian Logistics GmbH",
"iban_queried": "DE89 3704 0044 0532",
"jurisdiction": "DE"
},
"registry": {
"source": "Handelsregister",
"legal_name": "Meridian Logistics GmbH",
"registration_id": "HRB 198234",
"status": "active",
"director": "Johann Weber",
"registered_since": "2019-03-14"
},
"verdict": "confirmed",
"iban_correlation": "confirmed",
"name_match": "exact",
"payment_protected": true
}Audiences
Three audiences. One record satisfies all three.
Compliance Officer
AMLR Article 26 requires documented CDD update cycles. Every sikker.me verification is a timestamped compliance event. Export by entity, by date range, or by verdict type.
Auditor / Regulator
When a regulator requests verification records, sikker.me exports a structured log showing: what was checked, when, against what source, and what the finding was. No manual reconstruction. No spreadsheet audit.
Legal / Fraud Investigation
If a payment is disputed, the audit trail shows the verification state at the exact moment of payment. Source-cited. Timestamped. In the format courts and regulators request. If sikker.me returned Confirmed and fraud still occurred (the entity changed after verification), the record establishes the due diligence performed.
Agentic payments
When AI agents execute payments, the audit trail question becomes critical.
When an AI agent pays a vendor autonomously, liability is immediate: who is responsible if the payment goes to a fraudulent entity?
The Registry Verification Record answers this. It is timestamped, source-cited proof that the vendor was verified at the exact moment of payment — before the wire left. It documents what was known, when it was known, and from which registry source.
FIS — inside 12% of the world's banks — just deployed agentic AML with this exact design requirement: every conclusion must cite its source. sikker.me already produces that record for every verification, whether the payment was initiated by a human or an agent.*
* FIS/Anthropic announcement, May 2026.
Export formats
Your format. Your timeline.
JSON
Full record per verification — for API consumers
CSV
Bulk export — for compliance reporting
Formatted report per entity — for regulator submission
Webhook
Real-time push to your own audit system
Retention
Records kept for the full regulatory retention period.
Verification records are retained for 5 years from date of creation — the standard retention period under AMLR and most national AML legislation. Records are immutable after creation. No modification. No deletion within the retention window.
Every payment documented. Every verdict auditable.
Currently onboarding design partners in France, Italy, Germany.