Applicants take the photo. Reviewers see the evidence on the left, the decision on the right, the audit trail on every click. Built for Thai banks, telcos, and government counters that have to verify identity remotely.
If your team reviews more than a few hundred onboarding applications a month, you've felt at least one of these. VerifyOne is built for all three.
A clunky onboarding flow loses people halfway. They abandon the form, never come back, and your acquisition team still pays the marketing cost.
Reviewers flick between four tabs to compare the ID, the selfie, the address, the watchlist. Each click is unrecorded. The queue grows. SLA breaks quietly.
The regulator asks. Your team rebuilds the timeline from emails, screenshots, and memory. The audit lasts two weeks. The answer is still incomplete.
The cards marked ★ ONLY VERIFYONE are features that, to our knowledge, the publicly documented offerings of the major eKYC vendors do not ship out of the box. Each one is something we built because the work demanded it — not because a feature comparison sheet asked for it.
A bank-style onboarding flow for premium accounts, telecom SIMs, insurance, and crypto. A separate flow for Thai government counters — land deed transfer, license renewal, civil registry, tax filing, passport. The government track ends with a sworn declaration under penalty of law. No global eKYC vendor ships a citizen-government track.
A reviewer hits Pick Next and the highest-priority unassigned application opens in front of them. SLA countdowns sit on every queue row — urgent, high, normal — and escalate automatically when the timer trips. Most vendor consoles still ask the reviewer to pick from a list.
A QA analyst hits Pick Random Decision and reviews a sampled approval or rejection. They confirm or overturn. The original reviewer keeps their decision in their record; the overturn is logged separately with reason notes. Reviewer accuracy and overturn rate roll up to a dashboard.
An ID number that matches a watchlist entry — fraud, identity theft, document forgery, sanctioned, PEP — is auto-marked critical risk before a reviewer ever opens it. The hit appears in red on the review screen with the source of the listing.
Every action — review started, field corrected, note added, reupload requested, escalated, approved, rejected — writes a timestamped entry with the reviewer's name, IP address, and old/new values. A regulator's question becomes a query, not a reconstruction project.
For Today, This Week, This Month, Last Month: reviews count, approved/rejected split, average review time, approval rate, overturn rate, SLA compliance. Operations managers see their team. Reviewers see themselves. QA sees both.
Documents on the left with zoom and rotate. Applicant data, AI confidence, face-match score, and extracted fields on the right. Face comparison and audit-history drawer at the bottom. Approve, reject, request re-upload, or escalate from one action bar.
Officers work in Thai. Auditors and senior reviewers toggle to English in one click. Both languages are first-class — the locale switcher is built into every page, including the public applicant flow.
Selfie liveness runs at the point the photo is taken. A spoofed photo or a screen-replayed face is flagged before the application reaches the reviewer.
Name, ID number, date of birth, address, and expiry are extracted from the ID with a confidence score per field. Below threshold, the reviewer is asked to confirm.
ID photo and selfie compared with a numeric match score. A radial indicator on the review screen makes the reviewer's eye go to it first.
A standard catalogue of rejection reasons — blurred, expired, mismatch, suspected forgery, and more — that operations managers can edit per tenant.
Every extracted field has a verify checkbox and an inline-edit. A correction writes the old value, the new value, the reviewer, and the timestamp into the audit history. The reviewed page tracks verified count against total fields.
Reviewers ask for a specific document with specific instructions. The applicant gets a deep link back into the same flow, only at the step that needs fixing.
A reviewer escalates to a named senior with a written reason. The case moves to that person's queue. The original reviewer's clock stops.
Pull a hundred applications, assign them across a team in one screen. Useful when a senior reviewer is on leave or a campaign spikes the queue.
Approve, reject, request re-upload, or escalate — the reviewer is sent straight into the next assigned application, sorted urgent → high → normal. No back-to-queue click. Throughput stays in the work, not in the navigation.
Admin, Operations Manager, Senior Reviewer, Reviewer, QA Analyst. Each role sees a different dashboard, queue scope, and export permission. Reviewers see only their own performance. QA sees the whole team. Admins edit roles in Settings.
Operations managers edit max review minutes and escalation thresholds for urgent, high, and normal cases. Defaults: 30 / 60 / 120 minutes review, 45 / 90 / 180 to escalation. SLA-compliance percentages flow straight into the reviewer-performance report.
On every application detail, a panel surfaces other submissions that share the same ID number, email, or phone. Operators see repeat applicants and identity-reuse patterns without leaving the case.
Daily Operations Report and Application Register export as PDF, with the Sarabun font embedded so Thai characters render clean. Date-range parameters drive both. Filed straight to the regulator.
Every box below is a real screen in VerifyOne. Every arrow is a real action your team takes. Find the workflow closest to yours — that's how you'll use it on day one.
Organisations like: KBank, SCB, Krungsri, TMBThanachart — and finance companies running NDID-style remote onboarding for premium accounts and lending products.
Captures national ID, takes a selfie. OCR fills in name, ID number, address.
Runs liveness check and face match. Hits the watchlist.
Picks next case. Verifies fields. Approves on the action bar.
Picks a random approval. Confirms or overturns the decision.
Pulls the daily operations PDF for the regulator file.
Organisations like: AIS, True, dtac — and any operator running NBTC-compliant biometric SIM registration through retail counters and an app.
Captures Thai national ID at a counter. Selfie taken on the same screen.
Confirms the OCR. Submits to the review queue. Hands over the SIM.
Reviews queued applications. Approves clean ones in seconds.
Watches the queue. Reassigns spikes. Reads team performance.
Organisations like: the Land Department (deed transfers), the Department of Land Transport (license renewal), the Civil Registration Bureau, the Revenue Department, the Immigration Bureau.
Picks the procedure. Captures national ID. Affirms a sworn declaration.
Pulls the citizen reference. Sees AI confidence and watchlist status.
Handles escalations. Approves the citizen for counter service.
Pulls the per-click activity log for the inspector general.
Organisations like: Muang Thai Life, AIA, Bangkok Life — and digital-first insurers and health-tech platforms running fully remote enrolment.
Captures ID and selfie. Confirms beneficiaries. Accepts the data-use notice.
Spots an address mismatch. Requests a re-upload with instructions.
Returns to the same flow at the step that needs fixing. Re-uploads.
Files the per-policy audit pack. Includes every reviewer click.
Organisations like: Bitkub, Zipmex, InnovestX, Orbix — exchanges licensed under SEC Thailand requiring full KYC plus AML watchlist screening.
Submits ID, selfie, source-of-funds declaration.
Watchlist match. Auto-flags critical risk before a reviewer opens it.
Reviews the hit. Rejects with a documented reason and audit note.
Files the SEC quarterly. Pulls the application register PDF.
VerifyOne is built first for Thai banks, telcos, and government counters that operate under BoT, SEC, NBTC, ETDA, and PDPA — and then for everyone else. The list below is what you would otherwise spend three months adding to a generic eKYC tool.
The 13-digit national ID with the standard 1-1014-00132-77-3 format is parsed and checksum-validated at the OCR step.
Only verification status is shared with the brand the citizen is signing up with. Raw documents are deleted ninety days after the account closes — and the policy text reads exactly that on the consent screen.
A separate flow ending with "I declare under penalty of law" — the wording Thai e-services and counter procedures expect.
Review started, field corrected, note added, escalated, approved — every event has a reviewer name, a timestamp, an IP address, and old/new values.
Urgent / high / normal review-time targets are configurable by an admin. The countdown is visible in the queue. Auto-escalation hands the case to a senior reviewer when it trips.
Fraud, identity theft, document forgery, sanctioned, PEP — each entry sourced and added by a named compliance officer. The source flows through to the reviewer screen.
Admin, operations manager, senior reviewer, reviewer, QA analyst. Each sees their queue and their team — not the whole platform. Settings is admin-only.
Officers work in Thai. Auditors switch to English in one click. Sarabun for Thai PDFs. The applicant flow is bilingual end to end.
Here's what changes in the first month for a typical compliance team handling 5,000 to 30,000 applications a month across multiple channels.
A reviewer's average case time. Split-panel layout, Pick Next, and inline field verification cut the tab-switching that ate the day.
Drop-off between starting the flow and completing the selfie. A flow built for one thumb keeps the applicant on the page.
Time to assemble a regulator's "show me every decision on this customer" request. The audit trail is already there — the export takes minutes.
QA sampling plus overturn-rate tracking turn reviewer accuracy from a vague worry into a number you can train against.
In operational terms, a compliance team of ten reviewers handling 20,000 applications a month gets back the equivalent of three full-time reviewers' capacity — time that redirects to escalations, fraud investigation, and policy work the team is paid to do. In financial terms, the drop-off improvement on the applicant side typically pays for the engagement on its own. In compliance terms, the per-click audit trail closes the chain-of-decision gap that BoT, SEC, NBTC, and PDPA inspectors all ask about.
Figures are derived from pilot estimates and our founder's prior delivery of facial-recognition and eKYC systems for banks and telecoms across Southeast Asia (2018–2022). Individual results vary by application volume, channel mix, and existing process maturity.
Most teams are running real onboarding traffic on VerifyOne by week 8. Here's what each phase looks like for a single channel — multi-channel and multi-brand rollouts compound onto this baseline.
Your reviewer roles, SLA tiers, rejection reasons, and watchlist seed loaded. Branded applicant flow themed. Demo accounts ready for your team to log in.
A controlled traffic slice routed through VerifyOne. Reviewers using the console for everyday work — review, escalate, request re-upload, approve. We're on hand for questions and adjust workflows from what your team actually does.
Run the first QA cycle, the first reviewer-performance review, and the first compliance export. Operations confirms the numbers tell the story you need to tell the regulator.
Your team operates VerifyOne day-to-day without daily support. We monitor and respond to issues in the background, and start the conversation about additional channels and brands.
Investment is sized to your organisation, the number of channels and brands, and the application volume in scope — discussed in person or on a call when we meet, not on a public price list. Regulated industries usually have specific procurement processes; we'll work within yours.
No. The full applicant flow — context picker, ID capture, selfie, OCR confirmation, consent, sworn declaration — runs in the phone's web browser. There is nothing to download from the App Store and nothing for IT to push to staff phones at the counter. A counter app shell is available where a hardware integration is required, but the default is browser-only.
By default, the hosted version runs on Singapore-region infrastructure. For Thai banks, Thai government deployments, and any organisation with PDPA data-residency requirements, we offer a Thai-region managed-tenant option — specify residency at pilot scoping. We do not move data between regions without your written consent.
The AI features — OCR field extraction, liveness, face match, watchlist scoring — all require an internet connection at the moment of capture. Everything else inside the reviewer console runs on the same connection your office uses for normal browsing. If a reviewer's network drops mid-decision, in-progress work is preserved when they reconnect.
Yes. VerifyOne ships with fifteen standard rejection reasons across categories like document quality, identity mismatch, suspected forgery, and incomplete information. An admin can add, rename, or retire reasons per tenant. SLA tiers — urgent, high, normal — are editable at any time and apply to new cases entering the queue from that point forward.
The role model is built for teams with hundreds of reviewers. Five roles — admin, operations manager, senior reviewer, reviewer, QA analyst — scope what each person sees. Pick Next plus auto-assignment removes the bottleneck of someone manually distributing work. Bulk Assign lets an operations manager redistribute hundreds of cases when a senior is on leave or a campaign spikes the queue.
An ID-number match against the watchlist auto-flags the application as critical risk before a reviewer ever opens it. The hit appears on the review screen with the source of the listing — fraud, identity theft, document forgery, sanctioned, or PEP — and the source citation entered by the compliance officer who added it. Critical-risk cases route to senior reviewers, not juniors.
VerifyOne is built by Inline One Systems, a Bangkok-based product studio. Our founder previously built and deployed facial-recognition and eKYC systems for banks and telecoms across Southeast Asia between 2018 and 2022 — including production systems that processed hundreds of thousands of remote-onboarding decisions for regulated customers. VerifyOne carries that operational pattern forward into a product designed first for Thai financial regulation and government e-services.
A 30-minute walk-through. Bring your current applicant journey, your reviewer headcount, and a sample of three rejection reasons you actually use. We'll demo VerifyOne with shape-of-your-flow data — applicant intake, reviewer console, QA sampling, audit export. If the shape fits, we scope a structured engagement on one channel. If it doesn't, you leave with a clearer view of what your organisation actually needs.