> For the complete documentation index, see [llms.txt](https://docs.inqud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inqud.com/crypto-recurring/integration/web-hooks/authorization-web-hook.md).

# Authorization Web Hook

{% hint style="info" %}
For foundational information on webhooks, including key concepts and verification methods, please refer to the [Webhook Basics](/developer/web-hooks.md) page.
{% endhint %}

Authorization Web Hooks enable merchant systems to receive timely notifications regarding status changes of authorizations.

Learn more about authorizations:

{% content-ref url="/pages/VfOqMzU8kB8laaJrprQ5" %}
[Authorization](/crypto-recurring/explore/authorization.md)
{% endcontent-ref %}

### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

* Your business account with Inqud is set up.
* The Crypto Recurring Project has been established and configured within the Inqud platform.

### Setting up Web Hook <a href="#setting-up-web-hook" id="setting-up-web-hook"></a>

1. Open the app and sign in.
2. From the left menu bar, choose "Recurring".
3. Select the desired project.
4. Locate the "Authorization webhook" option and click on "Edit".
5. Enter the required details:
   * Webhook link: Provide the URL of your webserver that will handle the webhooks.
   * Webhook secret: Enter a secret key for signature calculation (optional).
6. Click on "Save" to finalize your settings.

### Notification

The Authorization Web Hook activates with every transition in authorization status. It requires your web server to respond with a 200 status code. If a different status code is returned, the Web Hook will attempt retries multiple times, using an exponential back-off strategy.

For detailed request specifications, please refer to the following page:

[Authorization Webhook Specification](https://apireference.inqud.com/#tag/crypto-recurring-webhooks/operation/user_crypto-recurring_create-webhook) (see **Callbacks** sections)