KYC Verification

Persona

Role: Backend developer at a fintech company (150 employees) building a compliance platform for digital banking partners.

Each banking partner is onboarded as a separate tenant, ensuring that customer identity data, verification documents, and risk assessments are strictly isolated. The platform must support regulatory requirements across multiple jurisdictions.

Business Problem

Financial institutions spend significant resources on Know Your Customer (KYC) compliance. Manual identity verification involves reviewing uploaded documents, cross-referencing customer data, and assigning risk scores -- all across disconnected systems. This scenario builds a unified KYC workflow where customer onboarding, document verification, and risk assessment happen in a single, auditable pipeline.

Four-Step Application

This scenario works best as a four-step, human-in-the-loop application. The existing object model already gives this scenario a strong delivery backbone through Customer, IdentityDocument, and RiskAssessment.

• Mission metric focus: faster cycle time, better compliance quality, and stronger revenue or loss performance.
• Human + AI pattern: Each step combines structured workflow data with chat assistance, background generation, document understanding, and accessible interaction patterns when they improve the experience.

Step 1. Capture demand and context

• Goal: Make it easy for the user to start the KYC Verification journey with complete, trusted context.
• Required data: Customer context such as name, address, dateOfBirth, and status.
• AI support: Use chat to guide intake, generate clearer prompts, create accessible summaries, and assist with voice or vision-led capture when a form alone is not the best experience. EAI can support structured intake, chat workflows, and document-centred capture today; richer native multimodal capture may still need workflow extensions or connected services.
• Business impact: Improve completion rate, reduce first-touch effort, and raise customer or staff confidence in the UX from the very first interaction.
• EAI delivery: Model the intake as tenant-isolated object types and resources, then use actions, chat workflows, and document indexing or classification to keep the initial record complete and usable.

Step 2. Prepare the decision

• Goal: Turn the captured context into the next best action for KYC Verification without forcing the human reviewer to assemble the case manually.
• Required data: Customer state and history; IdentityDocument fields such as type, fileUrl, verified, and verifiedBy.
• AI support: Run background summarisation, extraction, classification, recommendation drafting, and answer generation so a reviewer sees a prepared case instead of raw fragments. EAI delivers the structured records and AI workflow hooks for this today; specialised scoring engines, external rules, or advanced reasoning controls may still need integration work.
• Business impact: Reduce cycle time, improve quality and consistency, and protect the mission-critical metric before the case moves into execution.
• EAI delivery: Link records across the scenario, persist decision state as resources, and use workflow actions plus chat assistance to keep humans in control while AI prepares the work.

Step 3. Execute and collaborate

• Goal: Coordinate the actual work, handoffs, approvals, and user updates needed to deliver the service or outcome.
• Required data: IdentityDocument actions such as verifyDocument; RiskAssessment fields such as score, factors, decision, and reviewer.
• AI support: Draft replies, produce work packets, monitor exceptions in the background, and surface the next action for each operator. EAI can orchestrate tenant-isolated records, actions, chats, and document workflows today; deeper system-to-system automation may require additional connectors or workflow capability.
• Business impact: Increase operator productivity, reduce rework across handoffs, and improve service consistency across the application journey.
• EAI delivery: Use linked object types, actions, resource updates, and workflow-triggered AI assistance so the team can execute in one model instead of splitting work across disconnected tools.

Step 4. Resolve, explain, and improve

• Goal: Close the loop with a clear outcome, an understandable explanation, and feedback that improves the next case.
• Required data: final status, outcome, audit history, and follow-up signals across Customer, IdentityDocument, and RiskAssessment.
• AI support: Generate outcome summaries, customer-friendly answers, compliance-ready notes, management insights, and accessible follow-up content. EAI can store outcome records and support answer generation today, while richer proactive agents, advanced analytics, or channel-specific accessibility features may need additional product capability.
• Business impact: Increase trust, quality, and measurable business value through faster cycle time, better compliance quality, and stronger revenue or loss performance.
• EAI delivery: Keep the full audit trail in structured resources, use AI workflows to explain outcomes, and feed the resulting signals into future product, service, and operational improvement work.

EAI Platform Support By Step

EAI provides the safe service boundary for KYC Verification through Object Types, tenant-scoped resources, document processing, chat workflows, and CLI verification. For this scenario, the main records are Customer, IdentityDocument, and RiskAssessment.

