Skip to main content
Trelent Document Verification integrates with your platform to assess fraud risk in financial and identity documents. The API returns a fraud score and detailed reasoning. Your team builds the integration to display these results in your interface and support human review. Trelent can help you build that integration. Use cases include loan application review and legal document review. Document Verification is always deployed in your cloud environment. Your data is never sent to or retained on Trelent servers.

​
How it fits into your platform

  1. Your end-users submit supporting documents through your platform.
  2. Your integration sends a document URL to the API in your cloud environment. The API checks the document and returns a fraud score with detailed reasoning and supporting findings.
  3. Your team builds the display and review workflow in your platform, using the API results to route high-risk documents to human reviewers.
A higher fraud score means a higher likelihood of fraud, but it does not guarantee that a document is fraudulent. Humans should always review high-risk cases. Your platform owns the experience for your end-users and reviewers.

​
How verification works

The API downloads the document and runs checks over its signatures, metadata, identifiers, and pixels. An analysis agent evaluates the document and check results to produce a fraud score from 0 to 100 with detailed reasoning. Some checks can determine a verification result directly; in those cases, the API returns an authoritative finding in place of a score. Typical turnaround is 60–120 seconds, and we are continually improving processing time. Detection runs in the background: creating one returns an ID immediately, and your integration polls for the result and displays it when ready.

​
Where to go next

Quickstart

Token, submit, poll, read the score — the whole flow in one page.