Skip to main content

​
Verification System

Complete guide to the verification and passport system that provides cross-server identity validation and security features.
The verification system uses external web authentication to validate user identity and create global passports for cross-server reputation.

​
Passport System

Command: =passport [user]
Permissions: None
Category: Info
Cooldown: 10 secondsGlobal verification passport that tracks user verification status, premium tier, and reputation across all servers.
=passport
=passport @user
=passport 123456789012345678
Passports are global and follow users across all servers using the bot. Verification status is maintained for 30 days.

​
Verification Process

Command: =verify
Permissions: None
Category: Verification
Cooldown: 30 seconds
Guild Only: YesStart the verification process to gain access to server features and build global reputation.
1. User runs =verify command
2. Bot generates secure verification token
3. User visits external verification site
4. Complete CAPTCHA and identity validation
5. System creates/updates global passport
6. Bot assigns verified role automatically
Verification tokens expire after 10 minutes. Users must complete the process within this timeframe.
Server administrators can configure verification settings through the dashboard:
• Enable/disable verification requirement
• Set verification channel (optional)
• Configure verified role
• Set unverified role (auto-removed)
• Configure welcome messages

​
Premium Integration

Verified users with premium tiers receive enhanced features:
• Faster verification processing
• Priority support access
• Enhanced passport features
• Cross-server premium recognition

​
Security Features

The verification system includes comprehensive security measures:
• CAPTCHA validation (multiple types)
• Browser fingerprinting
• IP reputation checking
• VPN/proxy detection
• Rate limiting per user/IP
• Suspicious activity monitoring
Users attempting to bypass security measures may be permanently banned from the verification system.
The verification system follows strict privacy guidelines:
• Only necessary verification data stored
• IP addresses hashed for security
• Browser fingerprints anonymized
• No personal information required
• Data retention limited to 90 days

​
Administration Tools

Server administrators have access to verification oversight tools:
• View server verification statistics
• Manual verification approval/denial
• Bulk role management for verified users
• Verification requirement exemptions
• Custom verification messages

​
Troubleshooting

Verification Link Not Working
  • Check link hasn’t expired (10 minute limit)
  • Ensure you’re accessing from the same browser/device
  • Clear cookies and try again
  • Contact server moderators if issues persist
Role Not Assigned After Verification
  • Run =verify again to trigger role assignment
  • Check bot has Manage Roles permission
  • Ensure verified role exists and is below bot’s role
  • Contact administrator if bot permissions need updating
=passport
=passport @user
Common verification error messages and solutions:
❌ Verification is not enabled on this server
❌ Please use this command in #verification instead
❌ You are already verified on this server
❌ Verification link has expired
❌ Invalid verification token

​
API Integration

The verification system uses webhooks for real-time updates:
• verification-complete: User completed verification
• verification-failed: Verification attempt failed
• verification-expired: Token expired unused
• security-alert: Suspicious activity detected
Webhook integration is automatic and requires no additional configuration for basic functionality.

​
Best Practices

For optimal verification system performance:
• Create dedicated #verification channel
• Set appropriate role hierarchy
• Configure welcome messages
• Enable verification logging
• Set reasonable timeout periods