Solutions: verification and e-Stamp workflows by industry
Each solution page starts from a real operating problem, such as onboarding a borrower, paying a seller or stamping a renewal, and shows which StampMitra APIs answer it, what each response should decide, and what the flow costs.
The verification APIs check identifiers against registry and bank sources: PAN, GSTIN, CIN, Udyam, vehicle registration, driving licence, voter ID, passport file and bank accounts. The e-Stamp APIs calculate duty, create orders and return the issued certificate. Industries combine them differently, so the pages below are organised by the job a team has to do rather than by endpoint.
Every page has the same ingredients, because they are what a team needs before it ships: the workflow in order, a real request and response, a decision table for valid, mismatched, inactive and not-found results, review rules written as suggestions, what to store, a cost model worked from the published rate card, and a path from sandbox to production. The structure of each page follows its industry, so read the one closest to your problem and then follow its links.
Lending and fintech
Borrower and business onboarding where every check feeds a credit decision and a file that someone may review later.
KYC API for NBFC Loan Origination: A Lifecycle Guide
A KYC API for an NBFC works best when you map it to the loan lifecycle: PAN at login, entity or vehicle checks at credit, and a bank-account check just before disbursal. Each response drives one decision. API results are evidence on the file, not regulatory compliance, which stays with your policy and compliance officer.
KYC API for Fintech and NBFC Onboarding in India
A KYC API for fintech and NBFC onboarding runs one verification call per document (PAN, bank account, GSTIN, CIN, Udyam and more) from your backend and returns structured results. Run cheap, decisive checks first, queue ambiguous cases for human review, and log every result. An API check is evidence only; regulated entities must still follow their regulator's KYC rules.
Marketplaces, gig platforms and hiring
Sellers, riders and employees who are paid after they are verified, where the cost of a wrong account or a borrowed identity is a payout.
Seller Verification API for Marketplaces: A Trust Ladder
A seller verification API lets a marketplace replace trust with evidence in stages: PAN to list, a verified bank account to get paid, and GSTIN, CIN or Udyam checks for higher limits. Gate payouts in the payout service, detect linked accounts with keyed hashes, and route ambiguous cases to people instead of auto-banning.
Employee Background Verification API for India: What It Covers
An identity API can verify the PAN, driving licence, voter ID, passport file, vehicle registration and salary bank account a candidate provides. It does not run criminal, court, education or past-employment checks. Use role-based packages, take consent first, match Indian names tolerantly, and never auto-reject on a failed check.
B2B platforms, procurement and payouts
Businesses and suppliers who must be real, active and consistent across registers before they get credit, orders or money.
Vendor Verification API: Onboarding Checks Before the First Payment
A vendor verification API checks, when a vendor is created or changes bank details, that the PAN, GSTIN, MSME registration and bank account on the form exist, are active and belong together. Run free format checks first, then PAN, GSTIN or CIN, Udyam and the bank account, block payment until checks pass, and re-verify by risk tier.
KYB API India for B2B Platforms: Entity Checks, Tiers and Monitoring
KYB for a B2B platform is a consistency exercise across PAN, GSTIN, CIN and Udyam records, anchored on the PAN. Run free checks first, verify the entity and its signatory, turn the picture into risk tiers that set limits and terms, and monitor status drift afterwards. Registry data shows what registers say, not who owns the business.
Bank Account Verification Before Payout: Controls and Cost
Verify a bank account before the first payout, whenever it changes and when a payout returns. Call the bank-account endpoint with the payee's legal name, read the validity flag, account status and name-match score, set thresholds per payout type, gate the payout service rather than the form, and cache results. The rate is flat on every plan.
Property, legal and compliance teams
Agreements that must be stamped, parties that must be checked and records that must stand up when someone asks how a decision was made.
Rental Agreement E-Stamping for Property Managers and Brokerages
Property managers, brokerages and law offices can run rental agreement e-stamping as a pipeline: verify owner and tenant, calculate duty through the API, create idempotent orders, pay, track, store the certificate and reconcile daily. Duty and registration rules vary by state, so keep them as reviewed state profiles, never hardcoded numbers.
E-Stamping Rental Agreements via API for Proptech and Broker Apps
To e-stamp a rental agreement via API, resolve the state and article with the lookup endpoints, call the duty calculation endpoint, create an order with an e-Stamp serviceCode, attach the parties, collect payment, then poll status and download the certificate. Registration rules differ by state, so confirm them with qualified counsel.
Verification Workflows for Legal and Compliance Teams
Legal and compliance teams use verification APIs to build a defensible record: what was checked, against what source, when, by whom, with which transaction id. Check counterparties and signatories, treat the directors list as a prompt for authority documents, stamp when the text is final, and keep an evidence pack that states only what was checked.
Which page fits your problem
If you know the problem but not the industry label, start from the row that sounds most like yours.
- I disburse loans and need a check at each stage of the file
- I build a fintech app and want check order, retries and review queues
- I pay sellers or delivery partners and want to stop bad accounts
- I hire in volume and need to confirm identity documents and salary accounts
- I onboard suppliers and worry about fake vendors and changed bank details
- I onboard business customers and want to cross-check their registrations
- I send money to many accounts and want to verify them first
- I manage many tenancies and renew agreements every month
- I build a rental or broker app and need the stamping flow
- I run legal or compliance work and need a record I can defend
What these pages do not claim
- A verification result is evidence on a file. It is not regulatory compliance, and StampMitra makes no claim of regulatory approval for any customer.
- The APIs do not offer Aadhaar-based verification, sanctions or politically exposed person screening, criminal or court record checks, or live identification.
- Stamp duty, registration and tenancy rules vary by state and change. The pages tell you to confirm the current rule with qualified counsel and point to the duty calculation API instead of printing figures.
- Cost models use the published rate card and show the arithmetic, with the assumptions stated, so you can replace them with your own volumes.
Frequently asked questions
Do I need a production account to try any of these workflows?
No. A sandbox key is free, never debits your wallet and returns sample data, so you can build and test every workflow end to end. Production access needs your organisation's KYC approval and a per-product application, as described in the sandbox versus production keys guide.
Where do the cost figures on these pages come from?
From the published rate card on the pricing page: standard verification calls, the premium band for vehicle RC and passport, a flat bank-account rate and the per-order e-Stamp API fee, plus the monthly plan fees, with GST at 18 percent added. Each page states its assumptions and shows the arithmetic.
Are these pages legal or compliance advice?
No. StampMitra is a private LegalTech platform and not a law firm or a regulator. The pages describe engineering and operating practice, use general terms for regulation and tell readers to confirm rules, retention periods and wording with their own counsel and compliance officers.
Is there a Hindi version of every solution page?
Yes. Each solution page has a Hindi twin under /hi written as its own article for developers and compliance teams, with API terms, field names and code kept in English so they match the documentation.
What if my industry is not listed?
Start with the page whose workflow is closest to yours, since the decision tables and review rules transfer well, and read the guides for the individual APIs. For a design question specific to your product, the contact page routes you to the team.