USB DSC Token vs Cloud Signing: Which Should Your Business Use?
Gaurav Singhal
View LinkedInMost Indian businesses already own at least one USB DSC token. It lives in a drawer, gets plugged in when someone needs to sign something, and somehow always belongs to the one person who is on leave that day.
For an occasional signature, that is fine. For routine business documents signed every week or every day, the token becomes the bottleneck. This post compares the USB token with cloud signing using an organisation's document signer certificate, and explains when each one makes sense.
Key takeaways
- A USB DSC token keeps a certificate on a hardware device. Signing happens on the computer it is plugged into, one document at a time.
- Cloud signing uses an organisation's document signer certificate (a
.pfxfile) held by a signing service, so an authorised team can sign from a browser or from software.- Tokens tie signing to one person, one machine and a stack of drivers and plugins. Cloud signing removes that setup.
- Security comes from controls: who can sign, how the certificate is stored and what gets logged.
- Many businesses keep the token for personal signing and move routine, high-volume documents to cloud signing.
How each option works
The USB DSC token
A USB token is a small hardware device that stores a certificate and its private key. The key is designed never to leave the device. To sign, you plug the token in, install the vendor's driver, open a signing tool, pick the document and type the token PIN. The token does the signing inside the device and hands back the signature.
That design is the token's main strength. Someone has to physically hold the device and know the PIN, which makes it a good fit for signing that is tied to a specific person.
It is also the token's main weakness. Signing only happens where the token is plugged in. Every machine needs the right driver, and many signing tools also need a Java runtime or a browser extension that has to be kept compatible with the operating system and browser. The token travels with its owner, and documents are usually signed one at a time.
Cloud signing with a document signer certificate
Cloud signing uses a certificate issued to the organisation rather than to an individual. A document signer certificate is typically delivered as a .pfx file, which bundles the certificate and its private key, protected by a password. It is issued through a licensed certifying authority or its partners.
Instead of sitting in a drawer, the .pfx file is uploaded once to a signing service. Authorised users then sign documents from a browser, and software can request signatures directly. There is no token to plug in, no driver to install and no plugin to keep updated.
The signed PDF looks the same to the person who opens it. The reader can check who signed the document and confirm it has not been changed since it was signed. If you want the background on these certificates, read What Is a Document Signer Certificate?.
Side-by-side comparison
| USB DSC token | Cloud signing (.pfx) | |
|---|---|---|
| Issued to | Usually an individual | The organisation |
| Where signing happens | The machine the token is plugged into | A browser or your own software |
| Setup per machine | Driver, signing tool, often Java or a browser plugin | None beyond a browser |
| Who can sign | Whoever holds the token and PIN | Users you authorise |
| Volume | One document at a time in most tools | Batches of documents |
| Signing from software | Hard; needs the token attached to a machine | Built for it, through an API |
| Dependence on one person | High | Low |
Where the token slows teams down
The problems with tokens rarely show up on day one. They show up when signing becomes routine.
One person, one desk. If the token belongs to a director or a finance head, every signature waits for them. When they travel or are on leave, documents queue up or someone couriers the token around, which defeats the point of a hardware device.
Driver and plugin breakage. An operating system update, a new browser version or a new laptop can stop the token working until someone reinstalls the right driver or plugin. When it happens on billing day, signing stops.
One document at a time. Say your team issues 300 invoices at month end and each takes about a minute to open, sign with the PIN and save. That is five hours of someone's time, every month, spent clicking. The example is illustrative, but the shape of the problem is familiar to anyone who has done it.
No path to automation. If you want your own product or workflow to sign PDFs as it creates them, a token plugged into one machine is awkward to build around. This is why most signing APIs work with a stored certificate rather than a token. We cover this in more detail in Why Is Digitally Signing a PDF Still So Hard?.
What about security in the cloud?
The fair question is whether moving a certificate off a hardware device makes it less safe. The honest answer is that it depends on the controls around it, not on where the file sits.
A token protects the key physically, but it is also easy to share: a PIN written on a sticky note next to the token is a common sight. A cloud signing service should give you:
- Protected storage for the certificate, encrypted rather than sitting as a plain file on a shared drive.
- Access control, so only the people you choose can sign.
- A record of what was signed, by whom and when.
- Password handling that does not require the certificate password to be emailed around or saved in a spreadsheet.
When you compare options, ask each provider how they handle these four things. Clear answers matter more than whether the word "cloud" appears in the pitch.
Which should you use?
Use a USB token when signing is personal and occasional, and the signature needs to be tied to a named individual who will be present to sign.
Use cloud signing with a document signer certificate when documents are routine, signed in volume, signed on behalf of the organisation, or created by software. Invoices, credit and debit notes, statements and other business documents that go out in batches usually fall here.
Many businesses end up using both: the token for the occasional personal signature, and a document signer certificate for everything that goes out in volume. Which documents need which kind of signature depends on your situation. Check with your advisor on what your documents require.
How Ambill Sign approaches cloud signing
We built Ambill Sign because signing even a small PDF was harder than it should be, and the alternatives came with complex, expensive pricing: per-signature or per-envelope fees, annual minimums, setup fees and sales-led contracts. That puts digital signing out of reach for routine documents.
Ambill Sign applies your organisation's own document signer certificate to PDFs, with simple pricing and no per-signature fees.
- Live today: inside Ambill, finance teams bulk-sign the invoices and credit or debit notes they generate. The certificate is uploaded once, and invoices are signed in batches with one password entry. PumPumPum, Kazam and Workie already use it to sign their invoices.
- Coming soon: uploading and signing any PDF, and a developer-first signing API so your own product or workflow can sign PDFs with your certificate. Both are in early access.
If signing at volume is the problem, see How to Digitally Sign PDFs in Bulk Without a USB Token.
Get started
If your team is still passing a token around to sign routine documents, we would like to hear from you.
Building signing into your own software? Request API early access
FAQ
Can I turn my USB token certificate into a .pfx file?
Usually not. Tokens are designed so the private key cannot be exported, which is part of what makes them secure. For cloud signing, organisations typically obtain a separate document signer certificate delivered as a .pfx file.
Is a .pfx file less secure than a USB token?
Not inherently. A .pfx file is password protected, and its safety depends on where it is stored and who can use it. Kept in a signing service with encryption, access control and a record of signatures, it can be better controlled than a token that is shared between people.
Do I need to give up my USB token?
No. Many businesses keep their token for personal signing and use a document signer certificate for routine documents signed on behalf of the organisation.
Does Ambill Sign work with USB tokens?
No. Ambill Sign works with a document signer certificate in .pfx format, which is what makes browser-based and batch signing possible without drivers or plugins.
Which documents should be signed with which certificate?
That depends on your business and the document. Check with your advisor on what your documents require.