Skip to main content
Verifications in the console lists every verification of your workspaces, newest first. Filter by workspace, status, mode and date, search by your reference (external_id), and choose the columns you want.

​
A verification’s page

Opening a verification shows:
  • its status and, when declined or resubmitted, the reason;
  • every attempt, with the images the person submitted and what was read from their document;
  • duplicate detection matches, and blocklist matches;
  • the webhooks sent for it and your endpoint’s responses;
  • a link to the person in your own admin, if the workspace has an external profile URL template.
The images are kept for a limited time; see Data retention and erasure.

​
Deciding by hand

Automatic decisions are final in most cases, but an administrator can correct one: Declining an approved verification asks for a reason; approving records a fixed one. Each correction sends a webhook for the new status, carrying manual_moderation with who made it.

​
Correcting document fields

When the reader got a field wrong, for example a misread digit in the document number or a swapped day and month in the date of birth, an administrator or a support specialist can correct it on the verification page. The same is available to them in the MCP server as correct-document-fields.
  • It works on approved, declined and in-review verifications, for what ProofAge publishes. Every workspace can correct the document type, the issuing country and the issuing state or province. Age verification workspaces can also correct first name, last name, date of birth and document number; identity (KYC) workspaces can correct all eleven document fields. In a test workspace it also works when a document was photographed but never read, so you can try your webhook handler. A face-only verification has no document to correct.
  • A correction does not change the status and does not run any check again. If the corrected data should change the outcome, approve or decline by hand, as above.
  • The recognised value is kept. Your corrected value is what the webhook, GET /v1/verifications/{id}/document and the MCP server return. Clearing a correction brings the recognised value back.
  • Each correction sends a data.updated webhook with the corrected document and the names of the fields it changed. A correction that changes nothing sends none.
  • The verification’s timeline records who corrected which fields, and not the values. Erasing the person’s data removes the corrections too.

​
Dashboard

The console’s Dashboard shows volumes and outcomes day by day, and why people were asked to retake an image, for all your live workspaces or one of them. A reason that dominates the retakes usually points at something you can fix in your flow, such as people verifying in poor light. The MCP server answers with the same numbers: see MCP examples.

​
Other actions