Identity verification for insurers
Insurers need to know the policyholder is real at sign-up and that the claimant is the policyholder at payout. Zanyara verifies identity at both points — document, biometrics and AML — so impersonation and identity fraud don’t slip through.
Onboarding and claim-time verification
- Policyholder onboarding: document + NFC + face match + liveness, plus sanctions/PEP screening.
- Claim-time identity check: confirm the claimant is the insured person before a payout.
- Proof-of-address where the policy or regulation needs it.
- Embedded in quote-and-buy and claims journeys via API and the web/iOS/Android SDKs.
Deepfake-aware at the moments that matter
Remote claim verification is an obvious fraud target, so Zanyara pairs presentation-attack detection with device intelligence to resist photos, replays and injected camera feeds — protecting the payout decision, not just the sign-up.
Honest scopeZanyara verifies identity and screens against AML watchlists. It is not a claims-analytics, underwriting or fraud-scoring engine. UK-hosted with configurable data residency; ICO registered.
Frequently asked questions
- Where does identity verification help in insurance?
- Two places: onboarding a new policyholder (confirming they are who they claim to be, and screening against sanctions/PEP lists), and at claim time — confirming the claimant is the policyholder with face match and liveness before a payout.
- Can it reduce claims fraud?
- It closes one common gap — impersonation and identity fraud — by binding a real, present person to a verified document at onboarding and claim. It is not a claims-analytics or fraud-scoring engine for staged or exaggerated claims; pair us with your claims-fraud tooling for that.
- How is it integrated?
- Via the REST API and the web, iOS and Android SDKs — embedded in your quote-and-buy or claims journey — with decisions delivered by signed webhook and in the operator console.