UPI AutoPay for cloud hosting: mandates, limits, failures
How a UPI AutoPay mandate works for a recurring cloud hosting bill, the per-debit ceiling that catches growing accounts, and the common reasons a mandate fails.
Recurring payments in India do not work the way a card subscription works elsewhere. You do not hand over a card number and let the merchant charge it indefinitely. You approve a mandate — a standing instruction with an explicit ceiling, an explicit end date, and your own bank in the middle of it.
Understanding the shape of that mandate saves you from the two surprises that catch most teams: a renewal that silently fails, and a bill that outgrows the instruction approving it.
What a mandate actually is
When you set up AutoPay, you are not authorising a specific amount. You are authorising a maximum amount per debit, for a defined period. Your bank records it. Each time a payment is due, the platform requests a debit within that ceiling, and your bank executes it and notifies you.
Two numbers matter, and they are different from each other:
- The mandate maximum — the most that can ever be taken in a single debit. Set once, at approval.
- The actual debit — what is genuinely charged this cycle, which is normally much smaller.
Approving a mandate for a high maximum does not mean you are charged that. It means the instruction has headroom, so a legitimate increase in your bill does not require you to approve a whole new mandate.
Where to see what you approved. Billing → Payment method shows the method that is saved, the maximum per charge you approved, and the date the mandate stays valid until. Those are the same numbers your UPI app shows you, so the two can be compared. If a payment method you added did not register, that page will not show it as saved — a mandate only replaces the one you had by succeeding.
The maximum you are asked to approve is sized to your bill, not to the rail’s limit. Voroa asks for roughly three times your current monthly total, with a small floor so that adding your first few services does not send you back through approval. If your bill grows past that maximum, you will be asked to approve a new mandate once, at the new size. You will not be asked to authorise a figure in the lakhs to pay a few hundred rupees a month.
The per-debit ceiling
Voroa can register a UPI AutoPay mandate for a monthly total of up to Rs 1,00,000. That ceiling belongs to the payment rail and to the category Voroa’s merchant account sits in — it is not set by Voroa, and no one can raise it on request.
UPI AutoPay is the recurring payment method Voroa offers today. Other rails exist in India with higher ceilings, and Voroa expects to support them, but they are not available on your account right now.
The practical consequence: if a single cycle’s bill would exceed Rs 1,00,000, a UPI mandate cannot carry it. No amount of headroom in the mandate changes that — the rail will not execute a larger debit. Very large debits can also ask you to approve them in your UPI app at the time, instead of going through silently.
If your monthly bill is heading towards that figure, contact support before you get there so we can arrange payment rather than have a debit refused. Do not plan around a card or netbanking mandate being available.
What breaks, and why
The mandate expires. A mandate is approved for a period, not forever. When it reaches its end date it stops working, and the next payment simply does not happen. This is the most common cause of a “my payment failed for no reason” report — nothing failed, the instruction ran out. You will be asked to approve a new one.
The bill outgrows the ceiling. You add services, the cycle total rises past the mandate maximum, and the debit is refused as exceeding the instruction. The fix is a new mandate at a higher ceiling — up to the rail ceiling above, which cannot be exceeded.
Insufficient balance at debit time. UPI debits against a bank account. If the balance is short at the moment of the attempt, the debit fails even though the mandate is perfectly valid.
We have no phone number for you. A renewal charge carries your mobile number to the payment network, so it cannot be raised without one. In almost every case this is already handled: the number you confirm while approving the mandate is kept and reused, so you are never asked twice. If it is somehow missing, the charge is not attempted at all - nothing is debited, nothing is marked overdue - and adding your number under Billing lets the next cycle go through.
You revoked it and forgot. Mandates are visible and cancellable in your UPI app, independently of the platform. A mandate cancelled there stops working immediately, and Voroa is notified at that moment rather than at the next debit — so the account reflects it straight away.
What you should do
- Approve the mandate with sensible headroom, above your current bill, so ordinary growth does not force a re-approval.
- Watch for the expiry notice. Re-approving before expiry avoids a gap.
- Tell us before your bill approaches Rs 1,00,000 a cycle, rather than after a debit is refused.
- Keep the balance available in the account backing the mandate around your billing date.
How Voroa uses it
Voroa bills in rupees, and recurring payment runs on UPI AutoPay. You approve a mandate once, and each cycle is debited within it. Voroa emails you about payment events, including failures and mandates approaching expiry, so a lapsed instruction is something you are told about rather than something you discover.
You can see and change your payment method in your workspace billing settings.