Introduction
A mid-sized bank recently upgraded its core banking platform to a newer release of TCS BaNCS. Two weeks later, customer complaints about failed transactions, such as UPI payments debited but not credited, card declines and failed NEFT transfers, are up 30%. For a bank, this is serious: failed transactions hurt trust, trigger regulatory reporting and can lead to compensation obligations under turnaround-time rules. In this scenario, the product manager supporting this client needs to find the root cause quickly, separate correlation from causation and coordinate a fix across bank IT, TCS engineering and payment networks. I'll follow a structured root cause framework from clarification to resolution.
Clarify, rule out external factors, understand the journey, break down the metric, gather data, form hypotheses, find the root cause, validate, decide and resolve. In core banking, always check whether the problem is in the core, in the integration layer, or outside the bank.
Step 1
Clarifying Questions (3 minutes)
Why it matters: Complaints can rise due to better complaint channels even if failures are flat. Expected answer: Both; failed-transaction rate in logs rose from 0.8% to 1.1% of volume. Impact on approach: The problem is real, not just reporting.
Why it matters: It narrows the search to specific integrations. Expected answer: Mostly UPI and IMPS; branch and card transactions are only slightly up. Impact on approach: Focus on real-time payment flows and their interfaces with the core.
Why it matters: Upgrades often change APIs, timeouts and batch schedules. Expected answer: New BaNCS release, new API gateway configuration, and a database migration to new hardware. Impact on approach: Three candidate change areas.
Why it matters: Immediate spikes suggest configuration errors; gradual growth suggests load or data issues. Expected answer: Small rise at go-live, larger rise on peak days (salary day, weekends). Impact on approach: Suspect capacity or timeout issues under load.
Practice similar questions
Subscribe to access the full answer
.png){kind=logo}
