Click on Automation Rules tab from the top menu then click Subscriptions on the left side:
Under Subscriptions Dunning click add new rule, then choose Start from Scratch to begin and follow the steps below:
Name The Rule
Use a unique name to help differentiate between multiple rules.
Set Condition
You can set your conditions by either your product name or by customer types (VIP or standard).
You can set the logic to say if it “IS in” or “Isn’t In” the values you want.
If you pick the first condition as a product name you can pick which product you want to apply the rule to. You can apply the rules to as many products as you would like to. You can also make different rules for each product.
You can set rules for your customers as well. If you want different types of rules for VIP customers you are able to select “customer type” and then select the VIP customer under “Values”. This is to ensure that you can set your VIP customers apart from your other customers.
Set Amount of Retry Attempts
You can add as many retries as you would like for every condition. You can choose from: Retry Immediately, Retry on a Specific Date or Retry After a Certain Amount of Time.
You can also choose to retry the transaction for a full amount or partial amount.
Decide What Will Happen After Each Event
You may wish to push the renewal time into the future according to your plan schedule after each retry attempt. Otherwise, the next bill may occur while you are still within the retry schedule of the current bill.
Decide What Happens After The Last Failed Attempt
You will have the options of canceling the subscription, abandoning the invoice and triggering a webhook:
Mail Preview
See what the emails we send to your customers will look like.
If you have any additional questions, please contact our Support Team by clicking the support widget in the bottom right corner of this page or email us at support@payments.ai.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article