> 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-ev-code-signing-certificates/phase-2-steps-via-email-and-emsign/certificate-requester-verification.md).
# Certificate Requester Verification
*After the order is placed, the Certificate Requester (the Organization Representative - the person who filled out and submitted the application) will receive an email asking them to confirm their certificate request.*
**Email you will receive:**
• Subject: "ORDER #\[Order ID] – Certificate Requester consent required for Code signing EV request"
• The email confirms that an order has been submitted for Code Signing – EV and requires your verification as the Certificate Requester.
• It contains a button labeled "Click here to provide consent." Click this button.
**What happens when you click the button:**
• You will be taken to the emSign Subscriber portal (a separate website from CERTInext) where you can view the details of your request.
• The screen shows a "Consent Required" page with your Order Details and Organization Details.
• A note on screen reads: "Accepting this consent means that you confirm your certificate request."
• You will see two buttons: "Approve" (orange) and "Reject" (white).
**What to do:**
• *Review the order details shown. Verify the Order ID, date, product (Code Signing - EV), and organization name are correct.*
• *If everything is correct, click the "Approve" button.*
• *A confirmation popup will appear asking: "Are you sure you want to accept the consent?" Click "Yes" to confirm.*
• *After clicking "Yes," you will see a green success message confirming your consent has been recorded.*
**What the emSign portal also shows (Order Actions tracker):**
On the emSign portal, you can also see a list of all 5 Order Actions and their current statuses:
1\. Certificate Requester Verification - Awaiting Customer Action (becomes "Completed" after you approve)
2\. Subscriber Agreement - Pending
3\. EV Certificate Request Approval - Pending
4\. Organization Verification - Pending
5\. Certificate Download - Issuance Pending
**⚠ IMPORTANT NOTE**
• This consent email is sent to the Organization Representative's email address (entered in Step 3 of the application).
• Do not click "Reject" unless you intentionally want to cancel the certificate request.
• If you do not receive this email, check your spam/junk folder. The sender will be from CERTInext or emSign.
• Once you approve, Action 1 is marked as "Completed" on the Order Actions tracker.
• *A button labeled "Proceed for Verification" on the success page takes you back to the full Order Actions list. Click it to monitor the remaining steps.*
---
# 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-ev-code-signing-certificates/phase-2-steps-via-email-and-emsign/certificate-requester-verification.md?ask=&goal=
```
`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.