DEV Community

Cover image for Why More Digital Wallets Do Not Automatically Mean More Financial Progress
oluoma stella onyeukwa
oluoma stella onyeukwa

Posted on

Why More Digital Wallets Do Not Automatically Mean More Financial Progress

Opening a digital account can make financial services easier to access. People can receive payments, transfer money and use services without visiting a physical branch.

But access and financial progress are different things.

A person may use several wallets and still struggle to save. A small business may accept digital payments but remain unable to manage unpredictable cash flow. A customer may access credit quickly and still face difficulty repaying it.

That difference matters when fintech companies decide what success looks like.

Access is a starting point

Account openings, transaction activity and payment volume can show that a product is being used. They are useful indicators of reach and engagement.

They do not necessarily show whether customers are becoming more financially secure. A rise in transactions, for example, does not by itself tell us whether customers are saving more, managing expenses better or relying less on emergency borrowing.

These are different questions, and they need different measures.

Turn activity into useful signals

A fintech team could start by grouping transactions by customer and month, then calculating a few descriptive measures. This example uses fictional data and is intended to illustrate the approach:

import pandas as pd

transactions = pd.DataFrame([
    {"customer_id": "C01", "date": "2026-01-05", "type": "income",   "amount": 1200},
    {"customer_id": "C01", "date": "2026-01-12", "type": "saving",   "amount": 100},
    {"customer_id": "C01", "date": "2026-01-20", "type": "borrowing","amount": 250},
    {"customer_id": "C02", "date": "2026-01-03", "type": "income",   "amount": 900},
    {"customer_id": "C02", "date": "2026-01-18", "type": "saving",   "amount": 50},
])

transactions["date"] = pd.to_datetime(transactions["date"])
transactions["month"] = transactions["date"].dt.to_period("M")

monthly = (
    transactions
    .pivot_table(
        index=["customer_id", "month"],
        columns="type",
        values="amount",
        aggfunc="sum",
        fill_value=0,
    )
    .reset_index()
)

for column in ["income", "saving", "borrowing"]:
    if column not in monthly.columns:
        monthly[column] = 0

monthly["saving_to_income"] = (
    monthly["saving"] / monthly["income"].replace(0, pd.NA)
)

print(monthly[
    ["customer_id", "month", "saving", "borrowing", "saving_to_income"]
])
Enter fullscreen mode Exit fullscreen mode

This produces a simple view of savings and borrowing relative to recorded income. It does not prove that a customer is financially well or in distress. It is a starting point for analysis, not a verdict about an individual.

Interpret metrics with care

A reduction in borrowing might indicate improved financial stability, or it might mean customers can no longer access credit. A higher savings balance might reflect better saving habits, or a temporary increase in income.

Even the ratio in the code has limitations. Recorded income may be incomplete, and a monthly snapshot can miss irregular earnings or expenses. Teams should document these limitations and avoid treating a single metric as a complete measure of financial well-being.

Do not confuse correlation with impact

If customers who use a product have better outcomes, that does not automatically prove the product caused the improvement. Customers may differ in income, employment, financial knowledge or access to other support.

To understand whether a service contributes to an outcome, teams need to consider what else may explain the change. They should also be careful not to make claims that the data cannot support.

This is especially important when evaluating products aimed at people facing financial pressure. A useful metric should help teams understand customer outcomes without reducing complex circumstances to a single score.

Design measurement around customer needs

Before choosing a success metric, fintech teams can ask:

  1. What customer problem is this product intended to address?
  2. What observable change would indicate that the problem is being reduced?
  3. What other factors might explain that change?
  4. Could the metric encourage behaviour that harms customers?
  5. How will the team check whether different groups experience different outcomes?

These questions do not produce one universal measure. They help make the measurement approach more deliberate.

Fintech can make financial services more accessible, but access alone does not guarantee financial well-being. As digital products mature, companies should examine not only whether people use their services, but also whether those services help customers make progress toward the outcomes they value.

Top comments (0)