Overview
The eKYC flow guides users through a multi-step manual verification journey: welcome, consent, personal details, document entry, review, and result screens. All data is entered via form fields (no camera capture). This flow is ideal when you need full control over each step and want to collect information through a traditional form-based experience. Modules used:form
Instead of building from scratch, fork an existing flow from the public sample codes.
Flow Diagram
This flow requires a Google Places API key (
googleApiKey) in the form provider configuration. The key powers the address autocomplete field in the PERSONAL form screen. Without it, the address search will not work. Get a key from the Google Cloud Console with the Places API enabled.Full Implementation
- Vanilla HTML/JS
- React
Step-by-Step Breakdown
1. Initialize the SDK
Pass the session object from your backend toOneSDK(). Include the form.provider recipe to enable React-rendered form components and optional Google Places address autocomplete.
2. Configure Form Components
Create form components usingsdk.component("form", { name, type }). Each screen (WELCOME, CONSENT, PERSONAL, DOCUMENT, REVIEW, RESULT) is a separate component instance.
3. Wire Up Events
Use.on(event) listeners to transition between screens. Each form emits a form:<name>:ready event when the user completes that step.
4. Handle Results
The review form withverify: true handles verification and shows result screens automatically. form:result:success, form:result:failed, form:result:pending, and form:result:partial fire when the user presses the CTA on the corresponding result screen. Use these events for post-flow actions (redirects, analytics, retry logic). If you need to intercept the result before a screen is shown, use customResult: true — see Form Screens for details.
Adding Device Tracking (Fraud Detection)
To add fraud detection via device fingerprinting, initialize the device component before mounting the welcome screen:Retry Logic
The retry mechanism allows users a configurable number of attempts before showing a final failure screen:The retry form remounts the review step, giving the user another chance to correct any issues. After the maximum number of attempts, the failure screen is shown.
Customizing ID Documents
Configure which documents are accepted and how many are required:Customization Reference
| Aspect | Reference |
|---|---|
| SDK initialization options | SDK Initialization |
| Session token generation | Session Management |
| Form screen configuration | Form Module |
| Screen names and types | Form Screens |
| Custom field configuration | Form Configuration |
| Event names and payloads | Events |
| Error handling patterns | Error Scenarios |
| Device fraud detection | Device Module |