UPI Autopay's Rs 15,000 per-debit cap pushes Indian annual plans onto e-NACH or monthly billing

Start with what each system does when you call it. The gateway authorizes a card, a UPI request or a mandate, moves the rupees and hands back a success webhook ^[1]. None of that decides whether next month's debit is permitted. That was settled earlier, when the customer's bank approved a standing instruction and fixed the limits every later debit runs against ^[2].

The threshold that shapes the design is Rs 15,000 per debit on UPI Autopay ^[3]. At or below it, money moves with no customer action. Above it the debit is still allowed, but additional factor authentication fires on every single debit, so an OTP prompt arrives at every renewal ^[4].

Because the cap applies per debit, the billing period matters as much as the price. The guide's worked case is a Rs 24,000 annual plan: one debit a year sits above the threshold, so the OTP comes round every cycle ^[5]. Spread the same revenue over twelve months and each debit is Rs 2,000 ^[1]. The smallest split that clears the cap is two debits of Rs 12,000 ^[3]. Read it the other direction and a monthly plan only reaches Rs 15,000 per debit at Rs 1,80,000 a year ^[2]. Monthly SaaS priced under Rs 15,000 never touches the cap; annual prepay touches it at any price above Rs 15,000.

The enhanced Rs 1,00,000 AFA-free limit is scoped to insurance premiums, mutual funds and credit-card bills, and the guide is explicit that general SaaS does not qualify ^[7]. It is also, on the guide's account, misread as an e-NACH ceiling. e-NACH per-mandate limits are set at registration, can run much higher than Rs 1,00,000, and the actual ceiling depends on the sponsor bank and the gateway ^[8]. Card e-mandates are the third mandate rail, the one for card-first customers, and the guide's position is that the system picks the mandate type per plan ^[15].

The invoice pipeline runs on the same clock as the mandate. Every renewal needs a tax invoice with the correct place of supply, HSN/SAC and IRN ^[9]. The failure modes the guide lists are two: the debit fails, or the invoice does not match the money in the account ^[10].

This is one practitioner's account, written from recurring billing that runs in PlugEV, CloudNX and MultiVendor CRM ^[11]. It tells readers that where a number depends on the current rulebook or their own pricing, they should verify it against their own setup before shipping ^[12]. Its RBI section starts to name two rules that have to be built in, beginning with a pre-debit notification, and the published text breaks off mid-sentence ^[13].

On why the layer gets built at all, the guide says: "The accidental version still runs. It just leaks money quietly." ^[14] It names monthly-billing SaaS, OTT and streaming, edtech, gyms and coworking, and D2C subscription boxes as the businesses that have outgrown a raw gateway integration ^[16].