Subscription Settings

Modified on Tue, 1 Jul at 10:40 PM

Subscription-based businesses can efficiently handle failed payments by configuring automated payment retries. This ensures minimal disruption to services while giving businesses control over retry attempts and scheduling.

To get started, navigate the Settings tab inside the payments section and switch to the Subscription sector to configure payment retry options.

image


Payment Gateway Compatibility

These settings apply to the following payment providers:

Configuring Payment Retries

Customize the number of payment retry attempts and the intervals between them. You can define up to three (3) retries after an initial payment failure. The default setting includes three retries with a 1-day gap each, which can be adjusted as needed. Retry intervals can be set at 1, 3, 5, or 7 days between each attempt, and changes to retry settings will apply to both existing and new subscriptions, including those already in the retry process.

image


Subscription Status After Failed Retries

If all retries fail, you can handle the subscription in a few ways, besides keeping the subscription in an Unpaid state.

You can automatically cancel the subscription by selecting a checkbox in the settings.

image


To automatically create invoices after a subscription payment failed, enable this option.

image


Once enabled, select the channels you want to use to notify customers.

image


Once you have configured the retry settings, click “Save” to confirm and apply your changes.

image


This flexible approach allows you to effectively manage subscription payments while maintaining customer satisfaction and revenue continuity. By offering configurable retry settings and automated handling of failed payments, your business can reduce revenue loss, minimize manual intervention, and provide a more seamless experience for its subscribers.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article