Search for pricing pages from Surepass, AuthBridge, Arya.ai, IDmerit, or SpringVerify and you will notice the same thing: product pages, demo request forms, "talk to sales" buttons - and no rupee figures. This is standard practice across the category, not a gap specific to any one vendor, and it exists for a few genuine reasons worth understanding rather than resenting.

First, the underlying cost structure is itself variable. Vendors resell access to government and quasi-government data sources - UIDAI's Aadhaar authentication infrastructure, DigiLocker, PAN verification via NSDL/Protean, bank penny-drop rails, credit bureau data - and each source has its own fee structure, some of which change without much public notice. A flat public price risks going stale the moment an upstream cost shifts.

Second, pricing is genuinely a function of your usage pattern. A neobank onboarding 200,000 users a month with mostly Aadhaar-based video KYC has a completely different cost profile from a B2B lending platform doing 3,000 PAN and bank verifications a month. Publishing one number would either overcharge the high-volume buyer or undercharge the low-volume one, so vendors default to "let's talk."

Third - and worth being honest about - opacity also just favors the seller. When pricing isn't public, negotiating leverage sits almost entirely with the vendor in the first conversation, because you have no anchor to compare against. So walk into a pricing conversation assuming the first number quoted is a starting point, not a floor.

Despite the lack of published rate cards, the pricing structures themselves are fairly consistent across the Indian identity verification API market. Almost every vendor conversation will land on some combination of the following.

Per-API-call / per-verification pricing

The simplest and most common model: you pay a fixed amount each time you call a specific API - one rate for a PAN check, a different rate for Aadhaar OTP verification, another for a bank account penny-drop, another again for video KYC. This is the easiest model to compare across vendors, provided you are comparing the same verification type. It is also the model most likely to hide surprises, because the "per-call" rate quoted in a sales deck often assumes a successful call on the first attempt.

Tiered or slab-based pricing by volume

As your monthly verification volume crosses certain thresholds, the per-call rate drops. A vendor might quote one rate for 0-10,000 verifications a month, a lower rate for 10,001-50,000, and a negotiated rate beyond that. This rewards scale, but it also means your effective cost per verification depends entirely on which slab you land in - a team that consistently sits just above a slab boundary is often better off negotiating a flat blended rate than staying on the slab structure.

The workflow that matters here is understanding Expected monthly volume → Slab you'll actually fall into → Effective blended rate before you sign, not after your first invoice.

Minimum monthly commitments

Many vendors, especially for enterprise contracts, ask for a minimum monthly spend or minimum verification volume regardless of what you actually consume. This is standard in the industry and not inherently a red flag - it is how a vendor prices in the cost of dedicated support and infrastructure. It becomes a problem when the minimum is sized for the volume a sales conversation assumed you would hit, rather than the volume you can realistically commit to in your first two or three quarters live.

Platform, setup, or integration fees

Separate from the per-transaction cost, some vendors charge a one-time or annual platform fee covering API access, sandbox environments, dashboard access, and integration support. Whether this is bundled into your effective per-verification rate or billed separately is worth clarifying upfront, because it changes how you should model your unit economics.

This is the section most finance teams wish someone had shown them before signing a contract. None of these costs are secret exactly - they are usually disclosed somewhere in the fine print - but they rarely make it into the number a sales team quotes verbally, and they are the most common reason a monthly KYC bill comes in higher than budgeted.

• UIDAI and DigiLocker pass-through charges: Aadhaar authentication is not free for the vendor calling it, and that cost is typically passed through to you. UIDAI's own Aadhaar (Payment of Fees for Performance of Authentication) Regulations set a fee of fifty paise per Yes/No authentication transaction charged to the requesting agency, and higher fees for e-KYC transactions. Vendors build this into your per-call Aadhaar price, but a portion of what you pay is a regulated government fee, not vendor margin - and it is not something a vendor can meaningfully discount away.

• Failed-verification and retry charges: A verification that fails because the user entered the wrong OTP, uploaded a blurry document, or a source database timed out is not always free. Some vendors charge for every attempt regardless of outcome; others only on success. This one distinction can change your effective cost per successfully verified user substantially, especially for products with higher first-attempt failure rates.

• SLA and support tier upcharges: The base contract usually assumes standard support - email tickets, business-hours response. Faster response times, a dedicated account manager, or stronger uptime SLAs often sit in a separate, higher-priced tier. If your product genuinely needs 24x7 support, budget for that tier explicitly rather than assuming it is included.

• Data storage and audit trail fees: Some vendors charge separately for retaining verification records, logs, or document images beyond a default retention window - relevant if your compliance function needs longer retention for audits.

• Overage penalties beyond committed volume: If you are on a minimum-commitment contract and exceed it, the overage rate is sometimes priced higher than your base rate, not lower - the opposite of what volume-based intuition suggests.

