- iProov does not publish a standard rate card. Every price comes from a negotiated enterprise contract, and the figures circulating online reflect wildly different deal structures.
- Third-party software review sites list starting prices ranging from $0.45 per month to $250 per month for platform access, but these figures do not capture per-verification fees, volume minimums, or the implementation costs that often double year-one spend.
- iProov’s listing on the UK government’s Digital Marketplace shows transaction fees between £0.12 and £1.63 per check , a 13x spread that only makes sense once you understand how volume tiers, product tier selection, and liveness check type interact. These figures come from a public procurement listing, not from iProov’s commercial rate card, and should be treated as a directional range rather than confirmed pricing.
- Before signing, buyers should model three cost layers: platform access, per-verification consumption, and ancillary fees covering implementation, support tiers, compliance reporting, and data retention.
- At least four credible alternatives offer published pricing or lower entry points for teams that cannot justify iProov’s contract minimums.
iProov pricing is entirely negotiated and not publicly disclosed on the vendor’s website. Based on publicly available government procurement data from the UK’s Digital Marketplace, per-transaction fees range from approximately £0.12 to £1.63 per liveness check depending on volume and product tier. These are procurement listing figures, not confirmed US commercial rates. Buyers should expect a minimum annual contract value well above a self-serve threshold, plus separate implementation, support, and integration fees that are not included in the per-check rate.
Why iProov Pricing Is So Hard to Pin Down
iProov’s website has no pricing page. Clicking through to any commercial inquiry lands on a contact-sales form, which means every buyer enters a negotiation without a baseline. That is not unusual for enterprise biometrics, but it creates a specific problem for budget modeling: the numbers floating around online come from four different contexts, and they are not directly comparable.
The four sources are the UK government’s Digital Marketplace procurement listings, third-party software review aggregators, buyer-reported figures on community forums, and analyst estimates. Each reflects a different buyer profile, contract structure, and product tier. Treating any one of them as a market rate leads to a budget that misses by a large margin in either direction.
According to iProov’s listing on the UK government’s Digital Marketplace, transaction pricing runs between £0.12 and £1.63 per check. That range exists because the cheapest tier applies to massive-volume government programs running millions of checks per year, while the higher end applies to lower-volume commercial deployments with premium liveness products. A mid-market fintech sitting at 50,000 annual verifications is not going to land at the £0.12 floor. These figures reflect UK public-sector procurement terms and may not translate directly to US commercial contract structures.
What iProov Actually Sells: Products That Affect Per-Check Cost
iProov offers several distinct biometric products, and the product you select drives the per-check price before volume even enters the conversation. The core distinction is between passive liveness and active liveness detection, and within those categories, iProov has proprietary technology layers that carry premium pricing.
The company’s flagship product, Genuine Presence Assurance (GPA), is a passive liveness check that uses illumination-based analysis to confirm a real person is present. It is iProov’s highest-assurance product and targets regulated use cases: financial account opening, government ID verification, border control. GPA commands a higher per-check rate than simpler active liveness alternatives.
Liveness Assurance, iProov’s other major product line, delivers a lower-cost passive check suited for authentication use cases where the risk level is lower. The per-check rate is cheaper, but so is the fraud resistance ceiling. Buyers in high-risk categories like account origination, credit decisioning, or regulated KYC onboarding typically need GPA, not Liveness Assurance. Choosing the wrong product to save on per-check cost creates a different, more expensive problem downstream.
The FintechSpecs iProov Cost Stack: Three Layers Every Buyer Must Model
Most buyers entering an iProov negotiation focus on the per-check rate. That is the wrong starting point. The full cost of an iProov deployment runs across three distinct layers, and the second and third layers frequently exceed the first-year consumption cost.
Layer 1: Per-Verification Consumption Cost
This is the rate-per-check multiplied by annual verification volume. Based on the UK government procurement listing, which shows a band of £0.12 to £1.63 per check, a working assumption for commercial deployments in the 25,000 to 500,000 annual check range would sit in the £0.30 to £0.80 portion of that band. The USD figures in the table below apply a approximate conversion rate of 1.27 USD per GBP, reflecting the general trading range during 2024 to 2025; buyers should apply the prevailing rate at time of contract. These are directional planning figures derived from the procurement listing, not confirmed US commercial rates, and iProov does not publicly confirm what it charges non-government buyers in the US.
Volume commitments matter here. iProov structures contracts around committed annual volumes, not true pay-as-you-go consumption. Committing to 100,000 checks per year and actually running 60,000 means paying for the shortfall or renegotiating. Buyers who are uncertain about ramp speed should push for a lower committed floor with overage pricing rather than locking a volume they may not hit.
Layer 2: Platform and Contract Minimums
Third-party review sites including Capterra and G2 list iProov starting prices at $250 per month at the platform access level. These figures are user-reported and almost certainly reflect small pilot or evaluation tiers, not production deployments. Buyers at several fintech forums have reported contract minimums in the $50,000 to $150,000 annual range for enterprise production access, though iProov does not confirm minimum contract values publicly.
The platform fee, where it exists, covers API access, dashboard access, and baseline SLA coverage. It does not cover dedicated implementation support, custom integration work, or advanced reporting exports.
Layer 3: Implementation, Support, and Ancillary Fees
This is where most first-time buyers get surprised. iProov’s SDKs cover iOS, Android, and web, and the integration requires work. A typical production deployment involves several weeks of engineering time, and buyers with complex environments (multi-tenant platforms, embedded flows inside existing KYC orchestration, regulated jurisdictions requiring specific data residency configurations) report longer timelines. Engineering cost at $150 to $200 per hour for a 200-hour integration is $30,000 to $40,000 that never appears in the per-check quote.
Support tiers are a separate line. Standard support is included, but SLA-backed enterprise support with named technical account managers is typically sold as an add-on or baked into higher-tier contract structures. Buyers running iProov in production for regulated financial services should budget for premium support explicitly rather than assuming it comes with the base contract.
Data retention configuration, compliance reporting exports, and regional data residency (relevant for EU deployments under GDPR) also carry either implementation overhead or explicit fees depending on the contract structure. These are not hypothetical costs. They show up at renewal or when a compliance audit requires documentation that is not in the default configuration.
Three Usage Band Cost Models
The following illustrative models use rate data from iProov’s UK government procurement listing as a directional input. USD figures apply an approximate conversion of 1.27 USD per GBP (reflecting the general 2024 to 2025 trading range) and are extrapolated to commercial deployment scenarios. These are planning estimates, not confirmed quotes from iProov, and the exchange rate applied will affect the output. Treat them as internal budget scaffolding, not price guarantees.
| Usage Band | Annual Verifications | Estimated Per-Check Rate (USD) | Estimated Consumption Cost | Estimated Platform + Ancillary | Estimated Year-One Total |
|---|---|---|---|---|---|
| Early-stage fintech | 10,000 to 25,000 | $0.90 to $1.80 | $9,000 to $45,000 | $30,000 to $60,000 | $40,000 to $105,000 |
| Growth-stage fintech | 100,000 to 500,000 | $0.40 to $0.90 | $40,000 to $450,000 | $50,000 to $100,000 | $90,000 to $550,000 |
| Enterprise / regulated program | 1,000,000+ | $0.15 to $0.35 | $150,000 to $350,000+ | $75,000 to $150,000 | $225,000 to $500,000+ |
The early-stage band reveals a structural problem: at low volumes, the ancillary and platform costs dominate the total, meaning iProov is cost-inefficient for most seed-stage teams even if the per-check rate looked acceptable in isolation. A $100,000 year-one spend for 25,000 checks is $4.00 per effective verification once all costs are counted. That is hard to justify against alternatives priced for SMB and growth-stage buyers.
The growth band is where iProov becomes more defensible if the use case genuinely requires high-assurance liveness for regulated KYC. At 250,000 annual checks with a $0.60 blended rate plus $75,000 in platform and ancillary costs, total spend lands around $225,000 per year. That is a material but not absurd line item for a Series B fintech running account origination at scale, especially if fraud losses without high-assurance liveness would exceed that figure.
What the Per-Check Rate Does Not Include
The per-check rate covers a completed biometric transaction. It does not cover failed attempts, which count differently depending on contract terms. iProov reports on its website that its products achieve greater than 98% completion rates and an average of 1.08 to 1.22 attempts per successful session. That is marketing language, but it implies some users require multiple attempts, and contract language around whether partial attempts are billable is worth clarifying before signing.
Retries and fraud-flagged sessions may not be billed at the standard rate, or they may be. The contract defines this, and most buyers do not ask during the sales process. Ask specifically: “Are failed or fraud-rejected liveness attempts billed at the same rate as successful ones?”
Webhook delivery, audit log retention beyond a default window, and SIEM integration for compliance teams also fall outside standard per-check billing. If your compliance team needs a 90-day exportable audit trail in a specific format, confirm whether that is included or an add-on before the contract is signed. This is the same pattern that generates surprise costs across most identity infrastructure vendors, and iProov is not an exception to it. See also our analysis of hidden costs that kill fintech SaaS margins for the broader pattern.
iProov Contract Negotiation: Eight Questions That Change the Deal
Enterprise biometric contracts have significant room for negotiation, particularly on volume minimums, ramp provisions, and support inclusions. Buyers who arrive at the first commercial call with these questions ready consistently report better outcomes than those who respond reactively to the initial quote.
- What is the minimum annual contract value, and is there a pilot tier below it?
- How are failed or fraud-rejected liveness checks billed relative to successful completions?
- Is there a volume ramp provision for the first 6 to 12 months while our user base scales?
- What SLA tier is included in the base contract, and what does a named technical account manager cost?
- Which data residency regions are supported, and do non-default regions carry additional fees?
- What is the audit log retention window, and what format are exports delivered in?
- Are SDK updates and new model versions included in the contract, or licensed separately?
- What are the contract renewal terms and pricing escalation caps?
The pricing escalation question matters more than most buyers realize at signing. A contract with no cap on year-two pricing and a significant volume commitment puts the vendor in a strong position at renewal. A cap of 5% to 10% annual increase, written into the contract, is a reasonable ask and most enterprise identity vendors will agree to it.
How iProov Pricing Compares to Alternatives
For buyers who need high-assurance biometric liveness specifically for regulated KYC, iProov competes in a defined set of vendors. For buyers with lower assurance requirements, the competitive set is broader and substantially cheaper. Our full KYC provider comparison by cost, UX, and approval rates covers the broader market, but the direct biometric liveness alternatives worth quoting alongside iProov are the following.
| Vendor | Pricing Model | Published Starting Rate | Best For | Key Difference vs iProov |
|---|---|---|---|---|
| FaceTec | Per-match license + SDK | Not publicly disclosed | On-device / server biometrics, regulated KYC | On-premise and hybrid deployment options; iProov is cloud-only |
| Amazon Rekognition Face Liveness | Pay-per-use | Approximately $0.01 per check in US regions as listed on AWS’s public pricing page; rates vary by AWS region and volume tier , confirm current pricing at aws.amazon.com/rekognition/pricing | AWS-native teams, high volume, lower assurance | Significantly lower per-check cost; less regulatory track record in financial services |
| Azure Face Liveness Detection | Pay-per-use | Varies by transaction volume tier | Microsoft stack, enterprise compliance teams | Deep Microsoft integration; lower fraud resistance ceiling than iProov GPA |
| Jumio | Negotiated enterprise | Not publicly disclosed | Full KYC orchestration including liveness + document | Bundled document + liveness pricing; iProov is liveness-only and integrates with document vendors separately |
| Onfido | Negotiated enterprise | Not publicly disclosed | Identity orchestration, global coverage | Acquired by Entrust; stronger document verification bundling; similar liveness capability |
Amazon Rekognition Face Liveness is the starkest comparison. At approximately $0.01 per check in standard US regions (per AWS’s public pricing page), it is an order of magnitude cheaper than iProov for comparable transaction counts. The reason most regulated financial services buyers do not use it is the assurance level, regulatory acceptance, and certification footprint. iProov holds certifications that matter for specific use cases: iBeta Level 1 and Level 2 PAD compliance, NIST participation, and a track record with government programs in the US and UK. Rekognition does not carry the same regulatory pedigree for financial services KYC. The premium is real and defensible for those use cases. For lower-risk authentication flows, it is harder to justify.
FaceTec is the closest architectural competitor to iProov’s GPA product and the vendor most commonly mentioned alongside iProov in regulated fintech RFPs. Both companies decline to publish pricing. Buyers should request quotes from both simultaneously and use each quote as a negotiating reference with the other. For a structured comparison of the two, see our dedicated iProov vs FaceTec analysis.
What the Switching Cost Looks Like
Switching a biometric liveness vendor mid-stream is not a sprint. It involves SDK replacement across mobile and web surfaces, re-validation of the new vendor against your compliance framework, and a parallel-run period to confirm match rates do not degrade. Buyers who have done it report four to six months of engineering and compliance time. Cost estimates in the $40,000 to $100,000 range appear in buyer discussions across fintech community forums and procurement conversations, though iProov and its competitors do not publish switching cost data and these figures are buyer-reported, not sourced to a public statement.
That switching friction is part of iProov’s pricing position at renewal. When you have embedded their SDK into a regulated onboarding flow, completed the integration with compliance sign-off, and trained your fraud team on their dashboard, the vendor holds a meaningful structural advantage. Negotiating a multi-year pricing cap upfront is cheaper than absorbing a 20% rate increase at year two when migration costs make it difficult to push back. Our guide on switching KYC providers without hurting approval rates or compliance covers the transition process in detail if you are already in that situation.
The same dynamic shows up broadly across identity infrastructure. When evaluating any biometric vendor, factor the exit cost into the initial contract negotiation. A lower-cost vendor with a two-year lock-in and no SLA may cost more in total over three years than a more expensive vendor with a hard SLA, price cap, and quarterly usage reporting that keeps the relationship honest.
How to Request Competing Quotes Effectively
Walking into an iProov quote request as a single buyer leaves money on the table. Running a competitive process with at least two other biometric vendors and documenting it in writing changes the seller’s behavior. The process does not need to be a formal RFP. Three structured emails with the same set of questions sent to iProov, FaceTec, and one of the bundled orchestration vendors (Jumio, Onfido, or a similar full-stack provider) is enough to generate real competitive tension.
Include in every outreach: your estimated annual verification volume, the specific product category (account opening, ongoing authentication, or both), your required data residency regions, your compliance certification requirements, and your target go-live date. Vague inquiries get vague quotes. Specific parameters get specific numbers. If you are building or evaluating your broader identity and fraud infrastructure stack, the fraud detection and risk tools comparison for fintech startups provides broader context on where biometric liveness fits in the overall risk architecture.
Ask each vendor to break out the quote into platform access, per-verification rate at your committed volume, implementation support, SLA tier, and any fees not included in those four categories. A vendor that cannot produce a line-item breakdown is telling you something about how the contract will read later. Transparency in the quoting process is a reasonable proxy for transparency in the vendor relationship.
Frequently Asked Questions
How much does iProov cost per liveness check?
iProov does not publish commercial per-check pricing. Based on its listing on the UK government’s Digital Marketplace, transaction fees range from £0.12 to £1.63 per check depending on volume and product tier. These are UK public-sector procurement figures and may not reflect US commercial rates. For US commercial deployments, buyer-reported estimates suggest per-check rates between $0.40 and $1.80 depending on volume band and whether the buyer is using Genuine Presence Assurance or Liveness Assurance. These are estimates, not confirmed rates. Request a direct quote for your specific volume.
Does iProov have a minimum contract value?
iProov does not publicly confirm a minimum contract threshold. Third-party review sites report starting platform prices of $250 per month, but buyer community reports suggest enterprise production contracts begin in the $50,000 to $150,000 annual range. Pilot or evaluation tiers may be available below this at the vendor’s discretion, but iProov is not structured as a self-serve or usage-based product with a low-cost entry point.
What is the difference between iProov Genuine Presence Assurance and Liveness Assurance for pricing?
Genuine Presence Assurance is iProov’s highest-assurance product, using passive illumination analysis to confirm a real, live person in real time. It carries a higher per-check rate and is designed for regulated use cases like financial account opening and government identity verification. Liveness Assurance is a lower-assurance passive check suited for ongoing authentication where the fraud risk threshold is lower. Selecting GPA when Liveness Assurance would suffice is a common way buyers overpay per check, while selecting Liveness Assurance for high-risk onboarding creates compliance exposure.
What are the main alternatives to iProov for liveness detection?
The main alternatives are FaceTec (closest comparable for regulated KYC, no published pricing), Amazon Rekognition Face Liveness (pay-per-use at approximately $0.01 per check in standard US regions per AWS’s public pricing page, though rates vary by region), Azure Face Liveness Detection (Microsoft-native, published tiered pricing), Jumio (full KYC orchestration bundle including liveness and document), and Onfido (now part of Entrust, strong document plus liveness offering). The right choice depends on your assurance requirement, regulatory obligations, and whether you need liveness-only or a full KYC orchestration layer.
Are failed liveness checks billed by iProov?
iProov does not publicly clarify its billing treatment of failed or fraud-rejected liveness attempts. Contract terms on this point vary by deal. iProov reports greater than 98% completion rates and an average of 1.08 to 1.22 attempts per successful session, meaning a portion of sessions involve partial attempts before success. Whether those partial attempts are billed, how retries are counted, and whether fraud-flagged sessions carry the same rate as successful ones are contract-level questions that every buyer should resolve in writing before signing.
How much does it cost to implement iProov?
iProov provides iOS, Android, and web SDKs, but production integration requires meaningful engineering investment. A standard deployment involves SDK integration into an existing onboarding flow, backend webhook configuration, and compliance documentation. Engineering time of 150 to 250 hours is a reasonable working assumption for a mid-complexity integration, translating to $22,500 to $50,000 at typical contractor rates. More complex environments with multi-tenant architecture, custom data residency requirements, or existing KYC orchestration layers (like Alloy or Persona) will take longer. Implementation costs are not included in iProov’s per-check or platform fees.
How does iProov pricing compare to KYC bundle providers?
iProov sells liveness detection as a standalone biometric component. Full KYC providers like Jumio and Onfido bundle document verification, liveness, and watchlist screening into a single per-transaction price, which often runs $1.50 to $5.00 per complete KYC check. iProov’s per-check rate covers only the liveness layer, so buyers must add document verification from a separate vendor. The total cost of an iProov-anchored KYC stack can exceed a bundled alternative on a per-complete-onboarding basis, even if iProov’s per-liveness rate is competitive. Model both approaches before choosing.
Building a Realistic iProov Budget
The buyers who get the best iProov deals share one characteristic: they walk into the negotiation with a fully modeled TCO across all three cost layers, a documented competitive quote from at least one other vendor, and specific questions about the contract terms that affect long-term cost. The per-check rate is a starting point, not a budget.
For teams at seed or early Series A with annual verification volumes below 25,000, iProov’s cost structure is difficult to justify unless the regulatory requirement is explicit and no cheaper alternative meets the compliance bar. At growth stage and beyond, the calculus shifts. If fraud losses from weaker liveness detection exceed $150,000 annually and the regulatory environment requires a certified solution, iProov’s total cost can be rationalized. That math needs to be done before the sales call, not during it. A useful cross-reference for that analysis is our breakdown of KYC cost per verification across the broader market.
The real budget trap is not the per-check rate. It is underestimating implementation, locking a volume commitment you cannot ramp to in year one, and arriving at renewal without a documented price cap. Get the line-item breakdown, run the competing quotes, and negotiate the escalation cap in writing. That sequence changes the outcome more reliably than any other step in the buying process.
