A DSC is not your signature. It is your ability to sign.

Not a signature

The misunderstanding is built into the name, so it is worth taking apart before anything else.

A signature is an act. You perform it, it happens in a moment, and nobody can perform it for you without forging it — and forgery is detectable, because the act leaves traces of whoever actually performed it.

A digital signature certificate is not an act. It is a thing, and the thing is your capacity to produce a valid signature.

Everything in the rest of this page follows from that sentence, including the parts that sound like security advice and the parts that sound like business advice. It is one idea.

What it actually is

Stated without technical detail, because the technical detail does not help anybody make a decision and goes out of date.

A certifying authority checks who you are. Having satisfied itself, it issues a certificate that says, in effect: signatures produced with this belong to this named person. The means of producing those signatures is then placed inside a small device, and the device is given to you.

• The certificate is the statement of identity. It names you and carries the details that were checked.
• The device holds the means of signing. It is designed so that what is inside cannot be copied out.
• The PIN is what lets the device be used.

Three parts, and notice what the arrangement is designed to guarantee and what it is not. It is designed to guarantee that a signature came from this certificate. It is not designed to establish, and cannot establish, which human being operated it.

Possession is authority

So here is the question to put to every arrangement in your own setup, and it is the question this page sorts by:

Not "who is authorised". Not "who would I say is allowed to". Who could, today, if they chose. Because in this subject those are the same thing, and the gap between them is where everybody's comfortable assumptions live.

The indistinguishable test

This is the fact that changes people's minds, and it is worth stating three times in three ways because the first two do not land.

1. Nothing in the signed record shows who operated the token.
2. A filing made by somebody else holding your token and PIN is not hard to distinguish from one made by you. It is the same record.
3. There is no field for the operator, no log of the operator, and nothing for an expert to examine afterwards. The question cannot be answered from the record because the record never contained the answer.

Note what is not being claimed. This is not a reason to distrust your accountant, who is in all probability entirely reliable. It is a reason to understand that reliability is the only thing standing in the gap, and to decide knowingly rather than by default.

Who can use it right now

Go and answer it, now, about your own. It takes a minute and it is the only diagnostic on this page.

• Where is the device? Physically. If the answer is "with them, I think", that is the answer.
• Who knows the PIN? Count honestly, including anybody who has ever been told it and anybody who has watched it typed.
• Is anybody on that list no longer in your life? A previous firm, a departed employee, a former partner.
• When was it last used, and for what? If you do not know, that is not a small gap; it is the whole gap.

Almost everybody who does this exercise finds one item they had not thought about, and it is nearly always the third one.

The handed-over token

Now the practice everybody follows, named plainly and without disapproval, because disapproval is useless here.

You gave the token and the PIN to your accountant, your company secretary, or your consultant. It was not careless; it was practical. They do the filings, the filings need signing, you are not sitting next to them, and the deadline was that week. A very large share of routine compliance in this country runs exactly this way.

What you are consenting to

Said precisely, because the precision is the useful part. When you hand over the token and PIN, you are consenting to:

1. Anything signed in your name with it — not only the filing you asked for.
2. At any time — not only during the week you handed it over.
3. By whoever has it — not only the person you handed it to, since offices have staff and staff have desks.
4. Until you take it back or revoke it — and not when the engagement ends, or when you stop working with them, or when you assume it lapsed.

Read the fourth one twice, because it is the one that catches people. The arrangement does not expire when the relationship does. Nothing happens automatically.

If you do it anyway: four things

The honest second best. None of these prevents misuse; together they make the arrangement one you can live with.

The three situations in which people reliably do not revoke, and should: you changed consultants and the old firm still has it; a staff member who was a signatory has left; it cannot be accounted for and is being treated as mislaid rather than as unaccounted for.

The PIN is not the protection

Worth its own section because it is where almost everybody's comfort actually comes from, and it is misplaced.

Put another way: the PIN is protection against loss, not against use. And since no delegation is possible without handing over both — a token with no PIN is a paperweight — the PIN has, by design, already been surrendered in exactly the situation people are relying on it for.

