Paid candidates start the exam in one click.

You add your Eklavvya credentials once per institute, and a background worker keeps the connection alive by auto-refreshing the access token. That matters across long admission windows, where a token expiring quietly would otherwise break exam launches on the worst possible day. Sync status is monitored so mismatches surface early rather than on exam morning.

Map each course to its Eklavvya Exam, Batch and Schedule using the built-in lookup. You pick the exam, schedule and batch from a list rather than copy-pasting IDs between two systems, which is where mapping errors usually creep in. Set it once per course and the flow runs itself.

A confirmed payment. Once the payment is confirmed, the "Appear For Exam" pill enables on that applicant's dashboard; a submitted-but-unpaid candidate sees "Awaiting payment" instead. Nobody has to send exam links manually or check a fee register before letting someone sit the test.

No. Each attempt opens a freshly generated SSO link that takes the candidate from their ePravesh dashboard straight into the Eklavvya exam in one click. There is no second set of credentials to distribute, and no support queue on exam day from candidates who cannot log in to a system they have never seen.

No — it is a configurable feature switched on per institute, and it needs a valid Eklavvya account. When enabled it is part of the Admission Engine itself, not a separate purchase. The AI Counseling Suite, which confirms payments and points candidates to the Appear-For-Exam launch, is the optional add-on.