- BFSIBanking, Financial Services & Insurance
- HealthcareComing soon
- ManufacturingComing soon
- Retail & E-CommerceComing soon
Digital Contracting
Ninety seconds to verify. Three days to sign — Verified in ninety seconds, then three days for a stamped agreement — Signzy closes the step that stays manual after everything else in the journey is digital.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
The Signzy API family
This page covers Digital Contracting — stamping and signature. The rest of the marketplace:
Quick facts
30-second orientation- Product
- Digital Contracting — stamp, sign, execute
- Inside it
- Contract 360, eStamping, Aadhaar eSign
- The gap it fills
- The last manual step in a digital journey
- Why India is hard
- Stamp duty is a state subject, rates differ
- The stake
- Wrong duty makes an agreement unenforceable
- Legal basis
- Aadhaar eSign under the IT Act
- Pricing
- Quote-only — typically per document
- In India via
- TechBag — INR/GST, scoping and support
Understand digital contracting before you buy it
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
What is Signzy Digital Contracting?
Stamp, sign and execute, inside the same journey — Contract 360 for the document lifecycle, eStamping for state-correct duty, and Aadhaar eSign for a legally valid signature.
A scanned signature vs an executed agreement — the honest table
What consolidation actually replaces, dimension by dimension.
| Dimension | A scanned signature on a PDF | Digital Contracting (Signzy) |
|---|---|---|
| The last step | Three days, manual | Minutes, in the same journey |
| Stamp duty | Legal review per state | Computed for the state and instrument |
| The signature | A scanned image on a PDF | Aadhaar eSign, valid under the IT Act |
| Multi-party | Email chains and reminders | Sequenced routing with status |
| If disputed | Prove who signed, somehow | An execution record with the duty paid |
| What it is NOT | — | Not your counsel — it executes, not drafts |
It EXECUTES agreements; your counsel drafts them and characterises each instrument. An instrument categorised wrongly gets stamped correctly for the wrong category, which protects you no better than not stamping it.
The five pieces of the platform
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
eStamping
Stamp duty in India is levied by states, each with its own rates, instruments and procedures. Paying the wrong amount or under the wrong state's rules affects whether the agreement can be enforced, not merely whether it looks tidy.
Aadhaar eSign
An electronic signature backed by Aadhaar authentication, carrying validity under the IT Act. The signatory authenticates with an OTP against their Aadhaar record and the signature is affixed with an audit trail.
Contract 360
Templates, generation, routing for signature, and storage of the executed agreement. The unglamorous part, and the reason the whole step often takes days even when the signature itself takes seconds.
The audit trail
Who signed, when, authenticated how, with what duty paid. This becomes the record if the agreement is ever disputed, and it is the reason a scanned signature on an emailed PDF is a weaker position than it feels.
One telemetry fabric across endpoint, cloud, and network — threats correlated once, not chased console to console.
Six capabilities. Generate, stamp, sign.
Signzy Digital Contracting stamps, signs and executes — state-correct duty and the portfolio, and paired with the human firewall.
State-correct stamp duty
Duty computed and paid according to the relevant state's rates and instrument type. The part that decides enforceability, and the part most teams underestimate entirely.
Legally valid, in seconds
OTP authentication against the signatory's Aadhaar record, with the signature affixed and an audit trail recorded. Valid under the IT Act rather than merely convenient.
Templates to executed copy
Generating the document, routing it for signature and storing the executed version. This lifecycle work is why the step takes days even when signing takes seconds.
More than one signatory
Sequencing signatures across parties, with reminders and status visible. Two-party agreements are simple; a guarantor or co-applicant is where manual processes usually collapse.
The evidence if disputed
Who signed, when, authenticated how, and what duty was paid. If an agreement is ever challenged, this record is the position you argue from.
The signatory already verified
Because contracting sits on the same marketplace as onboarding, the person signing has already been identity-verified rather than authenticated again from scratch.
A journey is only as fast as its slowest step.
Here’s what genuinely sets it apart — and exactly where it stops.
The last manual step, and the one nobody budgets
Digital onboarding programmes follow a predictable arc. Identity verification is digitised, the team celebrates a ninety-second journey, and then the customer waits three days for a stamped and signed agreement produced by a process nobody modernised. The contracting step is consistently the last thing funded and consistently the one that determines the customer's actual experience of speed, because the journey is only as fast as its slowest part. Scoping eStamping and eSign at the same time as verification rather than as a phase two is the single most useful piece of sequencing advice on this page — phase two frequently does not get funded, and a fast verification feeding a slow agreement produces a worse impression than a uniformly moderate process.
eStamping is harder than it looks because India is federal
Stamp duty is levied by state governments, not centrally. Each state sets its own rates, recognises its own instrument categories and runs its own payment procedures, and the applicable state depends on where the instrument is executed and where the property or transaction sits. This is genuinely complicated, and it is not paperwork pedantry: an agreement that is insufficiently stamped can be inadmissible as evidence, which means the document you are relying on may not help you in the situation you drafted it for. That makes correct duty computation a legal question wearing an operational disguise. When evaluating, ask which states are covered, how rate changes are tracked, and what happens when a rate moves mid-flow.
Aadhaar eSign is a legal instrument, not a convenience feature
A scanned signature pasted onto an emailed PDF feels like a signed agreement and is a considerably weaker evidentiary position than it appears — proving who applied it, when, and with what intent is difficult after the fact. Aadhaar eSign authenticates the signatory against their Aadhaar record via OTP and affixes a signature carrying validity under the IT Act, with an audit trail recording the authentication. The practical difference only becomes visible when an agreement is disputed, which is precisely when you cannot fix it retrospectively. For agreements that matter — loan documents, guarantees, anything you might need to enforce — the distinction between a legally recognised signature and a convenient image is worth the integration effort by itself.
What it does not decide for you
Two boundaries. First, the platform executes documents; it does not draft them or tell you what duty applies to an instrument you have designed unusually. Template design, clause content and the legal characterisation of your agreements remain your counsel's work, and an incorrectly characterised instrument will be stamped correctly for the wrong category. Second, coverage is a question rather than an assumption: ask which states are supported for eStamping, how rate changes are tracked, and what the fallback is when a state's system is unavailable, because that outage becomes your customer's delay. Neither point diminishes the capability — they are simply the questions that separate a smooth deployment from one that discovers its gaps in production.
The numbers behind the platform
What your contracting rollout looks like
Scope it with verification, not after
Contracting is funded last and felt first. A phase two that never gets funded leaves a fast verification feeding a three-day wait.
List your instruments and states
Which agreement types, executed where. Duty depends on both, and the answer determines what coverage you actually need.
Have counsel confirm characterisation
The platform stamps correctly for the category you declare. An instrument characterised wrongly gets stamped correctly for the wrong thing.
Ask about coverage and fallbacks
Which states, how rate changes are tracked, and what happens when a state portal is unavailable — that outage becomes your customer's delay.
Wire it into the journey
Verified customer straight to executed agreement, without re-authenticating a person you already verified minutes earlier.
Keep the execution records
Who signed, when, authenticated how, duty paid. It is the position you argue from if an agreement is ever challenged.
The review scoreboard
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
Quick poll — what’s driving your evaluation?
Talk to an advisor“We digitised verification and left contracting for phase two. Phase two took a year, and customers experienced our fast onboarding as a three-day wait the whole time.”
“eStamping across states was the reason we bought. Doing it correctly per state was consuming legal review time we could not keep spending.”
“Ask about state coverage explicitly and what happens when a state portal is down. That outage becomes your customer's delay and you should know the fallback.”
“Aadhaar eSign changed our recovery position more than our speed. A properly executed agreement is a different conversation when something goes wrong.”
Where everyone sits — the grids
Analyst firms bury this view behind paywalls, and G2 retired its Grid. So here’s TechBag’s synthesis of the digital contracting market — tap any vendor to see why it sits where it does.
TechBag Digital Contracting Grid
Execution strength vs product vision — the classic market map, minus the paywall.
eStamping plus Aadhaar eSign, India-native.
Detection × Portfolio Integration
The grid nobody publishes — fit with Indian stamping and signature law vs how well it joins the wider journey.
State-aware duty on one contract.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Digital Contracting vs the alternatives
Against a global eSign vendor, manual stamp and sign, and a scanned PDF signature — on Indian duty, legal standing and speed.
| Dimension | Signzy Contracting | A global eSign vendor | Manual stamp and sign | Scanned PDF signature |
|---|---|---|---|---|
| India eStamping | State-aware | Usually not | Correct, slowly | Skipped |
| Aadhaar eSign | Native | Sometimes | Wet signature | No |
| Evidentiary position | Strong | Strong | Strong | Weak |
| Speed to executed | Minutes | Minutes | Days | Minutes |
| Identity already verified | Same contract | Separate | In person | No |
| Published pricing | Quote-only | Often published | Staff + duty | Free |
Which cybersecurity approach fits you?
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Choose Signzy Digital Contracting if…
- ✓Indian stamp duty across states is consuming legal review time
- ✓Your fast onboarding still ends in a three-day wait for an agreement
- ✓Agreements you may need to enforce are being signed as scanned images
- ✓Onboarding already runs here, so the signatory is already identity-verified
A global eSign vendor may fit if…
- ✓Your agreements are international and Indian stamp duty is not in scope
- ✓You already have an eStamping process that works and only need signatures
- ✓Published per-envelope pricing matters more than India-specific handling
Do not expect…
- ✓It to draft your agreements or characterise an unusual instrument for duty
- ✓Every state to be covered identically — ask which, and how rate changes are tracked
- ✓The advantage of pre-verified signatories unless you buy the onboarding line too
What does the last manual step cost you?
Drag the sliders (agreements executed monthly; cost of a day's delay). Estimates model the wait between verification and execution, plus legal review time spent on per-state stamp duty. Illustrative.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Three ways to consume it
Quote-only — Signzy publishes no price. TechBag scopes the billing unit and confirms the stamp duty is passed through as its own line, then quotes in INR with GST.
Digital Contracting
Best when agreements still take days
- State-correct eStamping
- Aadhaar eSign, valid under the IT Act
- Execution records that survive dispute
+ Platform add-ons
Best for a broader rollout
- Scoped to your estate
- Add-on modules as needed
- Phased, right-sized deployment
+ the wider marketplace
Best across the journey
- Signatory already identity-verified
- Verification straight through to executed
- One contract, not a separate integration
Buy it for less — TechBag pricing beats list
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Get an India-ready quote
Tell us your requirements and current tools — we’ll model it against what you spend today.
The 8 questions to ask every vendor
Take this into your next vendor call — including ours.
Is contracting scoped alongside verification, or parked in a phase two that may never be funded?
Which agreement types do you execute, and in which states? Duty depends on both.
Has counsel confirmed how each instrument is categorised? Correct stamping of a wrong category is still wrong.
Which states are supported for eStamping, and how are rate changes tracked when a state revises them?
What happens when a state portal is unavailable? That outage becomes your customer's delay.
Are agreements you may need to enforce currently signed as scanned images? That is a weaker position than it feels.
Do any agreements need a guarantor or co-applicant? That is where manual routing usually collapses.
Is billing per document, per signature or per envelope, and is the duty itself passed through separately?
Questions buyers ask
Ready to evaluate Signzy Digital Contracting?
Scope this alongside verification rather than as a phase two — phase two often does not get funded — or let a TechBag advisor confirm state coverage and the fallback when a portal is down.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.