> For the complete documentation index, see [llms.txt](https://docs.certinext.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-doc-signer-certificates/phase-2-steps-via-email-and-emsign/face-to-face-verification.md).

# Face To Face Verification

<p align="center"></p>

<figure><img src="/files/QCKUUZVqxbTygs5CzJ1I" alt=""><figcaption></figcaption></figure>

Face To Face Verification confirms your physical identity. You can complete this either by uploading a supporting document or by recording a short identity verification video.

#### Option A: Upload a Supporting Document

•       Applicant Name (pre-filled): Your name as entered in the application.  Verify this is correct.

•       Supporting Document: A document used to verify your identity in person (e.g., a photo with your identity document).  Click Choose File and upload the required document. Refer to the specific instructions on the portal for what document types are accepted.

#### Option B: Record a Video

As an alternative to document upload, you may verify your identity through a video recording. This involves a short video where you hold up your identity document and state your name and organization.

•       Record Video button: Initiates the video recording process for remote identity verification.  Click the Record Video button and follow the on-screen instructions. Ensure you hold your identity document clearly visible and state your name and organization.

&#x20;

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>TIP:</strong> Video verification is often faster as it can be processed without waiting for a document to be reviewed manually. Ensure good lighting and a quiet environment when recording.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>IMPORTANT:</strong> Whether uploading a document or recording a video, ensure your identity document (the same one used in Individual Verification) is clearly visible and not obscured.</td></tr></tbody></table>

### 2.10  Submitting All Verifications

&#x20;

<figure><img src="/files/abYCzbUWy9LznEy0GfOp" alt=""><figcaption></figcaption></figure>

Once you have completed all pending verification actions, return to the Order Actions page on the emsSign portal. Review the step statuses to confirm all required steps are done.

#### Final Status Summary

•       Step 1: Subscriber Agreement - Completed

•       Step 2: Email Verification - Completed

•       Step 3: Individual Verification - Completed

•       Step 4: Organization Verification - Completed

•       Step 5: Face To Face Verification - Completed

•       Step 6: Certificate Download - Issuance Pending

&#x20;

When all steps show Completed, click the Submit For Verification button at the bottom of the Order Actions page to formally notify the CA that all verifications are complete and the order is ready for final review and certificate issuance.

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>NOTE:</strong> After submitting, the certificate will be reviewed and approved by the CA. Once approved, the Certificate Status in CERTInext will change from "Pending for Approver" to "Issued" and you will receive a notification email.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-doc-signer-certificates/phase-2-steps-via-email-and-emsign/face-to-face-verification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
