KYC/KYB Flow

CRYMBO Connect supports a flexible, metadata-based KYC/KYB system designed for institutional onboarding, wallet registration, and Travel Rule compliance. It enables platforms to enforce identity verification and disclosure only when required, such as during crypto withdrawal or cross-VASP transfers — not at the point of user signup.

💡 Key Principles

No default KYC at signup — enforcement is configurable per policy
Metadata first — identity is represented via wallet metadata and custom attributes
Selective enforcement — require KYC/KYB only when interacting with specific services or networks
Travel Rule integrated — identity submission happens via encrypted payloads only when legally required

🧾 User & Business Metadata

All compliance flows start by attaching metadata to the user or VASP.

Endpoint:
POST /v3/users/meta/update

Payload example:

{
	"userId": "user_001",
	"meta": {
		"KYC_STATUS": "pending",
		"RISK_SCORE": 72,
		"JURISDICTION": "DE",
		"USER_TYPE": "individual"
	}
}

This metadata is used later to determine whether to trigger a PII request or allow a transaction.

🔁 Conditional KYC Triggering

Compliance policies can be enforced dynamically:

Policy Condition	Enforcement Action
RISK_SCORE > 80	Require enhanced questionnaire
Crypto Withdrawal > $10,000	Require PII submission
Destination wallet is a VASP	Trigger Travel Rule identity check
User country = restricted jurisdiction	Require KYB & manual review

📝 Submit KYB for a Business

Endpoint:
POST /connect/api/kyb/onboard

Payload includes business metadata and contact details. Documents can be attached later.

🔐 Submit Questionnaire (Dynamic Form)

Endpoint:
POST /v3/users/meta/submitQuestionnaire

Use this to gather jurisdiction-specific or risk-based answers before advancing the user flow.

🧩 Link to On-Chain Transaction

Once a transaction occurs, the Oracle determines if identity is required via metadata rules.

If so, it emits PIIRequested and expects encrypted identity data to be submitted to:

POST /deposits/pii

✅ Marking KYC Complete

When the institution or Oracle confirms identity validation, update user status:

Endpoint:
POST /v3/users/meta/update

{
	"userId": "user_001",
	"meta": {
		"KYC_STATUS": "verified"
	}
}

This metadata state will skip further verification unless new rules are triggered.

Let me know if you’d like to proceed with the next doc: Travel Rule & Encrypted PII Submission.

💡 Key Principles​

🧾 User & Business Metadata​

🔁 Conditional KYC Triggering​

📝 Submit KYB for a Business​

🔐 Submit Questionnaire (Dynamic Form)​

🧩 Link to On-Chain Transaction​

✅ Marking KYC Complete​