Somebody spends the first week of every month ringing forty customers to ask them to pay.
A mandate is the customer’s standing permission to charge him each cycle, taken once through your payment gateway or your bank. The module keeps the mandate, sends the notice before each debit, raises the charge on the due date, and records what came back. Collection stops being forty phone calls and becomes a list of the few that failed.
Recurring collection is where small businesses lose the most time for the least reason. The service was delivered and the customer is willing. Still somebody has to call, send a link, wait, and check the bank in the evening. A gym with three hundred members loses a person to this work.
With a mandate, the customer approves once, in his UPI app or at his bank. After that the charge is raised on the due date, and he is told before it happens. Your side becomes a list of failures instead of a list of everybody.
What mandates and auto-debit does.
Taken at sign-up
UPI AutoPay, a card mandate or a bank e-mandate, created through the gateway or the sponsor bank you already use.
Notice before the debit
The customer is told at least twenty-four hours before each charge, as the RBI framework requires, with the amount and the date.
The customer can say no
He can opt out of a single debit or cancel the mandate entirely. Both are recorded, and neither needs a call to your office.
Large debits need his approval
Above the per-debit limit in the RBI rules, the customer has to authenticate each charge. Confirm the current limit with your gateway before fixing plan prices.
Debits raised and answered
Success, failure and the reason the bank gave, recorded against the invoice the charge was raised for.
The mandate register
Live mandates, the maximum amount each allows, when it expires, and which customers still have none.
The people who open this every day.
Accounts assistant
Works the failures. Everything that succeeded needs nothing from anybody.
Sales or front desk
Gets the mandate approved while the customer is signing up, which is the only moment he will do it.
Owner
Sees how much of the month’s collection arrives without a phone call.
It is one part of a system, not an island.
A module earns its place by what it passes to the next one. These are the connections we set up most often.
- Subscription billing
- Invoice management
- UPI AutoPay and payment gateways
- WhatsApp and SMS
- Tally
How we would put it in.
Questions owners ask about mandates and auto-debit.
Is auto-debit allowed for a small business?
Yes, under the RBI e-mandate framework, through a payment gateway or your bank. The customer must get a notice before each debit and must be able to opt out of one charge or of the mandate itself. The rules sit with the gateway, and we build to them.
Do you hold our customers’ money?
No. We are not a payment aggregator and never touch the funds. The money moves from your customer through your own gateway into your own account. Which gateway suits you is settled during the free technology audit, before anybody signs anything.
How many customers will actually approve a mandate?
Fewer than you hope, and more each year. Ask at the counter while somebody is signing up, not by sending a link three weeks later. Keep a payment link for the rest.
What happens when a debit fails?
It is retried on the schedule you set, the customer is told with a link to pay another way, and a short grace period runs before service stops. All of that lives in subscription billing, which this module collects for.
Businesses that ask for this.
Modules that work with it.
Tell us how you handle mandates and auto-debit today.
A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.
- No obligation
- We reply the same working day
- Your details stay private