Skip to main content
knowledgecenter.avangate.com

License Change Notification (LCN)

Overview

License Change Notification (LCN) works as a message service generating automatic subscription notifications for your Avangate account. Use the notifications to process subscription data into your own management systems by synchronizing it with Avangate account events. Avangate generates notifications for subscription update and expiration events (including past due notifications).

How can I use LCN?

Use LCN to automate back-end functions for your services, including but not limited to:

  • Creating end user accounts
  • Providing access to acquired services
  • Manage subscriptions
  • Fulfilling purchases
  • Engaging subscribers
  • Converting trials to paid subscriptions
  • Cutting access to delinquent account

Webhook asynchronicity

Avangate’s webhooks (IPN and LCN) operate asynchronously

How does LCN work?

  1. Create one or multiple LCN listener pages on your website. Avangate sends LCNs to publicly accessible servers.
  2. Configure the LCN settings of your Avangate account to point to the URLs of your default/preferred listener pages.
  3. Set up multiple URLs if you require more listener pages, such as in testing scenarios in which you don’t want to use your default LCN listener. 
  4. Avangate sends subscription notifications to the endpoints you defined when subscribers change specific subscription details, using secure (HTTPS) POST.
  5. Avangate uses a HMAC_MD5 signature to validate the HTTPS POST. Calculate the signature using data sent and your Avangate account’s secret key, following the instructions included in this article.
  6. Your custom LCN listener scripts consume the notifications and process the info received.
  7. Configure your LCN listener to output a read receipt confirmation in the listener page after receiving a valid LCN message. This article includes guidance on how to generate the confirmation.
  8. In the absence of a confirmation from one of your LCN listeners, Avangate continues to send notifications to that endpoint, according to the failure retry process, until you provide a valid response.
  9. The Avangate system regularly checks the status of subscriptions to identify expired items and modifications. Avangate then sends notifications for expirations as well as for updates occurred in the last 24 hours prior to the moment when it perform the check. Avangate does not re-send notifications for the same event unless the status of the subscription changes or it identifies additional modifications.

Set up the default LCN URL

  1. Login into your Avangate account.
  2. Navigate to LCN settings under System settings.
  3. Enter the URL corresponding to your default LCN listener in the LCN URL field.
  4. Save your settings.
  5. Avangate checks the validity of the URLs in terms of access to ensure that notifications reach your LCN listener without issues.

Set up multiple LCN URLs

You can set up multiple endpoints for your LCN notifications, for scenarios in which you have multiple Internal System that require to receive this information. You can set up to 3 URLs for each notification type, and you can particularize the IPN / LCN triggers for each endpoint.

To add multiple endpoints, navigate to the LCN settings tab and click New LCN configuration.

Set up additional LCN URLs

Navigate to LCN settings under System settings, select the Notification URLs tab and click New URL configuration to create an additional URL configuration for your notifications.

Debug LCN

To view or debug LCN notifications during the integration phase, place TEST orders.

Alternatively, search for specific subscriptions in the Subscriptions area. In the subscription details page you have the option to resend notifications. You can also see how many LCN notifications have been sent so far for a subscription. Opt to reissue the LCN for debug and Avangate re-generates and re-sends the LCN, but also displays a copy of the content sent in the control panel.

Secure your LCN script 

For security reasons, Avangate recommends that you restrict access to the LCN script.