Facturas de servicios, extractos bancarios, cartas gubernamentales: leídos, analizados, cotejados con la identificación y validados con el registro de direcciones del país. $0.20 por verificación. 500 verificaciones gratis cada mes.
Robinhood Ventures
Con la confianza de más de 2.000 organizaciones en todo el mundo.
Lo que debe una plataforma regulada
Una dirección escrita a mano no pasa una auditoría. Una factura de servicios escaneada que no se coteja con la identificación no pasa una auditoría. Didit te ofrece la receta completa de Prueba de Domicilio, captura, OCR, coincidencia de nombre + dirección con la identificación, más validación de registro nacional en más de 18 jurisdicciones, como un paquete de evidencia firmado por $0.20 por verificación.
Elige las verificaciones que necesites: ID, prueba de vida, coincidencia facial, sanciones, dirección, edad, teléfono, email, preguntas personalizadas. Arrástralas a un flujo en el panel de control o envía el mismo flujo a nuestra API. Crea ramificaciones condicionales, haz pruebas A/B, sin necesidad de código.
Intégralo de forma nativa con nuestros SDK para Web, iOS, Android, React Native o Flutter. Redirige a una página alojada. O simplemente envía a tu usuario un enlace por email, SMS, WhatsApp, donde quieras. Elige lo que mejor se adapte a tu stack.
Didit gestiona la cámara, las indicaciones de iluminación, la transferencia móvil y la accesibilidad. Mientras el usuario está en el flujo, puntuamos más de 200 señales de fraude en tiempo real y verificamos cada campo con fuentes de datos autorizadas. Resultados en menos de dos segundos.
Los webhooks firmados en tiempo real mantienen tu base de datos sincronizada en el momento en que un usuario es aprobado, rechazado o enviado a revisión. Consulta la API bajo demanda. O abre la consola para inspeccionar cada sesión, cada señal y gestionar los casos a tu manera.
Didit · Proof of Address
Step 4 / 5
Upload your proof of address
Didit · OCR + address normalisation
Parsed address
Didit · ID Verification + POA
Didit · Database Validation
Didit · Global coverage
Didit · Compliance
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"workflow_id": "wf_proof_of_address",
"vendor_data": "user-42",
"expected_country": "ES"
}'$ curl https://verification.didit.me/v3/session/$SESSION/decision/ \
-H "x-api-key: $DIDIT_API_KEY"
# Decision payload (excerpted):
{ "proof_of_address": { "status": "Aprobado", "address": { ... } },
"database_validation": { "service": "es_catastro_address", "result": { "registry_match": true } } }You are integrating Didit's Proof of Address into a regulated onboarding flow (bank, fintech, lender, crypto exchange, EU payment institution). Regulators want a current address on every customer file; the legacy "ask the user to type it" approach fails audit because the typed address is unverified.
Four obligations on every Proof of Address:
1. Capture an acceptable document — utility bill, bank statement, government letter, lease, mortgage, mobile / internet contract — dated within the last 90 days.
2. Read the address fields with Optical Character Recognition (OCR) and parse them into the canonical address envelope (line 1, line 2, city, postal code, country).
3. Cross-check the address against the address on the underlying ID document AND against the name on both — a mismatched address or a mismatched name fails the check.
4. Where the country supports it, validate the parsed address against the authoritative address registry (UK Royal Mail PAF, Spain Catastro / Padrón, France BAN, Germany DATEV, US USPS).
Pricing (verified live):
- Proof of Address: $0.20 per check
- ID Verification (required as the cross-check anchor): $0.15 per check
- Database Validation (per-country registry validation, optional): variable per service
- Combined bundle (ID + Liveness + Face Match + Proof of Address): $0.55 per user
- First 500 verifications free every month, forever
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60s, no card).
- Webhook endpoint with HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
- A workflow_id from the Workflow Builder bundling ID Verification + Passive Liveness + Face Match 1:1 + Proof of Address. Add a Database Validation node for the country-specific address registry where available.
STEP 1 — Create the session
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<your proof-of-address workflow id>",
"vendor_data": "<your user id, max 256 chars>",
"callback_url": "https://<your-app>/onboarding/poa/callback",
"expected_country": "ES",
"metadata": {
"purpose": "regulatory_address_capture",
"user_id": "<your internal id>"
}
}
Response: 201 Created with the hosted session URL. SMS or email the URL to the user; they complete ID capture + selfie + Proof of Address upload on their phone in under five minutes.
STEP 2 — Read the signed webhook on completion
Didit POSTs to your callback. Session statuses are Title Case With Spaces:
Body (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your user id>",
"status": "Approved",
"id_verification": { "status": "Approved", "document_type": "passport", "country_code": "ES" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"proof_of_address": {
"status": "Approved",
"document_type": "utility_bill",
"issuer": "Iberdrola",
"issued_at": "2026-04-12",
"address": {
"line1": "C. Diagonal 612",
"line2": "3a",
"city": "Barcelona",
"postal_code": "08021",
"country": "ES"
},
"cross_check": {
"name_match": true,
"address_match_with_id": true,
"within_90_day_window": true
}
},
"database_validation": {
"status": "Approved",
"service": "es_catastro_address",
"result": { "registry_match": true }
}
}
Session status enum (exact case):
Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned
Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw bytes with your webhook secret.
STEP 3 — Decide
Branch logic:
Approved → file the canonical address payload on the customer record.
In Review → hold the onboarding, wait for analyst webhook update.
Declined → refuse onboarding, log the decline reason (typically: document over 90 days old, name mismatch, address mismatch with the ID).
Resubmitted → user updated the upload; re-read the decision.
The Proof of Address sub-result is independent of the parent session — even if the parent session is Approved, the proof_of_address.status might be In Review if the cross-check flagged a different city. Switch on proof_of_address.status when you persist the address.
STEP 4 — Persist the canonical address envelope
When proof_of_address.status === "Approved", save the entire address object to your customer record as the regulatory current address. Use the canonical fields (line1, line2, city, postal_code, country) — Didit normalises across document layouts so the same shape works for an English utility bill, a Spanish bank statement, and a German Anmeldung.
Keep the issuer + issued_at fields for your audit log — they prove the document type and the recency window the regulator audited.
STEP 5 — Registry validation result
When the workflow includes a Database Validation node, the database_validation block returns the per-country registry-validation outcome:
- es_catastro_address — Spanish Catastro property registry
- uk_royal_mail_paf — UK Postcode Address File
- fr_ban — France Base Adresse Nationale
- de_anmeldung — German municipal registration check
- us_usps — US Postal Service address validation
A registry-match-false result on a country that supports validation is a signal worth manual review even if the OCR pass succeeded — most fake addresses fail registry validation immediately.
STEP 6 — Refresh on a cadence (optional)
Most regulators ask for the address on file to be re-confirmed every 1-3 years (longer for low-risk customers, shorter for high-risk). Add a periodic Proof of Address session to your account-refresh cadence — same workflow, same hosted URL flow.
WEBHOOK EVENT NAMES
- status.updated — session status changed.
- data.updated — session data changed (resubmission, document re-upload).
Verify X-Signature-V2 on every payload. The webhook secret is per-environment — sandbox key is separate from production.
CONSTRAINTS
- Session statuses use Title Case With Spaces (Approved, In Review).
- Acceptable documents must be dated within the last 90 days by default; some workflows extend to 180 days for low-risk customer segments.
- The address on the Proof of Address document MUST cross-check against the address on the underlying ID OR against a previously-Approved address on file. If neither match, the proof flips to In Review automatically.
- Default record retention is 5 years post-relationship per the EU AML package.
Read the docs:
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/sessions-api/retrieve-session
- https://docs.didit.me/core-technology/proof-of-address/overview
- https://docs.didit.me/core-technology/database-validation/overview
- https://docs.didit.me/integration/webhooks
Start free at https://business.didit.me — sandbox key in 60 seconds, 500 verifications free every month, no credit card.$0 / mes. No se requiere tarjeta de crédito.
Paga solo por lo que usas. Más de 25 módulos. Precios públicos por módulo, sin cuota mínima mensual.
MSA y SLA personalizados. Para grandes volúmenes y programas regulados.
Empieza gratis → paga solo cuando se ejecuta una verificación → desbloquea Enterprise para un contrato personalizado, SLA o residencia de datos.
Didit is infrastructure for identity and fraud, the platform we wished existed when we were building products ourselves: open, flexible, and developer-friendly, so it works as a real part of your stack instead of a black box you integrate around.
One API covers verifying people (KYC, know your customer), verifying businesses (KYB, know your business), screening crypto wallets (KYT, know your transaction), and monitoring transactions in real time, on a stack built to be:
The footprint underneath: 14,000+ document types in 48+ languages, 1,000+ data sources, and 200+ fraud signals on every session. The Didit infrastructure dynamically learns from every session and gets better every day.
Proof of Address is exactly what it sounds like, evidence that the person you're onboarding actually lives at the address they claim. The conventional artefacts are:
Why regulators care: an address on file is the anchor for anti-money-laundering record-keeping, tax-residency reporting (FATCA / CRS), and the legal jurisdiction of any future enforcement. A typed self-attested address is unverifiable; a Proof of Address backed by a recent document + a cross-check against the ID is the standard. Didit ships the full recipe for $0.20 per check.
Three reasons regulators consistently reject self-attested addresses:
The Proof of Address recipe, capture, OCR, cross-check, registry validation, produces a regulator-grade artefact in under five minutes on the user's phone. $0.20 per check end-to-end.
The full flow normally takes under 30 seconds end-to-end, pick up the ID, snap the document, snap the selfie, done. That is the fastest in the market. Legacy KYC providers usually take more than 90 seconds for the same flow.
On the back end, Didit returns the result in under two seconds at p99, measured from the moment the user finishes the selfie to the moment your webhook fires. Mobile capture is tuned for slow phones and slow networks: progressive image compression, lazy software development kit load, and a one-tap hand-off from desktop to phone via QR code if the user starts on web.
If you stop at "upload your utility bill", a determined attacker can:
The Didit recipe catches all four by stacking three layers of validation on top of the OCR:
All three run server-side. The agent never sees a raw upload, only the validated result.
Every session lands on one of seven clear statuses, so your code always knows what to do:
Approved, every check passed. Move the user forward.Declined, one or more checks failed. You can allow the user to resubmit the specific failed step (for example, re-take the selfie) without re-running the whole flow.In Review, flagged for compliance review. Open the case in the console, see every signal, decide approve or decline.In Progress, user is mid-flow.Not Started, link sent, user has not opened it yet. Send a reminder if it sits too long.Abandoned, user opened the link but did not finish in time. Re-engage or expire.Expired, the session link aged out. Create a new session.A signed webhook fires on every status change, so your database always stays in sync. Abandoned and declined sessions are free.
Production data is processed and stored in the European Union by default, on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.
Encryption everywhere. AES-256 at rest across every database, object store, and backup. Transport Layer Security 1.3 in transit on every API call, webhook, and Business Console session. Biometric data is encrypted under a separate Customer Master Key.
Retention is yours to control. Default retention is indefinite (unlimited) unless you configure shorter, between 30 days and 10 years per application, and you can delete any individual session at any time from the dashboard or the API.
Certifications: SOC 2 Type 1 (Type 2 audit in progress), ISO/IEC 27001:2022, iBeta Level 1 PAD, and a public attestation from Spain''s Tesoro / SEPBLAC / CNMV that Didit''s remote identity verification is safer than verifying someone in person. Full report at /security-compliance.
Didit ships compliant by default for the regulators that matter to identity infrastructure:
Detailed memo, every certificate, every regulator letter: /security-compliance.
Three integration paths, pick whichever fits your stack:
Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.
Most regulators want the Proof of Address document to be dated within the last 90 days at the moment of verification, anything older is treated as stale on the assumption that the user might have moved since.
Didit's OCR reads the document date and checks it against the verification timestamp automatically:
within_90_day_window: true → proof passes the recency checkwithin_90_day_window: false → session flips to In Review and the user is prompted to upload a more recent documentFor low-risk customer segments you can configure the workflow to extend the window to 180 days, or drop it to 60 days for high-risk segments. The configuration is per workflow, not per session, so changes apply uniformly. UK Right to Rent uses 90 days; EU AML guidance generally accepts 90-180 days depending on the supervisor.
Most regulators ask for the address on file to be re-confirmed periodically:
Didit's refresh is the same POST /v3/session/ against your Proof-of-Address workflow with the existing customer's vendor_data. The new document supersedes the previous one in the customer file; both are kept in the audit trail. Schedule the refresh from your customer-data pipeline, Didit doesn't auto-trigger refreshes because the cadence belongs to your risk policy.
Most KYC providers price Proof of Address between $0.50 and $2.00 per check, often as a separate line item on top of a higher KYC base, with per-country surcharges for any registry validation. The Onfido / Jumio / Veriff archetype.
Didit's published price is $0.20 per Proof of Address + $0.15 for the underlying ID Verification (required as the cross-check anchor) = $0.35 for the combined recipe. Database Validation adds variable per-country cost, typically $0.05-$0.20. No floor, no minimum, no per-country surcharge.
That's roughly 3-5× cheaper than the incumbent stack on the same regulatory output. At a 50,000-user month, the saving versus a $1.50-per-POA incumbent is around $65,000 per year. Full pricing at /pricing.
Una API para KYC, KYB, Monitoreo de Transacciones y Detección de Fraude en Wallets. Intégrala en 5 minutos.