Customer KYC
Forest orchestrates the customer KYC lifecycle. Document review, sanctions screening, manual checks, perpetual refresh, all in one decision flow your compliance team owns.
Forest is where your compliance team owns customer KYC. Provider calls, AI agent reasoning, reviewer decisions, refreshes all land on the same case. Pre-built templates make the first workflow live in days.
One review queue, every provider
Cases flagged by Sumsub, Onfido, IDnow, Veriff, ComplyAdvantage aggregate in one inbox on Forest. Your team filters and assigns from a single view.
Plug into your IDV stack
Forest connects to Sumsub, Onfido, IDnow, Veriff, Persona, ComplyAdvantage via datasources, MCP connectors, and direct APIs. One decision workflow above them all.
Retry and step-up workflow templates
Biometric fail, document mismatch, manual review needed: Forest ships KYC workflow templates with retry, step-up, and escalation logic. Compliance configures without engineering.
Perpetual KYC, as a process
Your team configures risk-based refreshes, watchlist re-screenings, and anniversary reviews on Forest. KYC becomes a process you actually run, not a policy you document.
AI agents under your governance
Your AI agents extract documents, score risk, recommend decisions. Your reviewers approve or override. Every action runs under the same RBAC and audit as your humans.
Every decision, regulator-ready
Every action (human, AI, provider) captured with the full causal chain. Filtered exports for ACPR, DORA, MiCA, GDPR, SOC 2 in one click.

Why Forest
Every KYC step in one workflow
Forest connects IDV, AML, biometric retries, manual review, and refresh into one flow. No more orchestrating across dashboards or losing customers in handoffs.
KYC becomes a process, not an event
Forest gives your team the workflow engine to run risk-based refreshes, watchlist re-screenings, and anniversary reviews, all under the same RBAC and audit trail as initial onboarding.
Every decision, provable in one click
Forest logs every action (human, AI, or provider) with the full causal chain. Your regulator asks 'why was this customer approved?', you export the answer in seconds.
Vendor agnostic
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
What is a KYC workflow on Forest?
A KYC workflow is the end-to-end process your team runs to verify a customer: document collection, IDV provider call, sanctions screening, risk scoring, reviewer approval, audit logging. On Forest, every step is a configurable task and every action logs to the case.
How is Forest different from Sumsub, Onfido, or ComplyAdvantage?
Forest is not an IDV provider, it is the operational layer above them. Sumsub, Onfido, and ComplyAdvantage verify and screen. Forest handles what happens around them: review queues, escalation chains, multi-provider conflicts, AI agent governance, audit trail.
Can I keep my existing KYC provider?
Yes. Forest integrates with Sumsub, Onfido, Veriff, ComplyAdvantage, IDnow, Persona and most major providers via datasources, MCP connectors, or direct APIs. You add Forest as the operational layer above your stack, no migration needed.
How do I run perpetual KYC on Forest?
On Forest, your team configures perpetual KYC as scheduled workflows: risk-based refreshes, anniversary reviews, watchlist re-screenings. Forest surfaces refresh cases with the reason logged. Every refresh shares the same RBAC and audit as initial onboarding.
How do AI agents fit into KYC?
Your AI agents read passports, extract structured data, enrich with public registries, score risk. Forest is both an MCP Client and an MCP Server, with human-in-the-loop approval gates where regulation requires.
How fast can we deploy a KYC workflow with Forest?
Most teams ship their first KYC workflow in under a week. Forest connects to your databases in hours, comes with pre-built KYC templates, and lets compliance teams configure without engineering tickets.
How do you ensure customer data never leaves our environment?
The Forest backend runs inside your infrastructure, alongside your databases. Customer data travels to a provider only at the point where its service is called, and the response logs back to the case. Data stays in your systems of record.

