什么是印度的RBI电子授权？

E-Mandate 是一种数字化授权系统，用于从客户银行账户扣款，处理订阅费、等额月供、保险费和公用事业费等周期性支付，而无需单独授权每笔支付。在授权创建过程中，只需进行一次性验证，之后符合条件的支付将继续进行，直到授权发生变更或被取消。

2026年4月21日，印度储备银行（RBI）发布了《2026年数字支付 – 电子授权框架》（Digital Payments – e-Mandate Framework, 2026）。该框架废止了八项先前的通函，并为管理使用银行卡、预付支付选项或UPI的循环数字交易（包括国内和国际交易）制定了一套行政程序。该框架概述了循环支付流程中每个参与方在支付限额、通知和身份验证规则等方面的要求。

E-Mandate是指允许从客户账户进行重复数字扣款的任何授权。实现这一点有多种渠道，其中e-NACH（电子国家自动清算所）就是一个常见例子，它通过印度的NACH系统处理银行账户的交易。每次通过e-NACH进行的交易都属于e-Mandate的概念范畴，但e-Mandate的指南也涵盖了Card mandates和UPI AutoPay等其他概念。e-NACH只是利用此框架管理定期借记交易的一种方式。Card mandates和UPI AutoPay是另外两种以数字方式管理定期收款的方式。

印度有三种授权类型涵盖了大多数循环计费用例，每种都针对特定形式的交易而设立：

• 基于卡的授权 关联到客户的借记卡或信用卡，对于已经习惯使用银行卡支付的客户来说很熟悉。
• 基于银行账户的授权 (e-NACH)，也称为 e-NACH，通过 NACH 平台授权从银行账户直接扣款；这种方法通常用于 EMI、保险或共同基金。
• UPI AutoPay 连接到客户的UPI ID，通过公认的UPI应用程序（例如GPay或PhonePe）或直接通过银行的UPI界面自动处理借记。

银行电子授权（或NACH授权）直接在银行账户和商户之间注册一个循环借记协议。而UPI授权则通过与UPI ID绑定的UPI通道路由每次循环转账来操作。这三种授权结构都遵循统一的指导方针：低于₹15,000的交易无需额外因素认证（AFA）即可通过，对于保险费、共同基金申购和信用卡账单支付，则有更高的₹1,00,000阈值。

Setting up e-Mandates for SaaS involves following a defined pattern:

• You should begin with picking the mandate type that suits your customer segment; the UPI Autopay mandate applies to customers who use their mobile phones most, whereas the card mandate applies to those familiar with making card payments.
• The mandate registration process is usually concurrent with the process of validating the initial transaction because the latter requires AFA validation.
• Provide renewal notifications to customers at least 24 hours before any debit, and send a confirmation whenever a payment proceeds.
• Build in an easy self-service cancellation or modification flow, since any modification or withdrawal of an existing mandate requires AFA validation from the issuer.
• Use payment partners or 记录商户 that handle e-Mandate details, which allows necessary processes to be addressed outside of the main operations.

Mandate failures might result from low account balances, technical issues at the bank, or outdated authentication. Banks normally allow a limited number of retries within a specified timeframe, so setting up a simple system with appropriate timing and clear customer notifications fits the norm.

If a mistaken debit takes place, customers are encouraged to contact their bank promptly; this starts the zero-liability resolution process according to regulatory timeline requirements.

优势：

• Some payments fall within a limit where OTP is not required for every cycle, which changes the steps for renewals.
• The framework does not require a distinct fee specifically for customers making use of the e-Mandate process.
• Notifications are sent before and after recurring debits, as set by policy, mainly to keep customers informed of payments.
• Businesses now follow a consolidated guideline for compliance rather than relying on multiple earlier instructions.

Risks:

• For transactions above ₹15,000, or up to ₹1,00,000 in certain cases, another form of authentication is needed with each payment, so these renewals may look different compared to smaller amounts.
• If a business’s 付款重试逻辑 or notification systems operate outside regulatory expectations, banks may choose not to accept these payments or might apply additional examination.
• Organizations with limited background in domestic billing rules can experience added effort or delays when applying e-Mandate procedures on their own.

Let’s break it down: Does your business accept 定期付款 from customers in India? Would using an OTP for each payment create a slightly longer renewal process? If either of these describes your setup, e-Mandate support operates as a standard compliance requirement for recurring billing. In India, this continues to be a routine practice and not an optional add-on for companies managing SaaS订阅 或 automatic renewal payments.