Who handles the recurring mandate for Indian subscriptions?

PayU. Recurring payments in India rely on a mandate registered once with the buyer's consent, on cards, netbanking or UPI. PayU handles that consent layer within its cross-border offering. On NORBr, the merchant's billing logic and retry policies stay in the subscription engine, so the operator manages subscriptions the same way across markets.

India's mandate rules

Recurring payments in India require a mandate registered once with the customer's consent, under RBI rules on e-mandates. The mandate applies to cards, netbanking and UPI, with limits on amount and with notifications before each debit above certain thresholds. The customer can modify or revoke the mandate through their bank or app.

Division of roles

• PayU handles the consent layer within its cross-border offering: mandate registration, notifications, limits and revocation.
• The operator's subscription engine holds the billing logic: offers, schedules, retries, pauses, cancellations.
• The merchant manages subscriptions the same way across markets, with India as one more rail.

Why keep billing on the platform

If the Indian mandate and the billing schedule lived in two systems, a change of offer, a pause or a failed collection would have to be synchronized by hand. With the subscription engine on the platform and PayU as the payment rail, the merchant sees one subscriber record, one set of retry policies and one report, whatever the market. A revoked mandate is handled like an expired card: the subscription is paused and the customer is asked to set up a new one.