Data Analytics · Indian Fintech
How Data Analytics Is Used in Indian Fintech Companies Today
Quick summary — data analytics in Indian fintech
Indian fintech companies use data analytics to track payment success rates and failure reasons, analyse lending funnels and default cohorts, review fraud signals and rules, and measure customer retention and repeat usage. Analysts mainly use SQL, Excel, BI dashboards and some Python, with strong attention to data privacy.
In this guide you will learn:
- Payment analytics — success rates and failure analysis.
- Lending analytics — funnels and cohort risk views.
- Fraud and retention — analysis patterns.
- Fintech analytics templates — to practise with.
- Interview questions — for fintech analyst roles.
SECTION 01Payment analytics: success rates and failures
For payment apps and payment gateways, the payment success rate is one of the most watched numbers. When it drops, users get frustrated and may switch apps. Analysts break success rates down by bank, payment method, app version, time of day and error code to find exactly where problems are happening. Typical payment questions include:
| Question | Data used | Analysis | Who uses it |
|---|---|---|---|
| Why did success rate drop today? | Transaction events with status and error code | Split by bank, method, app version | Payments and engineering teams |
| Which failures are user errors? | Error codes | Group codes into user vs system | Product team |
| When do failures peak? | Hourly transaction data | Hour-by-hour trend | Operations |
| Is a new app version worse? | Version and status | Compare versions | Release team |
-- Payment success rate by bank for one day
SELECT
bank,
COUNT(*) AS attempts,
SUM(CASE WHEN status = 'SUCCESS' THEN 1 ELSE 0 END) AS successes,
ROUND(100.0 * SUM(CASE WHEN status = 'SUCCESS' THEN 1 ELSE 0 END)
/ COUNT(*), 2) AS success_pct
FROM transactions
WHERE txn_date = '2026-11-05'
GROUP BY bank
HAVING COUNT(*) >= 100
ORDER BY success_pct ASC;
import pandas as pd
tx = pd.DataFrame({
"status": ["SUCCESS", "FAILED", "FAILED", "SUCCESS", "FAILED", "SUCCESS"],
"error": [None, "BANK_TIMEOUT", "WRONG_PIN", None, "BANK_TIMEOUT", None],
})
user_errors = {"WRONG_PIN", "INSUFFICIENT_FUNDS"}
failed = tx[tx["status"] == "FAILED"].copy()
failed["type"] = failed["error"].apply(
lambda e: "user" if e in user_errors else "system")
print(failed.groupby(["type", "error"]).size())
SECTION 02Lending analytics: funnels and cohorts
Digital lenders need to understand both growth and risk. Growth questions look at how many applicants move through each step of the loan journey. Risk questions look at how loans perform over time. Analysts use funnels and cohort tables to answer both, and they work closely with risk and credit teams who make the final policy decisions:
| Analysis | Question | Method | Output |
|---|---|---|---|
| Application funnel | Where do applicants drop off? | Step-by-step conversion | Funnel chart |
| Approval analysis | How do approvals vary by channel? | Group by channel and segment | Comparison table |
| Repayment cohorts | How do loans from each month perform? | Cohort by disbursal month | Cohort table |
| Early warning | Which segments show rising late payments? | Trend by segment | Dashboard with alerts |
import pandas as pd
steps = pd.DataFrame({
"step": ["Started", "KYC done", "Offer shown", "Accepted", "Disbursed"],
"users": [10000, 7200, 5100, 2300, 2050],
})
steps["from_prev_%"] = (steps["users"] / steps["users"].shift(1) * 100).round(1)
steps["from_start_%"] = (steps["users"] / steps["users"].iloc[0] * 100).round(1)
print(steps)
# The biggest drop shows where to investigate first.
-- Share of loans more than 30 days late, by disbursal month
-- and months since disbursal (dummy schema)
SELECT
strftime('%Y-%m', disbursed_on) AS cohort,
months_since_disbursal,
ROUND(100.0 * AVG(CASE WHEN days_past_due > 30 THEN 1 ELSE 0 END), 2)
AS dpd30_pct
FROM loan_monthly_status
GROUP BY cohort, months_since_disbursal
ORDER BY cohort, months_since_disbursal;
SECTION 03Fraud signals and customer retention
Fraud teams often combine automated rules and models with human review. Analysts help by monitoring signals, reviewing how rules perform and finding new patterns. On the growth side, analysts measure whether users keep coming back after their first transaction. Both areas rely on careful, privacy-aware analysis of customer data:
| Area | Question | Analysis | Care needed |
|---|---|---|---|
| Fraud signals | Are there unusual spikes? | Transactions per device or account per hour | Avoid blocking genuine users |
| Rule review | Is a rule catching fraud or blocking good users? | Flagged vs confirmed cases | Balance both errors |
| Retention | Do users return after first payment? | Weekly retention cohorts | Define 'active' clearly |
| Feature impact | Did cashback change repeat usage? | Before/after or test vs control | Watch for other causes |
import pandas as pd
tx = pd.DataFrame({
"device": ["d1"] * 6 + ["d2"] * 2,
"ts": pd.to_datetime([
"2026-11-05 10:01", "10:03", "10:04", "10:05", "10:06", "10:07",
"2026-11-05 11:00", "15:00"], format="mixed"),
})
tx["hour"] = tx["ts"].dt.floor("h")
counts = tx.groupby(["device", "hour"]).size().rename("txns").reset_index()
print(counts[counts["txns"] >= 5]) # candidates for review, not auto-block
import pandas as pd
ev = pd.DataFrame({
"user": ["u1", "u1", "u2", "u3", "u3", "u3"],
"week": [0, 1, 0, 0, 1, 2], # weeks since first payment
})
cohort_size = ev[ev["week"] == 0]["user"].nunique()
retention = (ev.groupby("week")["user"].nunique() / cohort_size * 100).round(1)
print(retention)
SECTION 04Fintech analytics practice templates
Use these templates to practise fintech analytics with dummy or public data. Never use real customer data for personal projects:
transactions(txn_id, user_id, txn_time, amount, bank,
method, app_version, status, error_code)
loans(loan_id, user_id, channel, disbursed_on, amount)
loan_monthly_status(loan_id, months_since_disbursal,
days_past_due)
Generate rows with Python (random + faker) for practice.
Payments dashboard
- Success rate today vs last 7 days
- Success rate by bank and method
- Top 5 error codes (user vs system)
- Hourly attempts and failures
Filters: date, bank, method, app version
Case: Payment success fell on 5 Nov
Finding: Drop concentrated in one bank, 7-9 pm
Evidence: Bank success 88% vs 97% usual; others normal
Error: BANK_TIMEOUT made up most failures
Action: Share with payments team for partner follow-up
Caveat: Based on one day; monitor next 3 days
SECTION 05Tips for analyst roles in fintech
These habits help analysts do well in fintech teams:
- Master SQL aggregations — CASE, GROUP BY and window functions are used daily.
- Learn funnels and cohorts — they appear in payments, lending and retention.
- Respect data privacy — use dummy data for projects and follow access rules at work.
- Segment before concluding — overall averages hide the real problem.
- Explain both error types — especially for fraud and risk rules.
SECTION 06Interview Q&A — fintech analytics
Q1Payment success rate dropped today. How would you investigate?
Confirm the data is complete, compare with recent days, then segment by bank, method, app version, time and error code to find where the drop is concentrated.
Q2What is a cohort analysis?
Grouping users or loans by a shared starting period, such as signup or disbursal month, and tracking how each group behaves over time.
Q3How would you evaluate a fraud rule?
Compare flagged cases with confirmed fraud to see how much fraud it catches and how many genuine users it wrongly blocks.
Q4How do you calculate weekly retention?
Take users by their first-activity week, then measure the share active in each later week.
Q5Why is data privacy important for fintech analysts?
Financial and personal data is sensitive and regulated, so analysts must follow access controls, avoid sharing raw data and use only what is needed.
SECTION 07Test yourself — fintech analytics quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
How do Indian fintech companies use data analytics?
For tracking payment success and failures, analysing lending funnels and loan performance, monitoring fraud signals, measuring retention and evaluating product changes. Analysts support payments, risk, product and operations teams.
What tools do fintech data analysts use?
SQL, Excel, BI tools such as Power BI or Tableau, and often Python. Specific tools vary by company.
Is fintech a good industry for data analysts?
Fintech generates a lot of data and many measurable questions, which builds strong analytical skills. Evaluate each company and role individually.
Do I need finance knowledge to become a fintech analyst?
Basic understanding of payments, loans and key terms helps. Much domain knowledge is learned on the job, but showing some awareness helps in interviews.
What project shows fintech analytics skills?
A payments dashboard and a lending cohort analysis built on dummy data, with a short write-up explaining a finding and recommendation.
SECTION 09Related reads
Classroom & online · Noida
Become a data analyst for real industries
Our Data Analytics Training Course covers Excel, SQL, Power BI and Python with industry-style projects including payments and lending case studies.
₹15,500 · full programme- SQL and Power BI
- Industry case studies
- Portfolio projects
- Weekday & weekend batches