For licensed institutions

You hold the licence. We hold the technology.

Your institution already has everything the regulator requires — the licence, the capital, the customers. What it may not have is a digital lending stack and the engineering team to run one. That is the entire trade.

  • No NRB application and no additional capital requirement
  • Money never leaves your control — Khepee has no settlement account
  • You set the products, the pricing and the credit policy
  • Your brand faces the borrower
NRB licence

Why now

The window is open, and it will not stay open

NRB has issued a digital lending framework and opened a regulatory sandbox. The institutions that move first will define what a digital loan looks like in Nepal; the rest will compete against it.

  • A defined regulatory framework to build within, rather than ambiguity
  • Borrower expectations set by remittance and wallet apps they already use
  • Digital origination reaches borrowers your branch network does not
  • First-mover advantage in a market where few competitors have shipped

The division of labour

Two contributions, cleanly separated

What your institution brings

  • The NRB licence — the legal authority to lend
  • The capital and the balance sheet
  • Credit policy, pricing and risk appetite
  • The final approval decision on every loan
  • Payment rails and fund custody
  • The regulatory relationship
NRB licence

What Khepee brings

  • Borrower app for iOS and Android
  • Officer console and admin panel
  • KYC workflow and decisioning engine
  • Servicing, collections and reminders
  • Audit trail and NRB extracts
  • Engineering, hosting and support

Fair questions

What your compliance team will ask

Does this create a new regulatory obligation for us?
It should not create a licensing one. You are already licensed to lend; Khepee is a technology service provider under a service agreement, which is a procurement and outsourcing question rather than a licensing one. Your compliance team should still review the arrangement against NRB’s outsourcing and IT guidelines, and we will provide whatever documentation that review needs.
Who is liable if something goes wrong?
Liability is allocated in the service agreement. As a matter of substance: you remain the lender of record and own the credit decision, and Khepee is responsible for the technology performing as specified. We would rather negotiate this precisely up front than discover a gap later.
Is our borrower data shared with anyone?
No. Borrower data is scoped to your institution and is not pooled across partners. Khepee’s own administrators are not granted permission to read borrower personal data — the permission does not exist in the super-admin role. Data collected for your lending process is used only for that process.
What if we want to leave?
Exit terms belong in the agreement, and we will not make them punitive. Your data is yours: you receive a complete structured export of borrowers, applications, schedules and the audit trail. We would rather be chosen each year than locked in.
Can we use our existing KYC or SMS vendors?
Usually yes. Every external capability sits behind an interface, and the driver is configured per institution. If you already have a provider under contract, implementing against it is normal work rather than an exception.
Does Khepee touch our funds at any point?
No, and it structurally cannot. The payment interface has no method that moves money into a Khepee-controlled account. Khepee constructs and records the disbursement instruction; your rails execute it and remain the source of truth.

Isolation

Your data cannot be seen by another partner

Khepee is multi-tenant, and tenancy is the first module rather than a later addition. A lookup across institutions returns “not found”, never “forbidden” — a “forbidden” would confirm the record exists.

  • Every query pinned to your institution by the signed access token
  • Your products, limits, branding and integrations configured independently
  • Borrower records scoped to your institution, never shared
  • Isolation verified by tests, not asserted in a document

Getting started

What the first months look like

Indicative. The pace depends far more on your internal approvals than on our engineering.

  1. Week 1

    Technical & compliance walkthrough

    Your credit, IT and compliance leads see the platform and interrogate the architecture.

  2. Weeks 2–4

    Commercial and legal terms

    Service agreement, data processing terms, liability allocation and exit provisions.

  3. Month 2

    Configuration

    Your loan products, limits, roles, branding and vendor integrations set up in a test environment.

  4. Month 3

    Pilot

    A controlled cohort of real borrowers, with your officers making every decision.

  5. Month 4+

    Scale

    Wider launch, with reporting and reconciliation proven against your own systems first.

What you get from us

A partner, not a licence key

  • Named engineering contact

    A person who knows your configuration, not a ticket queue that starts from zero each time.

  • Compliance documentation

    Architecture, data flow and control documentation your compliance function can hand to an examiner.

  • Officer training

    Training for your credit officers on the console and the decision workflow.

  • Configuration changes

    Product, limit and policy changes made without waiting for a release cycle.

  • Regulatory updates

    When NRB revises a rule, the constants change and we tell you what moved and when.

  • Reliability commitments

    Availability, recovery and incident response defined in the agreement, not assumed.

Coming soon

We are selecting launch partners now

A small number of institutions for the initial launch, with more of our attention than a later cohort will get.