Recurring Transaction

1. Introduction

Recurring transactions are essentially required for continuation of subscriptions or mandates. The API can be used to create a recurring charge request with the specific reference of the underlying mandateid.

To initiate a recurring charge, an invoiceid is required, which can be generated using our initiate invoice API mentioned in the prior section.

If the recurring charge debit amount is higher than the permissible limit (as per regulations), the customer requires to provide an additional AFA for processing the recurring charge.

❗️

AFA Requirement

Mandate executions for amounts over ₹15,000 need to be authorized by the customer through an AFA each time.

AFA is also required when recurring charge debit amount is greater than the amount set at mandate creation.


2. API Orchestration

The orchestration of the API/s workflow has been explained below:

API Reference

Description

Initiate Recurring Transaction

Merchant can initiate recurring transaction for a defined mandate.

For sample code click here.


2.1 Recurring Transaction attributes

Here are some of the attributes required to initiate invoice request. For more details click here.

AttributeDescription
invoiceidUnique id created by BillDesk in the Create Invoice request, using which the pre-debit notification was sent.
mandateidUnique mandateid by BillDesk for the associated mandate.
txn_process_typeFixed value si.
subscription_refidUnique reference assigned by merchant for the subscription.