Since nobody is going to hand you a clean number, the practical move is to build your own estimate before the vendor conversation, so you can sanity-check whatever you're quoted rather than reacting to it blind.

Start with your funnel, not your target

Budget based on the number of verification attempts your funnel will actually generate, not your target number of successful sign-ups. If your product converts 70% of started KYC attempts to completed ones, and you want 10,000 successful onboardings a month, you are realistically paying for closer to 13,000-15,000 attempts once retries and drop-offs are factored in. Most teams budget on the smaller number and get surprised by the bill.

Map your verification mix, not just your volume

A single "verifications per month" number is not enough to budget accurately, because - as covered below - Aadhaar, PAN, bank, and video KYC checks do not cost the same. Get specific about how many users need each check type, because your blended cost per user depends heavily on this mix, not just the total count.

Model three volume scenarios, not one

Build a conservative, expected, and optimistic monthly volume scenario, and ask the vendor to quote pricing (or at least slab boundaries) against all three. Minimum commitments and slab pricing behave very differently depending on which scenario plays out, and you want to know your worst-case cost before you sign, not after.

Separate one-time cost from recurring cost

Integration effort, platform fees, and custom development work are one-time or annual costs that should not be blended into your per-verification unit economics - doing so makes early months look artificially expensive and later months look artificially cheap.

One of the most common budgeting mistakes is treating "identity verification" as one line item. Each verification type pulls from a different data source with a different cost structure, and a realistic budget has to account for that mix rather than a single blended guess.

Aadhaar-based verification (OTP-based e-KYC, Aadhaar-PAN linkage checks, offline XML/QR verification) typically carries the UIDAI pass-through fee described earlier, on top of the vendor's own margin. It tends to sit lower when done via OTP, and higher when it involves e-KYC data retrieval.

PAN verification (basic PAN-name match, PAN comprehensive checks) generally costs less per call than Aadhaar-based checks, since it draws from NSDL/Protean's infrastructure without the same regulated authentication fee structure.

Bank account verification (penny-drop, name-match validation) usually prices per successful validation and varies with which banking network or aggregator the vendor routes through - some banks charge more for their validation APIs, and that differential often gets passed through.

Video KYC is consistently the most expensive check in the stack, and by a wide margin. It involves a live or recorded video interaction, often human-agent-reviewed, plus liveness and face-match checks - more infrastructure per session than a simple database lookup. If your product requires video KYC for RBI-mandated use cases, budget for it as a meaningfully higher per-user cost, not a marginal add-on.

The practical implication: a fintech doing mostly PAN and bank verification will have a materially lower blended cost per user than one doing Aadhaar e-KYC plus mandatory video KYC, even at identical onboarding volumes. When comparing vendor quotes, always ask for pricing broken down by verification type rather than accepting one blended number - it is the only way to compare providers like-for-like.

Since you cannot compare published rate cards, the pricing conversation itself has to do the work a price list would normally do. These are worth asking directly, and getting in writing, not just verbally confirmed on a call.

• Are failed or retried verifications billed? Ask whether you pay per attempt or only per successful verification, and what counts as a "failure" versus an "error" for billing.

• Is the UIDAI/DigiLocker/bureau pass-through cost itemized or bundled? Ask for the breakdown, so you know how much of your per-verification cost is a regulated pass-through versus vendor margin.

• What happens if we go under our committed minimum? Some contracts still bill the full minimum; others allow partial rollover. Know this before you sign.

• What happens if we exceed our committed volume? Confirm whether overage pricing is better, worse, or the same as your base committed rate.

• What support tier is included by default, and what does the next tier cost? Get the actual SLA numbers - response time, uptime guarantee - not just the label "priority support."

• Can we get verification-type-level pricing, not a blended number? The single most useful question for comparing vendors like-for-like, and any credible vendor should be able to answer it.

• Is pricing locked for the contract term, or can rates change if government fees change? Passed-through fees can and do change; know whether that risk sits with you or the vendor.

Identity verification API pricing in India is not going to become transparent industry-wide anytime soon - the category is built on negotiated, volume-and-mix-dependent contracts, and that is unlikely to change while the underlying cost structure (government fees, bureau data, banking rail charges) keeps shifting. What can change is how prepared you are walking into that pricing conversation: know your funnel, know your verification mix, know which questions to ask about retries, pass-through fees, and support tiers, and you will get a quote that reflects your actual usage rather than a number built around what a sales team assumed about you.

We have deliberately not published a price list in this post, because doing so without knowing your specific verification mix and volume would be a guess dressed up as a fact - precisely the kind of opacity this piece is arguing against. If you want a real, itemized quote based on your actual onboarding volume and verification needs, talk to SecureEdge directly. Our team will walk you through how Verify Edge pricing works for your mix of Aadhaar, PAN, bank, and video KYC checks, itemized clearly enough that you can budget against it with confidence.