Tax Connect API

Three surfaces: public policy (catalog + classify mapping rules), Tax Connect — Estimate for CA and analytics, and Tax Connect — File for licensed filing portals (ClearTax and partners). PayMyQR classifies income and expenses in the background, builds a Filing Pack, and hands off after user review — the partner files with the government.

PayMyQR is not the filer. We provide prefill and audit trails; licensed partners complete validation, DSC, and e-filing. Always ship catalogVersion, mappingVersion, and gaps[] in filing payloads.

Documentation map

Full reference pages ship with the API launch. Planned Connect portal sections:

Tax Catalog API — GET /v1/finance/tax-catalog (slabs, caps, regimes)
Tax Mapping API — GET /v1/finance/tax-mapping (classify rules for apps)
Tax Estimate API — GET /v1/connect/tax/estimates (OAuth, consent)
Tax Connect — File — Filing Pack, handoff, filing webhooks
Filing Pack schema — ITR-shaped prefill + gap fields
Webhooks — estimate.updated, filing.submitted

Who manages the data?

Data	Managed in
Regions, AYs, slabs, rebates, deduction caps	Admin → `tax-catalog` → KV
Classify rules (tag → 80C, 80D, …)	Admin → `tax-mapping` → KV
Filing partners + field maps	Admin → `tax-filing-partners`
User allocations, Filing Pack, estimates	PayMyQR app; partners receive after consent

Engineering manifest

Implementation contracts and phases: docs/architecture/tax-connect-platform.md (canonical manifest in the PayMyQR repo).