> 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/organization-verification.md). # Organization Verification
Organization Verification confirms that your organization is legitimate and that its identity and address are verifiable. When automatic verification via public registries fails (which is common for smaller or newer organizations), the CA requests an Attestation Letter. #### What is an Attestation Letter? An Attestation Letter is a formal document signed by a qualified professional (a Practicing/Qualified Accountant, a Lawyer, or a Government Official) that confirms the existence, identity, and registered address of your organization. This letter serves as a manual verification method in place of automated public registry checks. #### What To Do • Receive the email with subject: ORDER #\[Order ID] - Submit Attestation Letter for \[Organization Name] Organization. • Click the link in the email to open the Organization Verification form on the emsSign portal. • Prepare the Attestation Letter with the help of a Practicing Accountant, Lawyer, or Government Official. • Complete the form and upload the letter. #### Field Reference • Organization Name (pre-filled): The name of your organization, auto-filled from your application. Verify this is correct. • Document Type (pre-filled): Set to "Attestation Letter" by default. No input needed. • Document \*: The Attestation Letter file to be uploaded. Must be in PDF format. Click Choose File and upload the signed, stamped Attestation Letter in PDF format. • Document Issued By \*: The professional category of the person who signed the attestation letter. Select the appropriate option: "Practicing / Qualified Accountant", "Lawyer", or "Government Official". • Issuer Name \*: The full name of the professional who signed and issued the Attestation Letter. Enter the complete name of the accountant, lawyer, or official who signed the letter. • Issuer Email ID \*: The email address of the issuer (the professional who signed the letter). Enter the official email address of the issuing professional. • Issuer Contact No. \*: The phone number of the issuer. Enter the phone number of the issuing professional with the correct country code. • After filling all fields and attaching the PDF, click Submit For Verification. #### Instructions Summary (as shown on portal) • Upload the Attestation Letter signed by a Practicing/Qualified Accountant, Lawyer, or Government Official. Platform supports PDF documents only. • Once the document is uploaded successfully, proceed to submit it for verification. • A Validation Agent will validate the submitted Attestation Letter and verify the Issuer details.
IMPORTANT: Do not submit a scanned copy that is unclear, incomplete, or lacks a proper stamp/seal from the issuing professional. Rejection will cause delays.
### 2.8 Organization Authentication Code Verification

[ INSERT SCREENSHOT ]

Email to Organization Contact: "ORDER #[Order ID] - Authentication Code for [Organization Name]" containing the 6-digit code

Figure 2.8a: Authentication Code email sent to organization contact

[ INSERT SCREENSHOT ]

Email to Certificate Holder: "ORDER #[Order ID] - Authentication Code Verification Link for [Organization Name]" with orange verification link button

Figure 2.8b: Authentication Code Verification Link email sent to certificate holder

[ INSERT SCREENSHOT ]

emsSign portal - Organization Authentication Code Verification page with code entry field

Figure 2.8c: Organization Authentication Code entry page

[ INSERT SCREENSHOT ]

emsSign portal - Success: "Thank you for submitting the organization authentication code for [Organization Name] and completing the verification successfully"

Figure 2.8d: Organization authentication code verification success

As part of Organization Verification, the CA sends an Organization Authentication Code to the Organization Representative's registered email address to further confirm the organization's identity. Simultaneously, a separate verification link is sent to the Certificate Holder (you) to enter the code. #### How This Two-Party Verification Works • The CA sends a 6-digit Organization Authentication Code to the Organization Representative's registered email. • The CA sends a separate Verification Link email to the Certificate Holder (the individual named on the certificate). • The Certificate Holder contacts the Organization Representative to collect the code. • The Certificate Holder visits the verification link, enters the code, and submits it. #### Field Reference - Code Entry Page • Organization Name (pre-filled): Your organization's name, auto-populated. Verify this is correct. • Organization Authentication Code \*: The 6-digit code sent to the Organization Representative's email. Enter the exact code as received. The code is case-sensitive and numeric. Ask your Organization Representative for this code. • Designation \*: The Certificate Holder's job title, pre-filled from the application. Verify this is correct. Edit if needed. • After entering the code, click Submit. • A success page will appear: "Thank you for submitting the organization authentication code for \[Organization Name] and completing the verification successfully." • Click Proceed for Verification to return to the Order Actions page.
IMPORTANT: The authentication code expires within 24 hours. Coordinate with your Organization Representative promptly to obtain the code before it expires.
NOTE: Two separate emails are sent in this step - one to the Organization Representative and one to the Certificate Holder. Do not confuse the two. Only the code email goes to the Representative; the verification link goes to the Certificate Holder.
--- # 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/organization-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.