Verifica cualquier dirección. De una factura, un banco o una carta.
Verifica la residencia a partir de una factura de servicios, extracto bancario, carta gubernamental o contrato de alquiler. Leemos el documento, extraemos la dirección, cotejamos el nombre con el DNI verificado y devolvemos un resultado estructurado. 0,20 $ por verificación, 500 gratis/mes.
Con la confianza de más de 2.000 organizaciones en todo el mundo.
Factura + extracto bancario
Extrae la dirección. Compara el nombre.
Leemos el documento, extraemos la dirección y el nombre, y los cotejamos
ambos con la identidad verificada. Factura de servicios, extracto bancario, contrato de alquiler, carta de impuestos
, 0,20 $ por verificación.
Cómo funciona
De la suscripción al usuario verificado en cuatro pasos.
Paso 01
Crea el flujo de trabajo
Elige las verificaciones que quieras: DNI, prueba de vida, cotejo facial, sanciones, dirección, edad, teléfono, email, preguntas personalizadas. Arrástralas a un flujo en el panel de control, o publica el mismo flujo en nuestra API. Crea ramificaciones condicionales, haz pruebas A/B, sin necesidad de código.
Paso 02
Integra
Intégralo de forma nativa con nuestros SDKs 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.
Paso 03
El usuario completa el flujo
Didit aloja la cámara, las indicaciones de iluminación, el traspaso 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 contra fuentes de datos autorizadas. Resultado en menos de dos segundos.
Paso 04
Recibes los resultados
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.
Diseñado para desarrolladores · Creado contra el fraude · Abierto por diseño
Seis funcionalidades. Un solo feature flag: PROOF_OF_ADDRESS.
Cada funcionalidad a continuación es un "toggle" en el mismo módulo. Sin niveles de venta adicionales, sin SKUs separados, sin llamadas de complemento. Actívalas por flujo de trabajo o pásalas en línea en la llamada a la API.
Facturas, extractos bancarios, cartas oficiales, contratos de alquiler.
Cuatro categorías: facturas de servicios (electricidad, agua, gas, internet, teléfono), extractos bancarios (cuenta, tarjeta de crédito, hipoteca, préstamo), documentos oficiales (declaración de impuestos, tarjeta de votante, certificado de residencia) y otros (contrato de alquiler, carta de empleador, seguro, declaración jurada notarial). JPG, PNG, TIFF o PDF de hasta 15 MB. Procesamiento de varias páginas en una sola inferencia.
Accepted documents
document_type enum · 4 buckets
15 MB
4
Buckets
5
File formats
15 MB
Per upload
Multi
Page support
Utility bill
UTILITY_BILL
Bank statement
BANK_STATEMENT
Government doc
GOVERNMENT_ISSUED_DOCUMENT
Other PoA
OTHER_POA_DOCUMENT
FormatsJPGJPEGPNGTIFFPDF
02 · Extracción + autenticidad
Lee cada campo de dirección. Detecta cada falsificación.
El OCR (reconocimiento óptico de caracteres) extrae la dirección y la normaliza en un objeto estructurado: calle, ciudad, región, código postal, tipo de dirección. Incluye latitud y longitud. En la misma pasada se realizan análisis forenses de autenticidad del documento: detección de manipulación a nivel de píxel, residuos de copiar/pegar o clonar, inconsistencias de fuente y kerning, señales de imágenes sintéticas generadas por IA y discrepancias de metadatos. Los documentos manipulados se marcan como `In Review` con una advertencia explícita, no se aprueban en silencio.
Configura la ventana de validez del documento por aplicación: 30, 60, 90 días o lo que tú elijas. El valor predeterminado es 90. Extraemos la fecha de emisión y la comparamos con la marca de tiempo de envío; cualquier documento más antiguo que el umbral se rechaza automáticamente con `EXPIRED_DOCUMENT`. Los documentos sin fecha de emisión legible, o con una fecha futura, activan advertencias que puedes dirigir a revisión manual.
Recency check
issue_date · configurable · 90 d default
Configurable
Issue date · warning codeAgeAction
14 Mar 2026
—
12 daysApprove
02 Feb 2026
NEAR_AGE_LIMIT
82 daysReview
11 Nov 2025
EXPIRED_DOCUMENT
184 daysDecline
Configurable threshold · default 90 days · older fires EXPIRED_DOCUMENT
04 · Coincidencia de nombre con KYC
La factura coincide con la ID. O no.
Se activan tres advertencias de discrepancia de nombre cuando el nombre del documento difiere de la identidad verificada, del valor que enviaste a través de la API o de otra prueba de dirección en la misma sesión. Un umbral de coincidencia configurable (normalmente 90-95%) tolera variaciones en el segundo nombre y la ortografía. Cada advertencia se puede configurar para Rechazar, Revisar o Aprobar por aplicación.
Name match
vs verified KYC subject
Matched
JA
Name on billJohn A. Smith
JS
Name on KYCJohn Smith
Similarity 96%
No mismatch with API value
NAME_MISMATCH_WITH_PROVIDED
No mismatch with verified identity
NAME_MISMATCH_ID_VERIFICATION
No mismatch across PoA documents
POA_NAME_MISMATCH_BETWEEN_DOCUMENTS
05 · Dirección estructurada y parseada
El OCR devuelve un string. Didit devuelve un esquema.
Cada respuesta incluye un objeto de dirección parseada,calle, ciudad, región, código postal, tipo de dirección, además de las coordenadas sin procesar. Intégralo en tu registro de clientes, modelo de fraude o enrutamiento de entregas. Sin expresiones regulares, sin post-procesamiento, sin un parser por país. La misma estructura, ya sea que el documento se haya emitido en EE. UU., España, Brasil o Singapur.
poa_parsed_address
Structured response · same shape every country
Approved
street_1123 Main St
street_2Apartment 4B
cityNew York
regionNY
postal_code10001
address_typeRESIDENTIAL
geometry.lat 40.7128
geometry.lng -74.0060
06 · Listo para compliance
Evidencia para AMLD6 y la Recomendación 10 del FATF. $0.20 por verificación.
La verificación de dirección es obligatoria según la AMLD6 (6ª Directiva Antilavado de Dinero de la UE) para la diligencia debida del cliente y la Recomendación 10 del FATF. Cada veredicto incluye una URL de documento firmado, un array de advertencias listo para auditorías y análisis forenses de manipulación de superposiciones en PDF; tu oficial de compliance tendrá el paquete de pruebas a mano. Precios públicos de pago por llamada, sin contrato.
Compliance evidence
AMLD6 · FATF Rec 10 · auditor ready
Live
$0.20
Per check
500
Free / month
< 2s
Verdict
Webhook fired · poa_9f01a3c status Approved1.4 s
S
Signed document_file URL
S3 · 7-day pre-signed
On every call
W
warnings[] audit array
EXPIRED · NAME_MISMATCH · TAMPERED
Signed
P
PDF overlay forensics
duplicate_font_subset · glyph_fragmentation
Ready
Integra
Dos endpoints. Mismo JSON. Mismo precio.
Crea una sesión cuando quieras que nuestra interfaz de usuario alojada gestione la captura y la carga de varias páginas. Llama al endpoint independiente cuando ya tengas el documento. El formato del informe es el mismo en ambos casos.
Tú controlas la captura. Te devolvemos el informe completo en línea.docs →
Integración lista para agentes
Lanza la Prueba de Domicilio con un solo prompt.
Pega el siguiente bloque en Claude Code, Cursor, Codex, Devin, Aider o Replit Agent. Rellena el marcador de posición `my_stack` con tu framework, lenguaje y caso de uso. El agente provisiona Didit, crea el flujo de trabajo, conecta el webhook y lo lanza.
didit-integration-prompt.md
# Didit Proof of Address — integrate in 5 minutes
You are integrating Didit's Proof of Address (PoA) module into <my_stack>.
Follow these steps exactly. Every URL, header, and enum value below is
canonical — do not paraphrase or "improve" them.
## 1. Provision an account
- Sign up: https://business.didit.me (no credit card required).
- Or provision programmatically: POST https://apx.didit.me/auth/v2/programmatic/register/
(returns an API key bound to the workspace + application).
## 2. Two integration paths — pick one
### Path A — Workflow Builder (hosted UI)
Best when you want Didit to handle document capture, multi-page upload,
auto-capture, mobile handoff, and accessibility for you.
1. Create a workflow that contains the PROOF_OF_ADDRESS feature:
POST https://verification.didit.me/v3/workflows/
Authorization header: x-api-key: <your-api-key>
Body: workflow_label, features array with the single entry
{ feature: "PROOF_OF_ADDRESS" } (UPPERCASE — strict enum)
Optional config: accepted document_type filters
(UTILITY_BILL, BANK_STATEMENT, GOVERNMENT_ISSUED_DOCUMENT,
OTHER_POA_DOCUMENT) and per-warning threshold overrides.
2. Create a verification session for an end user:
POST https://verification.didit.me/v3/session/
Body: workflow_id (from step 1), vendor_data (your own user id).
Response: session_url — redirect the user to it.
3. Listen for webhook callbacks (see "Webhooks" below).
### Path B — Standalone server-to-server API
Best when you already have a captured document image or PDF (mobile SDK
capture, native onboarding app, reseller pipeline).
POST https://verification.didit.me/v3/poa/
Content-Type: multipart/form-data
Body fields:
- document (required, file — JPG, JPEG, PNG, TIFF, or PDF, <= 15 MB)
- vendor_data (optional string, your user id)
- full_name (optional string, name to cross-check against the document)
- address (optional string, address to cross-check against the document)
Response: JSON report with the parsed address, document_type, issuer,
issue_date, name_on_document, and a warnings array.
## 3. Webhooks (Path A only — Path B returns synchronously)
- Register a webhook destination once via
POST https://verification.didit.me/v3/webhook/destinations/
Body: url, subscribed_events: ["session.verified", "session.review_started",
"session.declined"]
- Response includes secret_shared_key — store it.
- Every webhook delivery carries an X-Signature-V2 header you MUST verify
before trusting the payload. HMAC-SHA256 verification MUST run against the raw body bytes (the raw payload as Didit sent it) BEFORE any JSON parsing — re-serialising the parsed body changes whitespace and key order, which invalidates the signature.Algorithm:
1. sortKeys(payload) recursively
2. shortenFloats (truncate trailing zeros after the decimal point)
3. JSON.stringify the result
4. HMAC-SHA256 with the secret_shared_key
5. Hex-encode, compare to the X-Signature-V2 header.
## 4. Reading the report (both paths return the same shape)
The poa object includes:
- status: "Approved" | "Declined" | "In Review" | "Not Finished"
- issuing_state: ISO 3166-1 alpha-3 country code
- document_type: "UTILITY_BILL" | "BANK_STATEMENT" |
"GOVERNMENT_ISSUED_DOCUMENT" | "OTHER_POA_DOCUMENT" |
"UNKNOWN"
- issuer: string (the issuing institution or company)
- issue_date: YYYY-MM-DD
- expiration_date: YYYY-MM-DD or null
- document_language: ISO 639-1 language code
- name_on_document: string (full name extracted from the document)
- poa_address: raw extracted address string
- poa_formatted_address: normalized human-readable address string
- poa_parsed_address: structured object with street_1, street_2, city,
region, postal_code, address_type, and raw_results.geometry.location
(lat / lng for geocoding)
- document_file: signed URL to the captured document (expires in 60 minutes)
- document_metadata: optional file_size, content_type, creation_date,
modified_date, and overlay_manipulation forensic block for PDFs (detected
flag, signals such as duplicate_font_subset or glyph_fragmentation, and
manipulated_regions in PDF page coordinates)
- warnings: Array<{ risk, additional_data, log_type, short_description,
long_description }>
Auto-decline risks (always enforced by Didit, not configurable):
- POA_DOCUMENT_NOT_SUPPORTED_FOR_APPLICATION
- EXPIRED_DOCUMENT
- INVALID_DOCUMENT_TYPE
- MISSING_ADDRESS_INFORMATION
Configurable risks (action per workflow — Decline, Review, or Approve):
- NAME_MISMATCH_WITH_PROVIDED
- NAME_MISMATCH_ID_VERIFICATION
- POA_NAME_MISMATCH_BETWEEN_DOCUMENTS
- POOR_DOCUMENT_QUALITY
- DOCUMENT_METADATA_MISMATCH
- SUSPECTED_DOCUMENT_MANIPULATION
- UNSUPPORTED_DOCUMENT_LANGUAGE
- ADDRESS_MISMATCH_WITH_PROVIDED
- UNABLE_TO_EXTRACT_ISSUE_DATE
- UNPARSABLE_OR_INVALID_ADDRESS
- ISSUER_NOT_IDENTIFIED
- UNABLE_TO_VALIDATE_DOCUMENT_AGE
- FUTURE_ISSUE_DATE
## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: PROOF_OF_ADDRESS, ID_VERIFICATION, LIVENESS,
FACE_MATCH, AML, IP_ANALYSIS.
- document_type enum is UPPERCASE_SNAKE: UTILITY_BILL, BANK_STATEMENT,
GOVERNMENT_ISSUED_DOCUMENT, OTHER_POA_DOCUMENT, UNKNOWN.
- Auth header is x-api-key (lowercase, hyphenated).
- Webhook signature header is X-Signature-V2 (NOT X-Signature).
- Always verify webhook signatures before trusting payload data.
- Status casing matches exactly: "Approved", "Declined", "In Review",
"Not Finished" (title-cased, space-separated).
- Documents must be issued within 90 days of submission — older documents
trigger the EXPIRED_DOCUMENT auto-decline regardless of policy.
- The PoA document must be different from the document submitted for ID
Verification — same image triggers POA_DOCUMENT_NOT_SUPPORTED.
## 6. Accepted document types (do not paraphrase to users)
- Utility Bill — Electricity, Water, Gas, Internet, Phone, Cable TV,
Satellite TV, Trash Collection, Sewage, Heating, Combined Utilities,
Municipal Services.
- Bank Statement — Account Statement, Credit Card Statement, Bank Letter
Confirming Address, Mortgage Statement, Loan Statement, Savings,
Checking, Investment, Business Account, Credit Union, Debit Card,
Line of Credit.
- Government-Issued Document — Tax Assessment, Voter Registration Card,
ID document, Residency Certificate, Government Letter, Census Letter,
Property Tax Bill, Vehicle Registration, Social Security Statement,
Unemployment Benefits Letter, Pension Statement, Court Summons,
Municipal Permit, Immigration Document.
- Other Proof of Address — Lease Agreement, Rental Agreement, Employer
Letter Confirming Address, Insurance Policy, School Enrollment Letter,
Notarized Affidavit, Solicitor Letter, Payroll Stub, Employment
Verification Letter, Retirement / Brokerage Account Statement.
Image requirements: JPG, JPEG, PNG, TIFF, or PDF. Maximum file size 15 MB.
Full-color, all corners visible, no digital editing, all pages included
for multi-page documents.
## 7. Pricing reference (public)
- Standalone /v3/poa/ call: $0.20 per check.
- Bundled inside a Didit workflow (KYC plus PoA): $0.20 per check on top
of the bundle base.
- 500 free verifications every month, forever, on every account.
## 8. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test documents: deterministic synthetic bills returned in sandbox
(Approved by default; trigger Declined by submitting the canonical
"expired" test bill from the sandbox sample pack).
- Switch to live: flip the application's environment toggle in console.
When in doubt: https://docs.didit.me/core-technology/proof-of-address/overview
¿Necesitas más contexto? Consulta la documentación completa del módulo.docs.didit.me →
Cumplimiento por diseño
Abre un nuevo país en un clic. Nosotros hacemos el trabajo duro.
Abrimos las filiales locales, aseguramos las licencias, realizamos las pruebas de penetración, obtenemos las certificaciones y nos alineamos con cada nueva regulación. Para lanzar verificaciones en un nuevo país, activa un interruptor. Más de 220 países en vivo, auditados y probados trimestralmente, el único proveedor de identidad que un gobierno de un estado miembro de la UE ha calificado formalmente como más seguro que la verificación presencial.
Tipos de documentos: factura de servicios, extracto bancario, documento oficial, otros.
0d
Antigüedad máxima de la fecha de emisión antes del rechazo automático.
<0s
Inferencia de extremo a extremo por verificación de Prueba de Domicilio.
$0.00
Por verificación de Prueba de Domicilio independiente.
Tres niveles, una lista de precios
Empieza gratis. Paga por uso. Escala a Enterprise.
500 verificaciones gratuitas cada mes, para siempre. Pago por uso para producción. Contratos personalizados, residencia de datos y SLAs (Acuerdos de Nivel de Servicio) en Enterprise.
Gratis
Gratis
$0 / mes. No se requiere tarjeta de crédito.
Paquete KYC gratuito (Verificación de ID + Prueba de vida pasiva + Coincidencia facial + Análisis de dispositivo e IP), 500 / mes, cada mes
Empieza gratis → paga solo cuando se ejecuta una verificación → desbloquea Enterprise para un contrato personalizado, SLA o residencia de datos.
FAQ
Preguntas frecuentes
What is Didit?
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:
Fast, sub-2-second p99 on every session
Reliable, in production with 1,500+ companies across 220+ countries
Secure, SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person
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.
What is Proof of Address?
Proof of Address (PoA) is the verification of a person's residency using a utility bill, bank statement, government letter, or lease, captured, Optical Character Recognition (OCR)-extracted, validated, and returned as a structured address in seconds.
Didit handles the document capture, parses the issuer and issue date, runs tamper-detection forensics, cross-checks the name against the verified Identity Document, normalizes the address into structured fields (street_1, city, region, postal_code), and geocodes it.
$0.20 per check. Full reference: docs.didit.me/core-technology/proof-of-address.
What does Proof of Address cost?
$0.20 per standalone POST /v3/poa/ call, or $0.20 when bundled into a Didit workflow on top of the underlying bundle base.
No monthly minimum, no contract, no overage surprises, the price on didit.me/pricing is the price on the invoice. Volume discounts kick in automatically as you grow.
How fast is the verification for my end user?
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.
What is the response shape?
A single poa JavaScript Object Notation (JSON) object on the session report and on the standalone Application Programming Interface (API):
status, Approved, Declined, In Review, Not Finished.
name_on_document, poa_address (raw Optical Character Recognition (OCR) string), poa_formatted_address (normalized).
poa_parsed_address, structured street_1, street_2, city, region, postal_code, address_type, with raw_results geometry coordinates for geocoding.
Signed document_file Uniform Resource Locator (URL) that expires in 60 minutes.
Portable Document Format (PDF) submissions also include a document_metadata.overlay_manipulation forensic block. Full reference: docs.didit.me/core-technology/proof-of-address/report-proof-of-address.
What happens if a user fails, abandons, or expires?
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.
Where does my customer data live and how is it protected?
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.
Is Didit compliant for my industry?
Didit ships compliant by default for the regulators that matter to identity infrastructure:
GDPR + UK GDPR, controller / processor split, full Data Processing Agreement published, lead supervisory authority named (Spain''s AEPD).
AMLD6 + EU AML Single Rulebook, 1,300+ sanctions, politically exposed person, and adverse-media lists screened in real time.
eIDAS 2.0, EU Digital Identity Wallet aligned; reusable-identity ready.
MiCA (Markets in Crypto-Assets), ready for crypto on-ramps, exchanges, and custodians.
DORA, Digital Operational Resilience Act, EU financial-services operational resilience.
BIPA, CUBI, Washington HB 1493, CCPA / CPRA, US biometric privacy (Illinois, Texas, Washington) and California consumer privacy.
UK Online Safety Act, age-gating and child-safety obligations.
FATF Travel Rule, originator and beneficiary data on crypto transfers, IVMS-101 interoperable.