IDENTITY VERIFICATION
Hosted identity verification, with the decision left to you
Send customers to a hosted verification flow. Read the case status in your own backend and route exceptions to human review.
WHAT YOU GET
A governed workflow, not an automatic verdict
Identity verification returns a case status and a review path. It supports your decision. It does not make it.
Session path
Session created
A single-use link and an expiry.
Link opened
The customer reads a privacy notice. The window to complete is time-limited.
Case status
Status read or event
Finished, unverified or needs review. Treat each status as input to your own decision.
Fallbacks to plan for
Expired
Emits no event. Read the status to observe it.
Cancelled
Read the status from your backend.
Ends in an error
Sessions can end in an error. Plan a fallback.
Hosted verification link
Your backend creates a verification session and hands the link to your customer by redirect, email, or QR code. The customer works on a Noxtica-hosted page. Your backend never receives the customer's raw answers directly.
Case status for your decision
Read the session status from your backend, such as finished, unverified, needs review, expired, or cancelled. Treat each status as input to your own decision.
Human review path
Cases that need a second look can go to operator review in the console. Review activity is recorded in an audit trail.
Event notifications
Subscribe your endpoint to session events, or poll the status. An expired session emits no event, so read its status to observe expiry.
HOW IT WORKS
From session to case status
Your backend stays in control of the session. The customer works on the hosted page.
Server
Create a session
Uses your own reference for the subject. You receive a single-use link and an expiry.
Noxtica
Customer works on the hosted page
Single-use link
The customer reads a privacy notice, then supplies the requested evidence in a time-limited window.
Server
Status read or event
Case status
Read the status from your backend, or receive an event on your endpoint.
Console
Human review
Exceptions
Cases that need a second look go to operator review. Review activity is recorded in an audit trail.
Your team
Your decision
Your team makes the decision.
Create a session
Your server creates a verification session with your own reference for the subject. You receive a single-use link and an expiry. You can set where the customer returns afterward, from your approved list.
The customer works on the hosted page
Your customer opens the link, reads a privacy notice, and supplies the requested evidence. The window for doing so is time-limited once the link is opened.
Read the status and decide
Read the status from your backend or receive an event. Route exceptions to review. Your team makes the decision.
WHERE IT FITS
Workflows that need identity evidence
Use it where your policy requires identity evidence and a person on your team owns the review.
Onboarding and account opening
Collect supported identity evidence through a hosted flow, without building your own capture screens.
Exceptions and review queues
Separate finished, expired, cancelled, and needs-review cases. Keep the exception path visible to your operators.
Deciding when to ask
Pair verification with Device Intelligence and Risk Scoring to decide which journeys call for identity evidence. Device risk can support identity evidence but should not replace it.
HOW TEAMS CONNECT
Server API, hosted page, and console
Setup depends on an eligible identity configuration. Your account team confirms what applies to your tenant.
- Server API: your backend creates sessions and reads their status with a server-held credential that carries the right permission.
- Hosted page: your customer works through the flow on a Noxtica-hosted page. Your own servers do not handle the raw answers.
- Console and events: operators review cases in the console, and your endpoints can subscribe to session events.
LIMITS TO PLAN FOR
What identity verification does not do
Read these boundaries before you design the flow.
- Controlled availability. Identity verification is provisioned per tenant. What applies depends on an eligible identity configuration, your jurisdiction, and your contract. Confirm with your account team before you plan around it.
- Not legal identity proof. No result is legal identity proof outside the scope of the configured provider and contract. Results are probabilistic and can include false positives and false negatives. They are not statements of fact. Read the disclaimer.
- You decide. A qualified person on your team should review adverse decisions. Noxtica is not a consumer reporting agency. Do not use output for credit, insurance, employment, or housing eligibility.
- Your responsibilities. You own the notices, consents, and legal basis for collecting identity evidence from your customers in each jurisdiction you serve. Plan a fallback for sessions that expire, are cancelled, or end in an error. The Privacy Policy and the Security page describe how Noxtica handles personal data; no module-specific data-scope statement for identity verification is published yet.
Scores, reasons and verdicts are probabilistic estimates, not statements of fact. Your team makes every decision.Read the disclaimer
FAQ
Common questions
Does Noxtica approve or reject my customers?
No. Noxtica returns a case status and routes exceptions to review. Your team makes every decision and owns the review of adverse decisions.
Can I turn identity verification on myself?
No. It is provisioned per tenant under controlled availability. Contact the team to discuss your use case and jurisdiction.
How does it relate to Device Intelligence and Risk Scoring?
They answer different questions. Device and risk evidence describe a browser context and an interaction. Identity verification gathers evidence about a person for your decision. Neither replaces the other.
Related products
IDENTITY VERIFICATION
Talk to the team about your identity workflow
Share the journeys you want to cover, your jurisdictions, and who reviews exceptions. We confirm what applies to your tenant under controlled availability.