A guided session that stays inside the browser
The browser based session is the front end of a remote verification workflow. A customer opens a secure link, follows a guided sequence, shows an identity document to the camera and completes a live face check while a trained agent watches the session flow and checks the material on screen.
It suits onboarding teams that want a controlled process without asking clients to install extra software. The browser handles the session steps, document capture prompts and camera access, while your team keeps the process aligned to your own onboarding rules and risk checks. In practice that means cleaner handovers, fewer abandoned attempts and a more uniform record of each session.
- Supported on current mobile and benchtop browsers
- Works with front facing cameras and standard internet access
- Can include consent capture before the verification begins
- Session logs support internal audit trails and record keeping
Where the browser flow fits in a South African onboarding path
This format works well for banks, insurers, loan origination teams, telco onboarding, investment accounts and other customer journeys that begin online. It is also helpful where branches sit across Johannesburg, Pretoria, Cape Town, Durban and Gqeberha, because the same process can work whether the customer is in Sandton or in a smaller town farther out.
For higher touch accounts, the browser session can sit alongside back office review, document matching and escalation steps. For lower volume operations, it can run as a clear standalone screen that guides the customer from start to finish. Either way, the flow is designed to keep the session practical for staff and familiar enough for customers who are using their phone camera for the first time.
- Suitable for residential and business account opening
- Useful for branches, call centres and remote sales teams
- Can support repeatable checks across multiple branches
- Can be paired with scripted prompts for agents and customers
Session sizes and workflow options
Most clients use a standard browser flow with the same core stages, but the session can be set up with different levels of control. A lean version suits straightforward onboarding with document capture, consent and face match. A fuller version adds scripted guidance, image quality checks, escalation paths and a more detailed handoff to your internal review team.
Where a business needs more structure, the workflow can include branch specific scripts, separate routes for identity document types and clearer status markers for pending, passed or escalated sessions. The aim is to keep the process manageable. It is to make sure the same rules are followed each time, even when different teams are handling the account opening.
- Standard guided session for everyday onboarding
- Enhanced flow with scripted prompts and branching steps
- Escalation route for poor image quality or mismatch checks
- Training version for new staff and pilot launches
What the system checks during a live verification
The browser session usually covers four practical checks. First, the customer confirms consent and basic session details. Second, the identity document is captured clearly enough for reading and review. Third, the live face is compared to the document image and movement or liveness prompts help reduce spoofing. Fourth, the session record is stored for internal review and future reference.
For South African onboarding teams, this structure supports customer due diligence and record keeping under normal business controls, while still leaving room for your own policy rules and risk thresholds. POPIA aligned handling of personal information matters here, especially where recordings, document images and session notes are stored for review or later audit.
- Document capture from a live camera stream
- Face comparison against the presented ID image
- Liveness prompts such as head movement or blinking
- Consent capture and session record retention
Integration planning for teams that already have systems in place
Some businesses want the browser session to sit neatly inside an existing onboarding stack. In those cases, integration planning matters as much as the session itself. We map the handoff points, agree what data moves where and make sure the verification result lands in the right place for your operations team, CRM or case management workflow.
Our team supports API coordination, staff training, agent script design and quality monitoring. That includes pilot launch support, change request handling, escalation design and go live stabilising where the process needs careful tuning. For offices in Rosebank and client teams across South Africa, the work often starts with workflow mapping so the browser steps fit the actual way your staff open accounts.
- API coordination for status updates and session outcomes
- Workflow mapping before the browser journey is turned on
- Staff training for operations, compliance and front line teams
- Quality monitoring and refresh training after launch
Care, upkeep and the details to confirm before launch
The browser flow needs light operational care rather than physical servicing. Teams should keep session scripts current, check camera and browser compatibility, review document types accepted by the journey and watch for friction points where customers struggle with framing, lighting or consent steps. If a process changes, the agent script and escalation path should change with it.
Before rollout, confirm the supported devices, the minimum browser versions, the documents to be accepted, the retention rules for session records and the internal owner for exceptions. It also helps to confirm who reviews failed sessions, how staff are trained on edge cases and what reporting your management team wants from the verification dashboard. The browser flow is only useful when the operational detail is settled.
- Supported browsers and camera access rules
- Accepted identity document types and image standards
- Record retention, consent wording and access controls
- Escalation owner for failed, partial or unclear sessions
Key facts
| Session type | Browser based remote video identity verification |
|---|---|
| Core checks | Consent, ID capture, live face comparison, liveness prompts |
| Delivery model | Guided session through a secure browser flow |
| Support services | Workflow Mapping, Integration Planning, API Coordination, Staff Training |
| Operating base | Rosebank, Johannesburg |
| Client areas | Johannesburg, Pretoria, Cape Town, Durban, Gqeberha, Midrand, Sandton |
