Pre-Exam Identity Check-in for Online Assessments | MyProof
Assessment products can evaluate MyProof as a pre-exam identity check-in layer: their server creates a session, polls for a bounded identity-policy result, links it to the candidate record, and decides whether to admit the candidate. Compatibility, exact handoff fields, and enrollment binding require pilot validation.
Documented partner-result fields
- Documented partner-result omissions: raw document image, document number, birthdate, address, and face image (verify target path)
Best for
- Remote assessment products adding a pre-exam identity gate.
- Certification teams evaluating a supported document/device path.
- Product and engineering leads who need a defined handoff before exam access.
Not for
- A full proctoring replacement or exam-surveillance service.
- A promise of universal document or device support.
- An identity-data repository for exam records.
Place identity verification at the exam-launch boundary
Use MyProof for the identity decision before exam launch. Your platform links the returned result to the candidate record and decides whether to admit the candidate; it keeps scheduling, accommodations, exam delivery, monitoring, and review.
The documented integration uses server-side session creation and polling. During a compatible own-device demo, your team can check the document/device path, accessibility, failure handling, and the result your workflow needs.
Review the data your platform would receive
Ask which inputs leave the device, which bounded result reaches your server, and what your team retains. Current partner-result documentation describes omitting raw document images, document numbers, birthdates, addresses, and face images; confirm the boundary for your target path.
Frequently asked questions
Where does MyProof integrate into an online proctoring flow?
It is intended as a pre-exam identity check-in layer. Your platform keeps exam delivery, monitoring, accommodations, and review.
How does our server connect?
Current support documentation describes server-side session creation and polling for a bounded identity-policy result. Exact handoff fields should be confirmed in a pilot.
What can we evaluate in a demo?
Bring your own device and target document path. A virtual or in-person session can review compatibility, accessibility, failure handling, and the result your workflow needs; availability is confirmed before the appointment.
Does MyProof monitor the exam?
No. MyProof's proposed use here is identity check-in; your platform owns monitoring and review.
Which data should we ask about?
Ask what crosses from device to server and what your team retains. Current partner-result documentation describes omitting raw images, document numbers, birthdates, addresses, and face images; verify the boundary for the target path before relying on it.
Does MyProof support every document or device?
Compatibility is document-, device-, and path-specific. Confirm target coverage before the appointment and treat unsupported paths as a pilot gate.
Related solutions
Canonical page: https://myproof.ai/online-proctoring-identity-verification