Link an account via consent, never a password
Purpose, scope, window and expiry as real columns, validated against each other. Needs an RBI-licensed Account Aggregator client before any data can flow.
Needs a keyBanking Information Assistant
“The statement is forty pages of a font nobody chose, and the only thing I actually need to know is why the balance dropped in March.”
Ask your bank statement a question, and get an answer you can check.
A bank statement is a wall of narrations, reference codes and running balances, and the one question you actually have — why did this drop, what's this recurring charge, am I ready to walk into a bank and ask for a loan — is buried somewhere inside it, not answered by it. Reading five statements from five accounts by hand to find one pattern is not a reasonable ask of anyone running a business. Dena is information only — it cannot move money, cannot store a card number, and never scores or lends.
The narrowest boundary in the product
Read-only, by consent, alwaysNo score, no verdict, no lenderCannot store a card number
How it works
Link, see, get ready.
Three steps, and the third one refuses the one thing every competitor in this category quietly implies: a verdict on whether you'd get the loan.
- 01
Link, with consent
Approve a time-bound, purpose-bound consent inside your own bank's or Account Aggregator's screen — never inside Dena, and never by handing over a password. Dena receives read-only data through the licensed AA channel only, and never sees or stores your net-banking credentials.
- 02
See it plainly
Balances per account, a searchable transaction timeline, recurring payments spotted by pattern, and a plain-language cash-flow summary — all read-only, all describing the past. Ask a question about a statement and every answer cites the specific transactions behind it, so you can check it yourself rather than trust it blind.
- 03
Get ready, not scored
A loan-readiness checklist reports which standard documents are present or missing against your own connected data — and pointedly returns no score, no eligibility verdict, no rate and no lender. Those are lending decisions, and Dena is not a lender.
The branch you'd otherwise queue at to ask what a transaction was. Dena answers that from data you've already consented to share.
Your consent, your control
Every linked account, with what it can see and for how long.
Purpose, scope, data window and expiry are columns on the consent itself, validated so a request cannot ask for more than its stated purpose needs. Revoking here stops any further pull immediately — and approving a consent only ever happens inside your own bank's or AA's own screen, never inside Dena.
- Dena never asks for or stores net-banking ID, password, card PIN or an OTP.
- Every consent, live and dead, is listed with its scope and expiry.
- Revocation is recorded immediately, not after a third party gets around to answering.
See it, don't hunt for it
Every linked balance in one place, marked stale when it is.
Balances are totalled per currency — never merged into one blended figure that means nothing — and marked stale past 36 hours instead of shown with false confidence. This is a read path only: there is no route here that can trigger a transfer, standing instruction or debit.
- One screen for every linked account instead of five separate bank apps.
- Freshness is stated plainly, not implied.
- A scheduled refresh needs the Account Aggregator connection to be active.
Before you walk in
Which documents you have — never whether you'd get approved.
Six documentation categories checked against what is actually in the register: present, missing, unknown, or not applicable. No score, no eligibility verdict, no approval probability, no interest-rate estimate, and no lender named anywhere in the response — those are regulated credit-advisory activity Dena stays out of entirely.
- Built from publicly known categories of lender paperwork, not a proprietary model.
- Available today, with no credential required beyond what's already linked.
- Never returns a number that could be mistaken for a credit score.
A second look
Statement tampering and odd entries, flagged with their evidence.
Running-balance tally, duplicate entries, date ordering, period gaps and round-figure clustering all run on imported rows, each flag carrying exactly what triggered it. This is advisory to you alone — Dena certifies nothing to a third party and never shares a flag with a lender, landlord or regulator on its own.
- Every flag names its evidence — never a bare 'suspicious' label.
- There is no verdict column anywhere in the response.
- Font and metadata forensics need the original file, not a photographed copy.
What it does
Fifteen things Dena does today.
Each label is derived from the backend's own capability module — not written on this page.
See and revoke every permission
Every consent live and dead, with scope, purpose and expiry, and one-call revocation recorded immediately.
Works todayEvery balance, one screen, marked stale honestly
Latest balance per account with its age, totalled per currency rather than merged into one misleading figure.
Built, with limitsEvery transaction, searchable, across accounts
Filter by account, date, direction, amount band and free text — or POST the same filters as JSON for a multi-value query a query string can't express. A keyword-rule classifier fills a blank category on import, but your own category always wins, and every category records whether you set it or it was guessed. Narrations are masked of long digit runs on write. No credential needed.
Works todayMoney in versus money out, plainly
Inflow, outflow and net by day, week or month, template-filled from the totals rather than model-written. No projection.
Works todayRepeating debits and credits, spotted for you
By counterparty and cadence, with the next date labelled an estimate. Observation only — nothing creates, changes or cancels a mandate.
Works todayAsk a statement a question, get a cited answer
A searchable, citable transaction store means any answer can point at the line items behind it. Parsing an uploaded PDF needs OCR; questions need an LLM key.
Built, with limitsTampering and odd entries, with evidence
Balance-tally checks, duplicate detection, date ordering and round-figure clustering on imported rows — plus, when you supply the document's own bytes, byte-level checks for an incremental re-save, a modification date before the creation date, or more than one producing application. Every flag carries its evidence and none is a verdict. No library, no credential, nothing stored.
Works todayBank credits against declared GST turnover
Lines up credits for a period against a turnover figure you supply — now saved once instead of re-typed on every read — with the standard caveat about non-turnover credits. Never a tax opinion. Automatic fetch from GSTN or a GST Suvidha Provider isn't built; that needs a real client written for it, not a key pasted in.
Works todayPresent, missing, unknown — never a verdict
Six documentation categories against what's actually in the register. No score, no verdict, no rate, no lender named.
Works todayOne combined statement, watermarked — JSON, CSV or PDF
Every linked account's transactions for a period, compiled and watermarked as informational only, generated on request and not stored. All three formats come from one compiled payload, so they cannot disagree about a figure.
Works todayA warning the moment a balance drops
Owner thresholds evaluated the moment a balance is recorded, with each breach written to an event log. Delivery needs a notification provider.
Needs a keyUPI, NEFT, RTGS and IMPS, explained
Timing, typical limits and normal use, attributed to published RBI and NPCI guidance. Every response repeats that Dena cannot use any of these rails.
Works todayEvery linking request, one list
Status by state across every AA-mediated linking request, with a queryable status history per consent and an expired one swept automatically. Live updates from the aggregator need its webhook, verified by an HMAC-SHA256 signature this deployment hasn't configured yet.
Needs a keyAny banking term, explained plainly
Eighteen curated terms from a closed catalogue — no model, nothing to hallucinate. Advice and eligibility questions are refused with a redirect.
Works todayRead-only access for your accountant
Invite an email address to a read-only link — a hashed bearer token, never a second platform login — defaulting to a summaries-only role; a viewer role additionally reaches the consolidated export, and neither reaches a raw transaction's narration or counterparty. Invite, role change and revoke are all real and logged. The invite emails itself if this deployment's mailer is configured; either way the same link is handed back for you to share by hand, so nothing here waits on a credential.
Works todayWhat Dena will never do
Not a roadmap gap. A boundary.
Dena is Domain.BANKING — the narrowest boundary in the product. Each of these is enforced by an absence in the schema, not a rule in prose.
It cannot store a card or account number
An identifier is reduced to at most its last four digits on the way in, and anything that looks like a Luhn-valid 13-19 digit card number in free text is rejected before it is ever stored. This is not a policy Dena follows — the schema has no column that could hold the rest of the digits.
It never moves money, and structurally cannot
There is no payee or mandate column anywhere in Dena's schema. Every route is a read against data already fetched under consent — no route exposes an action that could resubmit, reverse or trigger a payment, standing instruction or transfer.
No credit score, no eligibility verdict, no lender
The loan-readiness checklist reports document completeness only. Approval probability, an interest-rate estimate, and naming a lender are all regulated credit-advisory activity, and none of them exist anywhere in the response.
It never certifies a statement's authenticity to anyone else
Integrity flags are advisory to you, the owner, alone. Dena is not a KYC utility: a flag is never shared with a lender, landlord or regulator without your own separate, explicit action.
Not sure which one
Laxmi, Khata or Dena — which one do I want?
All three touch money, and from outside it will not be obvious which to open first. This page will not pretend the line between them is cleaner than it is.
Laxmi
Running the business day to day — what you're owed, what you owe, a forecast, a budget. This is operational cash flow, not the books themselves.
Khata
The actual double-entry ledger, kept in a state your accountant can review. Khata does not replace your CA — it stops at handing the CA a reviewable pack.
Dena
Read-only banking information pulled from your own accounts with your consent — statements, balances, a loan-readiness checklist. It cannot move money and is not a lender.
There is an open question inside the product about whether Laxmi and Khata eventually merge into one ledger. Dena stays separate from that question either way — its boundary is information only, and that doesn't change based on how the other two settle.
Before you switch
Read your own statements before you decide anything.
Tell us which accounts you'd want linked and we'll tell you plainly what Dena can show today — and what still needs an Account Aggregator connection.
Questions
Straight answers.
Does Dena ever ask for my net-banking password?
No, and it structurally cannot use one even if you tried to give it. Dena is a Financial Information User equivalent, receiving data only through an RBI-licensed Account Aggregator channel. It never asks for or stores net-banking ID, password, card PIN or an OTP, and it holds no signing authority over any account.
Can Dena move money, set up a standing instruction, or pay someone?
No. There is no payee or mandate column anywhere in the schema, so there is nothing for a route to write even if one tried. The recurring-payment detector only reports a pattern it has observed — it never creates, modifies or cancels a mandate.
Will the loan-readiness checklist tell me if I'd get approved?
No. It reports which of six standard documentation categories are present, missing, unknown or not applicable against what's actually linked — nothing more. There is no score, no eligibility verdict, no approval probability, no interest-rate estimate and no lender named anywhere in the response. Dena is not a lender and does not pretend to predict one's decision.
Can Dena store my card number?
No. Any account or card identifier is reduced to at most its last four digits the moment it's written, and free text containing what looks like a full, Luhn-valid card number is rejected outright before it reaches storage. This is enforced by the code that writes the row, not a policy someone could forget to apply.
If Dena flags a statement as suspicious, who finds out?
Only you. A flag names its evidence — a broken running-balance tally, a duplicate entry, unusual round-figure clustering — for your own review. Dena is not a KYC utility and never shares a flag with a lender, landlord or regulator without your own separate, explicit action.
I already use Laxmi or Khata — do I need Dena too?
All three touch money, and from outside it will not be obvious which to open first. This page will not pretend the line between them is cleaner than it is. Laxmi: Running the business day to day — what you're owed, what you owe, a forecast, a budget. This is operational cash flow, not the books themselves. Khata: The actual double-entry ledger, kept in a state your accountant can review. Khata does not replace your CA — it stops at handing the CA a reviewable pack. Dena: Read-only banking information pulled from your own accounts with your consent — statements, balances, a loan-readiness checklist. It cannot move money and is not a lender.