Exchange · Compliance

Middle Eastern compliance-oriented

Exchange delivery

PeriodAbout 1 month

Business LineCompliant CEX

Core StackGo / KYC SDK / Risk Engine

RegionMiddle East

Project Background and Challenges

The client is an overseas team targeting the Middle East market and requires a compliance-oriented trading system covering KYC/AML, regional restrictions, and suspicious transaction monitoring. Local regulators have high requirements for identity verification and auditability.

The challenge is not matchmaking, but the compliance and adaptation layer— How to seamlessly integrate KYC, sanctions lists, and suspicious transaction reporting modules into the main transaction chain, with auditable logs at every stage.

The scope we undertake

Compliance adaptation layer (KYC/AML/sanctions list integration), risk control engine, suspicious transaction monitoring, auditable logs, and compliance transformation of matching systems.

Scope 1

Compliance Adaptation Layer (KYC/AML/Sanctions List Integration)

Scope 2

Wind-controlled engine

Scope 3

Suspicious transaction monitoring

Scope 4

Auditable logs

Scope 5

Compliance upgrades of matching systems

Technology stack

KYC/AML

Mainstream KYC vendor SDK integration

Risk control

Real-time risk scoring + list filtering

Matchmaking

Go matching engine + compliance interception layer

Audit

Auditable logs throughout the entire chain, compliant with regulatory retention

Key technical decisions

Decision 01

Compliance module: EmbeddedvsDetour

Select bypass integration. Compliance checks are completed before orders enter matching; the matching itself is not perceptible, ensuring matching performance is not slowed down by compliance calls.

Decision 02

KYC vendor strategy

Supports switching between multiple KYC vendors to avoid service interruptions or regional outages caused by a single supplier.

Decision 03

Auditable logs

All compliance-related actions are on-chain or submitted to audit databases, meeting local regulatory retention requirements.

Delivery Success (Desensitization)

Compliance modules supported by the Emperor

0.05 ms

KYC check delays

5 years

Audit log retention

Teams and cycles

The total cycle is about 1 month, involving 10 people, and progressing in four stages:

Compliance requirements review

Core trading system

Compliance layer and risk control

Audit and online service

Want to see the complete Figma file?

Schedule a 30-minute technical consultation where we walk you through the most relevant Figma / Lanhu files for your project via remote demo, including all pages, component libraries, and interactive prototypes.

Book Technical Consultation Telegram