Wait for a Final Result
A status can be preliminary before it settles. Only act on it once it’s final:- Dashboard
- Webhook / API
Open the verification profile and check Final result under the Partner Information card. While a human reviewer is still working the case, it shows as Reviewing — wait until it changes.
What to Do with Each Status
Handling Suspected
Suspected means the checks may have already passed, but the system found something worth a second look. Before treating it as a rejection, check whether the document and face themselves came back clean — if so, only the tags below are actually in question.- Dashboard
- Webhook / API
Open the verification profile and check Final result details under the Partner Information card. If the document and face results both come back clean, the underlying checks succeeded and only the tags below caused the flag.
For the full list of every possible value, see Verification Statuses — Face Status, Document Status, Fraud Tag, and Mismatch Tag values.
Resolving a Suspected or Denied Result
- From the dashboard — a reviewer can clear the specific tag that caused the flag. See Resolving False Positives and Mismatch Tags. Removing the tag automatically re-evaluates the status; if it was the only reason for the flag, the status updates to Approved without any further action. This works for both Suspected and Denied.
- From your integration — Request Update reactivates the token, but only for three specific cases: uploading a POA document, completing a Risk Assessment, or answering a Questionnaire. None of those three can produce a Denied result, so Request Update only ever applies to a Suspected case caused by one of them — never to Denied, and never to resubmitting the primary ID document or selfie. For anything outside that scope, resolve it from the dashboard, or have the user start an entirely new verification session.
iDenfy Does Not Evaluate Suspected
For Approved and Denied, iDenfy’s automated and manual review pipeline commits to a decision on your behalf. Suspected is different by design: iDenfy detects and reports the signal — the specific tag — but does not judge whether that signal disqualifies the user. Whether a name mismatch, an age flag, an AML hit, or a duplicate face should block someone depends on your risk appetite, your jurisdiction, and your product. Those are business decisions only you can make, so iDenfy leaves the result open rather than guessing on your behalf.Build Your Own Evaluation Procedure
Because iDenfy won’t resolve Suspected for you, treat evaluating it as a required part of your process, not an edge case you’ll handle manually the first time it comes up:- Read every tag your configuration can produce — Fraud Tags and Mismatch Tags — and decide, per tag, whether it should auto-approve, auto-deny, or route to manual review.
- Write that decision down as an internal procedure that your team (support, compliance, risk) actually follows, rather than leaving it to ad hoc judgment calls each time a case comes up.
- Decide who is authorized to override a Suspected result, and how — see Resolving a Suspected or Denied Result above for the available mechanisms.
- Log the decision against the verification’s Scan ref for audit purposes, especially whenever a fraud tag is overridden.