Pricing Overview
Didit v3 takes a usage-based approach to identity verification pricing that stands out in the security space. The platform offers 500 free KYC checks per month, making it one of the few identity providers with a genuinely useful free tier. After exhausting the free allocation, pricing starts at $0.03 per user for core KYC features including ID verification, face match 1:1, passive liveness, and IP analysis. There are no contracts, no setup fees, and no monthly minimums. You only pay when a check completes successfully, which means failed or abandoned verifications cost nothing. This pay-per-successful-completion model is a meaningful cost advantage over providers that charge per attempt. For organizations needing dedicated support and custom SLAs, Didit offers an Enterprise tier with custom pricing.
Plan Comparison
Didit v3 structures its pricing around two core tiers: Self-Serve and Enterprise.
| Feature | Self-Serve | Enterprise |
|---|---|---|
| Monthly free checks | 500 | Custom |
| Base price per verification | $0.03 | Custom |
| ID Verification | Included | Included |
| Face Match 1:1 | Included | Included |
| Passive Liveness | Included | Included |
| IP Analysis | Included | Included |
| Active Liveness | Add-on ($0.05) | Included |
| AML/Watchlist Screening | Add-on ($0.10) | Included |
| Age Estimation | Add-on ($0.07) | Included |
| White Label | Add-on ($0.15) | Included |
| Dedicated Account Manager | No | Yes |
| SLA Guarantees | No | Yes |
| Integration Support | Self-serve docs | Dedicated |
The Self-Serve tier is where most small-to-mid-size teams will start. The $0.03 base covers the four core KYC features. Adding capabilities like active liveness ($0.05), AML screening ($0.10), age estimation ($0.07), or white-labeling ($0.15) increases the per-verification cost incrementally. At higher volumes, per-check costs can reach $0.20, $0.27, $0.30, or $0.57 depending on the feature combination. The Enterprise tier bundles everything with custom pricing, dedicated support, and SLAs.
Hidden Costs and Considerations
While Didit v3 advertises transparent pricing, we want to flag a few things. Feature stacking adds up quickly. A verification combining ID check, active liveness, AML screening, and white-labeling could cost $0.30 or more per user. The $149/month threshold appears tied to higher-volume or bundled plans. Teams requiring NFC document verification, biometric face search, or proof of address will need to factor in those add-on costs. We recommend mapping your exact workflow before estimating monthly spend.
Cost Estimates by Team Size
Because Didit v3 charges per verification rather than per seat, costs scale with user volume rather than team size. Here are estimates based on the core KYC workflow (ID verification + face match + passive liveness + IP analysis) at $0.03 per check:
| Monthly Verifications | Core KYC Cost | With AML Add-on ($0.10) | With Full Stack (~$0.30) |
|---|---|---|---|
| 500 | $0 (free tier) | $0 (free tier) | $0 (free tier) |
| 1,000 | $15 | $65 | $150 |
| 5,000 | $135 | $585 | $1,350 |
| 10,000 | $285 | $1,235 | $2,850 |
Note: the first 500 checks per month are free across all feature combinations, so the paid counts above reflect the overage beyond that allowance.
How Didit v3 Pricing Compares
Didit v3 occupies a distinct position in the security tools market with its pure usage-based model. Most competitors in this category use subscription-based pricing, which creates a fundamentally different cost structure.
| Tool | Pricing Model | Starting Price | Free Tier |
|---|---|---|---|
| Didit v3 | Usage-Based | $0.03/user | 500 checks/month |
| CodeWatchdog | Freemium | $9/month | 1 user |
| PromptBrake | Paid | $79/month | None |
| Vibio | Free | $29/month | Free plan available |
Didit v3 is the only tool here with true pay-per-use pricing. For teams running fewer than 500 identity checks monthly, Didit is entirely free. Even at 1,000 monthly verifications, the $15 core KYC cost undercuts every subscription-based competitor. The breakeven point where a flat subscription might win depends entirely on verification volume and the specific features required. We think the usage-based model is the smarter choice for teams with unpredictable or growing verification volumes.