API ReferenceIntegrationsKnowledge Base

Payment Retries

Recurring payments for a Subscription are auto-debited based on the scheduled day that you defined. However, these payments could fail.

Reasons for Payment Failures

What Happens in Case of a Payment Failure🔗

  • The Subscription will move to the pending state.
  • You are notified about it via our webhooks. We automatically retry the payment on the following day.
    • We automatically charge the last invoice if the customer changes the card when the Subscription is in the pending state.
    • If this charge is successful, the Subscription moves to the active state.
  • If the payment fails after all retries, the Subscription will move to the halted state.
    • If the customer successfully changes the card details when a Subscription is in the halted state, it moves to the active state. Invoices for such Subscriptions are still created. However, we will not charge these invoices. You will have to charge them manually.

Notifications🔗

If you have enabled the subscription.pending and subscription.halted webhook, you receive notifications every time a Subscription moves to one of the above-mentioned states. You can then decide to hold off the delivery of the service as per your business model.

We also send an email to the customer notifying them about the payment failure. This email contains a link that the customer can use to change the card details associated with the Subscription.

Retry Model for Cards🔗

In failure scenarios, we automatically retry the payment the next day without your interference.

In a T+3 days cycle, we will retry the payment thrice. That is, once every day for 3 days, excluding the date of the charge. If the payment fails on all retires, the Subscription moves to the halted state.

Below is the retry model:

  1. Let T=0 be the charge day.
  2. On T=0, we attempt to charge the card.
  3. If the charge fails, the Subscription moves to the pending state, and we automatically reattempt the charge on T+1 day.
  4. If the charge fails again, we automatically reattempt the charge two more times on T+2 and T+3 days, respectively.
  5. If the charge still fails, the Subscription moves to the halted state.

Retry Model for Emandate🔗

In failure scenarios, we attempt to retry thrice and process a retry only when we get the confirmation or rejection of the last payment made, as it may take more than 24 hours.

Below is the retry model:

  1. If the charge day (T) is a bank holiday, we will charge on T-1 days
  2. If the charge day (T) and the previous day (T-1) are bank holidays, we will charge on T-3 days.

Handy Tips
This process will not affect the charge cycle for the subsequent months.

Retry Model for UPI🔗

The retry option is not available for UPI. It is only available for Card and Emandate.

Manual Charge on the Same Card🔗

When an auto-charge fails, you can manually attempt to charge the invoice as long as the invoice is in the issued state.

For example, the customer's account might have an insufficient balance when you attempt to auto-charge. When they receive the payment failure email, they add money to their account and inform you about this. You can then try to charge manually on the invoice.

An authentication charge of ₹5 is made to authenticate the card. Once the manual charge is successful, the customer receives an email, and you receive a notification via webhook.

You can attempt a manual charge on the invoice using the Dashboard.

If you have enabled the subscription.pending and subscription.halted webhook, you receive notifications every time a Subscription moves to one of the above-mentioned states. You can then decide to hold off the delivery of the service as per your business model.

We also send an email to the customer notifying them about the payment failure. This email contains a link that the customer can use to change the card details associated with the Subscription.

Change the Card Linked to the Subscription🔗

When an auto-charge fails, we send the customer an email about the payment failure. This email has a link that the customer can use to change the card linked to the Subscription.

You can ask the customer to change the card linked to the Subscription.

Change the Card via your Checkout🔗

You can ask the customer to change the card details associated with the Subscription via your checkout using our APIs. Use the subscription_card_change parameter to control this feature:

  • 1 = Allow the customer to change the card details from your checkout
  • 0 = Do not allow the customer to change the card details from your checkout

Handler Function vs Callback URL

  • Handler Function
    When you use the handler function, the response object of the successful payment (razorpay_payment_id, razorpay_order_id and razorpay_signature) is submitted to the checkout form. You need to collect these and send them to your server.
  • Callback URL
    When you use a Callback URL, the response object of the successful payment (razorpay_payment_id, razorpay_order_id and razorpay_signature) is submitted to the callback URL.

Update the Payment Method via our Hosted Page🔗

You can use our ready-made hosted page solution to handle payment failures when you attempt an auto-charge. Here is how the hosted page handles payment failure:

  1. The customer is notified via email about the payment failure.
  2. The payment failure email contains a link that allows the customer to take further action on the failed payment.
  3. Customers can either retry the payment on the same card or update the card details or change the payment method to UPI using the link. These actions are handled seamlessly by the hosted page.

A sample hosted page is shown below:

After the customer clicks the Update Payment Method button, the checkout page appears as shown. The customer can choose a card (of supported banks) or UPI to make the payment. If the payment is successful, the Subscription moves back to the active state.

Additionally, you can use the dashboard status filter to search for halted and pending Subscriptions. You can send the Subscription link to the respective customers to clear dues and make those Subscriptions active.

Handy Tips
To use our Hosted Page solution, pass 1 against the customer_notify parameter (that is, customer_notify=1) when creating the Subscription via APIs. Know more about the Subscription APIs.

×