Coming soon — onboarding partner institutions

Technology Service Provider · Nepal

Lending infrastructure for Nepal

Khepee gives licensed banks and financial institutions a complete digital lending stack — borrower app, officer console, decision engine and audit trail — engineered to Nepal Rastra Bank’s digital lending requirements from the first line of code.

  • You hold the NRB licence. We hold the technology.
  • No NRB application, no capital requirement on your side.
  • Money never passes through Khepee — it moves on your rails.

The gap

Licences without technology

Nepal has no shortage of institutions permitted to lend. What most lack is the software to do it digitally — and building that in-house is a multi-year commitment few boards will make.

Lending on paper today

  • Applications arrive on paper and are keyed in twice
  • KYC documents live in a filing cabinet
  • Credit decisions vary by whoever is on duty
  • Reporting to NRB is assembled by hand each cycle
  • A borrower waits weeks and cannot see progress
  • Nobody can reconstruct why a loan was approved

Lending on Khepee

  • Borrowers apply from their phone in minutes
  • Documents captured, encrypted and verified digitally
  • Every decision scored against the same rules
  • Compliance extracts generated from the audit trail
  • Status visible to the borrower at every step
  • Every state change permanently recorded with a reason

How it works

They lend. We are the rails.

Under Nepali law only licensed Banks and Financial Institutions may disburse loans. Khepee does not try to become one. It operates as a Technology Service Provider: the partner BFI is the lender of record, and Khepee provides everything else.

  • The BFI holds the licence, the capital and the borrower relationship
  • Khepee provides origination, KYC, decisioning, servicing and reporting
  • Funds move on the BFI’s own rails — Khepee has no settlement account
  • No licence application, no paid-up capital, no prudential filing for either side
NRB licence

The platform

The whole lending lifecycle, in one system

Eight modules that together take a borrower from install to closed loan — and give your officers one place to work rather than six.

  • Origination

    Borrowers apply from the app. Your officers work a single ordered queue instead of a pile of forms.

  • Digital KYC

    Document capture, liveness and a verification workflow. Vendor-agnostic, so you are never locked in.

  • Credit decisioning

    A rule-based scorecard with a clean seam for bureau data or your own models. It advises; your officer decides.

  • Disbursement

    Khepee instructs and records. Your rails move the money and remain the source of truth.

  • Servicing

    EMI schedules, repayment tracking, overdue flagging and reminders in Nepali or English.

  • Collections

    Overdue accounts surfaced early with a clear escalation path, not discovered at month end.

  • Reporting

    Portfolio views for your team and exportable extracts for NRB, drawn from the audit trail.

  • Borrower app

    iOS and Android, in Nepali and English, so the borrower can see exactly where they stand.

Compliance

Regulation as architecture, not a checklist

Most systems treat compliance as a policy document and hope people follow it. Khepee encodes it. The regulatory limits are constants in one file, enforced server-side, and covered by tests that fail the build if a rule is weakened.

  • Loan ceilings of NPR 500,000 and NPR 200,000 enforced at four independent layers
  • The 36-month tenure cap applied at schema, service and database level
  • No route through the application state machine reaches disbursement without verified KYC
  • Every read of borrower data declares a purpose, and that purpose is logged
  • An append-only audit trail — corrections are new entries, never edits
no bypass exists

Multi-tenancy

Your data is yours alone

Khepee serves several partner institutions from one platform, and no institution can observe another — not in a list, not in a count, not in an error message. Cross-tenant lookups return “not found” rather than “forbidden”, because a “forbidden” would confirm the record exists.

  • Every query is pinned to your institution by the access token, not by a request parameter
  • Your loan products, limits and branding are configured independently
  • Khepee’s own staff cannot read your borrowers’ personal data — the permission does not exist for them
  • Borrower records are scoped to the institution they applied to, never pooled

What changes

The numbers that matter to a lending book

Indicative targets for a digital lending operation running on Khepee. Actual figures depend on your credit policy and approval workflow — we will model them with you before you commit.

  • Minutes

    To apply
    A borrower completes an application on their phone, not across three branch visits.

  • 36 mo

    Maximum tenure
    The NRB cap, enforced in code — a product cannot be configured above it.

  • NPR 5L

    Ceiling per borrower
    For salary and business account holders. NPR 2L for other account holders.

  • 100%

    Of state changes audited
    Every transition carries an actor, a timestamp and the ruleset version in force.

Engineering

One language, end to end

TypeScript across the entire platform, with the regulatory constants, domain types and validation schemas shared between the API, the console and the mobile app. A limit cannot mean one thing on the server and another in the app, because they are literally the same file.

  • Next.js for the marketing site and the operations console
  • Expo React Native for the borrower app on iOS and Android
  • Node, Express and MongoDB for the API and the system of record
  • Shared types, Zod schemas and NRB constants, verified in CI so nothing drifts

Who it is for

Built for the institutions that already hold the licence

  • Commercial & development banks

    Class A and B institutions launching a digital retail lending product without diverting the core banking roadmap.

  • Finance companies

    Class C institutions that need a modern origination and servicing stack to compete on speed.

  • Microfinance institutions

    Class D institutions reaching borrowers digitally without giving up the field relationship that makes the model work.

Who builds it

A product of Lacspace

Khepee is built by Lacspace Corporation Pvt. Ltd., a technology company registered in Nepal and India with software already running in production. You are not being asked to bet on a prototype from a first-time team.

  • LSKhata — billing, inventory and accounting for small businesses
  • POS Master — point of sale and restaurant management
  • iSmartClass — school ERP and learning platform
  • Lacspace One — the group’s super app

Straight answers

The questions we are actually asked

Does Khepee need a licence from Nepal Rastra Bank?
No. Khepee provides technology, not credit. The partner institution already holds the NRB licence and remains the lender of record. There is no licence application or capital requirement on Khepee’s side, and none is created for the partner either — they use the licence they already have.
Is Khepee approved or regulated by NRB?
No, and we will not say otherwise. Khepee is a technology company; NRB licenses financial institutions, not software vendors. What we can say accurately is that the platform is engineered to comply with NRB’s digital lending requirements, and that loans originated on it are issued by an NRB-licensed partner.
Does money ever pass through Khepee?
Never. There is no method in the platform that moves funds into an account Khepee controls — the payment interface can only instruct your rails and read back the status they report. Your institution holds and moves the money throughout.
Who owns the borrower relationship and the data?
Your institution. Borrower records are scoped to your tenant, and Khepee’s own administrators are not granted permission to read borrower personal data. Data collected for your lending process is used only for that process.
What about peer-to-peer lending?
P2P lending is not currently permitted in Nepal. NRB has issued a consultative document and a white paper, but no regulation. Khepee does not operate a P2P model. If NRB opens that route — most likely through its regulatory sandbox — the same platform core would serve it, but we will not run ahead of the regulator.
When can we start?
Khepee is pre-launch and we are onboarding partner institutions now. The practical first step is a technical and compliance walkthrough with your team, which we can usually schedule within a week.

Coming soon

Be the institution that launches first

We are selecting a small number of partner institutions for the initial launch. If you hold an NRB licence and want a digital lending product without building an engineering team, we should talk.