---
title: Trigger KYC flow in a customer journey
slug: detected-apis/trigger-kyc-flow-in-a-customer-journey
docTags: 
createdAt: 2025-05-27T08:57:35.540Z
---

# Overview

This pattern follows a simple approach to start the journey in the existing clients application and then redirect for the complex parts of the journey to minimise development effort on the client side.

# General Flow

- Start the journey in your existing onboarding application
- Push the customers information to Detected over API
- Then redirect the customer to the Detected KYC portal or load the 
- Customer then completes the required onboarding tasks in the Detected portal
- Webhook fires to notify existing systems that submission is complete

# Data Flow

```mermaid
---
config:
  theme: redux-dark
  look: classic
  layout: dagre
---
flowchart TD
    C1((("Customer"))) -- Completes information --> CS1["Client Systems"]
    CS1 -- "1.Push details & trigger KYC journey" --> API["Detected APIs"]
    API -- "2.Return KYC journey link" --> CS2["Client Systems"]
    CS2 -- "3.Redirect customer, iFrame or QR code to mobile" --> C2((("Customer")))
    C2 -- "4.Customer completes KYC" --> Portal["Detected Verify (KYC) Portal"]
    Portal -- "5.Webhook: profile updated" --> CS3["Client Systems"]
    classDef detected fill:#d3370c,stroke:#8f2408,color:#ffffff
    class API,Portal detected
```

# Integration View & Platform Setup

This approach uses the same overall integration  as [Trigger KYC flow](docId\:YD_k1rqKm5KcfMYdWcQQW)