Commercial
Pricing
No published price list · 11 August 2026
Settled: how a price is arrived at, what it would cover, and how you are onboarded.
Not settled: the unit, the rate, and every figure that follows from them.
FinLens is priced per client, agreed in writing during onboarding, and written into that client's order form. There is no self-serve signup, no plan to pick and no card to enter. Onboarding is a conversation, and then an operator provisions a credential by hand.
1. Why there is no number here
Two reasons, and they are different from each other.
No price has been set
FinLens has not delivered a document to any client. The partner register is empty and says so. Nothing has been sold, so no rate has survived a negotiation, and publishing one now would be a guess presented as a policy.
Nothing in the platform can count
There is no billing system. No meter. No per-client tally of sessions or delivered documents. No invoicing, no usage endpoint, no usage report. A per-unit price today would have no system of record behind it and would be reconciled by hand.
The second reason is the one worth dwelling on, because the opposite is easy to assume. The API does issue each client its own credential, and it does tag every artifact with their id. That is tenant isolation — it exists so one client cannot reach another client's documents. It is not accounting. Nothing adds those artifacts up, nothing keeps a running figure against a client, and nothing survives the three hours the artifacts themselves live for.
So a usage-based price is not merely unagreed. The thing that would substantiate an invoice under it does not exist yet. That is written into Partner Terms §12 as well, so it cannot be quietly assumed away in an order form.
2. What the unit would be
Two candidates. Choosing between them is a real commercial decision, not a formatting one. Both are set out here so you can push back on the wrong one before it is written into your order form.
| Candidate unit | What it counts | Argues for | Argues against | Rate |
|---|---|---|---|---|
| Per session | One POST /v1/sessions — one customer, one consent flow, whatever it returns | It matches the work: the consent pages, the scan and the unlock attempts happen once per session whether it yields ten documents or none | You pay for a session that returns nothing, and today a session can correctly return nothing | [to be confirmed] |
| Per delivered document | Each entry in GET /v1/sessions/:id/documents | It matches the value: you pay for the statement you actually received | It prices the outcome, not the cost, and a large mailbox is many times the work of a small one at the same rate | [to be confirmed] |
Which of the two is used — or some combination, such as a session fee with a document component, a platform fee with either, a minimum, or a volume arrangement — is [to be confirmed]. So are the currency, the treatment of taxes including GST, the invoicing frequency and the payment terms.
3. What a price would cover
Whatever the unit turns out to be, it buys the whole path rather than a stage of it. There is one service and there are no feature tiers:
- Both consent steps — Google's own screen, and the FinLens page that names your company, the document categories and how far back we will look.
- The scan — 18 months across registered financial senders by default, unbounded history for institutions you name at intake and for insurers, with each message checked to have genuinely come from the institution it claims.
- Unlock attempts on password-protected statements, derived from the four identity fields you supplied.
- Extraction, run in our own containers with no third party in the pipeline and no person reading anything.
- Delivery of both outcomes — extracted, the PDF plus its machine-read JSON, and delivered_unparsed, the PDF with a specific reason naming the identifier that would have opened it. A document we could not open still ships.
- The webhook notification, and the three hours in which you pull.
The API's single rate limit — 120 requests in 60 seconds — applies to every client identically. It is not a pricing tier, and there is no tier above it. If it is the wrong ceiling for your volume, that is an engineering conversation rather than a commercial one.
4. The questions a price has to answer first
These are the edge cases that decide what an invoice actually says. None of them has an answer yet. They are listed rather than left for a dispute, because each has already been argued about internally, and every one is [to be confirmed]:
| Case | What has to be decided |
|---|---|
| A session that finds nothing | Chargeable or not. Today this is a common outcome: only 11 of 187 registry entries are verified and the rest emit no queries — see integration docs §1. |
| A customer who declines | Whether a session that ends consent_declined costs anything at all. The work stops before the mailbox is touched. |
| A locked document | Whether delivered_unparsed counts as a delivered document. You receive the PDF and a specific reason, but not the extracted data. |
| A missed window | Whether a fresh session, made necessary because the three hours closed before you pulled, is charged again. It costs your customer a second consent either way. |
| A scan that retries | A stalled scan is picked up again automatically. It is one session and must be one charge, however many times the work runs. |
| Duplicate documents | The same statement can arrive in a mailbox more than once. Whether that is one unit or two. |
| What a first engagement looks like | Its shape, length and commercial terms. Nothing about a first engagement is standardised, because there has not been one. |
If you are evaluating FinLens, put these questions to us directly. An answer given in a conversation and written into your order form is worth more than a figure on a public page, and it is the only kind of answer that exists right now.
5. How you actually get access
There is no signup form, no plan selector, no free tier, no trial and no sandbox to provision yourself into. API credentials are issued by hand, by an operator, one client at a time.
That is a deliberate property rather than a missing feature. The consent page your customer reads names your company, and a credential anyone could mint by filling in a form would put a name on that page that nobody checked.
What onboarding is, in order:
- A conversation. The useful first one is about which documents you ask customers to upload today, and what happens when they do not. We will tell you plainly which of them we can fetch and which we cannot. The enquiry form on the home page is the way in; it composes an email rather than submitting anything to a server.
- Commercial terms in writing. The unit, the rate and everything in §4, agreed for you specifically and recorded in an order form alongside the Partner Terms.
- Your registered name. Exactly as it appears on the contract, because it is the string an individual reads in the sentence asking them to hand over their Gmail. There is no rename anywhere in the platform, so a wrong name means being provisioned again as a new client.
- An operator provisions you. One command creates the client, mints an API secret, seals it under the deployment's key-management service and prints it once. It is not recoverable — not by re-running the command, not from the database, not by us. You receive a key id and that secret over a channel one would send a password over.
- You register your webhook yourself, with POST /v1/webhooks, and receive its signing secret once on the same terms.
Nothing about that sequence is instant, and none of it is self-service. If you need to be live this week, say so in the first conversation rather than after it.
6. Your customer is never charged
FinLens does not charge the individual whose mailbox is read anything, ever. There is nothing for them to buy, subscribe to or cancel. There is no account and no payment step anywhere in the connection flow. The commercial relationship is with the business that made the request.
That is not a pricing decision we could revisit quietly. Terms of Service §1 states it to them directly, and Partner Terms §12 forbids a client from presenting a FinLens fee to them. Nothing agreed on this page may contradict either.
7. What is not for sale
Some things are absent from this page because no price has been set. These are absent because they do not exist, and no amount of money produces them today:
- No service level or uptime commitment, at any price. There is no tier that buys one, and nothing on this site creates one by implication.
- No support plan. There are addresses, in Partner Terms §17, and no committed response time behind them.
- No sandbox, test mode or fixture data — free or paid.
- No security certification. No CASA, ISO 27001 or SOC 2, and no third-party penetration test. Trust page §11 records it and §14 lists everything else that is not true yet.
- No priority queue, dedicated capacity or reserved throughput. One rate limit, the same for everyone.
- No data beyond your own customers' documents. Nothing aggregated, nothing pooled across clients, no benchmark and no dataset. Tenant isolation is the control the whole design turns on, and no commercial arrangement can loosen it.
8. Starting the conversation
Tell us what you collect from customers today, roughly how much of it there is, and what happens when someone does not send it. That is enough for us to say whether FinLens can fetch it, and enough for a first conversation about what it would cost.
Enquiries · the form on the home page
Partnerships · hello@finlenstech.com
Commercial terms and this agreement · partners@finlenstech.com
Integration and API access · developers@finlenstech.com
Read Partner Terms for what integrating commits you to, the integration documentation for what the API does and does not do, and the trust page for what is built and what is not. Each of them is written to be read before a contract rather than after one.
Value Garage Private Limited · CIN U66190DL2025PTC453505
Registered office: Flat no. 26, Vandana Apartment, East Delhi, Delhi, India — 110092