Docs

Releases/changelog

Changelog

What changed in each release of LoanPilot — new features, improvements and fixes.

32 sections

Every production deploy bumps the app version (shown at GET /api/health) and is recorded here. The npm SDK and MCP packages carry their own versions.

1.31.1 — 14 November 2026

  • Name gate accepts a surname-initial. A statement in the name "Mohan K" now matches a KYC/PAN name of "Mohan Karuppaiah" (the common Indian initial pattern) — a full given-name match plus trailing initials counts as the same person. Different spelled-out surnames and first-name-only initials still require review.

Flutter / Dart SDK — 14 November 2026

  • ippo_loanpilot published on pub.dev — the LoanPilot client for Flutter (iOS, Android, Web): statement analysis (upload / combine / waitFor), credit checks, customers, loans and products, with timeout / maxRetries / defaultHeaders and a baseUrl override. Mirrors the npm @ippopone/loanpilot surface. See SDK.
  • Pairs with ippo_agents (pub.dev) for the voice/chat assistant side — so a Flutter app can run the whole flow (talk to the borrower and analyse the statement) from an API key.

1.27.0 — 7 November 2026

Added

  • Loan servicing + monitoring (post-disbursal). Mirror a loan booked in the lender's system and layer servicing, DPD and top-up intelligence on top (LoanPilot never disburses or collects). New endpoints: POST/GET /v1/loans, GET /v1/loans/{id}, the repayment webhook POST /v1/loans/{id}/repayments (idempotent per loan on external_event_id), and GET /v1/customers/{id}/loans (loans + top-up headroom). Mirrored in the SDK (lp.loans.*) and MCP (create_loan, list_loans, get_loan, add_repayment, get_customer_loans).
  • DPD / NPA + monitoring clocks. Repayments reconcile against an EMI/EDI schedule and bucket days-past-due (0 / 1-30 / 31-60 / 61-90 / 90+). A daily servicing clock re-derives DPD for every live loan — a missed EMI becomes an alert with no lender event — and live-loan DPD folds into the borrower's health (watch / stress) and raises a dpd alert. A 30-day bureau re-pull clock is included but off by default (a paid enquiry).
  • Top-up / renewal. A borrower's repayment capacity net of the live EMI, gated by seasoning and clean DPD, shown on a new Loans tab on the borrower profile, with a renewal prompt once a loan closes.

Fixed

  • Hardened the recurring Account Aggregator monitoring sync (purpose-104): it now collects a fetched statement every tick and requests a fresh pull once per interval, so a statement is never ingested a cycle late or missed; and a multi-account monitoring consent stays in monitoring after the officer's pick.

1.15.0 — 6 November 2026

Added

  • Borrower KYC profiles. Each customer now carries a KYC profile — age/DOB, gender, marital status, dependents, residence (address, owned/rented, years), employment type, occupation/employer, declared monthly income, loan purpose and amount/tenure requested, spend region, and declared existing loans. Read it with GET /v1/customers/{id}/profile and upsert it with PUT (partial — only the fields sent are written; null clears one). It is refreshed on repeat lending. GET /v1/customers/catalog returns the controlled KYC vocabulary the profile and business bodies validate against.
  • Multiple businesses per borrower. A person can run several businesses, each with its category (a 76-category India vocabulary in 14 groups), legal type, GSTIN, vintage, turnover, employees, premises type and shop location. CRUD at /v1/customers/{id}/businesses. Each business is returned with a derived climate classification (none / low / medium / high + drivers) — climate is classified, not asked — and a cross-business portfolio aggregate appears on the customer detail.
  • Location, market & climate intelligence. POST /v1/customers/{id}/businesses/{businessId}/enrich fetches a live read of a shop's trade area — competition density, local-market quality, business reputation, demand trend, a current-market snapshot (nearby mix, open-now, rising Google-Trends queries), climate risk and a geo confidence level. It uses Google Maps with coordinates and Google Local with only a city/pincode; the climate signal comes free from Open-Meteo. Key-gated by APP_SERPAPI_KEY — inert and free without it.
  • Borrower-intelligence AI agent. POST /v1/customers/{id}/assess runs an advisory agent over the whole dossier — KYC, every business, the location/climate intelligence, the declared loans and the bank-statement monitoring signals — reasoning across every perspective (repayment capacity, business viability, local market, climate exposure, stability, leverage, data quality) and across base/stress/upside scenarios. It returns a summary, per-business assessments, a current-market analysis, a portfolio view, strengths, risks, a recommended stance, conditions and a confidence. It runs on the existing statement-AI stack (SARVAM_API_KEY), is metered the same way, and is advisory — never an automated lending decision. With no AI configured a deterministic rule-based profile score stays the only read. The customer detail now also carries profile, businesses, portfolio, profile_intelligence and intelligence + intelligence_at.
  • SDK & MCP. The SDK's Customers class gains catalog(), getProfile / putProfile, businesses / addBusiness / updateBusiness / removeBusiness, enrichBusiness and assess; the MCP server gains the matching tools. See the SDK and MCP server pages.

