Verkflo is in early access. Book a demo

KYC automation that follows your written procedure

Verkflo turns your KYC procedure into an agent that reads the applicant file, runs the screening and applies your risk rules. Reviewers take the decisions your procedure reserves for people.

Book a demoSee use cases

Works with

and any system with an API via Custom REST

What KYC automation covers in Verkflo

KYC automation here means an agent doing the file work in a KYC review: pulling the applicant record, checking each document against your procedure, screening the name and drafting the analyst note. Your analysts keep the judgment calls, such as possible matches and high-risk approvals.

The agent works from your own document. You upload the KYC procedure, Verkflo compiles it into a spec, and each run records which version it followed. A branch such as "High risk goes to a senior reviewer" is a CEL rule your team can read: risk_rating == "High".

Business customers and their owners have their own page, KYB automation. Alert and hit work after onboarding sits under AML automation.

Who does what in a KYC review

  • The procedure

    Your KYC procedure sets the documents you accept, the screening you run, how you rate risk and when a file needs a second pair of eyes. Verkflo runs those steps in order for each customer.

  • What the agent does

    • Fetches the applicant data and risk rating from Sumsub

    • Screens the customer for sanctions, PEP and adverse media in ComplyAdvantage

    • Finds periodic reviews that are due under your risk-based schedule

    • Drafts requests for missing documents and saves them to the case folder

  • What your team decides

    • Whether a possible match is the same person

    • Approval of customers rated High risk

    • Whether a document request goes to the customer

    • What to escalate to your MLRO or compliance officer

KYC procedures you can run today

Each one opens with example runs and the rules behind them.

Keep the KYC provider you have

Verkflo is not an identity verification service. It reads what your provider already holds: today that is Sumsub, through its API, with Veriff Coming soon. An in-house onboarding database or any other system with an API connects through Custom REST.

The Sumsub integration page lists the exact calls an agent makes, and the ComplyAdvantage integration covers screening.

Controls your auditors will ask about

These controls apply to each agent you build. Sample data

KYC automation questions

Who makes the KYC decision?

Your rules and your people. CEL rules choose the branch a run takes, and any decision your procedure gives to a person waits for a named reviewer. The model reads documents and drafts the notes.

Can we keep our existing KYC provider?

Yes. Verkflo reads from the tools you already have contracts with. Sumsub and ComplyAdvantage connect today, and other providers connect through Custom REST if they offer an API.

How is each review evidenced?

Each step, tool call and reviewer decision goes into a hash-chained audit log, tied to the procedure version in force at the time. An auditor can read the run and that version side by side.

Does it cover periodic reviews as well as onboarding?

Yes. A schedule finds the files that are due by risk rating, the agent refreshes the data and the screening, and any change goes to a reviewer. See periodic KYC review.

Bring your KYC procedure

Show us the procedure your analysts use today and we'll run a sample customer through it in a demo.

Book a demo