Customize Subscription Renewals

Tip

You can optimize subscription renewals and limit payment failures by customizing a scenario for subscription payment retry attempts.

Customize Your Ciklik Site

When you subscribe, a site hosted by Ciklik is deployed.

It will be displayed at the time of customer payment with the chosen PSP.

To maintain your brand identity, the following actions should be customized from your Ciklik account:

• Add your logo and favicon
• Apply your brand guidelines: dominant colors and fonts

Click on My Sites at the bottom of the left column, then on the small pencil icon (edit) next to your site, and go to the Appearance for your site tab.

You can import your logo and favicon, then save the changes by clicking the Update Site button at the bottom right.

Your color and font settings are configured in this same tab, in the CSS Variables field.

In addition to entering the names of your heading and text fonts in the CSS variables field, enter them in the Heading Font and Text Font fields, which are located above the first Custom CSS window.

Configure Payment Retry Attempts During Subscription Renewals

Default Settings

During subscription renewals, 4 payment retry attempts are scheduled by default in case of payment failure.

You can define the number of attempts and the number of days after which a new payment retry will be made from the day the transaction fails.

This setting is defined by clicking on My Sites then Edit, from the Marketing Settings tab, in the Rebill: Number of Days field.

In the example of a rebilling on the 1st of the month for a monthly subscription taken out on the 1st of the previous month, where 3 days is set for the number of days to trigger the new payment retry, here is what happens:

• transaction on the 1st of the month fails = next payment (payment attempt) on the 4th of the month (the 1st is the date when the transaction failure is detected, to which we add 3 days to define the date of the next attempt)
• transaction on the 4th fails = next payment on the 7th
• transaction on the 7th fails = next payment on the 10th
• transaction on the 10th fails = order closed and no order pushed to PrestaShop

Custom Settings

To define the number of attempts and the number of days between each attempt, indicate the attempt number followed by the number of days between each attempt, separated by :

Each sequence is separated by a ;

Sequence examples:

• 1:3;2:4;3:8: This means there are 4 attempts, a first attempt, the second 3 days later, the third 4 days later, and the fourth 8 days later. On the 4th attempt, the order fails and is permanently closed.
• 1:2;2:4: This means there are 3 payment retry attempts, spaced 2 then 4 days apart. On the 3rd attempt, the order fails and is permanently closed.
• 1:3;2:3;3:3;4:3: This means there are 5 payment retry attempts spaced 3 days apart. On the 5th attempt, the order fails and is permanently closed.

Email Notifications on Payment Failure

4 automatic emails are enabled to notify the subscriber that a payment has failed.

The content of these emails can be customized from the Content > Email Templates section.

These are the emails with Type:

• Payment Declined
• Payment Declined (2)
• Payment Declined (3)
• Payment Declined (4)

In the case where there are more than 4 payment retry attempts, the automatic email Payment Declined (4) will be sent for all attempts beyond the 4th.

Manage Payment Failures During Subscription Renewals

Each time a payment fails during subscription renewal, the subscriber receives an email informing them that there was a payment decline.

These automatic emails are accessible from your Ciklik account, in the Content category of the left column, Email Templates section. These emails have Type:

• Payment Declined
• Payment Declined (2)
• Payment Declined (3)
• Payment Declined (4)

You can customize the content of these emails.

A payment link is included in these emails to invite the subscriber to complete 3DS validation and finalize the transaction, with the variable {*link*}. Make sure to keep this variable.

Customize Automatic Emails Sent to Subscribers

When installing the Ciklik module, automatic emails are configured to be sent on your behalf to your subscribers.

You can choose to disable automatic sending of each email, keep some and disable others.

List of Automatic Emails

They cover the following subjects:

• User account creation
• Order confirmation
• Notification following subscription cancellation
• Notification following subscription reactivation
• Refund notification
• Notification in case of payment failure during subscription renewal
• Card expiring soon (The email is delivered on the 25th of the month if these 2 conditions are met: The customer will be rebilled between the 25th (day D) and the 25th of the following month + The customer’s credit card will expire at the end of the month)

Customizing Automatic Emails

Transactional Text Email or Email Template

You can customize the content of automatic emails by choosing a transactional text email format or by creating your own email template.

Click on the small pencil icon (edit) next to the email you want to customize.

You access the details of the email in question and can modify its subject.

Two options are then available:

• Use the text content window to stay with a transactional text email format
• Use the advanced mode with the email editor and uncheck the “enable deprecated mode” box (this box can be unchecked once the content from the editor is created)

If you choose to build your own email template, you have 3 accessible areas in the right column for:

• Blocks section: create the skeleton of your email with the desired number of rows and columns
• Content section: select the desired content per column: title, text, image, button, etc.
• Body section: define the background color of your emails, link color, etc.

For each element added to your email content, you access various settings in the second right column to customize it.

You can access a preview of your email in mobile version.

To save the email template you just created, you must click the Save Design button at the bottom left of the editor.

List of Available Variables

Variables are available for each email, to automatically include the customer’s name, order content, etc.

Some emails also contain a variable {*link*} that we recommend you keep.

This allows you to send a secure payment link in case of payment failure or to send a card update link to a customer without them needing to log into their customer account.

Template	Variables
Card Expiring Soon	{*shop*} {*logo*} {*domain*} {*first_name*} {*last_name*} {*address*} {*address2*} {*zipcode*} {*city*}
1st Rebilling Failure	{*shop*} {*logo*} {*domain*} {*first_name*} {*last_name*} {*address*} {*address2*} {*zipcode*} {*city*} {*link*}
2nd Rebilling Failure	{*shop*} {*logo*} {*domain*} {*first_name*} {*last_name*} {*address*} {*address2*} {*zipcode*} {*city*} {*link*}
3rd Rebilling Failure	{*shop*} {*logo*} {*domain*} {*first_name*} {*last_name*} {*address*} {*address2*} {*zipcode*} {*city*} {*link*}
Final Payment Failure	{*shop*} {*logo*} {*domain*} {*first_name*} {*last_name*} {*address*} {*address2*} {*zipcode*} {*city*} {*link*}
Subscription Cancelled	{*shop*} {*logo*} {*domain*} {*first_name*} {*last_name*} {*end_date*}
Subscription Resumed	{*shop*} {*logo*} {*domain*} {*first_name*} {*last_name*} {*address*} {*address1*} {*zipcode*} {*city*} {*customization*}
Subscription Confirmation	{*logo*} {*domain*} {*shop*} {*creation_date*} {*type_abo*} {*plan_price*} {*reduc*} {*total*} {*first_name*} {*last_name*} {*address*} {*address_1*} {*zipcode*} {*relay*} {*city*} {*resume*} {*referral_url*} {*end_date*} {*next_billing*} {*customization*}