A live check, not just a document upload
Video KYC is used when a business wants to meet a customer face to face without bringing them into a branch. The customer joins a guided video session on a phone, tablet or computer, then shows an ID document to the camera while the agent watches the live interaction.
The value is in the human check. A scanned image can be submitted by anyone, but a trained agent can ask the person to turn the document, move it closer, read out details and show that the person in front of the camera matches the ID photo. That live moment is where many onboarding risks are picked up.
In practice, video KYC sits between self-service onboarding and a full branch visit. It gives a business a clearer view of the applicant while keeping the process remote for customers in Johannesburg, Pretoria, Cape Town, Durban and Gqeberha.
What the agent is looking for during the session
A good session is structured, not casual. The agent follows a script, asks the customer to position the camera, and checks whether the document is readable, current and consistent with the person on screen. Liveness checks are part of that flow too, because the agent needs to know the person is present in real time and not passing off a static image or recording.
- Face comparison between the live video and the ID photograph
- Document checks for clarity, glare, cropping and visible details
- Liveness prompts such as movement, blinking or simple guided actions
- Consent steps so the customer understands the recording and use of the session
- Record keeping for the onboarding file and internal audit trail
For South African businesses, these steps usually support customer due diligence under FICA in a general sense, while consent and handling of personal information need to sit inside POPIA aware processes. The operational side matters just as much as the technology. If the script is loose, the session becomes messy and the record is weak.
Where video KYC fits in a real onboarding flow
Video KYC is not a stand alone trick. It sits inside a wider onboarding process that may include workflow mapping, identity capture, risk checks, escalation rules and a decision on what happens when something does not match. Some firms use it for higher risk accounts, while others use it for cases that need a manual look after digital capture.
A practical flow normally includes a short booking or launch point, document collection, the live session, quality review and then an outcome captured in the client record. If the business runs multiple product lines, the steps can differ by account type, customer category or transaction risk. That is why agent script design and escalation design matter. The same form does not suit every case.
- Document capture before the live session
- Guided video verification with a trained agent
- Internal review for exceptions or unclear evidence
- Record retention and reporting in line with company policy
When the flow is mapped properly, the team does less guessing and the customer gets a steadier experience.
A Johannesburg example that feels familiar
Picture a fintech team in Rosebank onboarding customers across Gauteng and beyond. A new customer in Midrand applies after hours, then joins a guided video session on a mobile device the next morning. The agent asks for the ID document, checks the face on screen against the photo, and uses the script to confirm live presence and document clarity.
If the customer image is clear and the details line up, the file moves forward. If the document is tilted, the lighting is poor or the face comparison is not clean, the agent escalates it. That might mean a repeat session, a quality review or a request for a different document image depending on the client’s process.
That is the practical side of video KYC in South Africa. It is not about drama or theatre. It is about giving an online business a controlled way to see who is actually applying, while keeping the steps traceable for the onboarding team.
What needs to be in place before the first pilot
Before a client goes live, the team should know exactly how the session will work and who handles each stage. Integration planning is one part, but training is just as important because the agent must know how to guide the customer without improvising.
- A clear workflow map for applications, review and escalation
- API coordination or other system integration points
- Agent script design with plain prompts and checks
- Quality monitoring for sessions that drift off standard
- Refresh training for staff when the process changes
- Go live stabilising for the first round of live customer use
For a business with teams in Sandton, Pretoria and Cape Town, this also helps keep the experience consistent across regions. Without shared process notes, one team may ask for too little and another may ask for too much. Both create problems later.
The part many teams underestimate
The hardest part is often not the video itself. It is keeping the method consistent when the work gets busy. A good quality assurance lead watches for gaps in the script, missed prompts, unclear records and sessions that should have been escalated earlier. A training coordinator then uses those findings to adjust the guidance, not just repeat the old notes.
Operational reporting also matters because the client needs to know where sessions stall, where the document quality drops and where staff need another round of coaching. For a remote verification service, that feedback loop is what keeps the process useful. If the team only looks at successful sessions, the edge cases keep slipping through.
At PersonVideo ID in Rosebank, that mix of workflow mapping, training and quality control is part of the service model. The point is not a flashy session. It is a clean record, a consistent check and a process that fits the way South African businesses onboard customers online.
