---
title: Overview of Verify | Developer Documentation
description: Verify reviews PDFs, documents, and images for signs of local tampering or synthetic fabrication and presents the evidence for further investigation.
---

Preview

**Verify reviews documents for signs that their content is not authentic.** It distinguishes between a real document that may have been edited and one that may have been fabricated in full, then presents the findings for further review.

Verify supports PDFs, DOCX files, and PNG, JPEG, and WebP images. It is designed for document-fraud review, including identity documents, receipts, invoices, statements, certificates, and other records where authenticity matters.

## What Verify evaluates

Verify considers the document as a whole and, when possible, the individual areas that contributed to its assessment. The result separates two forms of document fraud:

- **Tampering** is the likelihood that a real captured document was altered after creation, such as when a field is replaced or part of another document is inserted.
- **Synthetic fabrication** is the likelihood that the document was generated or fabricated as a whole rather than captured from a real document.

These assessments are independent. A fabricated identity document can show strong synthetic-fabrication signals without containing a locally edited area. A genuine receipt with one changed amount can show the opposite pattern. A document can also show evidence of both.

## What a Verify result contains

Each completed review brings the most useful findings together:

- **An overall verdict** summarizes whether Verify found meaningful signs of doctoring.
- **Doctoring likelihood and verdict confidence** separate how suspicious the document appears from how strongly the available evidence supports that conclusion.
- **Tampering and synthetic scores** indicate the type of authenticity risk detected.
- **A plain-language summary** explains the assessment.
- **Suspect regions** identify and explain specific areas that contributed to the result when the evidence can be localized.
- **Supporting evidence and visual overlays** help reviewers examine the findings in the context of the source document.
- **Unavailable checks** make clear when a kind of evidence could not be assessed. A check that could not run is not treated as a clean result.

## What teams use Verify for

- **Intake screening** — prioritize suspicious submissions before they enter an approval, payment, or onboarding workflow.
- **Fraud triage** — distinguish likely whole-document fabrication from a localized alteration so cases can follow the right review path.
- **Reviewer support** — direct an investigator to the pages and regions most relevant to the assessment.
- **Audit context** — retain an interpretable verdict, confidence, summary, and supporting findings alongside a business decision.

## Interpreting Verify findings

Verify provides evidence for a risk decision; it does not establish authenticity on its own. Screenshots, photographs, rescans, compression, and document editing workflows can remove or weaken useful forensic information. Some findings also apply only to particular file types.

Treat a suspicious result as a reason for further investigation. Treat an inconclusive result, an unavailable check, or the absence of a localized region as missing evidence rather than proof that a document is authentic. For high-impact decisions, combine Verify with source validation, business rules, and human review.

## Next steps

- [Run Verify through the API](./api)