The ten-second habit

The single most effective thing on this page, and it is much smaller than people expect.

Why it works where the four mitigations only help:

• It converts "somebody holds my ability to sign" into "somebody did a filing I watched".
• It costs almost nothing in convenience, including over a screen share, which is how most of this work happens anyway.
• It protects them too, which is the part people do not anticipate. A professional holding your signing ability is carrying a risk they did not price for, and most are relieved to put it down.

And the honest observation: a large share of people who say this is impossible have never put it to their accountant. It is worth one conversation before accepting that it cannot be done.

One more reason the habit is worth pressing for, and it is about how these arrangements decay rather than how they start. An arrangement where you keep the device has a natural check built into it: you see each filing go out, so you know roughly what is happening in your own compliance. An arrangement where somebody else keeps it tends, over a few years, to become an arrangement in which you have no idea what has been filed on your behalf at all — not through anybody's fault, simply because nothing ever prompted you to look. Then a notice arrives about something from two years ago and you are starting from nothing.

So the ten seconds buys two different things. It keeps the capacity with you, which is the security point. And it keeps you informed about your own affairs, which over a long period is probably the more useful of the two.

What cannot be undone

The structural fact that makes this subject different from everything else we write about documents.

Almost every documentary problem has a repair. A lost certificate is usually reissuable. A wrong affidavit can be redrafted. A mismatch can be explained. A missing paper can be applied for again.

Revocation is a door

Which is why the one lever you have needs to be understood for what it is.

Revocation tells the world that this certificate should no longer be relied on. It is genuinely valuable, it should be used immediately whenever control is in doubt, and it is cheap.

• What it does: stops further signing from the point it takes effect. Every day you delay is more that can be signed.
• What it does not do: reach back. Signatures already applied are not unmade by it.
• What it is not: an accusation, a dispute, or a step that needs justifying to anybody.

Compared with a paper original

Worth laying out side by side, because people arrive here with paper intuitions and the intuitions mislead in both directions.

If you have read our guide on physical custody of documents, this table is the deliberate contrast to it. There, the record is close to a complete answer. Here the record is only a way of finding out, and the answer is possession.

The name on the certificate

Now a change of subject, and from here the page becomes practical rather than cautionary.

The certificate does not merely enable signing. It asserts an identity — a named person, with the details that were verified. Which means it has to agree with something, and the thing it has to agree with is not your own sense of your name but whatever the system you are filing into already holds against you.

When it works and the filing fails

Producing the failure that confuses people more than any other in this subject, and that costs them money unnecessarily.

What is actually happening is a mismatch between the details on the certificate and the details the receiving system holds. The usual culprits are small and familiar:

• An initial expanded in one place and left as an initial in the other.
• A middle name present on one and absent on the other.
• A surname spelled two ways, often because two documents transliterated it differently.
• A name that was changed and updated in one record and not the other.
• A detail used as an identifier that does not match what is on the system.

The old problem of Indian documentation, arriving in a new costume. If you have a name mismatch across your own documents, it will follow you here.

The details that bind

So before any application, the question to answer is not "what is my name" but: what does the system I will file into already think my name is?

1. Find out what the receiving system holds — as it is recorded there, letter by letter, not as you believe it to be.
2. Have the certificate issued to match that, where the documents support it.
3. Where they cannot match, find out before applying what that system accepts by way of explanation, rather than discovering it at a deadline.
4. Keep a note of the exact spelling used, because you will need it again at renewal and you will not remember.

Getting it right the first time

Three small practices that prevent nearly all of the above.

• Decide on one canonical form of your name and use it consistently from now on in anything new. You cannot retrospectively fix everything; you can stop adding variants.
• Apply with the documents, not from memory. Read the name off the document you are submitting rather than typing what you call yourself.
• Check the issued certificate the day you get it, letter by letter, against what you asked for. A wrong detail is far cheaper to raise in week one than at the first filing.

