Rent-to-Own Driver Financing Not built

Full product & system design

Let a driver finance their motorcycle through Drivra. Who else is already doing this and how, what Nepal's regulator actually requires, the full system architecture, the driver-facing journey, and how credit gets decided with no external bureau in year one.

Competitive landscape

A local competitor is already running this exact model

RYD Nepal (rydnepal.com) rents Hero Super Splendor 125cc motorcycles to Kathmandu gig drivers today. Founded 2025, self-funded, 120+ bikes, claims 500+ active riders, single-SKU fleet. Only one of their three plans actually leads to ownership (Pro Monthly, Rs 7,000/week, after 1.5 years), which is worth noting since most of their marketing describes "own the bike in 18 months" as if it applies broadly. KYC is driving license + citizenship copy only, under 30 minutes, zero down payment, no app (web form + WhatsApp + in-person).

Category-wide finding: none of these companies, RYD Nepal included, have any real, independently documented UX: no screenshots, no coverage on UX pattern libraries. A well-designed, actually-screenshotted, transparent driver experience would be a genuine differentiator on its own, separate from pricing or terms.
Full competitor table: RYD Nepal, global comparables, Nepal digital-lending UX

RYD Nepal's plans

PlanPriceLeads to ownership?
WeeklyRs 5,600/weekNo
Pro Monthly ("Best Value")Rs 7,000/weekYes, after 1.5 years
PrepaymentRs 21,000/month (Rs 700/day, cheapest per-day rate)No

Free service every 1,500km, 24/7 breakdown line, a replacement bike within 30 to 40 minutes if repair runs long, and a welcome "Sagoon kit" (helmet, phone mount, raincoat) plus a Rs 1,500 fuel coupon on pickup. Missed-payment mechanics are not disclosed anywhere public, marketed only as "no penalty fees, no credit-bureau drama." Trust signal: only three self-hosted testimonials, zero independent reviews found anywhere (no Trustpilot, Google reviews, Reddit), so their credibility is entirely self-curated, itself an opening.

Global comparables

