Yes Bank is reportedly tightening the security of its banking APIs against AI-driven cyberattacks, and some fintechs and payment service providers say the change is slowing their settlements. According to a report by Inc42 on 21 November 2026, sources said the private sector lender’s upgrades have disrupted workflows and delayed payouts for businesses that move funds through its APIs.
The reported changes come days after the Reserve Bank of India (RBI) set out good practices for API governance and security at banks and NBFCs, in an advisory dated 16 November 2026.
What fintechs say about Yes Bank API security changes
One fintech executive told Inc42 that problems began after Yes Bank sent an email saying it was “implementing enhanced precautionary measures to safeguard” transactions. The platform was later told the bank was changing its banking APIs, which was delaying settlements, the report said.
Another industry insider linked the timing to RBI directions asking banks and other financial institutions to strengthen their cyber defences. According to that source, the directions followed the suspected cyberattack at State Bank of India that exposed customer records. The RBI is also said to have asked lenders to make sure customer funds are not hit by AI-assisted attacks.
Inc42 said it had sought comment from Yes Bank. No public statement from the bank on the reported delays was available at the time of writing.
Why API security is slowing fintech settlements
Fintechs and payout platforms depend on bank APIs to pay vendors and settle merchants. When a bank adds rate limits, beneficiary pre-validation or extra reconciliation, transactions that once cleared in seconds can queue up or need manual review.
The reported Yes Bank changes are not the only strain on payout rails this month:
- Coinbase India, CoinDCX and ZebPay have reported slower or paused INR withdrawals, citing outages or changes at unnamed banking partners.
- Razorpay temporarily delayed merchant settlements on 20 November 2026 because of a technical issue at a partner bank, and restored them within hours, Inc42 reported.
None of these firms has named the bank involved, and there is no public evidence linking these disruptions to Yes Bank.
How CERT-In and RBI are shaping bank cyber controls
On 20 November 2026 the Indian Computer Emergency Response Team issued a critical advisory, CIAD-2026-0062, on attackers misusing payment workflows. Elets BFSI covered the CERT-In warning on payment workflow fraud and AI-led attacks, which asks entities to restrict accounts that can approve payments.
Recent incidents show why lenders are acting. City Union Bank, for instance, shut an NEFT and RTGS gateway after an unauthorised transfer from one customer account on 16 November 2026.
For fintechs, bank-side security upgrades can arrive with little notice, making backup banking partners and clear payout communication as important as speed.
Key takeaways
- Inc42 reported on 21 November 2026 that Yes Bank’s API security upgrades are delaying settlements for some fintechs and payment service providers.
- Sources linked the changes to RBI cyber directions issued after the SBI data leak; Yes Bank has not publicly commented.
- CERT-In and RBI advisories this month push banks to add tighter controls on API-based fund transfers.
Featured image: Server racks in a data centre, used for illustration. Photo: Victor Grigas / Wikimedia Foundation via Wikimedia Commons (CC BY-SA 3.0).