One further note on the mismatch, because it has a second form that is harder to spot. Sometimes the certificate and the system agree perfectly and the problem is that you have two identities on the same system — an older record under a slightly different name and a newer one, both live, and the filing is being attempted against whichever the portal resolves to. No certificate will fix that. It is a cleanup job on the underlying records, and the only way to find it is to look at what the system holds rather than at the device in your hand.

Which is the general lesson of this half of the page. When a signing failure appears, look at the records before looking at the hardware. The device is the part that almost never fails, and it is the part everybody suspects first because it is the only part they can see.

Who needs one at all

The useful question is never "should I have a DSC". It is: which specific filing is asking me for one?

Because a certificate is not a general qualification or a mark of seriousness. It is a key to particular doors, and if you are not going through any of those doors you do not need a key.

The doors that commonly require one:

• Company and LLP filings. The most common reason by a wide margin — incorporation, annual filings, changes of officer and the like, where filings are signed by individuals in their capacity.
• Certain registrations. Several registration and licensing systems require a signed application rather than an uploaded form.
• Tenders and procurement. Where bids have to be signed and sometimes encrypted, and where the required type is usually specified.
• Some tax filings. Depending on who is filing and in what capacity.
• Intellectual property and various sectoral portals.

Who does not

Worth saying, because people buy these pre-emptively.

• A proprietor with no filings that require one. A great many small businesses never need one at all.
• Somebody who only needs to sign a document between private parties. That is a different subject with different tools — see e-sign assistance, which deals with electronic signing of ordinary documents and is not this.
• Somebody buying one "for the future". It has a validity period that starts running immediately, so an unused certificate is a subscription to nothing.
• A company, as such. See below — a company cannot hold one.

One per person, not per purpose

A common and avoidable waste: people end up with three certificates because three different consultants each arranged one.

A certificate identifies you. In most cases the same one serves across different filings and different systems. Where a second genuinely is needed, the reason is usually one of two things, and neither is "a different website":

1. A different type is required by a particular system — a higher assurance level, or one with a specific usage.
2. You sign in two genuinely different capacities and the system distinguishes them.

Which type, and who decides

There are different types, distinguished broadly by how rigorously the holder's identity was established and by what the certificate is intended to be used for. Higher assurance means a more thorough verification at issuance.

We are deliberately not reciting the current classes and their rules here, and the reason is practical rather than coy: which type a particular system requires is set by that system and changes, and a page that names them confidently is the way somebody ends up buying the wrong one with complete confidence, on a guide's authority.

• The rule that holds: the system you are filing into specifies what it will accept. Find that out first.
• The common upgrade: where a higher-assurance type is required — typically for tenders and for several statutory filings — that is class 3, and it is a different product rather than a premium version of the same one.
• The common error: buying the cheaper type and discovering at a deadline that the portal will not take it. The saving is small; the deadline is not.

Signing in a capacity

A distinction that causes real confusion and is simple once stated.

When you sign something for an organisation, two separate facts are in play:

1. That it was you — which is what the certificate establishes.
2. That you were entitled to sign for that organisation — which the certificate does not establish at all.

There is a practical consequence of the identity-not-authority distinction that catches people in the other direction too. Because a certificate says nothing about capacity, the same certificate can be used to sign in several capacities — for yourself personally, for a company you direct, for a firm you are a partner in. That is normally fine and it is how most people operate. But it means the certificate is not compartmentalised: the one device signs across all of your roles, and anybody holding it can sign in any of them. If you have one role you are relaxed about delegating and another you are not, the certificate does not know the difference, and handing it over for the first hands it over for the second as well.

A company has no DSC

Stated flatly because it is asked constantly in the form "how do I get a DSC for my company".

You do not. A certificate is issued to a person, after that person's identity is verified. A company is not a person who can stand in front of a camera. So filings for a company are signed by individuals — directors, designated partners, authorised signatories — using their own certificates.

Three practical consequences that follow directly:

