FAQ
The questions we get asked before a pilot
Answers on integration, coverage, data handling, evidence, and commercials. Anything we have not confirmed is marked rather than glossed over.
Getting started
Getting started
What the first two weeks actually look like.
How long does integration take?
The hosted flow needs one server call and a webhook handler, so a small team can be live in sandbox the same day. Embedded SDKs and case-management handoffs take longer because they touch your own product surfaces.
Can we start without an engineer?
Yes. Verification links in the console let a compliance or onboarding team send verifications and work results without any integration at all, and those sessions behave identically to API-created ones.
Do we get a sandbox?
Every account starts with sandbox keys, seeded test subjects for each outcome, and the ability to force any session status or webhook event so you can build the unhappy paths first.
Can we migrate existing verifications?
Yes. Historical verifications can be imported with their original evidence so your audit trail is continuous rather than starting fresh on cutover.
Product and coverage
Product and coverage
What runs, and what happens when something does not.
What happens when a document is not recognized?
You get a specific unsupported_document reason code instead of a generic decline, and the journey can route to manual review or an alternative document type.
Do you decline customers automatically?
Only where you configure it. Referral is a first-class outcome: anything that needs judgment goes to a queue with the signal that caused it, rather than being silently declined.
Can compliance change rules without a release?
Yes. Journeys, thresholds, and rules are configured in the console and versioned, and every session records the version it ran under.
Which documents and registries are covered?
Coverage is published per document class, issuer, and registry, dated and versioned, rather than as a headline number — see the coverage page. Specifics remain UAE-focused today, with the wider GCC next.
Data, security, and evidence
Data, security, and evidence
The questions a risk committee asks before procurement.
Where is data stored?
Residency is described by data class on the security page. The hosting region for each class is a UAE region on AWS or Microsoft Azure and confirmed contractually rather than asserted in marketing.
How long is data retained?
Retention is configurable per data class, with deletion on request, subject to the statutory retention period that applies to your license. The legal basis for anything held longer is recorded.
Do webhooks contain identity documents?
No. Payloads carry identifiers, statuses, scores, and reason codes. Images and biometric artifacts are only available from the evidence endpoint over an authenticated call.
What can we hand a regulator?
An evidence bundle per decision — captures, per-check signals, timings, journey and rule versions, reviewer notes, and sign-off — plus period exports in CSV and PDF.
Which certifications do you hold?
Certification status and audit reports are shared under NDA during due diligence — ITSEC holds ISO/IEC 27001 and ISO 22301 certification. We do not list certifications we cannot evidence.
Commercials
Commercials
How the plan maps to what you actually run.
How is pricing structured?
Per module consumed, inside a plan that sets governance features, seats, and support. You pay for the checks a journey actually runs, not for a bundle you do not use.
Are there setup fees?
Commercial terms including onboarding support and minimums are agreed per plan — talk to sales for a quote.
What support comes with a plan?
Support channels, response targets, and named contacts vary by plan — response targets are set in your contract. Implementation is handled by engineers who work on the platform, not a separate script-driven tier.
Who is VerifiX?
A product of ITSEC, a Dubai-headquartered cybersecurity and compliance engineering firm. The platform is built in the UAE for entities regulated in the UAE and wider GCC.
See VerifiX on your own onboarding flow
A 30-minute walkthrough with a compliance engineer, or a sandbox key in your inbox today.