> For the complete documentation index, see [llms.txt](https://docs.emudhradigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emudhradigital.com/documentation/remote-signing-document-signer/document-signer-certificates.md).

# Document Signer Certificates

A **Document Signer Certificate** identifies the organisation (and optionally a department or application) as the signer of system-generated documents.

## Certificate profile

| Field      | Example                                         |
| ---------- | ----------------------------------------------- |
| Subject CN | `ACME BANK LIMITED` or `ACME BANK – STATEMENTS` |
| O / OU     | Organisation and department                     |
| Key usage  | Digital signature, non-repudiation              |
| Algorithm  | RSA 2048/3072 or ECC P-256/P-384, SHA-256       |
| Validity   | 1–3 years                                       |
| Issuer     | emSign (eMudhra) Document Signer CA             |

## Issuance process

1. Organisation submits the application with organisational KYC documents and an authorisation letter for the authorised signatory.
2. eMudhra verifies the organisation and the authorised signatory.
3. A key pair is generated in the eMudhra HSM (or in the customer's HSM for on-prem) in a controlled key ceremony.
4. eMudhra CA issues the certificate and maps it to the customer's signing profile.
5. Credentials and API access are provisioned for UAT and production.

## Management

* **Multiple certificates** per organisation — for example one per business line or document type.
* **Renewal** before expiry with a new key pair; profiles are switched without application changes.
* **Revocation** on request or compromise; signing is blocked immediately.