• A departure is an operational event. When a signatory leaves, the company does not lose a certificate — a person outside the company keeps one that works. See below.
• You need enough signatories. One person holding the only usable certificate is a single point of failure when they travel, fall ill or resign.
• The company cannot "keep" anybody's token in any meaningful sense. It is somebody's personal signing ability sitting in a company drawer, and it remains theirs.

Ordering one

What to settle before the application, in this order, because each answer determines the next.

1. Which filing requires it, and what that system says it will accept.
2. Which type, accordingly.
3. In whose name — the individual who will actually sign, not the business.
4. With what details, matched to what the receiving system already holds. This is the step people skip.
5. For what period, within what the rules allow, and diarised the day it is issued.
6. Who will hold the device. Decided deliberately, having read the first half of this page.

What issuance involves

Described in general shape rather than in steps, because the steps and the acceptable documents are set by the issuing authority and are revised.

• An application with your identity and address details, and supporting documents.
• A verification step in which you are actually checked — typically including something live, because establishing that the certificate belongs to the person it names is the entire point of the exercise.
• Issuance onto a device, which is then yours.

The verification step

Two honest things about it, one reassuring and one not.

The reassuring one. It is supposed to be slightly inconvenient. The verification is the only reason anybody downstream trusts the certificate at all, and a process that verified nothing would produce a certificate worth nothing. The fifteen minutes is the product.

The other one. It is also the moment at which you should be most alert to who is arranging things for you.

The token itself

Prosaic but worth a paragraph, because it is the physical object the whole subject depends on.

• Keep it somewhere you can account for, and not plugged permanently into a shared machine, which is the practical equivalent of leaving it with whoever uses that machine.
• Do not write the PIN on it or beside it. The sentence is obvious and the practice is very common.
• Know how many you have. People accumulate them — an old expired one, one from a previous company, one arranged by a consultant. Expired ones are harmless; live ones you have forgotten about are not.
• Label them, with the name and the period, so that "which of these three is current" is not a question you answer by trial at a deadline.

Why it is not a file you can copy

Because people ask, usually while asking whether the inconvenience is necessary.

A file can be copied, and a copy of a signing ability is a second person able to sign as you, with nothing in any record to indicate which copy was used. The device exists so that there is one of it, and so that the one can be in a known place.

If it is lost

One instruction, and the unusual thing about this decision is how easy it is.

Revoke it. A token you cannot account for is a signing ability in a place you cannot see, with only the PIN between it and use. Then obtain a fresh one.

• Cost of revoking unnecessarily: a replacement certificate, and some inconvenience.
• Cost of not revoking when you should have: open-ended, and not reversible.
• Do not spend three weeks treating it as mislaid. That interval is the whole exposure, and it is the thing everybody does.

If it is stolen

The same first step, faster, and then it stops being our subject.

1. Revoke immediately. Before working out what happened, before telling anybody, before deciding whose fault it was.
2. Then take advice. Theft of a signing ability, and anything done with it, is an advocate's matter and may be a police one. What has been signed in your name is a question about your position and your liability, and nobody should be guessing at it, including us.
3. Establish what was filed and when — which is documentation work and which we can help with. What it means is not.

The first hour

The short version, for anybody reading this because something has already gone wrong.

Note what is not on the list: confronting anybody. That may well be necessary and it is not step one, and doing it first routinely costs people the first two steps.

Validity and renewal

You choose a period at issuance, within the limits the rules allow, and it expires at the end of it. We are not printing a number, because the permitted periods are set by the rules and have been revised.

Two practical points that matter more than the number:

• Diarise the expiry the day you receive it, with a reminder well before — not a week before.
• Note the exact name and details used, in the same place. At renewal you will need them to match, and you will not remember which spelling was used.

Renewal is not repair

The misconception that produces the most avoidable emergencies in this subject.

So the rule: renew with weeks in hand, not days. And use the occasion for the two things that only happen at renewal if they happen at all — checking the details still match the receiving system, and reconsidering who is going to hold the device.

Expiring mid-filing

