The statement was a PDF. Anyone could have edited it — Signzy Lending pulls bank data through India's Account Aggregator framework — structured, verifiable, and carrying a consent record instead of arriving as an emailed PDF.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
This page covers Lending — Account Aggregator and analysis. The rest of the marketplace:
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
Consent-based bank data and the signals derived from it — income regularity, obligations and cash-flow shape, with a consent artefact recording what was shared and why.
What consolidation actually replaces, dimension by dimension.
| Dimension | PDFs emailed by the borrower | Lending (Signzy) |
|---|---|---|
| Income proof | PDFs emailed by the borrower | AA data, direct from the bank |
| Provenance | Unknown and uneditable | A consent artefact with the pull |
| Parsing | Whatever format arrives | Structured on retrieval |
| Fraud context | A separate system | Onboarding signals on the same contract |
| Audit answer | Reconstructed under pressure | Recorded when it happened |
| What it is NOT | — | Not your credit policy, and not your model risk |
Account Aggregator is a PUBLIC framework: everyone retrieves the same data, so the analysis is what you are buying. Backtest it. And model risk, explainability and fair-lending scrutiny remain entirely yours.
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
India’s consent framework lets a borrower authorise their bank to share statement data with a lender, structured and verifiable with a consent artefact.
Derives income regularity, obligations, bounce history and cash-flow patterns from transactions. Analysis quality matters more than data access.
Combining the derived signals into something a credit team can act on. It informs a decision your policy makes — the thresholds, exclusions and approvals stay entirely on your side.
The record of what the borrower authorised, for what purpose and for how long. Easy to treat as plumbing, and it is part of the answer when a regulator asks how a decision was reached.
One consented path from Account Aggregator data to a credit signal — analysis your policy decides on, with the consent kept.
Signzy Lending reads cash flow with consent — income, obligations and the rest of the Signzy portfolio.
Pulls statement data through Account Aggregator, so it arrives structured with provenance, not as a borrower’s email attachment.
Derives income regularity, obligations, bounce history and cash-flow shape from transactions, where vendors actually differ.
Signals combined into a credit view your team can act on. The thresholds, exclusions and approval decisions remain entirely within your own credit policy.
What the borrower authorised, for what purpose, for how long. Part of the answer when a regulator or ombudsman asks how a lending decision was reached.
Shares a marketplace with onboarding, so identity checks and fraud signals reach the credit decision, not another system.
Records which data was pulled, under what consent and what the assessment returned, so decisions can be reconstructed.
Here’s what genuinely sets it apart — and exactly where it stops.
Statements once arrived as emailed PDFs — unverifiable, editable, needing parsing. Account Aggregator lets borrowers consent to banks sharing data directly, structured and verifiable, with a record of what was shared, by whom and why — part of a defensible answer to a regulator. Ask how vendors use AA data.
Account Aggregator is public, so every licensed participant gets the same statements. Vendors differ in interpretation: salary versus own-account transfers, seasonality versus decline, obligations missing from bureau files, real bounces versus bank errors. Test derived signals on your own past borrowers with known outcomes.
Lending shares a marketplace with Signzy’s onboarding and fraud APIs, so verified borrowers aren’t re-verified and onboarding fraud flags reach the credit decision, instead of sitting in separate systems. That only helps if you buy the other lines; standalone, Signzy competes on analysis quality.
The platform supplies data, signals and an assessment; your credit policy sets thresholds, exclusions and approval. You own model risk governance, explainability when borrowers or an ombudsman ask, and fair-lending scrutiny, since alternative data can correlate with prohibited characteristics. Plan the documentation gap.
Income you cannot verify, obligations off the bureau file, or borrowers with no history at all. Each points at a different part of this line.
Consent is part of the journey and the audit trail: a clumsy step costs completions, a sloppy record costs the audit.
Run derived signals against loans with known outcomes; with everyone reading the same statements, it’s the only real test.
Set thresholds, exclusions and what a score triggers. The model informs; your policy decides, and regulators read it.
Explainability, monitoring, drift and fair-lending review: ask what you get, and produce the rest before your first review.
Alternative signals can correlate with prohibited characteristics. Test for that on a schedule, not after a complaint.
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
“The consent trail mattered more than we expected. When our auditors asked how we sourced income data, it was a record rather than a reconstruction.”
“The signals looked good in the demo, but we needed to backtest them against our own loans with known outcomes.”
“Ask what documentation you get for the model risk committee. We had to produce a fair share of the explainability material ourselves.”
“Every vendor gets the same AA statements; we were really buying the interpretation, which is worth testing properly.”
Analyst firms bury this view behind paywalls, and review-site grids score satisfaction, not fit for your estate. So here’s TechBag’s synthesis of the alternative lending data market — tap any vendor to see why it sits where it does.
Execution strength vs product vision — the classic market map, minus the paywall.
AA with consent trail, on one contract.
The grid nobody publishes — the strength of the consent and audit record vs quality of the derived cash-flow signal.
Derived signals plus the audit artefact.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Against emailed statements, a bureau score alone and an in-house AA build — on provenance, analysis and who owns the decision.
| Dimension | Signzy Lending | Emailed statements | Bureau score alone | In-house AA build |
|---|---|---|---|---|
| Data provenance | AA with consent record | Unknown | Bureau-sourced | AA, yours |
| Income visibility | Derived from cash flow | Manual reading | None | Yours to build |
| Analysis quality | Test it yourself | Analyst judgement | N/A | Your data science |
| Who owns the decision | You do | You do | You do | You do |
| Model risk documentation | Ask for it | Human rationale | Bureau-supplied | Yours to produce |
| India data residency | Named region | Your inbox | In India | Your servers |
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Drag the sliders (monthly applications; average loan margin). Estimates model applicants declined for unverifiable income plus the manual effort of reading statements by hand. Illustrative.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Quote-only — Signzy publishes no price. TechBag scopes the billing unit, the AA integration and the backtesting effort, then quotes in INR with GST.
Best when you cannot verify income
Best for a broader rollout
Best across the journey
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Tell us your requirements and current tools — we’ll model it against what you spend today.
Take this into your next vendor call — including ours.
What can you not see today — income, hidden obligations, or no history at all? Each points at a different capability.
Can you run the derived signals against loans with known outcomes? AA access is universal; the interpretation is what you are buying.
Is the AA consent step clean for the borrower, and does it produce the record you will need at audit?
What explainability and monitoring material do you receive for your model risk committee? Expect to produce some yourself.
How will you test that derived signals do not correlate with characteristics you cannot lend on? That obligation is yours.
Is it documented that the model informs and your credit policy decides? A regulator will ask to see that.
Is in-country storage documented for your deployment? Bank statement data is sensitive under DPDP.
Is billing per consent, per pull or per assessment? Nothing is published, and the unit changes the economics at volume.
Backtest the derived signals against loans whose outcomes you already know — every vendor reads the same statements — or let a TechBag advisor scope the AA integration and the model risk file.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.