Process step	What EAI provides	Calling pattern
Step 1. Capture demand and context	Tenant-scoped intake resources for Customer context such as name, address, dateOfBirth, and status. Object Type validation, starter forms, optional document intake, and chat-guided capture keep the first record complete.	Define fields in src/eai.config/object-types.ts, run eai types validate and eai types seed, create initial Customer records with useResources('Customer') or eai resources create Customer, and keep browser calls behind /api/eai/....
Step 2. Prepare the decision	Linked resource queries over Customer state and history; IdentityDocument fields such as type, fileUrl, verified, and verifiedBy. Search, schema checks, document classification or RAG indexing, and chat summaries turn raw context into a prepared decision.	Use useResources('Customer') list/query/search patterns, verify shape with eai resources schema, use useDocuments().upload/classify/ragIndex, eai docs upload, eai docs classify, and eai docs index where supporting material exists, and send decision-support prompts through useChat(workflowId, 'chat') or eai chat send.
Step 3. Execute and collaborate	Resource updates and actions for IdentityDocument actions such as verifyDocument; RiskAssessment fields such as score, factors, decision, and reviewer. Status changes, assignments, notes, generated work packets, and chat support keep humans in control during execution.	Model actions in the Object Type code, call client.resources.executeAction(type, id, action) or the app hook equivalent, update records through the app service layer, and verify with eai resources get/list/query.
Step 4. Resolve, explain, and improve	Outcome resources for final status, outcome, audit history, and follow-up signals across Customer, IdentityDocument, and RiskAssessment. Audit-friendly links, indexed final documents, reporting snapshots, and answer generation make the result explainable and reusable.	Persist outcomes as resources, index final material with eai docs index or useDocuments().ragIndex, send explanation prompts with useChat or eai chat stream, and use eai resources aggregate/search for reporting checks.

Prompt, Code, And Service Pattern Mapping

The Object Type code example on this page is the implementation contract for the EAI platform services. eai-gofer should read that code as the source of truth for which resource, document, and chat calls belong in the app.

Use this prompt shape when asking eai-gofer or another coding agent to implement the scenario:

Use the EAI App Template. Model KYC Verification with Object Types for Customer, IdentityDocument, RiskAssessment. Use useResources for records and actions, useDocuments for uploads/classification/RAG where documents appear, useChat for workflow assistance, and verify with eai types/resources/docs/chat commands. Use eai publicapi only when no named command covers the required platform call.

Scenario artifact	How it maps to EAI service calls
Four-step process	Step 1 becomes resource creation, Step 2 becomes resource query/search plus optional document or chat preparation, Step 3 becomes resource update/action calls, and Step 4 becomes outcome persistence plus explanation/reporting calls.
Object Type definitions	eai types validate, eai types seed, and eai resources schema make the model available and checkable before UI work starts.
Properties and indexes	Fields become useResources payloads, filters, list views, and eai resources create/list/query/search checks. Indexed fields should support lookup and triage, not duplicate canonical records.
Links between Object Types	Relationships become linked-resource UI, timeline context, and audit trails that app code loads through resource queries rather than separate bespoke stores.
Actions and status fields	Workflow buttons and operator transitions call resource action/update helpers, then verify state with eai resources get/list/query.
Document and chat prompts	Prompts should call the platform documents and chat patterns: useDocuments().upload/classify/ragIndex, eai docs upload, eai docs classify, and eai docs index for documents, and useChat, eai chat send, or eai chat stream for conversational assistance.

Object Types

Name	Key Properties	Links	Actions
Customer	name (text), address (text), dateOfBirth (date), status (select: pending, verified, rejected, review-required), jurisdiction (text)	one-to-many → IdentityDocument, one-to-many → RiskAssessment	--
IdentityDocument	type (select: passport, drivers-license, national-id, utility-bill), fileUrl (text), verified (boolean), verifiedBy (text), uploadedDate (date)	many-to-one → Customer	verifyDocument
RiskAssessment	score (number), factors (text), decision (select: approve, reject, escalate), reviewer (text), assessmentDate (date)	many-to-one → Customer	submitAssessment

CLI Workflow

1. Scaffold the project

   eai init kyc-verification

2. Authenticate and pull environment

   eai login
   eai env pull --include-secrets

   If you are an external developer, see [Configuration](/docs/configuration) for login and local environment setup.

3. Define your Object Types

   Create the Customer, IdentityDocument, and RiskAssessment types in src/eai.config/object-types.ts (see code example below).

4. Validate the type definitions

   eai types validate

   Tenant: kyc-verification
   ✔ Customer — 5 props, 2 links, 0 actions
   ✔ IdentityDocument — 5 props, 1 link, 1 action
   ✔ RiskAssessment — 5 props, 1 link, 1 action
   
   ✔ All Object Types are valid

5. Seed types to the platform

   eai types seed

