Verification journeys you can trace to the rule.
Design the verification journey your customers go through, with every step tied to the rule it satisfies and a signed record of each run.
Compliance teams decide which forms an applicant fills, which checks run and through which vendor, when a person reviews, and what the outcome is. Nothing reaches Production without a second person approving it.
Journey Builder is in early access. Pricing on request — talk to us.
Traceable to the clause
Each step cites the regulatory requirement codes it satisfies, and those references are carried into the run's evidence. Review templates with your MLRO before go-live.
Bring your vendors
Steps are written against vendor-neutral checks and resolved to a vendor at run time. If a vendor errors or times out, the run fails over to the next one mid-journey.
Signed, replayable evidence
Every run ends with an Ed25519-signed bundle: the version that ran, the path taken, verdicts, reviews and a hash-chained timeline. Anyone can verify it against our public keys.
Design, approve, run, prove.
Design
Lay out forms, checks, conditions, reviews and waits on a canvas, or start from an AI-drafted proposal.
Approve
A version moves from draft to review to approved. A second person approves it before it can be published.
Run
Send applicants a hosted link, embed the Web SDK, or drive the journey from your backend through the API.
Prove
Download the signed evidence bundle for any run, and verify it offline.
What the builder covers.
On its own, or with KYC Orchestration.
Journey Builder is a separate product. On its own, checks run through the vendor connectors you configure in Journey Builder, under your own vendor contracts. Alongside KYC Orchestration, a check can run through your existing routing instead, so one vendor configuration serves both.
KYC / KYB Orchestration
One API routes each check to the best vendor per jurisdiction, with failover and a normalized verdict.
Explore KYC / KYB Orchestration →Journey Builder guide
How journeys, versions, review steps and evidence work, and how to deliver a journey through a hosted link, the Web SDK or the API.
Read the guide →