Go live
When your integration works in test mode, apply for live access. Vindex checks your company, and once approved you create live keys, buy credits and switch.
Apply for live access
- 1
In the Developers console, open Settings and choose Go live.
- 2
Tell Vindex about your company: legal name, registration number, country, website, what you will use Vindex for, and the volumes you expect. Say whether you are regulated, and by whom.
- 3
Give the contacts your customers will see on Vindex's consent screen: your privacy notice and your grievance contact.
- 4
Accept the partner terms and the data processing agreement, and confirm you will use Vindex only for lawful customer-due-diligence checks.
Vindex reviews the application and emails your owners and admins with the result. If something is missing you'll get a note saying what; fix it and apply again.
Before you switch
- A live key, kept secretCreated by an owner or admin, stored in your secrets manager, with an IP allowlist for your servers.
- A live webhook endpointhttps on port 443, verifying every signature, answering 2xx quickly and queueing the work.
- Duplicates and order handledSkip a webhook-id you've seen; act on the object's current status, not the event's order.
- Idempotency keys on every POSTSo a retried create never makes a second verification or a second charge.
- 402 and 429 handledOut of credits: alert your team, don't loop. Rate limited: wait for Retry-After.
- Credits boughtEnough for your first weeks, low-balance alerts set, and auto-recharge if your card allows it.
- Your brand and notice detailsLogo, colour, support email, privacy notice and grievance contact: your customers see them.
- Someone watchingRequest log and webhook health in the console; Request-Id logged on your side for support.
Then swap your test key for the live one in your server's configuration. Test data stays in test mode: create live verifications afresh.
Your responsibilities
partner_decision so your audit trail shows who decided.At launch
Two features open after approvals Vindex is waiting for: live screening through the API (from LSEG, the screening data provider) and DigiLocker in the hosted flow (from NeGD, which runs DigiLocker). Until then live screening returns 403 feature_not_enabled, and customers upload their documents instead of fetching them from DigiLocker. Verifications work fully, screening included.
Something missing or unclear? Signed-in users can tell us from Feedback in the app.
