What is an eStamp?
An eStamp is stamp duty paid electronically for an instrument, with a certificate issued digitally in place of physical stamp paper or a franking impression. The certificate carries its own number, and that number lets a counterparty, a court or an auditor check the stamping later.
Stamp duty in India is a state subject. What you pay, how it is computed and how you may pay it depend on the state and on the type of instrument.
Some states do not offer electronic stamping for every instrument. Treat the state as an input to your workflow.
How an eStamp API works
An eStamp API lets your application ask for an instrument to be stamped and get the certificate back. The step then sits inside the document workflow instead of interrupting it. For a business producing agreements all the time, such as a lender, a leasing company or a platform onboarding partners, that removes a trip to the stamp vendor.
The step it replaces is usually the slowest one in an otherwise digital process. Documents get drafted and signed in a system, then stop while somebody buys paper.
What goes into a stamping request
A stamping request describes the instrument. You supply the governing state, the kind of instrument, the amount duty is computed against, the parties and which of them pays. Settle those details before you submit, because they decide the treatment.
Whether a given instrument in a given state can be stamped this way depends on the data source behind it and on your service contract. The same goes for what the certificate carries. The attributes you get vary by state and by record.
Where eStamping is used
- Lending and NBFC: stamp loan, hypothecation and security documents for the right state before execution, at book volume.
- Real estate: stamp leave and license agreements, leases and allotment documents, where duty varies sharply between states.
- Fintech and PSP: stamp merchant and service agreements at onboarding, without waiting on paperwork bought at a counter.
- Logistics and fleet: stamp vehicle lease and transporter agreements across a network operating in several states.
- Marketplaces: stamp franchise, seller and channel agreements inside a repeatable onboarding pack.
- Staffing: stamp the agreements and undertakings that require it under the applicable state law.
Stamping, signing and registration in order
Stamping, signing and registration are three separate steps, and the order matters. Duty is paid on the instrument before the parties execute it, and registration, where it applies, comes last. Keep the certificate reference with the executed document, and reconcile the stamping details against the final instrument before signing.
A stamping request does not always resolve in one step. Build the workflow to start the request and then follow it. Hold the request reference, track the state it is in, and move the document on only once you have the certificate.
Decide early what happens when an instrument is abandoned after stamping. Some states let an unused certificate be canceled or refunded within conditions. Have that process ready.
Deciding the duty and handling party data
Getting the duty right is a legal judgment. Decide who inside your business owns that call for each instrument type and each state.
Keep a note of the basis they used, and revisit it when a state changes its rules. A workflow that quietly hardcodes one state's treatment keeps producing documents that look finished and are not.
A stamping request carries party details and handles personal data. Collect only the party information the instrument requires, get the parties' consent to use it for stamping that instrument, and restrict who can submit and retrieve a request.
Hold the request and the certificate under retention rules you can defend. Where a party's identity documents go into the instrument, handle them with the same consent and authorized-use care as any other identity data.