Stelo Credit Profile
Combines income, expenses, liabilities, repayment behaviour, verification confidence and relevant financial context into an account-level profile.
Explore the Credit Profile →Stelo connects financial profiling, scoring, affordability, product eligibility, M-Pesa money movement and repayment history into one server-authoritative lending journey.
Each feature has a specific job: understand the customer, control exposure, present only eligible credit, move money reliably and build a clearer repayment record over time.
Combines income, expenses, liabilities, repayment behaviour, verification confidence and relevant financial context into an account-level profile.
Explore the Credit Profile →A compact risk/credit indicator that can help summarize profile strength while remaining subordinate to affordability, exposure and product controls.
How scoring fits →Income is considered after recurring expenses and obligations so a headline income figure does not become the sole basis for borrowing capacity.
Eligibility & limits →The effective credit limit is a real maximum. Product visibility never overrides the current ceiling or remaining room after active exposure.
Understand the ceiling →Tiers can be visible, locked, eligible, requested or approved so customers can distinguish catalogue discovery from actual access.
See product states →Approved loans are designed for B2C disbursement and repayments for M-Pesa/STK flows, without introducing a generic withdrawal wallet.
See the M-Pesa architecture →Relevant Android transaction messages can be processed locally into derived aggregates instead of making raw message history the underwriting payload.
Privacy by design →Confirmed repayment outcomes can become part of future profile reviews while avoiding an automatic promise of a higher next limit.
Repayment journey →Stelo's credit score is designed as one output of the wider profile. The account can use it alongside data confidence, affordability, active exposure and product-specific controls rather than treating one number as automatic approval.
Evidence quality matters. A score is more meaningful when the underlying financial history is sufficiently complete and consistent.
Affordability remains separate. A strong indicator does not justify an amount the customer cannot reasonably service.
Current exposure can constrain access. Existing obligations can reduce available room even when other signals are positive.
Thresholds remain backend-controlled. Product eligibility and score thresholds should be maintained server-side rather than hard-coded into the public website.
Illustrative only. The public website does not publish underwriting weights or promise approval at a particular score.
Stelo's intended production flow uses M-Pesa for both directions of the lending journey: approved disbursement through B2C and repayment through supported M-Pesa/STK flows.
Approve first. Eligibility alone does not trigger disbursement.
Disburse through B2C. The backend records the resulting transaction state.
Repay through M-Pesa/STK. Sending a prompt is not the same as a successful payment.
Post only confirmed outcomes. Loan balances should change only after authoritative payment confirmation.
The Android design is built around explicit consent and local processing of relevant M-Pesa transaction messages into derived aggregates. The backend receives the financial signals needed for assessment rather than treating a full raw message history as the default credit payload.
Purpose-limited data. Use information for the lending function it was collected to support.
Backend-authoritative decisions. Sensitive lending calculations are not entrusted to client-side presentation logic.
Clear consent boundaries. Financial analysis should be understandable and permission-based.
No raw-history marketing claim. The website describes derived financial signals rather than implying indiscriminate message uploads.
Responsible lending is reflected in how limits, exposure, quotes, repayments and future reviews work—not just in a disclaimer at the bottom of the page.
Initial borrowing capacity can be staged rather than assuming a new customer should begin at the largest tier their headline income might suggest.
Active debt and relevant guarantee exposure remain part of the available-capacity picture.
Good repayment history can help future reviews, but each new limit remains subject to a current assessment.
The exact loan obligation should be visible before the customer confirms a request.
See the Stelo 1K through Stelo 75K catalogue and the states that determine what you can select.