By NHI Mgmt Group Editorial TeamBased on SumSub: “Sumsub Launches SEPBLAC-aligned Video KYC to Support Regulated Onboarding in Spain” (June 8, 2026)

TL;DR: SEPBLAC-aligned Video KYC in Spain now requires real-time recording, auditable evidence, and human review in the onboarding flow, according to Sumsub. For identity teams, the shift is not the video itself but the governance burden around proof, oversight, and regulator-ready records.


At a glance

What this is: This is SumSub’s analysis of SEPBLAC-aligned Video KYC for Spain, centred on real-time recording, operator review, and auditable evidence for onboarding.

Why it matters: It matters because IAM and compliance teams need onboarding controls that satisfy regulators without weakening fraud resistance, oversight, or evidence quality across human identity programmes.


Context

Video KYC is a recorded identity verification flow that creates evidence an organisation can retain and review after the session ends. In Spain, the governance gap is not whether onboarding happens digitally, but whether the process leaves a defensible record that an operator and regulator can later inspect.

For IAM, compliance, and fraud teams, the shift is toward auditable proof rather than one-time identity assertion. That changes onboarding design, review workflows, and the evidence standard for regulated sectors such as financial services, payments, crypto, and trading.


Key questions

Q: How should teams govern recorded video KYC in regulated onboarding flows?

A: Teams should govern recorded video KYC as a regulated evidence process, not just an identity check. That means preserving the full session, controlling who can review or approve it, and proving the decision path during audit. The process needs retention, access control, and immutable logging aligned to the relevant regulator’s expectations.

Q: What should security and compliance teams do first when onboarding evidence is not defensible?

A: First, identify which onboarding steps create the legal record and which only support the user journey. Then require retained video, operator review, and decision logging for the regulated flow, because a smooth journey without evidence is weak control in practice.

Q: What are the signs that human review in video KYC is too shallow?

A: Warning signs include approvals that cannot be tied to specific recorded evidence, reviewer decisions that are not logged, and exception handling that bypasses the normal verification path. If the file does not explain why the applicant passed, the control is not audit-ready.

Q: How do Spain’s video KYC rules change AML onboarding accountability?

A: They make accountability traceable across the session, the reviewer, and the retained evidence set. That means compliance teams must be able to show who approved the applicant, what they reviewed, and how the result aligns with recorded identity verification expectations.


How it works in practice

How real-time recording changes the verification chain

Real-time recording turns the identity proofing session into an artefact, not just an event. Instead of relying on a screenshot, transcript, or downstream case note, the system captures document submission, liveness checks, and operator review in a single evidence chain. That matters because regulators can test not only the decision outcome but also the integrity of the process that produced it. In practice, the evidence value comes from sequence, completeness, and retention, not from the video alone.

Practical implication: treat the recorded session as a governed control artefact with retention, integrity, and retrieval requirements.

Why human-in-the-loop approval remains central

Human-in-the-loop approval means the applicant is not finalised until an operator reviews the recorded session. That creates an accountability layer between automated capture and account issuance, which is especially important when liveness checks and document validation can be manipulated. The operator is not replacing the system, but confirming that the recorded evidence supports the onboarding decision. This is the part many teams underdesign when they focus only on capture technology rather than decision governance.

Practical implication: define who can approve, what evidence they must inspect, and what conditions require escalation or rejection.

Why auditable evidence matters more than the video channel itself

The compliance value is not the recording medium by itself. The real requirement is auditable evidence that shows what was collected, when it was reviewed, and why approval was granted. In regulated onboarding, this supports later challenge handling, fraud investigation, and supervisory review. Without that evidence chain, video KYC becomes a convenience feature instead of a defensible control. The underlying governance issue is evidentiary quality, not media format.

Practical implication: align onboarding workflows with evidence retention, review logging, and case traceability before expanding rollout.


NHI Mgmt Group analysis

Recorded onboarding is becoming an evidentiary control, not a convenience layer. The core change in Spain is that identity verification must now produce artefacts that survive review, challenge, and regulatory scrutiny. That shifts video KYC from a user-experience feature into part of the control stack for IAM and compliance. Practitioners should treat recording, review, and retention as a single governed workflow.

Human oversight remains the control boundary when identity proofing can be manipulated. Liveness checks and document capture reduce risk, but they do not by themselves establish accountability for the approval decision. The governing question is whether an operator can demonstrate what was reviewed and why the applicant passed. Teams should align approval authority with evidence quality, not with throughput targets.

