All routes open the same preparation workspace. The difference is whether you type details or practise a consent-based import using clearly labelled example documents.
Use the illustrated presentation for reference or watch the narrated walkthrough. Both explain the same preparation route and identify the points that must continue on the authorised MCA service.
Neither route asks for a government identifierNo PAN, no Aadhaar, no DIN, no CIN. The exposure engine computes from an entity type and a few dates, so none of that is needed to open a workspace or to get a figure.
Nothing here is filedA workspace holds your checklist and your computed exposure. Statutory filing, approval and payment stay on the authorised MCA system, signed by you.
The DigiLocker route is simulatedNo DigiLocker or API Setu connection is made and no identifier is accepted. It models the consent handshake honestly, including the parts usually skipped: purpose, scope, expiry and revocation.