CompanyMarketModelNotable mechanic
M-KOPAKenya, Uganda, Nigeria, Ghana, S. AfricaPAYG motorbike financing, KES 10 to 25k deposit + daily installmentsMissed payment extends the term with no penalty; can return the bike and walk away clean with deposit refunded. Strongest trust-building policy found in this research.
TugendeUganda, KenyaLease-to-own boda financing, about $120 down, about 82 weekly paymentsRequires a family guarantor plus 3-week training before financing, a soft underwriting layer. Builds its own proprietary repayment dataset via its own payments platform ("PayWay") rather than external bureau data.
Watu CreditEast Africa, plus Mexico/BrazilLease-to-own, under 2hr approval, "no credit history needed"Requires 6+ months of active mobile-money history as the alt-credit proxy. GPS remote-immobilize on default, 7-day redemption window. Real reputational problems: Facebook impersonation scams, consumer-advocacy complaints about collection conduct.
MooveAfrica, UK, India (Uber's financing partner)"Ride-to-own," up to 95% financed, 24 to 48mo tenureAuto-deducts weekly repayment directly from Uber trip earnings. Nigeria driver protests over insufficient take-home pay and aggressive in-person debt collection, a clear cautionary case.
Grab (GrabScheme)Indonesia (motorcycles)Platform = distribution/data, bank-backed multifinance company = balance sheetGrab partnered with PT Central Santosa Finance (a Bank Central Asia subsidiary) rather than self-financing, the clearest precedent for a tech-layer-plus-licensed-partner structure. Separately, Nikkei Asia reported Grab charging over 230% effective APR on short-term in-app loans to Philippine drivers.
Uber Vehicle SolutionsUSACurated marketplace of third-party rental/lease partners"Aggregator, not lender" pattern; Uber never originates financing itself.
Ola FleetIndiaLease-to-own, evolved over several program iterationsActive legal disputes with drivers over alleged vehicle confiscation and unfulfilled ownership promises, a direct warning on keeping ownership-transfer terms unambiguous.
Bangladesh banks (via Pathao)BangladeshBanks underwrite motorcycle loans using ride-share earnings as qualifying incomePathao itself runs no captive financing arm; banks accept 6 months of platform-earnings statements as income proof. The lighter-touch, no-captive-lender alternative.
Bajaj Finance / Hero FinCorpIndiaGeneral retail two-wheeler finance, up to 95 to 100% financedNo purpose-built gig-driver underwriting product; general bureau-based retail finance still dominates in India. A possible market gap rather than a proven approach.

Nepal digital-lending UX

ProductShapeTerms
eSewa easyloanIn-wallet lending, wallet-history-based eligibility, 6+ months active usage requiredRs 15,000 to 200,000, 17 to 18% annual interest, 2% penal interest
Khalti + NIC Asia "Super Chamatkarik Loan"Khalti is a pure front-end/PSP; an NIC Asia rep manually processes within 48 hours off-appHybrid, not fully self-serve
Foneloan (F1Soft/eSewa's parent group)White-labeled digital lending embedded across 11+ Nepali banks' appsPayday, EMI, and a BNPL product ("HamroBNPL"), the closest Nepali analogue to embedding financing inside an app people already use daily

The common thread across all three: wallet/account transaction history substitutes for a credit bureau score, and underwriting is handed off to a licensed bank/PSP partner behind the scenes, precisely the shape this product should take.

Recommended positioning

Nepal regulation

The single biggest thing shaping this design

Nepal Rastra Bank (NRB) regulation, not engineering choice, determines what's actually buildable. Under BAFIA, only a licensed BFI may originate or hold consumer loans, a pure tech company cannot lend directly (BAFIA 2073, Chapter 6, Section 31). Vehicle financing sits under a Hire Purchase Company license: NPR 300M minimum paid-up capital, a 60% LTV cap (at least 40% down payment), per the Sixth Amendment (roughly August 2026, only weeks before this research).

The single most load-bearing open legal question here: does a licensed hire-purchase company specifically get to invoke BAFIA §57's self-help repossession power? Sources conflict. This cannot be resolved by more research; it needs a Nepali banking/finance lawyer's direct read of Drivra's actual proposed corporate structure before the business treats fast repossession as a given.
flowchart TD Q{"How should Drivra
originate the loan?"} A["Path A
Partner with a licensed lender
e.g. Hulas Finserv"] B["Path B
Lease-with-purchase-option
RYD Nepal's structure"] C["Path C
Become a licensed
Hire Purchase Company"] Q --> A Q --> B Q --> C A --> AR["Avoids NPR 300M capital bar.
Gets §57 rights + CIB access
through the partner. Needs a
real partnership deal."] B --> BR["Lower capital bar, can offer
low/zero down. Legally less
tested, likely loses §57
fast repossession."] C --> CR["Full control. NPR 300M +
full NRB compliance burden.
Multi-quarter undertaking,
not a v1 move."] classDef rec fill:#d7ecdf,stroke:#1a7a42,color:#14532d,stroke-width:2px; classDef alt fill:#e5e7eb,stroke:#6b7280,color:#374151,stroke-width:2px; class A,AR rec; class B,BR,C,CR alt;

Recommended for design purposes: Path A. Closest fit to the standalone-service decisions already made, cleanest regulatory footing without a NPR 300M capital commitment. This is a legal decision for Nepali financial-regulatory counsel, not resolved here.

Full regulatory detail: repossession, AML/KYC, CIB Nepal
  • CIB Nepal (the credit bureau) is only accessible to NRB-registered BFIs.
  • Repossession is two separate legal instruments working together, not one. BAFIA §57 is the substantive power: a licensed BFI can auction mortgaged/pledged collateral without a court order on default. The commonly-cited "35-day notice," though, is not written into §57 itself; it comes from a separate law, the Act on Recovery of Debts of Banks and Financial Institutions, 2058 (2002), read with Rule 4 of its 2059 Regulations. In practice they're used together (real published bank repossession notices consistently cite the 35-day figure), but they're legally distinct instruments, and the Debt Recovery Act explicitly doesn't apply below NPR 500,000 principal.
  • AML/KYC obligations apply regardless of structure: e-KYC with biometric verification under the Asset (Money) Laundering Prevention Act 2008; suspicious-transaction reports filed via goAML within 3 days; records retained a minimum of 5 years.
  • One documented exception worth knowing: NRB approved LTV up to 80% for businesses replacing vehicles damaged in the 2026 Gen-Z protests. Narrow and situational, not a general relief valve.
  • Also new in the Sixth Amendment: a cost-of-funds-based interest mechanism (replacing a flat spread cap), 10-fiscal-year license renewal, a higher PAN-requirement threshold, and a mandatory multi-brand financing requirement.

Driver journey

End to end

flowchart LR A["Discovery
Own Your Bike entry
point inside Upahar"] --> B["Application
plan, vehicle,
down payment"] B --> C["KYC
citizenship + NID +
license + selfie"] C --> D["Underwriting
rules-based scorecard,
admin-overridable"] D --> E["Contract & terms
e-signature"] E --> F["Disbursement
lien recorded,
handover logged"] F --> G["Servicing
installments,
ownership tracker"] G --> H["Monitoring
periodic re-pull of
performance data"] H --> I["Completion or default
ownership transfer,
or repossession"] classDef missing fill:#e5e7eb,stroke:#6b7280,color:#374151,stroke-width:2px; class A,B,C,D,E,F,G,H,I missing;

Every step is new, part of the Financing build. Gray throughout: nothing here is built yet.

System architecture

A standalone service, plugged into the identity layer

Standalone service: own repo, own Postgres database, reusing Upahar's proven stack (FastAPI + SQLAlchemy 2.0 + Alembic + Jinja2/HTMX admin), but its own deployment and security perimeter, since it holds KYC documents and financial data. It reads driver identity and performance data from the canonical identity layer described in Architecture, never direct database access into Upahar or Express.

Auth

Driver auth: phone + SparrowSMS OTP, issuing a JWT scoped to a distinct financing_driver audience, deliberately not SSO-trusting Upahar's session for v1 to keep security boundaries independent. Admin auth mirrors the bcrypt+JWT pattern with more granular roles: KYC reviewer, underwriter, collections/ops, owner/compliance.

Storage: Supabase Storage over raw S3, for v1

At this scale (a few thousand drivers x about 5 documents), storage/egress cost is trivial either way. The deciding factor is integration effort: Supabase Storage wires directly into Postgres RLS. This must be its own Supabase project, never the one Upahar and GPS Dashboard already share.

eKYC: DIY Textract + Rekognition, for v1

Per-driver verification cost is roughly $0.07 (Textract AnalyzeID for 2 documents + Rekognition liveness + face-compare) versus $2 to $7 per verification for global vendors like Jumio/Onfido. DIY is roughly an order of magnitude cheaper; the trade-off is owning fraud-detection tuning in-house, acceptable when a human still signs off on every KYC approval regardless.

Three UI surfaces

Driver-facing web portal (not a second app), linked from Upahar. Admin console adding new tabs to the existing page+endpoint convention. A field-agent tool to record cash payments collected in person, matching how Nepali MFIs actually collect.

Full data model: 11 tables
TablePurpose
driversIdentity, linked to the canonical identity layer via phone
kyc_documentsUploaded documents: citizenship/NID/license/PAN/selfie, review status
guarantorsCold-start co-signers
vehiclesAsset registry, deliberately separate from Upahar's driver-vehicle columns, which reflect only the driver's current Yango-assigned vehicle
loan_productsConfigurable plan terms: tenure, down payment %, interest, penalty rate
applicationsOrigination workflow state
loan_accountsThe active agreement, including lender_of_record which absorbs the legal-path decision without blocking the build
repayment_scheduleAmortization
ledger_transactionsAppend-only ledger, mirrors Upahar's PointTransaction shape
delinquency_eventsCollections state: current/watch/substandard/loss
audit_logEvery state change and admin action

Every new table's migration revokes Supabase's default anon/authenticated PostgREST grants, per Upahar's existing hard rule, now a standing checklist item for any new Supabase-backed service across the whole platform.

Credit scoring v1

Internal-only, rules-based

Every thin-file lender researched (Watu, Tugende) starts here: a rules-based scorecard, not an ML model, since there's no proprietary repayment history yet to train on.

Inputs available day one, all from Upahar: tenure, lifetime trips/gross and their consistency, current/longest streak, active status, tier/XP. Once the identity layer exists, also from Express: delivery tenure and reliability, for drivers who do both.

Cold-start handling: a guarantor requirement and/or higher down payment for drivers with little history, mirroring Watu's guarantor model and Tugende's reference-plus-training approach, rather than an outright decline. Decision flow: hard gates (KYC complete, active status, minimum tenure) then a weighted score, then approve / decline / refer-to-manual-review, every decision and override audit-logged.

Explicitly not in v1: telematics/GPS-based scoring or remote asset-disable enforcement. The Moove/M-KOPA/Watu pattern is powerful but adds IoT dependency and real reputational risk (documented tracker-collusion allegations against comparable East African lenders). Drivra's GPS Dashboard infrastructure already exists and could support this later, see Product, but it's a phase-3 decision, not a v1 one.

Payments & collections

No wallet in Nepal supports auto-debit: plan around that

Confirmed directly against each provider's own developer documentation: none of eSewa, Khalti, or Fonepay support true unattended auto-debit. eSewa's closest product still requires the customer to actively enter their token at eSewa on every transaction. Khalti's docs show no subscription/mandate capability at all. Fonepay's merchant API docs on this specifically weren't locatable, treat as unresolved rather than confirmed absent. ConnectIPS/NCHL supports mandate-based direct debit, already used for hire-purchase EMI collection, the best path to real automation for drivers with a bank account.

flowchart LR A["SMS reminder
reused SparrowSMS client"] --> B["Driver pays
ConnectIPS/Fonepay QR
eSewa/Khalti fallback"] B --> C["Reconciliation
marks ledger paid"] C --> D{"On time?"} D -->|Yes| E["Current"] D -->|No| F["Delinquency bucket
watch to substandard to loss"] F --> G["Dunning, then
repossession trigger"] classDef good fill:#d7ecdf,stroke:#1a7a42,color:#14532d,stroke-width:2px; classDef rethink fill:#f7e6c4,stroke:#b26a00,color:#7a4900,stroke-width:2px; class A,B,C,E good; class D,F,G rethink;

ConnectIPS mandate automation is an opt-in later step, once the manual flow is proven. Cash/agent collection is the fallback via the field-agent tool.

Fee comparison: ConnectIPS is flat and cheap (Rs 2 to 8/transaction regardless of amount, NRB bars passing this to customers); Fonepay QR is free for merchants; eSewa/Khalti card-based loading runs 1.75 to 5%. Default drivers toward ConnectIPS or Fonepay QR; support eSewa/Khalti as fallback, not the primary path. This v1 flow matches how the market leader (Hulas Finserv) already operates.

Compliance & risk