Identity Analytics
The Identity Analytics dashboard provides comprehensive visibility into customer identity verification status, risk scores, and compliance metrics. This page helps fleet operators monitor verification rates, identify high-risk customers, and ensure regulatory compliance.
Accessing Identity Analytics
Navigate to Dashboard > Analytics, then click "ID Verification Stats" link in the header section. Alternatively, navigate directly to /dashboard/analytics/identity.
Requirements
You must have a subaccount selected to view Identity Analytics. This feature works with all user roles that have dashboard access.
Page Overview
The Identity Analytics page displays:
- Summary metrics cards (4 cards)
- Verification status breakdown grid (5 statuses)
- Recent verifications table
- Flagged customers requiring verification table
Summary Metrics Cards
Total Customers Card (Gray)
| Property | Description |
|---|---|
| Value | Total count of customers in the system |
| Icon | Users icon |
| Description | "All customers with identity data" |
Verified Customers Card (Green)
| Property | Description |
|---|---|
| Value | Number of customers with verified identity |
| Secondary Value | Verification rate percentage |
| Calculation | (verified / totalCustomers) * 100 |
| Icon | Shield with checkmark |
Example: "1,234 Verified" with "85.2% verification rate"
Blocked (Needs ID) Card (Yellow)
| Property | Description |
|---|---|
| Value | Customers who must verify before riding |
| Description | "Cannot start rides" |
| Icon | Shield with alert |
Customer Impact
These customers have identity_verification_required = true and cannot start new rides until they complete identity verification.
High Risk Customers Card (Red)
| Property | Description |
|---|---|
| Value | Customers with risk score >= 50 |
| Secondary Value | Average risk score across all scored customers |
| Icon | Alert triangle |
Risk Score Source: Stripe Radar fraud detection, captured during payment processing.
Verification Status Breakdown
A 5-column grid showing the distribution of verification statuses:
| Status | Icon | Color | Description |
|---|---|---|---|
| Verified | Shield Check | Green | Successfully completed verification |
| Not Started | Shield Question | Gray | Never attempted verification |
| Needs Input | Clock | Yellow | Verification requires additional customer action |
| Processing | Trending Up | Blue | Verification in progress with Stripe |
| Canceled | Shield Alert | Red | Verification attempt was cancelled |
Recent Verifications Table
Shows the last 5 customers who successfully completed identity verification.
Table Columns
| Column | Description |
|---|---|
| Customer | Name with clickable link to profile, customer number in parentheses |
| Verified | Timestamp of when verification completed |
| Risk Score | Numeric score (0-100) from Stripe Radar |
| Status | Badge showing verification status |
Risk Score Badges
Risk scores are displayed with color-coded backgrounds:
| Score Range | Risk Level | Badge Color |
|---|---|---|
| 0-49 | Normal | Green |
| 50-74 | Elevated | Yellow |
| 75-100 | Highest | Red |
Note
Risk scores only appear for customers with Stripe payment history.
Status Badges
| Status | Badge Color |
|---|---|
| verified | Green |
| requires_input | Yellow |
| processing | Blue |
| canceled | Red |
Flagged Customers Table
Shows the last 5 customers who are currently required to verify their identity.
Table Columns
| Column | Description |
|---|---|
| Customer | Name with clickable link to profile |
| Flagged | When the verification requirement was set |
| Risk Score | Current risk score if available |
| Reason | Why verification is required |
Flag Reasons
| Reason | Description |
|---|---|
| Policy | Subaccount requires all users to verify (mode: all_users) |
| Risk | Customer's risk score exceeded the configured threshold |
| Unknown | Flagged for other/legacy reasons |
Customer Impact
Flagged customers cannot start new rides until they complete identity verification.
Understanding Identity Verification
Verification Flow
Trigger
Customer is flagged based on subaccount policy or risk threshold
Initiation
Customer starts verification in mobile app or web
Stripe Identity
Customer submits documents and selfie via Stripe
Processing
Stripe verifies identity (typically 1-2 minutes)
Completion
Webhook updates customer status
Access Restored
Customer can resume riding
Verification Modes
Configured in Dashboard > Settings per subaccount:
| Mode | Behavior |
|---|---|
| Disabled | No identity verification required |
| All Users | Every customer must verify before first ride |
| Risk-Based | Only customers exceeding risk threshold must verify |
Risk Threshold
When using "Risk-Based" mode:
- Configure threshold from 0-100 in Settings
- Customers with Stripe risk score >= threshold are flagged
- Commonly set between 50-75
Risk Score Sources
Risk scores come from Stripe Radar, updated when:
- Customer makes a payment
- Charge includes risk assessment data
- Score ranges from 0 (lowest risk) to 100 (highest risk)
Stripe Identity Integration
What Gets Verified
Stripe Identity collects and verifies:
- Government-issued ID (license, passport, ID card)
- Live selfie (matched against ID photo)
- Name, date of birth, address
Verified Data Stored
After successful verification:
identity_verified_first_name/identity_verified_last_nameidentity_verified_dob(date of birth)identity_verified_address_*(address fields)identity_verified_id_type(document type used)identity_verification_status= 'verified'identity_verified_at(timestamp)
Manual Verification
Admins can manually verify customers from the customer detail page:
Navigate to Profile
Go to the customer's profile page
Find Identity Section
Locate the Identity Verification section
Click Manual Verify
Click "Manually Verify" button
Confirm Action
Confirm the verification action
Audit Trail
Manual verifications record identity_manually_verified = true, identity_manually_verified_by (admin user ID), and identity_manually_verified_at (timestamp).
Access Controls
Who Can View Identity Analytics
All users with dashboard access can view identity analytics for their assigned subaccount(s).
Who Can Manage Verification
| Action | Required Role |
|---|---|
| View analytics | Any dashboard user |
| Manually verify customers | Admin or higher |
| Configure verification settings | Admin or higher |
| Clear verification requirement | Admin or higher |
Best Practices
Monitoring Verification Rates
- Check daily: Monitor the verification rate percentage
- Investigate drops: If rate drops, check for technical issues
- Target > 80%: Aim for high verification rates in regulated markets
Managing Flagged Customers
- Review daily: Check newly flagged customers
- Customer outreach: Contact customers who remain flagged > 24 hours
- Manual override: Use sparingly and only with proper documentation
Risk Score Monitoring
- Track high-risk count: Rising numbers may indicate fraud attempts
- Review threshold: Adjust if too many/few customers are flagged
- Investigate outliers: Customers with scores > 75 warrant review
Compliance Considerations
- Document policies: Keep records of verification requirements
- Audit trail: Manual verifications are logged with timestamps
- Regulatory awareness: Some jurisdictions require identity verification
Troubleshooting
No Data Showing
Possible Causes:
- No subaccount selected
- Subaccount has no customers
- Identity features not enabled
Solutions:
- Select a subaccount from the header dropdown
- Verify customers exist in the Customers section
- Check Settings for identity verification configuration
Verification Rate Shows 0%
Possible Cause: No customers have completed verification
Solutions:
- Enable identity verification in Settings
- Wait for customers to complete the verification flow
- Check if verification emails/notifications are working
Customer Stuck in "Processing"
Possible Causes:
- Stripe Identity still processing
- Webhook not received
- Network/integration issue
Solutions:
- Wait up to 5 minutes for Stripe processing
- Check Stripe Dashboard for session status
- Verify webhook endpoint is configured correctly
Risk Scores Not Appearing
Possible Cause: Customer hasn't made a payment through Stripe
Note
Risk scores are only captured when payments are processed through Stripe Radar.
Data Scope
Current Limitations
The Identity Analytics page currently:
- Shows all customers (not filtered by subaccount)
- Does not include historical trend charts
- Does not support date range filtering
- Shows only last 5 recent verifications/flagged customers
Future Enhancements
Potential improvements:
- Subaccount-scoped metrics
- Historical verification trends
- Verification completion time analytics
- Risk score distribution charts
Mobile Experience
On mobile devices:
- Summary cards stack in 2x2 grid
- Status breakdown becomes scrollable
- Tables display key columns only
- All functionality remains accessible
What's Next?
Now that you understand Identity Analytics, explore these related topics:
- Analytics Dashboard - View revenue and ride metrics
- Database Statistics - System-level record counts
- Customer Management - Manage individual customers
Identity Verification Best Practice
Regular monitoring of identity analytics helps maintain compliance, reduce fraud, and ensure a safe fleet experience. Review these metrics daily, especially if you operate in regulated markets.