Console features

Shareable KYC links

One link — or its QR code — that many people can open. Every person who opens it gets their own, independent verification, and every result lands in your account. No integration, no code.

Use a shareable link when you want to verify a group of people — new staff, a cohort of sellers, event attendees — without building an integration. You create the link in the console and send it however you like: message, email, a printed QR code.

How it works

1
Create a link
In Dashboard → Verification links choose New link, pick the project, the environment (Sandbox or Live) and the limits below.
2
Share it
Copy the link (https://okias.io/l/<token>) or download its QR code as an SVG. The token is random and unguessable.
3
People verify themselves
Each person who opens the link starts their own verification session in the standard hosted flow. A refresh in the same browser resumes the same session instead of starting a new one.
4
Review the results
The link's page lists every session it started, and you can export them as CSV. Sessions are ordinary verifications — they appear in your verification list and trigger your webhooks like any other.

Limits and defaults

Every link carries all three limits. If you leave one unset, the default applies.

SettingDefaultAllowed range
Maximum sessions (uses)1001 – 10,000
Valid for30 days1 – 90 days
Sessions per network (IP) per day51 – 50
  • When the maximum is reached the link is used up; after its expiry date it is expired. Neither can be re-activated — create a new link instead.
  • The per-network cap limits how many new sessions one network can start in a rolling 24 hours. Raw IP addresses are never stored — only a salted digest bound to the link.
  • A person who already started a session can still finish it after the link is paused, used up or expired.

Sandbox and Live links

EnvironmentBehaviourBilling
Sandbox (default)Simulated results — use it to try the flow end to end.Never charged.
LiveReal verifications on the link's project settings.Billed exactly like a verification created through the API — see Pricing.
Live links need credits
Each Live session reserves credits when it starts, just like POST /v1/verifications. If your balance is too low (or billing on the account is paused), new sessions are refused with a neutral message and you receive an email — at most once an hour per reason — so you can top up.

Pause, resume and revoke

  • Pause stops new sessions; Resume turns the link back on.
  • Revoke is permanent: nobody can start a new session with the link. Sessions already started can still be completed.
  • Applicants never see why a link is unavailable — they get a neutral message that does not reveal anything about your account.

CSV export

From the link's page choose Export CSV. The file has one row per session: id, reference code, status, mode, processing mode, who decided, country, document type, end-user reference, credits charged, risk score, reason codes, and the created and completed times. Cells are escaped so a spreadsheet never evaluates them as formulas.

Next steps