Skip to main content

Overview of BillDesk payment gateway integration


Overview of BillDesk payment gateway integration

Zuora integrates with the BillDesk payment solution to provide a gateway integration called BillDesk for processing Credit Card transactions in Indian Rupees (INR).

This feature is in the Early Adopter phase. We are actively soliciting feedback from a small set of early adopters.

Supported features

The following table provides a quick reference for the supported features. For details about each feature, see the later sections in this article.

Supported payment methods Credit Card/Gift Card/Prepaid Card
Supported payment operations
  • Payment method validation
  • Payment
  • Referenced refund 
Support 3D Secure 2.0 Yes
Support Delayed Capture No
Support Level 2 and Level 3 card data No
Support stored credential transactions No
Support Gateway Options fields Yes
Gateway provider’s API version v1.4.4
Gateway provider’s production endpoint used for Zuora gateway integration service

Support Batch Gateway Reconciliation No
Support Real-Time Reconciliation No
Support Payment Method Updater No
Support inquiry call for retrying a transaction request Yes

Supported payment methods and payment operations

The BillDesk payment gateway integration supports Credit Card payment methods, including the following card brands:

  • American Express
  • Diners Club
  • Discover
  • JCB
  • MasterCard
  • RuPay
  • Visa

The following payment operation transactions in Indian Rupees (INR) are supported:

  • Payment method validation
  • Payment, including one-time and recurring payments
  • Referenced refund

The creation of Credit Card payment methods on BillDesk is only supported through hosted payment pages. During the payment method creation, BillDesk makes a 2 INR payment and refunds the same amount to the end user.

To support processing one-time and recurring payments, you can implement a hosted payment page by passing in additional client parameters. See Implement one-time payment flows for processing payments in India for detailed instructions.

One-time payment flow

On the hosted payment page, your customers enter their card information and submit the payment. A prompt dialog for a One Time Password is displayed. After your customers enter the password and submit, Zuora processes the payment. 

When implementing your hosted payment page, you have the option to store the payment method. If you choose to store it, the created Credit Card payment method can be accessed through the Zuora UI and API operations. You can also retrieve the following token information in the Electronic Payment Methods section of the customer account page. Token ID and Second Token ID will be used in subsequent recurring payments.

Zuora UI field Value

Token ID


Second Token ID

SubscriptionRef and Mandate Id

Recurring payment flow

As regulation requires, a pre-debit notification per invoice must be sent to the Card owners before collecting the recurring payments. Zuora sends a pre-debit notification to BillDesk for each invoice before the invoice due date, according to the configuration in Pre-debit Notification Rules in Zuora. By default, this notification is sent 2 days before the invoice due date. This minimum value ensures that Zuora has sufficient time to send the pre-debit notification request to the gateway for further processing.

For example, the payment term is 15, and an invoice is created and posted on March 1st. The invoice date is March 1st and the invoice due date is March 16th. If the Pre-debit Notification Rule is set to 2, the pre-debit notification is triggered on March 14th. The payment is collected on March 16th. For instructions on how to configure this rule, see Implement one-time payment flows for processing payments in India.

Support for 3D Secure 2.0 

See Enable 3DS2 for BillDesk gateway integration and Zuora’s implementation of 3D Secure 2.0 for more information.

Supported Gateway Options fields

To support processing recurring payments, you must pass in the required Gateway Options fields for generating the e-mandate for recurring payments in India when implementing the hosted payment page. For more information, see Implement Payment Pages 2.0 to support processing payments in India.

Features not supported

  • Payment cancel
  • Non-referenced refund
  • Delayed capture
  • Gateway Reconciliation
  • Payment Method Updater
  • Level 2 and Level 3 card data processing
  • Stored credential transactions