Use Case: Renew a Manual-Renewal Subscription Ahead of Schedule

Assumptions and Preconditions


  1. On May 15th, 2016, a customer purchases a client's anti-virus subscription for $80 annually but does not confirm automatic renewal. Instead, the customer decides to manually renew the subscription at the end of the billing interval.
  2. On March 15th, 2017, the customer sees a message in the client's Customer Self-Service area asking him to renew his subscription now because it will soon expire. The message redirects the customer to a page that uses the Get Subscription API endpoint to obtain and display the price, new expiration date (May 15th, 2018), and other details regarding the subscription.
  3. After reviewing this information, the customer confirms this purchase by clicking a Buy Now button on the page. The page uses the Renew Subscription API endpoint to renew the customer's anti-virus subscription immediately.
  4. The cleverbridge platform bills the customer the full $80 price for the next billing interval, which starts immediately. The remaining two months from the current billing interval are added to the next billing interval, moving the next billing date to May 15th, 2018.
  5. The customer sees a confirmation pageClosedThe 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:


Obtain the customer's consent for changes to subscriptions. For more information, see Best Practices: Obtaining Customer Consent.