Config

  • APP_SERPAPI_KEY enables location / market intelligence (the Google current-market reader). The AI agent uses the existing SARVAM_API_KEY. Both are inert-safe when unset.

1.7.0 — 31 October 2026

Added

  • Opportunities tab. A new report tab beside Decision that leads with how much more could be lent and the ways to get to "yes" — why a limit is where it is, documents to ask the borrower for, and what would improve the decision — with total cost, EMI burden, head-room on each limit, and borrowing seen elsewhere.
  • Email sign-up and sign-in. Create an account with an email address and a verification code, then sign in with email + password (previously Google only), with a forgot-password reset.
  • Free statement allowance. A public self-sign-up gets a fixed number of statements (default 10); existing customers, invited teammates and the owner stay unlimited. A statement counts only when its analysis finishes — failed, rejected or re-run uploads don't count.
  • Credit-check Demo button — plays a full credit check with sample data.

Changed

  • Credit score tab — the Bureau tab is folded in, the bureau cards are redesigned in lender order, and the credit-check upload section is aligned with it.
  • Report header leads with how much can be lent.
  • Statements & Applications tables — a shared Alert column (quiet when clean) with an Alerts filter, a Bank column, a statements table that scrolls both ways with its header/name/actions pinned, and square bank logos.

Fixed

  • Bank detection decides by agreeing votes rather than points and never reads the IFSC from a transaction row, so fewer statements are matched to the wrong bank.

1.6.2 — 30 October 2026

Added

  • Delete a loan product. An admin can now delete a custom product from the Credit rules page (product menu → Delete product). The product and all its rule versions are removed; past reports keep the rules they ran with and are unaffected. The two shipped defaults (Monthly EMI, Daily EDI) can't be deleted — turn one off instead.

1.6.1 — 30 October 2026

Fixed

  • Creating a new loan product could fail with "Could not create the product." One bureau reason code was longer than its database column, so on the production database every new-product save (Credit card, Monthly EMI or Daily EDI) was rejected. The column has been widened and a test now guards every rule against its column limits. Existing products were unaffected.

1.6.0 — 30 October 2026

Added

  • Credit card product. A new, highly-configurable loan-product type in the rules engine alongside EMI and EDI. Its output is a revolving credit limit (not an EMI): the limit is sized from the bank statement — an income multiple, capped by FOIR headroom, risk-shaved by the bureau and statement, within min/max bands — with knockouts for low income, low bureau score, excessive bounces and write-offs. 13 configurable params (income multiple, limits, FOIR cap, APR, MAD %, interest-free days, cash-advance %, fees, score floor). The analysis dashboard shows a card-offer panel (limit, rate/APR, MAD, interest-free days, cash-advance sub-limit, fee). Off by default.

1.5.0 — 29 October 2026