A specific and miserable situation worth anticipating.

A filing is prepared, the deadline is near, and the certificate expires between preparation and signing — or expires with the filing part-completed. There is no clever recovery. The certificate cannot be used, a fresh issuance takes its own time, and the deadline does not move for any of it.

• Before any deadline season, check the expiry of every certificate you will need. Not the one you are thinking about — every one.
• Where more than one person can sign, check all of theirs too. A company with three signatories has three expiry dates and usually knows one.
• If it is already close, renew first and file second, even though that feels like the wrong order.

Signatures already made

A question people worry about unnecessarily, and the answer has a reassuring half and an unreassuring one.

The reassuring half. Expiry means you can no longer sign with it. It is not an erasure. Things validly signed while it was live do not evaporate because the certificate later lapsed, and you do not have to re-sign your history every few years.

The unreassuring half is the same fact seen from the other side, and it is the thesis of this page returning at the end: a signature applied by somebody else in your name does not evaporate either. Neither expiry nor revocation reaches it. That is why the page spends its first half on possession and its second half on housekeeping, in that order.

The employee who left

The most common serious exposure we see in small companies, and it is almost always an oversight rather than a dispute.

Somebody was made a director or an authorised signatory. They obtained a certificate in their own name for that purpose. They have now left — amicably, with a handover, on good terms — and the certificate is still live and still theirs.

And the practical note: do it during the handover, when goodwill is highest and everybody is being helpful, rather than three months later when it has become a phone call nobody wants to make.

The consultant you changed

The second most common, and the one people are most reluctant about because it feels like an insinuation.

It is not. A token sitting in a firm you no longer work with is not a comment on that firm. It is a live ability to sign as you, in a drawer belonging to people who have no current reason to think about you at all — which is exactly the condition in which things get mislaid, reused by a junior who does not know the engagement ended, or simply forgotten.

1. Ask for it back, as a routine closing item alongside the files.
2. Whether or not you get it back, revoke it and obtain a fresh one. This is the part people skip when the token is returned, and it is still worth doing — you cannot know who held it meanwhile.
3. Do not frame it as a concern. "We are closing things off at our end" is both true and sufficient.

When relations break down

And the situation where all of the above becomes urgent rather than tidy: a partner, a co-director, a family member or a former associate with whom things have gone wrong, who holds a certificate in your name or a certificate that signs for your company.

After that it is not our subject. Who may sign for an entity in dispute, what happens to filings already made, and what can be done about them, is work for an advocate — and the honest advice is to get there in the first week rather than the second month. What we can do is establish, from the records, what was filed and when, which is the factual groundwork anybody advising you will want.

A related situation that is worth naming because it is genuinely common in family businesses and is nobody's fault: a certificate obtained in the name of a person who is not really running anything. An elderly parent made a director for structural reasons, a spouse added as a partner, a sibling who signed once years ago. The certificate is in their name, the token is in the firm's drawer, and the person named has no idea what is being signed with it or when.

That arrangement is not illegitimate and we are not going to pretend it is unusual. But the exposure is theirs rather than the firm's, which is the part nobody has told them, and two things are worth doing. Tell them what the thing is — in the terms at the top of this page, not as a technicality. And keep a use record for their certificate in particular, because they are the one person in the arrangement who has no way of knowing and the most to be surprised by.

The use record

A small habit, recommended with its limitations stated plainly, because overselling it would undo the point of the page.

Keep a short note of each use. One line, like any other record we recommend:

• What was signed, in ordinary words.
• When.
• Who asked for it.
• Who actually operated the token — the field nobody records and the only one that is not in the signed record either.

What a record can and cannot do

Stated honestly, because this is where the contrast with paper has to be held to.

Things people get wrong

Collected, in the order we hear them.

