At 11:40 on a Friday night, Prakash's phone buzzed on the table beside his bed. It was an from the monitoring system: the online payment service of the bank where he worked as a systems engineer was not responding. Within a minute, his phone rang. It was his manager, Anjali.
“Customers can't send money from the mobile app,” she said. “The started ten minutes ago. Can you log in and check the servers?” Prakash was already opening his laptop. He connected to the VPN and joined the team's emergency call, where two other engineers were waiting.
The first thirty minutes were confusing. Everyone had a different idea. One engineer thought it was the database; another blamed the network. Anjali stopped the discussion. “Let's not guess,” she said firmly. “Prakash, check the logs on the payment server. Nima, check the database. We'll share what we find every ten minutes.” The calm plan helped everyone focus.
While the engineers worked, Anjali wrote short updates for the customer service team, avoiding technical . “We are aware that mobile payments are not working. Our engineers are investigating. Customers' money is safe. Next update at 12:30.” She knew that clear, honest updates would stop people from panicking.
At 12:20, Prakash found something in the logs. A security certificate on the payment server had at exactly 11:30. Without it, the app could not make a secure connection. It was a small thing that had stopped thousands of payments. He felt both relieved and embarrassed, because renewing certificates was part of his team's job.
He installed a new certificate and restarted the service. At 12:41, the first test payment went through. By one o'clock, the service was fully , and Anjali sent the final update: “Mobile payments are working normally again. We apologise for the inconvenience.”
On Monday, the team held a meeting to discuss the . Prakash was worried that he would be blamed, but Anjali made it clear that the meeting was about the process, not about people. “The real problem,” she said, “is that we track certificate dates in a spreadsheet that nobody checks.” The team agreed on two actions: automatic reminders thirty days before any certificate expires, and a monthly check by a named person.
Prakash volunteered to set up the reminders himself. That night had taught him a lesson he would never forget: in IT, the biggest problems often come from the smallest details, and good communication matters as much as technical skill.