Every deal carries one identity answer for the file - whether you confirmed who the client is, and how - and, if you sent it to ComplyCube for a real photo-id check, the result of that specific verification.
When You'd Use This
Settle this on every file before you rely on the client's information, whichever way you get there: your own judgment, or a verification you send them to complete themselves.
Where Identity Sits on a File
The deal's Compliance tab carries a "Know Your Client (KYC) and PEP check" card with one Identity verified? answer for the whole file, above a per-applicant PEP register. Separately, the Compliance Hub's Identity tab lists every ComplyCube verification your brokerage has sent or collected, across every deal. The two describe the same underlying record when a verification exists, so approving or rejecting one from either place updates the other.
Recording a Verification You Did Yourself
Set Identity verified? to yes and pick how: you handled it in person, it was handled in another system, the client sent it to you directly, or something else. The choice autosaves the moment you make it, and switching back to no clears the method - a method next to a "no" would read as a verification that never happened.
Sending a Verification to the Client
Choose Request identity verification from the deal's compliance actions, pick the borrower if more than one is on the file, and send it by email or copy the link. The client completes it inside their own request without leaving it: BrokerPlus hands ComplyCube's capture tool a short-lived, single-use token, the client uploads a government photo ID and a live photo, and the upload becomes a document check, plus an identity check when a live photo was captured. A verification already in progress, or already verified inside your brokerage's re-verification window, is reused rather than started over.
Reviewing a Result
Once the client's captures are processed, the verification lands in Needs Review on the Identity tab, or opens straight from the deal. Review the status, method, when it completed, and whether the evidence is scoped to this deal or reusable across the contact's file, then approve or reject it with an optional note. Approving marks it Verified with a timestamp; rejecting marks it Failed and records your note as the reason. A rejected or failed verification doesn't fix itself: the client needs to retry through a fresh request, or you fall back to recording the verification yourself with a method and a note. A verification that was Verified can also go stale - past your brokerage's re-verification window, BrokerPlus treats it as expired and prompts a fresh attempt instead of trusting the old result.
Common Gotchas
- The file-level yes/no answer and a ComplyCube verification are related but not the same thing - you can answer yes from your own judgment on a file that never had a ComplyCube check at all.
- A capture that fires twice from the client's browser doesn't start a second check; BrokerPlus reuses the pending verification instead.
What to Do Next
- Complete a client's information record while you're gathering the rest of their file.
- Tour the Compliance Record on a Deal to see identity alongside every other requirement.
- Verify a Client's Documents Instantly if you want documents checked in the same pass.