Skip to main content

About Reusable KYC

Reusable KYC allows verified users to share their identity verification with other services, reducing friction and verification costs while maintaining compliance.

What is Reusable KYC?

Reusable KYC enables users who have already completed identity verification to:

  • Share verification results with partner organizations
  • Avoid repeated onboarding friction
  • Control their data through explicit consent
  • Speed up approvals at new services

How It Works

┌─────────────────────────────────────────────────────────┐
│ USER │
│ (Already verified at Company A) │
└─────────────────────────┬───────────────────────────────┘

│ 1. User wants to onboard at Company B
v
┌─────────────────────────────────────────────────────────┐
│ COMPANY B │
│ Requests verified identity │
└─────────────────────────┬───────────────────────────────┘

│ 2. Company B sends reuse request
v
┌─────────────────────────────────────────────────────────┐
│ TRUSTGATE │
│ Validates request, prompts user │
└─────────────────────────┬───────────────────────────────┘

│ 3. User consents to share data
v
┌─────────────────────────────────────────────────────────┐
│ USER │
│ Reviews and approves sharing │
└─────────────────────────┬───────────────────────────────┘

│ 4. Data shared with Company B
v
┌─────────────────────────────────────────────────────────┐
│ COMPANY B │
│ Receives verification, approves user │
└─────────────────────────────────────────────────────────┘

Benefits

For Users

BenefitDescription
Faster onboardingSkip verification, get approved in seconds
Less frictionNo document uploads or selfies needed
Privacy controlChoose what data to share
Single source of truthManage identity in one place

For Businesses

BenefitDescription
Lower costsNo verification costs for reused identities
Higher conversionReduce onboarding abandonment
Compliance maintainedVerification standards preserved
Network effectsAccess to pre-verified user pool

Verification Levels

Levels Supported for Reuse

LevelChecks IncludedReusable
BasicDocument verificationYes
StandardDocument + biometricYes
EnhancedStandard + screeningYes
FullEnhanced + address verificationYes

Level Compatibility

The receiving organization can accept:

  • Same level: User verified at Standard, org requires Standard
  • Higher level: User verified at Enhanced, org requires Basic
  • Not lower: User verified at Basic cannot satisfy Enhanced requirement

Getting Started

Enable Reusable KYC

curl -X PUT https://api.bytrustgate.com/v1/settings/reusable-kyc \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"enabled": true,
"allow_receiving": true,
"allow_sharing": true,
"minimum_verification_level": "standard",
"require_fresh_screening": true,
"max_verification_age_days": 365
}'

Request Verification Reuse

curl -X POST https://api.bytrustgate.com/v1/reusable-kyc/request \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"user_email": "john.doe@example.com",
"verification_level": "standard",
"data_requested": [
"full_name",
"date_of_birth",
"nationality",
"document_verification_status",
"screening_status"
],
"purpose": "account_opening",
"redirect_url": "https://your-app.com/onboarding/callback"
}'

Response

{
"request_id": "reuse_req_123456",
"status": "pending_consent",
"consent_url": "https://verify.bytrustgate.com/consent/abc123",
"expires_at": "2025-01-20T15:30:00Z"
}

User Experience

  1. User clicks consent link or is redirected
  2. TrustGate shows what data will be shared
  3. User reviews and approves or declines
  4. User is redirected back to requesting service
┌─────────────────────────────────────────────────────────┐
│ │
│ Company B wants to verify your identity │
│ │
│ They are requesting: │
│ ✓ Full name │
│ ✓ Date of birth │
│ ✓ Document verification status │
│ ✓ Screening status │
│ │
│ Your data will NOT include: │
│ ✗ Document images │
│ ✗ Biometric data │
│ ✗ Address │
│ │
│ [Approve] [Decline] │
│ │
└─────────────────────────────────────────────────────────┘

Data Sharing

What Can Be Shared

Data CategoryShareableNotes
Full nameYesFrom verified documents
Date of birthYesFrom verified documents
NationalityYesFrom documents
AddressOptionalIf verified
Document statusYesVerified/not verified
Screening statusYesClear/hit/pending
Risk scoreOptionalWith user consent
Document imagesNoNever shared
Biometric dataNoNever shared
Raw selfiesNoNever shared

Shared Data Response

{
"request_id": "reuse_req_123456",
"status": "approved",
"verification": {
"level": "standard",
"verified_at": "2024-06-15T10:00:00Z",
"provider": "Company A"
},
"shared_data": {
"full_name": "John Doe",
"date_of_birth": "1985-03-15",
"nationality": "USA",
"verification_status": "verified",
"screening_status": "clear"
},
"consent": {
"granted_at": "2025-01-20T14:45:00Z",
"consent_id": "consent_789"
}
}

Network Partners

Join the Network

Organizations in the TrustGate network can:

  • Share verifications with other network members
  • Receive verifications from network members
  • Set acceptance criteria for incoming verifications

Partner Requirements

RequirementDescription
Verification standardsMust meet minimum verification requirements
Data securitySOC 2 or equivalent certification
Privacy complianceGDPR/CCPA compliant
User consentMust obtain proper consent

Compliance Considerations

Regulatory Acceptance

  • Same organization: Always acceptable
  • Affiliated entities: Check jurisdiction requirements
  • Third parties: May require additional verification
  • Cross-border: Consider local regulations

Reliance on Third-Party KYC

Most AML regulations permit reliance on third-party KYC when:

  • The third party is regulated
  • Adequate records are maintained
  • Risk assessment supports reliance

Next Steps