Income & cash flow
Declared, observed and verified income context can help Stelo understand whether repayment fits the customer's normal financial activity.
The Credit Profile is the context Stelo uses to understand repayment capacity, confidence in available information and current financial exposure. It supports eligibility; it does not guarantee a loan.
Stelo's public model focuses on information that helps answer a practical question: can this obligation fit the customer's current financial position?
Declared, observed and verified income context can help Stelo understand whether repayment fits the customer's normal financial activity.
Recurring commitments matter because affordability is about what remains after ordinary financial obligations—not income in isolation.
How prior obligations are serviced can become part of the account's future risk context and confidence over time.
Verified information can carry more confidence than incomplete or inconsistent information, without turning any single signal into automatic approval.
Outstanding borrowing, current repayment obligations and relevant guarantee exposure can reduce room for additional credit.
A more complete and consistent financial history can provide clearer context than a single transaction or a one-day snapshot.
Stelo's public product language deliberately separates repayment-relevant evidence from personal characteristics that do not belong in an affordability decision.
Financial capacity — income patterns, obligations, exposure and repayment behaviour.
Verification confidence — whether information is complete, consistent and appropriately verified.
Irrelevant identity proxies — personal characteristics should not substitute for evidence of affordability.
One-signal shortcuts — a single transaction, relationship or behavioural guess should not become automatic approval.
Identify transaction information relevant to financial analysis.
Convert that information into useful aggregates and indicators.
Send the derived financial context needed for Stelo assessment.
Where the Android app uses M-Pesa transaction messages as one input, the intended architecture is to process relevant information locally and send derived aggregates used for assessment. This keeps the credit model focused on financial signals rather than collecting unrelated message content.
Read the homepage privacy summaryWhether the account currently meets the conditions to access particular lending options.
The current maximum borrowing ceiling after relevant profile and exposure controls.
Which amount tiers and terms can be selected within current eligibility.
How new evidence and repayment behaviour may change the financial picture over time.
Even when your profile supports a particular limit, a specific loan request can still be subject to approval checks. Registration, a profile, an eligible product and an approved loan are not the same thing.
The actual data and controls shown in your account remain authoritative for your own eligibility.
No. The profile supports eligibility and affordability assessment. A specific loan request can still require a separate approval decision.
Relevant context can include income and cash flow, recurring expenses, liabilities and exposure, repayment behaviour, verification information and consented transaction-derived aggregates.
No. Stelo considers the wider financial picture rather than treating any single signal as an automatic reason to increase borrowing capacity.
The intended Android design can process relevant transaction information locally and send derived financial aggregates rather than using raw message histories as the credit-analysis payload.
The next step is understanding what your current profile can actually make available.