Integrate Verify into your flow
Whitelabel TecTony Verify into your onboarding, exam, or session-continuity flow. The on-device engine drops in as a step; you own the evidence and the final decision.

1 · Embed the flow
Drop the Verify step into your web flow under your brand, locale and theme.
2 · Tier-0 runs on-device
Presence, liveness, anti-replay and face-match run in the visitor's browser — no raw video leaves the device.
3 · Evidence to your store
Snapshots and per-stage scores post to your endpoint (or our R2). The face embedding stays on-device.
4 · Hand off to your accredited vendor
For regulated identity proofing, Verify hands off to YOUR accredited eKYC/PAD provider through the adapter layer — clearly the vendor's verdict, not ours.
5 · Verdict + HITL
You receive pass / fail / inconclusive; inconclusive routes to your human-review queue.
🔐 Where the certified boundary sits
TecTony Verify is the Tier-0 on-device layer. Certified identity proofing and PAD verdicts come from your accredited vendor via the adapter — Verify orchestrates, the accredited vendor decides.
Configuration preview
Illustrative — the integration surface is shaped per engagement.
import { startVerify } from "@tectony/verify-sdk"; // conceptual
await startVerify({
tenant: "your-brand",
locale: "th",
stages: ["presence", "liveness", "antiReplay", "faceMatch"],
thresholds: { antiReplay: 0.45, faceMatch: 0.45 }, // tune per policy
evidence: { sink: "https://api.yourapp.com/verify/evidence" },
// For regulated identity proofing, hand off to YOUR accredited vendor:
certifiedVendor: { adapter: "your-ekyc-provider", mode: "handoff" },
onVerdict: (v) => {
// "pass" | "fail" | "inconclusive" (inconclusive -> your HITL queue)
},
});TecTony Verify is not certified eKYC, not certified PAD (ISO/IEC 30107-3), and not an identity provider. It integrates with certified providers; it does not replace them.