The platform
One stack, install to closed loan
Khepee is not a point solution bolted onto a core banking system. It is the full digital lending lifecycle — the borrower’s app, your officers’ console, the decision engine and the audit trail — designed as one system so nothing has to be reconciled between parts.
Four surfaces
Everyone gets the interface built for them
A borrower and a credit officer need very different things. Building one interface for both is the compromise that makes most lending software unpleasant to use.
Borrower app
Expo React Native on iOS and Android. Apply, complete KYC, track status, view the EMI schedule — in Nepali or English.
Officer console
One ordered queue, complete borrower context, and approve or reject with a reason that lands in the audit trail.
Admin panel
Your institution’s own settings: loan products, limits, staff roles, branding and reports.
API
The system of record, with a documented contract for integration into your core banking or reporting stack.
Module 1
Origination that respects everyone’s time
The borrower fills in one form, once, from their phone. Your officer sees a complete file with the KYC already verified and the score already computed — not a stack of paper to key in.
- Progressive application — a borrower can stop and resume without losing work
- Live limits fetched from the server, so the app never offers an amount you cannot approve
- Duplicate detection before submission, not after
- Officers work an ordered queue with SLA visibility
Module 2
KYC that cannot be skipped
Document capture, optional liveness, and a verification workflow your officers control. The important part is structural: there is no path through the platform that reaches disbursement without verified KYC, and no override flag exists to create one.
- Citizenship, national ID, passport, driving licence and voter ID supported
- Documents encrypted at rest; images stored as keys, never public URLs
- Liveness sits behind an interface — switch vendors without touching the workflow
- Every verification decision carries a reviewer and, on rejection, a written reason
Module 3
Decisioning that advises, never replaces
A rule-based scorecard produces a score and a recommendation. A human makes the decision. That division is deliberate: an automated rejection a borrower cannot get an explanation for is a reputational and regulatory problem waiting to happen.
- Configurable scorecard — income multiple, existing obligations, KYC quality, history
- Recommendation surfaced with the factors that drove it, not as a black-box number
- A clean interface for a credit bureau feed or your own model, when you want one
- The officer’s decision and reason are what the audit trail records
Module 4
Disbursement on your rails
Khepee constructs the disbursement instruction, records it, and reconciles the status your systems report. It does not hold, route or touch the funds — and structurally cannot, because the payment interface has no method that would.
- Idempotency keys, so a retried instruction never disburses twice
- Your institution remains the source of truth for money movement
- Reconciliation against the status your rails report, not an assumed outcome
- Failures surfaced with the reason, and safe to retry
Module 5
Servicing without spreadsheets
EMI schedules generated in integer paisa so the last instalment always reconciles to the rupee. Repayments recorded against the schedule, overdue accounts flagged the day they slip, and reminders sent in the borrower’s own language.
- Amortisation computed in paisa — no floating-point drift across 36 instalments
- Overdue detection runs daily and escalates on your policy, not on someone remembering
- Reminders by SMS and push, in Nepali or English
- A borrower can see their own schedule and history, which cuts support volume
Module 6
Reporting drawn from evidence
Your portfolio view and your NRB extract come from the same append-only audit trail, which means they agree with each other and with what actually happened. No end-of-cycle assembly, no reconciliation between two versions of the truth.
- Portfolio position, ageing and disbursement volume, live
- Compliance extracts generated without a developer involved
- Every figure traceable to the underlying audited events
- The regulatory ruleset version in force is stamped on every record
Architecture
Multi-tenant from the first module
Tenancy was not retrofitted. It is Module 1, because everything else depends on it — a user must belong to an institution before they can have a role, and a borrower record must be scoped before it can be created.
- One platform, many institutions, completely isolated data
- Per-institution products, limits, branding and integrations
- Queries pinned to your tenant by the token, never by a request parameter
- A tenant is a lending entity — so the same core serves a future licence holder unchanged
Integration
Fits alongside what you already run
Khepee does not ask you to replace your core banking system. It owns the digital lending process and exchanges the minimum with everything else, which keeps the integration small enough to actually finish.
- Documented API with a stable versioned contract
- Vendor interfaces for KYC, SMS and payments — your existing suppliers, where possible
- Webhook and polling reconciliation, whichever your rails support
- No requirement to migrate historical loans before going live
The platform is software. The lending is your institution’s.
Khepee provides technology under a service agreement. It is not a bank or financial institution, does not lend, does not accept deposits and does not hold customer funds. Loan products, credit policy, pricing and approval decisions are set and made by the partner institution licensed by Nepal Rastra Bank. Khepee makes no claim of NRB licensing, approval or endorsement.
Coming soon
Walk through the platform with our team
A technical and compliance walkthrough with your credit and IT leads, usually schedulable within a week.