Added

  • Full bureau data and a Bureau-vs-Statement comparison. Credit reports (Experian, Equifax, CRIF) are now read in full — identity, income, employment, addresses, score reason codes, secured/unsecured split, MFI exposure, enquiry windows, trends and per-loan detail. A new Bureau tab leads with a reconciliation of the bureau (the lenders' reported truth) against what we read from the bank statement — income, EMIs/obligations, total debt, recent borrowing, employment, address and delinquency — each marked agree / mismatch / bureau-only / statement-only with a plain note, to help the lender see where the story holds together.
  • Standalone bureau analysis — upload a credit report on its own (free, .json or .txt, no enquiry) and get the full bureau view without a bank statement.
  • Free credit-report upload for developers. The /v1 API, the SDK and the MCP server now expose the free upload too: a bureau_file part on POST /v1/analyses (and /v1/analyses/combine), a new POST /v1/credit-checks/upload, the SDK's bureauFile param plus creditChecks.upload(), and the MCP upload_credit_report tool (and bureau_report on analyze_statement/combine_statements). Auto-detected, no entitlement, no enquiry cost. SDK and MCP packages bumped to 0.2.4.
  • New optional rules-engine signals for the extra fields (income mismatch, MFI over-leverage, ever-written-off, undisclosed loan, recent loan not in cashflow) — off by default; turn on the ones you want.

1.4.8 — 29 October 2026

Added

  • Multi-bureau support and free credit-report upload. LoanPilot now reads Experian, Equifax (CIR) and CRIF High Mark reports, all normalized to the same underwriting model. Every user can upload a credit-report JSON for free on an analysis — the bureau is detected automatically and parsed, with no entitlement and no enquiry cost; it folds into the decision exactly like a fetched report. The paid "fetch by name + phone" API path is unchanged. The upload form offers a "choose your source" picker (Upload · Free | Fetch · Paid). One bureau per analysis.

1.4.7 — 26 October 2026

Added

  • Credit rules used — every report names the credit-rules version it ran on. The Policy button opens a read-only sheet of those exact rules, showing which fired and what they saw, even after your team edits its rules.

Changed

  • A cleaner report header — account, statement and file details sit on ruled lines instead of boxes, and the status chips fit on one row.
  • Clearer credit-check errors — when a credit check fails, you see what happened and what to do next (for example, check the name is exactly as printed on the PAN), with a Try again button where it helps.

1.4.6 — 25 October 2026

Added

  • AML / financial-crime signals — a new, optional layer of the rules engine that flags money-laundering typologies from the statement (structuring, funnel/pass-through, rapid in-and-out, cash-intensive, circular churn, round amounts, third-party funding, crypto/gambling counterparties, dormant-then-burst, return abuse, salary-spoofing) with stable reason-code keys. India-tuned to the Rs 10 lakh CTR line. It routes matches to manual review / enhanced due diligence and never auto-declines. Ships off by default; turn on the typologies you want in the rules engine.
  • Features pages at ippo.one/features — one page per capability, explaining what it is, how it works, and how it adds value.

1.4.5 — 25 October 2026

Fixed

  • Account-holder name showing as "Not Available" on some SBI statements. That template prints the name with an honorific and no "Name:" label (e.g. "Mrs. FIRSTNAME LASTNAME"); the reader now picks it up, and placeholder strings like "Not Available" / "N/A" can no longer be stored as a name. Balances and transactions were never affected — only the name field.

1.4.4 — 24 October 2026

Added

  • Duplicate alarm. A short alarm plays on the analysing screen when a statement is found under another holder — once per statement, louder when more copies are found. Turn it off from Sound alerts in the account menu.

Changed

  • Cash patterns that go both ways now show paid out, came back and net for each month and each party, so money coming back is never read as money going out.
  • Report header: a strip shows when a statement is reused under another holder. On phones the name is shown large, with sliding tabs and an easier actions sheet.
  • Upload: loan details and credit check are optional sections you add with one click; amounts in ₹ with Indian grouping, phone with +91, and a How it works strip with step times.
  • Credit rules: sections stack as you scroll; Add a rule is its own section with a full form.
  • Theme (Light, Dark, System) now sits in the account menu.

1.4.2 — 23 October 2026

  • Published the customer changelog cards for 1.4.0 and 1.4.1 to ippo.one/changelog; the marketing site was rebuilt. No app behaviour change.

1.4.1 — 23 October 2026

Fixed

  • The credit bureau now switches on from the rules engine. The analysis pipeline already decided whether to pull the bureau from the team's rules engine, but the upload form's gate (GET /api/features and the name/phone/consent capture on create) still read the old per-user credit policy — which lost its own page when it was folded into the team rules engine. So an entitled user could turn "Check the applicant's credit score" on in the rules engine yet never see the applicant fields on upload, and no report was fetched. All three bureau gates now resolve from the same source the pipeline uses (team rules engine, falling back to the user's flat policy). Admin entitlement (paid) is still required.

Added

  • GET /v1/me now returns user.is_admin (the platform-owner flag). Additive and backward-compatible, so sibling apps can reuse LoanPilot's single admin identity instead of keeping their own admin list — the LoanPilot Agents admin panel (agent.ippo.one/admin) now grants access to exactly the platform owners here, resolved over SSO on every /api/admin/* call.

1.4.0 — 23 October 2026

Added

  • Reused-statement detection. Every finished analysis is fingerprinted (MinHash over its transactions), so a later upload of the same statement — renamed, shuffled, date-shifted or trimmed — is found right after parsing, before any AI step. Flag only: no score change, no block.
    • Each match is rated red (same money under another holder), amber (same holder under another name or filed by a colleague) or grey (a re-check or re-upload).
    • Shown on the live scan, the report header, a Duplicates tab on the application, and an admin page.
    • Vendors are isolated: an upload is only ever compared with its own team's earlier uploads, never another vendor's. Rows every customer of a bank shares (charges, GST, interest, government transfers) are left out of the fingerprint.
  • New PDF tamper proofs: hidden text under a white overlay (shown old → new per page), an earlier saved version that differs (the PDF rewound to its first version with changed amounts/dates/balances shown old → new), and the bank's digital signature verified offline against the India CCA roots.
  • Mixed-font figure warning: an amount printed in a different font or size from the rest of its column.

Changed

  • File-history checks (non-bank tool, re-saved, extra versions, transaction dated after the PDF) no longer mark a statement as Fraud — they are warnings with the exact reason and a next step.

1.3.0 — 22 October 2026

Added

  • Credit rules page, redesigned. One page in the order a file is checked — loan terms, safety checks, credit bureau, red flags, approval, affordability, AI review — with each value in the units you think in (% a year, months, ₹, ×), per-loan-amount bands, and the shipped default a tap away.
  • Edits are a draft until you publish: a sticky bar counts unpublished changes, and Publish opens a review of every change old → new before it goes live as a new version.
  • Version history (GET /api/rules/products/{pid}/versions): every published version with who published it and when; restore an earlier one (POST …/versions/{vid}/restore).
  • Try on a file (POST /api/rules/products/{pid}/try): run the published rules and your unpublished draft on one finished application, side by side, without saving.
  • The rules API returns each rule's catalogue data_type and editor bounds.

1.2.2 — 19 October 2026

Added

  • Shared sign-on round-trip for sibling apps. LoanPilot is now the single identity provider (the Agents app owns no passwords). GET /api/auth/continue?next= signs the visitor in and returns them to next; GET /api/auth/signout?next= ends the shared session. next is validated to an https URL on this site's own registrable domain, so it can never be an open redirect.

1.2.1 — 19 October 2026

Added

  • Shared sign-on across *.ippo.one (APP_COOKIE_DOMAIN). The session cookie can be scoped to a parent domain (prod: .ippo.one) so one login works across app.ippo.one and agent.ippo.one. Default stays host-only, so local dev is unchanged.

1.2.0 — 19 October 2026

Changed

  • Database moved from SQLite to PostgreSQL in production (APP_DATABASE_URL=postgresql+asyncpg://…), ahead of the agent-platform work that needs concurrent writes. The app is backend-agnostic — SQLite is still fully supported and remains the default for local/dev. Added the asyncpg driver and a one-time ORM-based migration (server/sqlite_to_pg.py) that converts types, resets sequences and verifies row counts.

1.1.9 — 17 October 2026

Added

  • Multi-statement combine in the public API, SDK and MCP. The combine flow (2–6 statements for one account — same bank + account, continuous balances — merged into a single analysis) is now a first-class part of the developer platform: POST /v1/analyses/combine and GET /v1/analyses/{id}/original. SDK @ippopone/loanpilot 0.2.3 adds analyses.combine(...) and analyses.original(id); MCP @ippopone/loanpilot-mcp 0.2.3 adds a combine_statements tool.

1.1.8 — 16 October 2026

Fixed

  • Bank of Baroda statements silently dropped transactions. A mid-ledger "Page Total:" subtotal was treated as the end of the table, cutting every transaction below it. An end marker now ends the table only when no dated transaction follows it. A real 23-page Baroda statement went 404 → 442 transactions, all reconciling; zero regressions across the batch.

1.1.7 — 16 October 2026

Added

  • Download the original statement from any analysis — the PDF for a single upload, or a ZIP of the original files for a combined analysis. GET /api/analyses/{id}/original.

Fixed

  • More statements reconcile fully. When a bank prints the figure inside the narration under a narrow column, the amount read as zero; it is now taken from the running-balance change for any row that has no amount but a balance movement (can only fix a wrong row, never change a correct one). Many low-reconciliation statements now reconcile at 100%, with zero regressions.

1.1.6 — 16 October 2026

Added

  • Branded HTML emails in the landing-page style (account-approval notifications and team invites), each with a plain-text fallback.

1.1.5 — 16 October 2026

Added

  • Changelog page on the website (/changelog): every release as a dated, blog-style card.
  • Docs link in the landing header and footer.

Fixed

  • Docs sidebar/scroll: removed an overflow-x: hidden that broke Fumadocs' sticky sidebar and table-of-contents; wide tables/code now scroll within their own box.

1.1.4 — 16 October 2026

Changed

  • New sign-ups now require admin approval. A Google sign-in from an unknown e-mail creates the account but it stays inactive until an admin activates it, and info@ippo.one is e-mailed to review it. APP_SIGNUP_AUTO_APPROVE=true restores immediate access.

Fixed

  • Statement-parsing coverage: trailing stub pages, no-digit notes pages and irregular header spacing no longer reject or mis-parse a statement. Verified across a 1272-statement batch — ~99% of openable statements parse, nearly all at 100% balance reconciliation.

1.1.3 — 16 October 2026

Fixed

  • SBI (JasperReports) statements were rejected or failed to parse. That template labels only the Balance column, so header-based table detection found nothing. Added data-shape column inference: when a table has no usable header labels, roles are inferred from the data and debit vs credit is decided by reconciling each money column against the running-balance deltas. A 45-page SBI statement now parses all 594 transactions with every balance reconciling.

1.1.2 — 16 October 2026

Fixed

  • Landing module cards didn't render. The global security middleware sent X-Frame-Options: DENY on every response, blocking the same-origin /landing/cards.html iframe. The middleware now sends SAMEORIGIN for that one path; every other response stays frame-denied.

1.1.1 — 15 October 2026

  • New landing site is live at ippo.one.
  • The @ippopone/loanpilot SDK and @ippopone/loanpilot-mcp server were published to npm at version 0.2.2.
  • Fixed static assets (logo, preview image) on this documentation site.

1.1.0 — 15 October 2026

The configurable rules engine now truly owns the credit score.

Added

  • Score-adjustment rules drive the score. A team's Adjust the score rule is now a first-class action in the rules engine, with a signed points value. The points are applied to the final score before the band, decision, risk-based FOIR and loan offer are derived — one coherent decision pass.
  • 11 new rule-engine variables (from the bureau report and the bank statement we already parse): credit-history length, accounts ever 90+ DPD, currently-delinquent accounts, new loans in 6 months, overdue-to-outstanding %, debt-to-income %, 30-day enquiries, total accounts, total outstanding, minimum end-of-day balance, and total bounces. They appear automatically in the Add a rule picker.
  • Decision-trace audit now records the net score points the engine applied.

Changed

  • Knockout rules are stricter-only and clear the offer. A knockout can send an approval to manual review or decline — never loosen a decision — and a declined/referred file now shows no loan offer.
  • The engine's condition rules are evaluated inside the analysis pipeline and folded into the single decision pass (no separate overlay).

Fixed

  • GET /v1/analyses returned a server error in some cases — fixed.

Docs

  • The credit-rules-engine, scoring-layers and loan-products pages were rewritten end-to-end to match the engine exactly, including the full variable catalog and the five scoring layers.

1.0.0 — 15 October 2026

The developer platform and the configurable rules engine went live.

Added

  • Developer platform: public /v1 REST API, per-user API keys (scoped to your org), the @ippopone/loanpilot npm SDK, the @ippopone/loanpilot-mcp MCP server, mobile auth, and this documentation site.
  • Configurable credit rules engine: per-team, per-loan-product rulesets; a variable catalog; amount tiers; application inputs and LTV; bureau ⇄ statement obligation merge; a name/phone ownership gate; and a default EMI and EDI product for every team.