Skip to content

Digital Signature Certificate API

New

Bring signing by a named authorized signatory into your workflow. The signature comes from a certificate on the signatory's own token, and you can check that certificate before you rely on the document.

Overview

A Digital Signature Certificate goes to a named person once their identity has been checked. It lives on a hardware token, and that person uses it to sign documents electronically for a fixed validity period. Where a company signs, the holder is a director, a company secretary or another authorized signatory acting for it. Statutory filings, tender portals and many corporate counterparties ask for exactly this. They want a signature that traces back to an identified officer of the business. An API keeps the document, the signature and the certificate details in one workflow. You can check the signed file and store it without retyping anything. Which fields and checks you get depends on your service contract and on the data source behind the certificate.

Coverage
India, for certificates held by named individuals and organization role holders
Input
The finalized document and the certificate held by the named signatory, or a certificate you want to check
Output
The signed document, and the certificate details available behind the signature, such as holder, organization, validity and status
Typical users
Company secretarial, legal, finance, trade compliance and tendering teams
Coverage note
India. Your service contract and the data source decide the document types supported, the certificate handling and the checks available

The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.

Reference in progress

The request and response reference for this endpoint is not published yet.

Everything below this block is the live catalog record for this service, and it is accurate. The platform’s published API contract does not include this service yet, so there is no request or response detail to document. Rather than fill these sections with a plausible example, the page lists what is missing:

Endpoint URL and method
The host, path and HTTP verb for this service.
Authentication
How a request identifies itself, and where credentials come from.
Request parameters
Field names, types, which are required, and validation rules.
Response schema
The success body, field by field, with a real example.
Error codes
What each failure means and which are worth retrying.
Rate limits
Request ceilings, and what happens at the ceiling.

No sample payload, URL, response body, error code, rate limit or latency figure appears anywhere on this site unless it has been supplied and attributed. Each item in this list is removed only when its own detail arrives; none of them is held back to wait for the rest, and none is ever placed beside a guess in the meantime.

Use cases

  • Lending and NBFC: security and sanction documents signed by an authorized officer
  • Fintech and PSP: partner and enterprise agreements executed by a named signatory
  • Insurance: corporate and statutory filings signed by the recorded role holder
  • Logistics and freight: customs and trade filings signed by an authorized signatory
  • Staffing and payroll: employer filings signed by the signatory on record
  • Real estate and infrastructure: tender submissions that need a certificate-based signature

What this service does

  • What a certificate check shows

    When you check a certificate, the response can carry the holder name and the organization recorded against it. It can also carry the validity period, the certificate type and the status where that is published. Which fields you see can vary with the data source and with the certificate itself.

  • A signature tied to a named person

    The certificate belongs to an identified individual. Where a company signs, it belongs to a director, company secretary or other authorized signatory acting for it. That is the assurance statutory filings and corporate counterparties ask for.

  • The signing key stays on the token

    The key works only when the holder connects the token and enters the PIN. Custody stays with the signatory instead of moving into a shared system or a vendor process.

  • One certificate, many documents

    A certificate that runs for a period supports repeated signing by the same role holder. That suits filings, tenders and contract sets that recur.

How a check runs

  1. Freeze the final document

    Your application assembles the document and locks it. Nothing then changes between the signature and the filing.

  2. Hand it to the signatory

    The named authorized signatory connects the token holding their certificate and authorizes the signing with their PIN.

  3. Sign with the certificate on the token

    The certificate on the token applies the signature to the document, and your application receives the signed file.

  4. Read the certificate behind the signature

    You can retrieve and record the certificate details available: the holder, the organization recorded against it, the validity period and the status where it is published.

  5. Store the signed file

    Keep the signed document with the certificate details you relied on, against the filing, matter or counterparty record it belongs to.

Questions

What is a Digital Signature Certificate?
A certificate issued to a named person once their identity has been checked. It lives on a hardware cryptographic token, and that person uses it to sign documents electronically. It runs for a fixed period and can carry an organization name where the holder signs as a role holder of a business.
How does DSC signing fit into an automated workflow?
Your application finalizes the document, and the signatory signs it with the certificate on their token. The signed file and the certificate details behind it are recorded in the same workflow. The signing itself still needs the holder and their token. What the integration removes is the retyping, the emailing and the lost trail.
Who can hold a Digital Signature Certificate?
A named individual. Where a company signs, a director, a company secretary or another authorized signatory holds the certificate for it, and the organization can be recorded against the certificate. The certificate is personal to the holder: keep the token and the PIN unshared.
When do I need a DSC instead of an Aadhaar eSign?
Use a DSC when a named signatory signs repeatedly in a defined role and holds a certificate on a token for a fixed validity period. Aadhaar eSign checks who the signer is as they sign and needs no token, which suits customers who sign once. Both are covered in this catalog on their own pages.
Can I check a DSC before accepting a signed document?
Yes, as far as the certificate publishes it: who holds it, the organization named on it, how long it runs and whether it is still good. Record what you relied on at the time, because a certificate that is valid today may have expired by the time somebody reviews the document again.
Can I sign documents in bulk under an organization certificate?
Arrangements exist for signing high volumes of documents, such as invoices and statements, under a certificate held by the organization rather than by an individual. Whether that is open to you depends on how it is set up and on your service contract.

Catalog entry last updated .