Most identity verifications approve automatically. When one doesn't, the AML profile parks in Verification Review until a member of your team makes a call. This article explains the statuses, the review workflow, and what a declined verification blocks.
The Identity Verification card on an AML profile's Overview shows the latest check's Status, Provider (Didit for the AML module), when it was Initiated and when it Completed:
Pending — the session has been created but the client hasn't started.
In Progress — the client is part-way through.
In Review — the automated checks were inconclusive and a human decision is needed.
Approved — the verification passed.
Declined — the provider did not approve the verification, or a reviewer declined it.
Abandoned — the client started but never finished the session.
Expired — the session lapsed before completion.
Before any check has been started the card simply says No identity verification has been initiated yet.
An In Review result shows an amber alert — Identity verification needs review — listing the specific reasons the provider flagged, for example Face Match: Low face match similarity (score 65) or a flagged liveness or ID check. If the provider gave no specifics, Nagaris explains The automated photo match was inconclusive.
For privacy reasons the captured ID and selfie can't be shown in Nagaris. The alert suggests your two options: re-verify the client (best for poor-quality photos), or confirm their identity another way — for example sighting their original ID in person or on a video call. You have three actions:
Re-Verify — generates a fresh verification session and link (it opens in a new tab, and Copy Verification Link in the card's actions menu lets you send it to the client).
Confirm manually — opens the Confirm identity manually dialog. Record How identity was established — e.g. Video call on 19/06, sighted original driver licence — satisfied same person. This note is kept as the audit record. A note is required before you can click Confirm identity.
Decline — opens the Decline verification dialog. Record the Reason; the dialog reminds you to raise an unusual activity report with your compliance officer if you suspect impersonation.
After you confirm you'll see Identity confirmed manually; after declining, Verification declined.
A declined check shows a red alert — Identity verification was declined — with the provider's reasons where available, or: The provider did not approve this verification. Re-verify to send a new link, or follow up with the client.
While the latest verification is declined, the profile is deliberately blocked from advancing:
Run Screening is disabled, with the tooltip Resolve identity verification first.
Start Assessment / Re-Assess on the Risk Assessment card is disabled with the same tooltip.
Use Re-Verify to give the client another attempt, or cancel the session if the relationship isn't proceeding.
Each verification attempt is recorded on the profile's Timeline (Verification Initiated, Verification Completed with the outcome and provider, and any review flags such as a face-match issue).
An approved verification moves the pipeline forward automatically; the CDD status advances from Pending Verification towards Pending Screening.
The AML dashboard's CDD Status column shows Verification Review so flagged profiles are easy to find.
Re-verifying doesn't erase the earlier attempt — all checks stay listed against the profile for your audit trail.
Manual confirmation is an accountable decision: your name, the timestamp and your note are stored with the profile.
If a client's verification keeps failing on photo quality, ask them to try in good light, remove the ID from any sleeve, and use a phone rather than a webcam before you fall back to manual confirmation.
