Worked Example — Indian Fintech and Digital Payments

The word that did not mean what he thought

Aditya had been at the payments company in Gurugram for six days when he saw the dashboard for the first time. The company processed UPI payments for about twelve thousand small merchants — kirana stores, chai stalls, salons, neighbourhood pharmacies. The dashboard showed the previous day's transactions. One column said "settled." Another said "settlement pending."

The settlement-pending column showed forty-seven crore rupees.

Aditya felt the kind of cold that has nothing to do with the air conditioning. Forty-seven crore rupees was not settled. Was it lost? Had something failed? He checked the error logs. Nothing. He checked the alerts channel. Nothing. He sat for ten minutes trying to decide whether to tell someone or whether asking would reveal that he did not understand the most basic thing about the system he had been hired to work on.

He asked. His tech lead, a woman named Priti who had been in payments for five years, did not laugh. She explained. "Settlement pending" does not mean the money has not arrived anywhere. It means the money has already arrived — in the company's own escrow account, sent by each customer's bank through NPCI in something close to real time, the same way it always does — but has not yet been paid out to the twelve thousand individual merchants it actually belongs to. That payout is a separate step, run as a scheduled batch across every merchant the company serves, and it typically completes by the next business day. The forty-seven crore was not missing and it was not in transit between banks. It was sitting correctly in escrow, waiting for that day's payout batch to run. The "pending" was normal. Every payment aggregator in India wakes up every morning to a settlement-pending number for exactly this reason, and the engineering team's job is to make sure that number resolves to zero by end of day, every day, and to catch it immediately when it does not.