Bynn Onboarding Process (KYC)

Overview

Bynn's onboarding system is built around Sessions - individual verification instances that guide users through a configurable verification workflow. Each session is tied to a Dossier (verification case) and contains one or more Entities (subjects being verified).

graph TD
    A[User Starts Verification] --> B[Create Dossier & Session]
    B --> C[Identity Document Capture]
    C --> D[Document Forensic Analysis]
    D --> E[Biometric Liveness Verification]
    E --> F[AML/Sanctions Screening]
    F --> G[Government Database Check]
    G --> G1{Optional Checks Required?}
    
    G1 -->|Yes| G2[Address Verification]
    G2 --> G3[Source of Funds Check]
    G3 --> G4[Proof of Funds Check]
    G4 --> G5[Mobile Verification]
    G5 --> H[AI Decision Engine]
    
    G1 -->|No| H[AI Decision Engine]
    
    H --> I{Decision}
    
    I -->|Accept| J[Verification Complete]
    I -->|Reject| K[Verification Failed]
    I -->|Review| L[Manual Review Required]
    
    style A fill:#e1f5fe
    style J fill:#e8f5e8
    style K fill:#ffebee
    style L fill:#fff3e0
    style G1 fill:#f3e5f5
    style G2 fill:#f3e5f5
    style G3 fill:#f3e5f5
    style G4 fill:#f3e5f5
    style G5 fill:#f3e5f5

Core Components

🗂️ Dossiers

Dossiers are verification cases that organize all information about a verification process. They serve as containers for entities and maintain the overall verification state.

Dossier Types:

KYC (Know Your Customer) - Individual person verification
KYB (Know Your Business) - Business entity verification

Dossier Features:

Unique customer identification
Verification level assignment
Progress tracking
Risk scoring
Completion status

👤 Entities

Entities represent the subjects being verified within a dossier. Each entity can be an individual, corporation, or organization.

Entity Categories:

Individual - Single persons requiring verification
Corporation - Business entities with ownership structures
Organization - Non-profit or institutional entities
Family - Family groups with shared verification needs

🔐 Sessions

Sessions manage the interactive verification workflow for entities. They track user progress through each verification step and maintain state between interactions.

Session Features:

Real-time progress tracking
Mobile and web compatibility
Secure data collection
Automated workflow progression
Rate limiting and security controls

Verification Levels

Bynn offers flexible verification levels to match your business needs—whether you’re aiming for high-throughput compliance with basic regulatory requirements or seeking robust identity assurance.

Each verification level defines which modules are required, and every component—over 100 in total—can be precisely configured. Want fewer false positives? No problem. We can adjust the specific modules that may be rejecting legitimate customers. Whether you’re optimizing for speed, security, or fraud prevention, Bynn tailors the KYC flow to deliver a seamless onboarding experience.

See KYC parameters

Bynn Integration Methods

Bynn offers multiple integration approaches to fit different technical requirements, development resources, and user experience goals. Each method provides varying levels of customization and technical complexity.

Integration methods determine how verification workflows are embedded into your application and what level of development effort is required. Bynn supports everything from no-code solutions that can be implemented in minutes to fully customizable API integrations.

Method Categories:

Integration methods are organized by technical complexity and customization level:

No-Code Solutions - Ready-to-use verification without any development
Low-Code Integration - Pre-built components with minimal development
Full Integration - Complete control with custom development

No-Code Solutions

These solutions require no development work and can be implemented immediately by business users.

📋 Manual Verification

🔗 Bynn Verification Link

🌐 Hosted Verification

Purpose: Complete verification solution hosted by Bynn with your branding.

Hosted verification provides a full verification interface that users access through a dedicated URL. The interface can be customized with your branding, colors, and messaging while being fully managed by Bynn.

Customization Options:

Company logo and branding
Custom color schemes
Personalized messaging
Domain customization
Multi-language support

How It Works:

Configure your hosted verification settings through the Bynn dashboard. Users access verification through your custom URL and complete the entire process on Bynn-hosted pages. Results are delivered via webhooks or dashboard notifications.

Best For:

Quick time-to-market
Minimal development resources
Consistent user experience
Compliance-focused scenarios

Low-Code Integration

These solutions require minimal development work while providing more customization and control.

🔧 Bynn.js (Web SDK)

📱 Mobile SDK

Full Integration

This approach provides complete control over the verification experience through direct API access.

🔌 API Integration

Choosing an Integration Method

Consider Your Requirements:

Select an integration method based on your technical resources, customization needs, development timeline, and user experience goals.

Development Resources:

No development team - Choose no-code solutions
Limited development - Use SDK integration (with web hooks)
Full development capability - Use SDK integration (with hybrid API calls)

Customization Needs:

Standard experience - Hosted verification works well
Moderate customization - SDKs provide flexibility
Complete control - API integration required

Timeline Considerations:

Immediate launch - No-code solutions deploy instantly
Quick development - SDKs accelerate implementation
Custom development - API integration requires more time

Volume and Scale:

Low volume - Manual or link-based verification
Medium volume - Hosted or SDK solutions
High volume - SDK integration for optimization

Hybrid Approaches

Many organizations combine multiple integration methods to serve different use cases or user segments.

Common Combinations:

Hosted verification for standard users, manual review for edge cases
API integration for primary flows, verification links for support scenarios
Mobile SDK for app users, web SDK for browser-based workflows
SDK for user verification, API for backend retrieving statuses and documents

Workflow Customization

Entity Requirements

Each verification level automatically generates Entity Requirements that define what verification steps must be completed.

Requirement Types:

Identity document verification
Liveness detection
AML screening
Phone verification
Email verification
Proof of address
Proof of funds
Manual review