6. Create a sample customer and document

   eai resources create Customer --data '{"name": "Alex Johnson", "address": "123 Main St, New York, NY 10001", "dateOfBirth": "1990-07-22", "status": "pending", "jurisdiction": "US"}'
   
   eai resources create IdentityDocument --data '{"type": "drivers-license", "fileUrl": "/documents/dl-aj-001.pdf", "verified": false, "verifiedBy": "", "uploadedDate": "2026-03-05"}'

7. Start local development

   eai dev

Code Example

// src/eai.config/object-types.ts
export const objectTypes = {
  'kyc-verification': [
    {
      name: 'Customer',
      displayName: 'Customer',
      description: 'A customer undergoing identity verification for account onboarding',
      properties: [
        { name: 'name', type: 'text' as const, required: true, indexed: true },
        { name: 'address', type: 'text' as const, required: true },
        { name: 'dateOfBirth', type: 'date' as const, required: true },
        {
          name: 'status', type: 'select' as const, required: true,
          defaultValue: 'pending',
          options: [
            { label: 'Pending', value: 'pending' },
            { label: 'Verified', value: 'verified' },
            { label: 'Rejected', value: 'rejected' },
            { label: 'Review Required', value: 'review-required' },
          ],
        },
        { name: 'jurisdiction', type: 'text' as const, required: true, indexed: true },
      ],
      linkTypes: [
        { name: 'identityDocuments', targetObjectType: 'IdentityDocument', cardinality: 'one-to-many' as const },
        { name: 'riskAssessments', targetObjectType: 'RiskAssessment', cardinality: 'one-to-many' as const },
      ],
      actions: [],
      status: 'published' as const,
    },
    {
      name: 'IdentityDocument',
      displayName: 'Identity Document',
      description: 'An uploaded identity document submitted for verification',
      properties: [
        {
          name: 'type', type: 'select' as const, required: true,
          options: [
            { label: 'Passport', value: 'passport' },
            { label: 'Drivers License', value: 'drivers-license' },
            { label: 'National ID', value: 'national-id' },
            { label: 'Utility Bill', value: 'utility-bill' },
          ],
        },
        { name: 'fileUrl', type: 'text' as const, required: true },
        { name: 'verified', type: 'boolean' as const, required: true },
        { name: 'verifiedBy', type: 'text' as const, required: false },
        { name: 'uploadedDate', type: 'date' as const, required: true },
      ],
      linkTypes: [
        { name: 'customer', targetObjectType: 'Customer', cardinality: 'many-to-one' as const },
      ],
      actions: [
        {
          name: 'verifyDocument',
          displayName: 'Verify Document',
          description: 'Mark the identity document as verified after manual or automated review',
          inputs: [
            { name: 'verified', type: 'boolean' as const, required: true },
            { name: 'verifiedBy', type: 'text' as const, required: true },
          ],
        },
      ],
      status: 'published' as const,
    },
    {
      name: 'RiskAssessment',
      displayName: 'Risk Assessment',
      description: 'A compliance risk evaluation for a customer based on identity and transaction data',
      properties: [
        { name: 'score', type: 'number' as const, required: true },
        { name: 'factors', type: 'text' as const, required: true },
        {
          name: 'decision', type: 'select' as const, required: true,
          options: [
            { label: 'Approve', value: 'approve' },
            { label: 'Reject', value: 'reject' },
            { label: 'Escalate', value: 'escalate' },
          ],
        },
        { name: 'reviewer', type: 'text' as const, required: true },
        { name: 'assessmentDate', type: 'date' as const, required: true },
      ],
      linkTypes: [
        { name: 'customer', targetObjectType: 'Customer', cardinality: 'many-to-one' as const },
      ],
      actions: [
        {
          name: 'submitAssessment',
          displayName: 'Submit Assessment',
          description: 'Record the risk assessment decision and update customer verification status',
          inputs: [
            { name: 'score', type: 'number' as const, required: true },
            { name: 'factors', type: 'text' as const, required: true },
            { name: 'decision', type: 'select' as const, required: true },
          ],
        },
      ],
      status: 'published' as const,
    },
  ],
};

Key Takeaways

• End-to-end verification pipeline: The Customer, IdentityDocument, and RiskAssessment types model the full KYC lifecycle, from document submission through risk scoring to final decision.
• Audit trail by design: Every document verification and risk assessment records who performed the review and when, satisfying regulatory audit requirements without additional tooling.
• Jurisdiction-aware processing: The jurisdiction field on Customer enables location-specific compliance rules, supporting multi-market operations within a single platform instance.
• Partner isolation: Each banking partner operates in a separate tenant, ensuring that customer PII and verification decisions are never accessible across institutional boundaries.