Assumptions and Preconditions
- The subscription has the
Automaticrenewal type, which does not require the customer to initiate the renewal at the end of the billing interval.
- The current billing interval has started and the next billing date has not been reached yet.
- The renewal is not combined with an alignmentAlignment is the act of consolidating the billing for two separate subscriptions into a single recurring billing event. of the subscription. For more information, see Align Subscriptions.
- On February 15th, 2018, the IT department at Net Corp signs up for a subscription to anti-virus software. They receive 100 seats for $5,000 annually. The subscription renews automatically on February 15th of each year.
- On December 22nd, 2018, the director is informed that he has excess budget in the IT department which must be spent before December 31st. To spend his excess budget, the director decides to renew Net Corp's anti-virus subscription early.
- The director logs onto his Customer Self-Service and clicks on the Renew Now button. The Renew Now button redirects the customer to a review pageThe review page contains summary information about the purchase a customer is about to make. that uses the Renew Subscription API endpoint to obtain and display the price, new expiration date (February 15th, 2020), and other details regarding the subscription.
- After reviewing this information, the customer confirms this purchase by clicking a Buy Now button on the review page. The page uses the Subscription API to renew the customer's anti-virus subscription immediately.
The cleverbridge platform immediately bills the customer the price for the next billing interval ($5,000). The next billing interval starts on February 15th, 2019.
The remaining days of the current billing interval (December 22nd, 2018 - February 15th, 2019) were paid for when the customer completed the initial payment on February 15th, 2018.
- The customer sees a confirmation pageThe confirmation page is displayed after a customer makes a purchase. The confirmation page contains the order confirmation and delivery information., which is either created by the client or provided by the Subscription API. If the transaction is not successful, the page provided by the API will inform the customer about the next steps, such as updating the payment details in case of a failed payment.
Although not utilized in this use case, the following option is also available:
- Combine the early renewal with an upgrade of the subscription, for example, from monthly to yearly or from basic to premium. For more information, see Use Case: Combine an Immediate Upgrade with an Early Renewal (Monthly to Yearly) and Use Case: Combine an Immediate Upgrade with an Early Renewal (Basic to Premium).
Obtain the customer's consent for changes to subscriptions. For more information, see Best Practices: Obtaining Customer Consent.