• "The PIN protects me." Against a thief, yes. Against the person you gave it to, not at all.
• "The system must log who used it." It does not. There is no such field.
• "I can get the filing reversed." Not administratively, and not technically. Whatever remedy exists is legal.
• "The engagement ended, so the arrangement ended." Nothing ends automatically. Only revocation ends it.
• "My company has a DSC." It does not. People do.
• "Revoking is an accusation." It is housekeeping, and it costs very little.
• "The device is faulty." Usually a details mismatch, and a second certificate will fail the same way.
• "I need one for each portal." Usually one per person. Ask which system refuses the one you have.
• "Renewal is a button." It is a fresh issuance with verification again.
• "I will sort the lost token out next week." That interval is the exposure.

Who orders this from us

Four situations, in the order we hear them.

1. "A portal is asking for a DSC and I do not know what to get." The ordinary case, and the work is mostly the type and the details.
2. "My filing keeps getting rejected and I have already bought two certificates." Almost always the mismatch, and a short conversation rather than a third purchase.
3. "Our signatory has left / we have changed consultants." Revocation and a fresh issuance, plus a plain explanation of the second step that is not ours.
4. "Somebody has been signing in my name." We will help establish what was filed and when, and then tell you that the rest is an advocate's.

What we need

Short, and asked in this order because each answer changes the next.

• Which filing or portal is requiring it, and what exactly it says it needs.
• In whose name — the individual, and in what capacity if that matters.
• The identity and address documents for that person.
• ★ What the receiving system already holds as that person's name and details, letter by letter. This is the step that decides whether the certificate will actually work.
• Whether a certificate already exists in that name, live or expired, and where it is.
• Who will hold the device, and whether you have read the first half of this page.

What we do and do not touch

The service, described as what it actually is: getting it issued, correctly, into your own hands.

And once it is issued, it is yours and it stays yours. There is no ongoing arrangement in which we keep anything of yours, because there is nothing of yours we should be keeping.

What we will never hold

The refusal, stated last because it is the one that costs us work, and it will be a disappointment to some people reading this.

The reason, and it is the whole page compressed:

• What we would be holding is not a document of yours. It is your ability to act, and no service should have that.
• Nothing in the record would ever distinguish our use of it from yours, which means neither of us could ever establish what happened — a position that is bad for you and bad for us.
• And unlike almost every other mistake in documentation work, there would be no repair available if it went wrong.

We know this is the most ordinary request in this market, and that saying no to it loses work to people who say yes. We would rather tell you here, before you order, than be the firm that held your signing ability for three years and then had a difficult conversation with you about a filing.

Our fee on this

Our part for a digital signature certificate — establishing whether you need one and of which type, matching the name and details to the system you will actually file into, preparing the application, taking you through the verification, and getting it issued onto a device handed to you — is ₹1,299, with a turnaround of 1 – 2 days.

What is separate:

• A higher-assurance type where a portal requires it — class 3.
• The certifying authority's own charges and the cost of the device, which are not ours and which we will state before you commit rather than after.
• Any filing you then make, which is its own work — director KYC, a return, a registration, an import-export code, a procurement registration, a trademark, an LLP, a startup registration.
• Correcting a name or detail at source, where it has to be fixed before the certificate can usefully be issued.
• Electronic signing of ordinary documents, which is a different subject altogether — e-sign assistance.
• An advocate's fee, wherever something has been signed in your name, or a signatory is in dispute.

And the honest framing. Most of the value here is in twenty minutes nobody charges separately for — deciding whether you need one at all, which type, and making the details agree with the receiving system before anything is applied for. The ordering itself is straightforward and plenty of people sell it. If you already know which type you need, your details already match, and you are clear that the device stays with you, then this is a simple purchase and you do not need us for the thinking part. We will say so.

Court work is for your advocate, whose fee is engaged and paid by you directly; we do not quote, collect or share it.

The filings a certificate signs are only the output. What has to sit behind them — and why those records cannot be written up later — is in statutory registers and minutes — the day somebody asks.

One expiry that catches people mid-closure: the certificate needed to sign the filings. Why that matters, and what else must be true before a company can be closed, is in company strike off — a company you stopped using has not stopped existing.

Questions people actually ask