Policyholder verification for Insurtech
Identity verification with liveness, the CURP cross-checked against RENAPO and the credential status from the INE Lista Nominal. The same verification runs at policy issuance and at claim time. The evidence is stored in the insured's file.
The same verification runs at policy issuance and at claim time
The insured receives a link valid for 24 hours. The beneficiary is verified separately, on their own file. The Lista Nominal returns the credential status and its removal cause. The verdict arrives on a signed webhook.
We do not adjudicate claims. We hand you the verdict, the field-by-field match and the submission audit trail; paying, denying or rescinding stays with your technical team.
Where it fits in your operation
The products behind this solution
Identity verification
ID or passport plus a selfie with liveness, matched against the photo on the document. Verdict: verified, partial or rejected.
INE Lista Nominal
Credential status: active, removed from the roll, duplicated or stolen.
CURP against RENAPO
Official lookup plus a field-by-field match against the record you captured.
Sanctions screening
Nine categories per search, all from public sources: sanctions, criminal, PEP, fiscal, adverse media.
Court records
Case files by name, with court, state and case status. Individuals and companies.
Risk score
Aggregates the signals from the tools already run on that person, in a single read.
How it works
From onboarding the insured to adjudicating the claim, on the same file.
Verify at issuance
You generate one link per insured. The person uploads their ID or passport and a selfie with liveness from their phone, no app to install.
expires in 24 h
Confirm the credential
We read front and back and pull the INE status: active, removed, duplicated or stolen, not found, or data that does not match.
5 possible statuses
Screen lists and courts
Sanctions, criminal, PEP, fiscal and adverse media in one search; plus court files with court, state and case status.
public sources
Repeat at claim time
The same call runs on the same file. The webhook carries the verdict, the selfie-to-document-photo match, the liveness result and the validated fields.
signed webhook
The file gathers the evidence the Mexican framework requires you to keep.
The CNSF supervises insurance institutions. The Insurance Contract Act governs the relationship with the insured. The federal privacy act governs the biometric and health data collected to underwrite. All three require keeping the evidence of identification.
Singula is not an insurance company, is not supervised by the CNSF and does not adjudicate anything. We supply the verification and its evidence; underwriting policy, claim decisions and suspicious activity reporting remain yours. The legal references on this page are orientation and do not constitute legal advice; have your legal team confirm them.
- 01
Know your customer
AML rules for the insurance sector require identifying the customer and keeping the supporting evidence. The KYC verdict, the images and the sanctions screening are stored in the same customer file.
- 02
Omission or inaccurate declaration
Article 48 of the LSCS counts the deadline to communicate rescission from the moment the insurer learns of the omission. Singula's evidence records who identified themselves and when; that date stays in the file. The risk declaration is made in the questionnaire, which lives in your core and outside our metadata.
- 03
Express consent for biometrics
A selfie and a liveness check are sensitive personal data. Processing them requires express written consent under article 8 of the federal privacy act published in the DOF on 20 March 2025. The privacy notice and the consent are collected by the insurer; Singula does not obtain them on your behalf. The flow records what was queried, when and with what result, and on the identity link, the device, the IP address and the time.
- 04
Claim payment deadline
Under article 71 of the LSCS, payment falls due thirty days after the insurer receives the documents supporting the claim. That deadline runs separately from the rescission deadline. The verification runs asynchronously and the verdict arrives on a webhook as soon as the insured finishes.
The same call runs at issuance and at claim time.
You create the verification and send the link to the insured. When it finishes, a signed webhook arrives with the verdict, the selfie-to-document-photo match and the liveness result. The same customer file is reused when the claim is adjudicated.
# Emisión: crea la verificación y mándale el link al asegurado
curl -X POST https://api.singula.mx/app/identity-verification/customer/cus_lzk9m4ab3f/create \
-H "Authorization: Bearer sk_live_..."
→ {
"request_id": "6622f8a1c1d2e3f4a5b6c7d8",
"verification_url": "https://app.singula.mx/verify/8f3ka9dq",
"expires_at": "2026-05-01T14:22:08Z"
}
# El webhook identity.completed avisa cuando el asegurado sube documento
# y selfie. El veredicto se lee con el request_id:
curl https://api.singula.mx/dashboard/request/6622f8a1c1d2e3f4a5b6c7d8 \
-H "Authorization: Bearer sk_live_..."
→ {
"tool_type": "identityVerification",
"status": "success",
"response": {
"verification": {
"status": "verified",
"overall_confidence": 0.912,
"document_type": "INE",
"face_result": {
"match_score": 0.94,
"match_decision": true,
"liveness_score": 0.97,
"liveness_decision": true
},
"checks": [
{ "check_name": "curp_validation", "passed": true, "confidence": 0.98 }
]
}
}
}
# Siniestro: antes de pagar, criba al beneficiario
curl https://api.singula.mx/app/blacklist/customer/cus_9q2mv7xd1r \
-H "Authorization: Bearer sk_live_..."
→ {
"request_id": "6622f8a1c1d2e3f4a5b6c7d8",
"data": {
"risk_summary": { "level": "clear", "categories_found": [] }
}
}Frequently asked questions
Yes. Each person has their own file with their own verification history. The insured, the policyholder and the beneficiary are verified separately and linked to the same account. A beneficiary needs no policy to be verified or screened against lists.
We do not query death registries and we do not issue certificates. The INE removal catalogue includes death as a cause; when the credential is removed from the roll, the response returns that cause. The removal cause is a signal to investigate and carries no probative value.
The verdict returns rejected when the liveness check or the selfie-to-document-photo match fails. The verification works on the document image and on the official sources; it does not inspect the physical card under UV or read a chip.
The response indicates the key is not in the national registry. If the provider does not answer or the query times out, the request is marked as an error. A later lookup returns the record if it has since appeared in RENAPO.
No. It is REST with an API key plus a webhook signed with HMAC SHA-256 to the endpoint you define. The sandbox uses the same calls with sample responses, so the whole flow is tested before touching production.
Other solutions
Verify at issuance, and again at claim time
Create your account and wire the whole flow in the free sandbox. The same call promotes to production. To review the evidence model with your legal team, write to us.