Spain’s approach shows how local regulatory requirements are reshaping global onboarding design. Businesses operating across multiple jurisdictions cannot assume one verification flow satisfies all supervisory expectations. The challenge is not just localisation of policy text, but localisation of evidence standards, review steps, and retention rules. IAM programmes need market-specific control mappings, not one global onboarding template.Auditable identity proofing is now a regulatory design pattern. The more supervisory regimes demand verifiable onboarding, the more identity teams must design for evidence, not just authentication. That affects fraud resistance, AML workflows, and the handoff between automated capture and human approval. The practical conclusion is that onboarding governance has become a first-class identity discipline.

SEPBLAC-aligned video review should be treated as a governance workflow, not a product feature. The capability only works when approval criteria, retention, and exception handling are explicit. Otherwise, the organisation records activity without being able to prove control. Practitioners should map the full onboarding chain and assign ownership at each decision point.

What this signals

Auditable onboarding is becoming a baseline expectation in regulated identity flows. Teams that still treat video verification as a one-off onboarding event will struggle to prove control when challenged. The programme question is whether your verification workflow can be replayed, reviewed, and defended after the fact, not whether it looked efficient at the point of capture.

Recorded identity proofing shifts governance from evidence creation to evidence stewardship. Once the session is stored, the harder problem becomes ensuring the record is complete, tamper-evident, and tied to a named approval decision. That is where IAM, compliance, and fraud operations have to converge.

Human review remains essential when regulators require a defensible decision trail. Automation can support capture and screening, but the organisation still needs a review model that assigns accountability to a person, not to the platform alone.


For practitioners

  • Define the evidence standard for onboarding Specify which artefacts must be captured, retained, and retrievable for each approved identity verification session. Include the recorded video, document capture, liveness outcome, and operator decision record.
  • Separate capture from approval Make the human review step mandatory before account activation for regulated Spanish onboarding flows. Document when automation may pre-screen and when a reviewer must make the final call.
  • Map jurisdiction-specific requirements Compare Spain’s recorded verification expectations with your global onboarding policy so local evidence rules do not get diluted into a single generic workflow.
  • Test audit readiness end to end Run a supervisory-style trace from applicant session to stored evidence and approval record, and verify that a reviewer can reconstruct the decision without relying on memory.

Key takeaways

  • Spain’s Video KYC story is really about evidence quality, not just digital onboarding.
  • The control model combines real-time capture, human review, and a record that can survive later scrutiny.
  • IAM and compliance teams need to align approval authority, retention, and auditability before expanding regulated onboarding flows.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-63 and NIST CSF 2.0 set the technical controls, while GDPR and ISO/IEC 42001:2023 define the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-63SP 800-63A — Enrollment and Identity ProofingThe article is about recorded identity proofing and onboarding assurance.
Recommendation — Apply SP 800-63A-style proofing rigor to make onboarding evidence reviewable and defensible.
NIST CSF 2.0PR.AA-05 — Access Permissions, Entitlements and AuthorizationsApproval of the identity session governs who is authorised to proceed into the system.
Recommendation — Use PR.AA-05 to tie onboarding approval to documented identity evidence and authorisation.
GDPRArt.32 — Security of ProcessingRecorded identity verification stores personal data and needs protected handling.
Recommendation — Apply Art.32 controls to protect recorded verification data and limit exposure in storage and review.
ISO/IEC 42001:2023GOVERN — AI Governance and AccountabilityThe article mentions human oversight and regulated workflow governance, but AI is not central.
Recommendation — Use governed accountability for any automated support that influences identity approval.

Key terms

  • Embedded KYC: Embedded KYC is the practice of placing customer identity verification directly inside the onboarding workflow instead of managing it as a separate process. In regulated environments, it creates a single control path for identity proofing, sanctions screening, and audit evidence, which can improve consistency if governance is clear.
  • Human-in-the-Loop Approval: A review step where a person explicitly approves a high-risk access request before it is granted. It is most useful for exceptional privilege expansion, not for routine automation, because the goal is to catch unusual requests without turning every machine action into a manual process.
  • Auditable Evidence Chain: An auditable evidence chain is the recorded sequence of telemetry, reasoning steps, and supporting artifacts that justify a security verdict. It lets analysts inspect how a conclusion was reached and supports review, escalation, and compliance. In AI-driven operations, it is essential for trust and accountability.
  • Identity proofing: The process of verifying that a person is who they claim to be before granting or restoring access. In higher-risk recovery paths, proofing can include stronger evidence checks such as government ID validation or liveness-based facial verification so the assurance level matches the sensitivity of the request.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.
NHIMG Editorial Note
Published by the NHIMG editorial team on June 10, 2026.
Updated on October 10, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org