GST status signal
Cancelled or inactive statuses are surfaced for review.
Review GST identity, legal name, trade name, registration, taxpayer type, status, and principal-place signals without claiming payment capacity.
Cancelled or inactive statuses are surfaced for review.
Compare GSTIN details against vendor submissions.
GSTIN verification is not a payment-capacity assessment.
Choose GSTIN, state the reason for verification, and invite the subject or enter fixture data in sandbox.
The data principal sees the requester, purpose, and check type before any live verification starts.
PRAMAAN evaluates document signals and match evidence while keeping sensitive values minimized.
Teams receive a masked, timestamped result with consent reference, signals, and review guidance.
GSTIN verification supports vendor and business onboarding, but it should not be used as a tax-compliance score unless that capability is explicitly configured.
Checks format and returned GST identity signals.
Compares legal name with vendor onboarding records.
Surfaces trade-name signal where available.
Shows registration-date context for business history.
Returns type and active/cancelled/inactive-style status signals.
Shows address signal for KYB review.
GSTIN helps procurement and finance teams compare invoices, vendor records, and business registrations.
Vendor onboarding
Invoice validation
Marketplace seller review
Check GST identity before adding a vendor.
Review legal and trade-name signals for business accounts.
Compare GSTIN details against invoice records.
Attach KYB signals to procurement approvals.
Standardize seller business checks.
Review staffing agency GST identity.
PRAMAAN should surface GST identity and status signals only. Filing or compliance indicators should appear only when actually supported.
Every preview uses dummy sandbox data, a consent reference, a timestamp, document-specific signals, and bounded report language.
Sample sandbox report — no real PII
Sample sandbox report — no real company record. GSTIN verification does not prove tax posture or payment capacity.
Cancelled or inactive signals should route to vendor review.
Mismatch between invoice, contract, PAN, CIN, and GSTIN needs context.
State-code issues may indicate wrong entity or wrong registration.
Use GSTIN as a business identity signal in procurement, finance, and marketplace workflows.
Single live verification
₹99
Integrate GSTIN checks into vendor master, seller onboarding, and invoice validation systems.
Large B2B contracts, marketplace KYB, investor diligence on prospective partners.
Tenant, vendor, employee — anyone receiving payment in India.
Tenant verification, household help address proof, vendor verification.
Household help, driver, tutor — the default identity rail in India.
Mid-to-senior hires, tutors, professional services contractors.
High-trust hires — drivers, nannies, security staff, anyone with home-access.
No. Live checks require explicit consent from the data principal before processing begins.
Yes. The sandbox demo uses fixture data only and does not require real PII.
PRAMAAN surfaces the mismatch as a verification signal and recommends manual review where the evidence is incomplete, stale, or inconsistent.
No. Reports provide verification signals and consent evidence for reviewer decision support. They should not be treated as a guaranteed legal outcome.
No. It surfaces GST identity and status signals. Compliance indicators should only be shown if your configured rail supports them.
No. GSTIN verification provides business identity and status signals only.
Use sandbox fixture data first, then run a live ₹99 verification when the requester, purpose, and consent path are ready.