Origination

From intent to decision, without the paperwork

Origination is where most lending operations lose the most time — and where borrowers most often give up. Khepee makes the application short, the file complete, and the queue ordered.

The borrower journey

Six steps, one sitting

  1. Sign in with a phone number

    A six-digit code, no password to forget. Borrowers never hold a credential that can be phished.

  2. Choose a product

    Only the products your institution has published, with the limits it has configured.

  3. Pick an amount and term

    Bounded by the live server limits, so nothing is offered that cannot be approved.

  4. Complete KYC

    Document capture and, where you require it, a liveness check.

  5. Review and submit

    A plain-language summary of the amount, term, instalment and total cost before anything is committed.

  6. Track progress

    The borrower sees the real state — identity check, assessment, decision — not a silent wait.

The state machine

Eleven states, and no shortcuts between them

An application moves through an explicit state machine. Transitions that are not defined simply cannot happen — the platform denies by default rather than allowing anything not forbidden.

  • draft → submitted → kyc_review → credit_assessment → approved → disbursed → active → closed
  • Every transition records the actor, their role, the timestamp and the ruleset version
  • Rejections, cancellations and defaults require a written reason before they will save
  • A test walks every path in the graph and fails the build if any reaches disbursement without KYC

Limits

The app cannot offer what you cannot approve

The borrower app fetches the current regulatory and product limits from the server rather than hard-coding them. That keeps the interface honest, and it means a rule change reaches every installed app immediately.

  • NPR 500,000 for salary and business account holders; NPR 200,000 for others
  • A product may be configured lower than the ceiling, never higher
  • Amounts validated as integer paisa — a fractional amount is rejected outright
  • The server remains authoritative; a stale app produces a poor experience, never a bad loan
NRB CEILING

The officer view

One queue, complete files

Your officers do not chase missing documents or re-key forms. Each item in the queue arrives with the KYC status, the score, the borrower history and the reason it needs attention.

  • Ordered by age and priority, with ageing visible at a glance
  • Approve, reject or return for more information — each with a recorded reason
  • Approve for less than the requested amount where your policy allows
  • Borrower personal data revealed only under a declared purpose, which is logged

Data quality

Problems caught before they reach a decision

  • Duplicate applications

    Detected against the encrypted phone and document index before submission, not after two officers have worked the same file.

  • Incomplete files

    An application cannot be submitted without the fields your product requires. The borrower is told what is missing, in their language.

  • Stale KYC

    Verifications carry an expiry. An application whose KYC has lapsed returns to review rather than proceeding on old evidence.

Evidence

Every decision reconstructable, months later

When an examiner or a borrower asks why a loan was approved or declined, the answer is in the audit trail — with who decided, when, on what evidence, and under which version of the rules.

  • Append-only: corrections are new entries, never edits to old ones
  • Personal data appears in the trail as a hash, never in clear
  • The regulatory ruleset version is stamped on every entry
  • One request id ties a support ticket to the exact events behind it

Coming soon

See origination with your own products

We will configure a walkthrough using your loan products and your credit policy so you are evaluating your operation, not a generic demo.