How it works
You build one order of up to 10 companies, authorise a single UPI payment, and collect a validated set. Everything between those two points is automated — and observable while it runs.
Find any of 3.6 million companies and LLPs by name or CIN, and see immediately whether it is real, active or struck off.
Add up to 10 companies to one order. You confirm the list before anything is paid for.
One order, one QR code, covering every company in it. You authorise the payment yourself in your own UPI app.
Entiva walks all eight document categories per company, verifies every archive, validates every PDF, and hands you an indexed set with SHA-256 checksums.
Under the bonnet
MCA V3 does not offer a documents API. Entiva drives the same visible navigation a person uses — search, category, year filter, cart — because the portal redirects anything that tries to skip ahead. Login is verified against the registry server-side rather than trusting a cached page header, so a run never starts on a dead session.
The registry allows a single document category per pass, with a fresh CAPTCHA for each batch of files. That loop is the entire cost of the exercise by hand, and the entire argument for automating it. Entiva runs the loop to completion, per company.
A 5xx from the registry is treated as a retryable source error, never as "this company has no documents". Progress is checkpointed per category and per batch, so an interrupted run resumes at the last completed batch instead of re-paying or re-fetching from scratch.
Every archive's bytes are verified, extracted, and each PDF validated before an order is allowed to report success. The set you receive ships with a SHA-256 inventory so you can prove later that no file changed after delivery.
The payment boundary
This is the part of the system that gets the most care, because it is the only part that cannot be undone.
Payment is deliberately attempted at most once. Before the first payment action, an irreversible boundary is recorded durably. Any crash, timeout, or ambiguous gateway response after that point switches the order permanently into reconciliation polling — it becomes structurally incapable of opening a second charge.
The registry allows itself up to 48 hours to reconcile a payment. An order in that state waits and is polled; it does not hold up anyone else's work and it does not silently fail. The order page names the stage it is at, and tells you when the documents are ready.
You perform the final authorisation yourself, on your own UPI app, against a QR code showing the exact amount. Entiva never holds a payment instrument on your behalf.
Every figure traces to a filing you also receive. Nothing is inferred, rounded from a third-party database, or presented without the document behind it.
Before any payment action the system records an irreversible boundary. A crash, timeout or ambiguous gateway response after that switches permanently to reconciliation — it cannot open a second charge.
Documents arrive from MCA as encoded archives. We check the bytes, extract them, validate each PDF, and publish a SHA-256 inventory so you can prove what you hold.
If a company has not filed, we say so. An empty category is a finding, and we never let a failed retrieval masquerade as one.
Tell us which companies you need to look at, and we will set your account up.