Skip to main content
Document AI lets you collect documents that don’t fit a fixed template — proof of funds, payslips, source-of-wealth letters, tax statements, and anything else — and extract exactly the fields you define. You configure each document’s on-screen title and description (automatically translated into every verification language) and the list of data points to read. Didit’s AI extracts those fields, optionally cross-references them against other verification steps, and applies your rules to produce a status.

​
How it works

Configure documents and fields

In the workflow builder you define up to 3 documents. For each document you set:Start from a template or build from scratch.

The user uploads documents

The user uploads one file per configured document (PDF or image). Each upload is processed independently; the step completes once every required document has been provided.

AI extraction

Didit renders each document and runs a vision-language model with a schema built from your field definitions. Extracted values are returned typed (numbers as numbers, dates as YYYY-MM-DD) and stored per document. PDF/EXIF forensics run to detect manipulation.

Cross-reference & rules

Extracted fields can be cross-checked against other steps — for example, the document holder name against the verified ID, or any field against questionnaire answers — and against your basic rules and custom status rules. The resulting per-document statuses combine into the feature status.

​
Starter templates

When you add a Document AI node you can start from a ready-made template that pre-fills the title, description, and typed fields. Customize anything afterward.

​
Cross-referencing other steps

Document AI fields are addressable as document_ai.<field_key> and can be compared against fields from other completed steps using a custom status rule with value_type: "field". For example:
  • document_ai.account_holder equals kyc.full_name — the document holder matches the verified identity.
  • document_ai.balance greater_than 50000 — flag high balances for review.
Matching rules fold into the decision using the platform precedence Declined > In Review > Approved, so a rule can raise severity but never override a stricter risk-driven status. See Rules & warnings.

​
Document requirements

Document AI performs unstructured-text reading, which introduces a few seconds of latency per document. Webhooks fire only when the entire workflow step completes — do not poll the decision endpoint faster than every 5 s during this window.