GSTIN Verification + Vendor Intelligence APIs for Fintech — Real-Time KYC, 6-Month Return Trend, Risk Score
Verify a GSTIN + pull last-6-month return cadence + ITC trend in a single 250 ms call.
Try the vendor-risk demo with a sample GSTIN — full risk JSON in 300 ms
The problem
For Head of Credit at a fintech (lending / supply-chain finance / TReDS / B2B payments). Underwriting a borrower needs proof of GSTIN status + 6-month return history + GSTR-2B trend. Stitching that from the government portal at scale is impossible — manual portal lookups don't scale to hundreds of underwriting decisions per day.
How WhiteBooks solves it
- Single API call returns GSTIN status, legal name, registration date, last-6-month filing cadence, and GSTR-2B ITC trend.
- Risk-score endpoint normalises the signals into a 0-100 score with explainable factors (filing regularity, ITC consistency, supplier diversification).
- DPDP Act 2023 consent flow built in: every fetch is logged with consent reference and retention metadata.
- Audit trail with immutable 7-year retention — RBI / credit-committee ready.
Key APIs
| Tool / Endpoint | What it does | Path |
|---|---|---|
gst.verify_gstin | Legal name, status, registration | /api/v1/gstin/{gstin} |
gst.fetch_gstr1 | Last 6 months filed B2B / B2C | /api/v1/gstr1/history |
gst.fetch_gstr2b | ITC behaviour by month | /api/v1/gstr2b/fetch |
vendor_intelligence | Compliance check + risk score | /api/v1/vendor-intelligence |
Compliance angle
RBI account-aggregator alignment, DPDP Act 2023 consent flow, audit trail (immutable, 7-year retention), KYC-Lite eligibility per RBI master direction on digital lending.
Live numbers
- Throughput: 1,000 invoices / EWBs per single API call (bulk mode).
- Latency: p50 87 ms IRN, p95 312 ms — live at whitebooks.in/status.
- Uptime: 99.994% rolling 30-day; 99.99% SLA with credits on Enterprise.
- Region: Mumbai + Hyderabad active-active; KSA in
me-south-1.
Sample architecture
Sample customer pattern
A Tier-1 fintech routes every underwriting decision through WhiteBooks vendor-intelligence. A typical loan-approval call pulls verify_gstin + 6-month GSTR-1 + GSTR-2B + risk score in under 300 ms, gates the borrower decision, and writes the audit trail before the credit committee meets.
Frequently asked questions
How does the DPDP Act 2023 consent flow work?
Every borrower-data fetch requires a consent reference (typically the underwriting case ID). We log the consent grant, the data fetched, the purpose, and the retention horizon — all immutable for 7 years. The borrower can request the audit log via your support flow.
What's the typical risk-score latency end-to-end?
Under 300 ms for the four parallel calls (verify_gstin, GSTR-1 history, GSTR-2B trend, risk roll-up). Latency budget is dominated by the GSTN response time; our edge caches refresh nightly so most underwriting hits a warm cache.
Is this aligned with RBI's account-aggregator framework?
Yes — the consent flow follows the AA reference architecture (data-principal consent ID, data-fiduciary attestation, fiduciary-to-fiduciary signed handoff). For lenders already on Sahamati / OneMoney we provide a thin adapter.
Can we get the full 6-month return history in a single call?
Yes. gst.fetch_gstr1 with a date-range parameter returns all monthly filings in the window; gst.fetch_gstr2b with the same range returns ITC behaviour. The risk endpoint composes both with the verify_gstin response in one parallel batch.
What's your SLA for an underwriting workflow that calls you every minute?
Enterprise SLA is 99.99% with credits. We publish live p50 / p95 / p99 latency at whitebooks.in/status and we run multi-region active-active (Mumbai + Hyderabad) so a single-region outage does not block underwriting.
Get started
Related use cases: Logistics · Retail · Manufacturing · Fintech · Pharma · E-Commerce · SaaS · CA Firms · ERP Providers
Reference: All APIs hub · /docs/gst · /docs/einvoice · /docs/eway · Pricing · Architecture · Status · Changelog