> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/2checkout-apis/2checkout-apis/webhooks/ipn-and-lcn-url-settings.md).

# IPN and LCN URL Settings

## Overview

Set the IPN and LCN settings in your Merchant Control Panel and assign a single specific webhook to a single URL by using the NOTIFICATION\_URL parameter. If you add a second, third, or fourth endpoint in the IPN or LCN tab, 2Checkout can send [Instant Payment Notifications](/2checkout-apis/2checkout-apis/webhooks/instant-payment-notification-ipn.md) (IPN) and [License Change Notifications](/2checkout-apis/2checkout-apis/webhooks/license-change-notification-lcn.md)(LCN) to alternative URLs, not just the defaults.

## Availability

Available for all 2Checkout accounts using the Default Flows cart. Not available to 2Checkout accounts using only the ConvertPlus shopping cart.

## How it works

The 2Checkout system sends out notifications (IPNs and LCNs) to the URLs that you can configure in the URL areas under:

* [IPN settings](https://secure.avangate.com/cpanel/ipn_settings.php) (<https://secure.2checkout.com/cpanel/ipn\\_settings.php>)
* [LCN settings](https://secure.avangate.com/cpanel/lcn_settings.php) (<https://secure.2checkout.com/cpanel/lcn\\_settings.php>)
* [Both IPN and LCN](https://secure.avangate.com/cpanel/notification_urls.php) (<https://secure.2checkout.com/cpanel/webhooks\\_api.php>)

You can prioritize sending to a specific endpoint URL using the NOTIFICATION\_URL parameter, as described below under the "How do I get 2Checkout to send IPNs and LCNs to URLs other than the default links set?" section. However, if you set a default URL in the Notification URLs section, then the notification is sent to that particular URL, as well as any other URL set in the IPN/LCN dedicated tab unless specified otherwise when using the parameter.

## Requirements

Enter valid URLs for both IPN and LCN when editing URL configurations.

## Default IPN and LCN URLs

{% stepper %}
{% step %}

### IPN

1. Navigate to [IPN settings](https://secure.avangate.com/cpanel/ipn_settings.php) (<https://secure.2checkout.com/cpanel/ipn\\_settings.php>).
2. Enter the default URL where the 2Checkout system will send out Instant Payment Notifications (IPNs).
3. Changes to the IPN URL in the [IPN settings](https://secure.avangate.com/cpanel/ipn_settings.php) area reflect under the default URL notification [configuration](https://secure.avangate.com/cpanel/notification_urls.php) for your account, if only one value is entered and edited. For multiple values, only the first one is taken into account.
   {% endstep %}

{% step %}

### LCN

1. Navigate to [LCN settings](https://secure.avangate.com/cpanel/lcn_settings.php) (<https://secure.2checkout.com/cpanel/lcn\\_settings.php>).
2. Enter the default URL where the 2Checkout system will send out License Change Notifications (LCNs).
3. Changes to the LCN URL in the [LCN settings](https://secure.avangate.com/cpanel/ipn_settings.php) area reflect under the default URL notification [configuration](https://secure.2checkout.com/cpanel/webhooks_api.php) for your account, if only one value is entered and edited. For multiple values, only the first one is taken into account.
   {% endstep %}

{% step %}

### Default URL configuration

1. Navigate to the Integrations → Webhooks and API section (<https://secure.2checkout.com/cpanel/webhooks\\_api.php>).
2. Edit the Default URL configuration.
3. Enter URLs for both IPN (mandatory) and LCN notifications (mandatory) and Save.
4. The settings automatically reflect under the IPN URL in the [IPN settings](https://secure.avangate.com/cpanel/ipn_settings.php) area and the LCN URL in the [LCN](https://secure.avangate.com/cpanel/ipn_settings.php) [settings](https://secure.avangate.com/cpanel/ipn_settings.php) area. Note that this will not edit the current value, but add one new entry. Removing this value from a total of 4 in the dedicated IPN/LCN section will not replace the default one in the general section, it will only leave a blank.
5. Changes to the default URL notification [configuration](https://secure.avangate.com/cpanel/notification_urls.php) for your account reflect under the IPN URL in the [IPN](https://secure.avangate.com/cpanel/ipn_settings.php) [settings](https://secure.avangate.com/cpanel/ipn_settings.php) area and the LCN URL in the [LCN settings](https://secure.avangate.com/cpanel/ipn_settings.php) area.
6. Click Reset to revert a URL configuration to the last saved state.
   {% endstep %}
   {% endstepper %}

## Custom IPN and LCN URLs

{% stepper %}
{% step %}

1. Navigate to the Integrations → Webhooks and API section (<https://secure.2checkout.com/cpanel/webhooks\\_api.php>) in your Merchant Control Panel.
   {% endstep %}

{% step %}
2\. Scroll down to the Notification URLs section and click on the Add additional URL button to gain access to the parameter value field.
{% endstep %}

{% step %}
3\. Enter a parameter value. You will use this parameter in buy-links for new purchases, manual subscription renewals, and upgrades, controlling the URLs used by the 2Checkout system to send IPN and LCN notifications. Read below for instructions.
{% endstep %}

{% step %}
4\. Enter URLs for both IPN (mandatory) and LCN notifications (mandatory) and click Save.
{% endstep %}

{% step %}
5\. The settings reflect under the IPN URL in the [IPN settings](https://secure.avangate.com/cpanel/ipn_settings.php) area and the LCN URL in the [LCN](https://secure.avangate.com/cpanel/ipn_settings.php) [settings](https://secure.avangate.com/cpanel/ipn_settings.php) area.
{% endstep %}

{% step %}
6\. Changes to the default URL notification configuration for your account reflect under the IPN URL in the [IPN](https://secure.avangate.com/cpanel/ipn_settings.php) [settings](https://secure.avangate.com/cpanel/ipn_settings.php) area and the LCN URL in the [LCN settings](https://secure.avangate.com/cpanel/ipn_settings.php) area.
{% endstep %}

{% step %}
7\. Click Reset to revert a URL configuration to the last saved state.
{% endstep %}
{% endstepper %}

### How do I get 2Checkout to send IPNs and LCNs to URLs other than the default links set?

You can use the multiple URL functionality and send IPN and LCN notifications to several URLs. Once you set multiple URLs for receiving IPN or LCN notifications, you will receive the same keys/parameters on all endpoints without having the possibility to customize them based on the defined endpoints. However, if the URL from the general section is not declared under the IPN/LCN tabs as well, the notification will still be sent if the parameter is used. You can set up eight (8) URLs for both your IPN and LCN notifications.

To set multiple URLs, you need to use the:

* Parameter value specified for each new URL configuration. The parameter value can be found in the Parameter Value field by navigating to Integrations → Webhooks and API section, scrolling down to the Notification URLs section, selecting the Configuration parameter, and clicking on the Edit button.

![parameter\_value.png](/files/ada28006bfc9d4b26272faa55320b54d51d16379)

* And the NOTIFICATION\_URL parameter in buy-links (for new purchases, manual subscription renewals, and upgrades).

For example, let's assume that you created a URL configuration with the following settings:

|                  |                                                                                       |
| ---------------- | ------------------------------------------------------------------------------------- |
| Parameter value: | MYTESTNOTIFICATIONS                                                                   |
| IPN URL:         | [http://www.MyDomain.com/ipn\_response.php](http://www.mydomain.com/ipn_response.php) |
| LCN URL:         | [http://www.MyDomain.com/lcn\_response.php](http://www.mydomain.com/lcn_response.php) |

And that you're using this buy-link:

```
https://secure.2checkout.com/order/checkout.php?PRODS=1234567&QTY=1&CART=1&CARD=2
```

You need to insert NOTIFICATION\_URL=MYTESTNOTIFICATIONS into the buy-link:

```
https://secure.2checkout.com/order/checkout.php?PRODS=1234567&QTY=1&CART=1&CARD=2&NOTIFICATION_URL=MYTESTNOTIFICATIONS
```

### IPN and LCN HASH

#### Default URLs for IPN and LCN

IPN HASH = HMAC\_SHA signature calculated from IPN\_PID\[0], IPN\_PNAME\[0], IPN\_DATE and DATE and the [Secret key for your account](https://secure.avangate.com/cpanel/account_settings.php) for notifications sent to the default URL parameters configured for your account.

LCN HASH = HMAC\_SHA signature calculated using the secret key for your account and the values received for LICENSE\_CODE, EXPIRATION\_DATE, DATE and the [Secret key for your account](https://secure.avangate.com/cpanel/account_settings.php) for notifications sent to the default URL parameters configured for your account.

#### Custom IPN and LCN configurations

IPN HASH = HMAC\_SHA signature calculated from IPN\_PID\[0], IPN\_PNAME\[0], IPN\_DATE and DATE and the system-generated secret keys when custom URL configurations are used.

LCN HASH = HMAC\_SHA signature calculated using the values received for LICENSE\_CODE, EXPIRATION\_DATE, DATE and the system-generated secret keys when custom URL configurations are used.

### FAQs

<details>

<summary>Where can I find the secret key?</summary>

For custom IPN and LCN URL:

1. Navigate to the Integrations → Webhooks and API section (<https://secure.2checkout.com/cpanel/webhooks\\_api.php>).
2. Click on the Add IPN URL or on the Add LCN URL buttons, or the Edit button of one of the existing URL configurations.
3. The system-generated secret key valid for each URL configuration respectively is available in the IPN/LCN secret key field.

</details>

<details>

<summary>What notifications are sent to the URLs set through the NOTIFICATION_URL parameter and for what triggers?</summary>

The IPN and LCN notifications for the initial purchase, as well as for the subsequent renewals of the subscriptions generated for this order and for any future upgrades will be sent to the IPN and URL parameters.

| Trigger                              | IPN | LCN | Non-default URLs set using NOTIFICATION\_URL |
| ------------------------------------ | --: | --: | -------------------------------------------: |
| New purchase/order of a subscription | YES | YES |                                          YES |
| Manual renewal of the subscription   | YES | YES |                                          YES |
| Automatic subscription renewal       | YES | YES |                                          YES |
| Subscription upgrade                 | YES | YES |                                          YES |

</details>

<details>

<summary>What is the default value of NOTIFICATION_URL?</summary>

Include NOTIFICATION\_URL=DEFAULT (case sensitive) to send IPN and LCN notifications to the default URLs you configure.

</details>

<details>

<summary>Is the value of the parameter saved on each order and subscription?</summary>

The IPN value is mentioned in the order history, but at the subscription level, neither the IPN nor the LCN is visible, unless you use the subscription reference number in the reporting section to identify the LCN.

</details>

<details>

<summary>What happens with future notifications if I used the NOTIFICATION_URL parameter?</summary>

All future LCN and IPN notifications for future renewals and upgrades of current subscriptions for which a NOTIFICATION\_URL value was used will be sent to the URLs configured for that value.

</details>

<details>

<summary>What happens if I change the value for a parameter used?</summary>

All future LCN and IPN notifications for renewals and upgrades of current subscriptions for which a NOTIFICATION\_URL value was used will be sent to the default URLs configured for your account.

What happens if I change the custom URLs for a configuration?

All future LCN and IPN notifications for renewals and upgrades of current subscriptions for which a NOTIFICATION\_URL value was used will be sent to the new URLs configured.

</details>

<details>

<summary>Can I use multiple endpoints for the NOTIFICATION_URL parameter and send IPNs and LCNs to more than one URL each?</summary>

You can use multiple endpoints in the specific LCN/IPN section, but you cannot add multiple endpoints in the general section. The NOTIFICATION\_URL parameter offers the option to use specific endpoints for specific buy-links, but does not “add” to the default ones. You can set up eight (8) URLs for both your IPN and LCN notifications.

</details>

<details>

<summary>Is this parameter available for network cross-selling orders through the 2Checkout system?</summary>

No, the parameter will only work for your account.

</details>

<details>

<summary>Does this parameter work for partner and API orders?</summary>

This functionality is not supported for the time being.

</details>

### Related

* [Webhooks upgrade to the SHA algorithm](https://verifone.cloud/docs/2checkout/API-Integration/01Start-using-the-2Checkout-API/2Checkout-API-general-information/Migration_guide_SHA2_SHA3/Webhooks_upgrade_to_the_SHA_algorithm)
* [Webhooks](https://verifone.cloud/docs/2checkout/API-Integration/Webhooks)
* [LCN POST failure recovery process](/2checkout-apis/2checkout-apis/webhooks/license-change-notification-lcn/lcn-post-failure-recovery-process.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.2checkout.com/2checkout-apis/2checkout-apis/webhooks/ipn-and-lcn-url-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.