> 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/developer/web-hooks/payment-web-hook.md).

# Payment Web Hook

### Setup payment web hook

In order to receive payment updates you firstly need to specify the endpoint where you expect a web hook to come.

Use endpoint to create a payment webhook:\
[Create Payment Web Hook Endpoint ](https://apireference.inqud.com/#tag/payment-webhooks/operation/user_payment_create-webhook)

If **secret** is set up a special header will be passed along with every callback request:

```
X-Payload-Digest
```

The value of it is a **HmacSHA1** signature of the callback's body created using the callback secret provided by the user.

To know more about webhook verification refer to the following page:

{% content-ref url="/pages/tjNZjwL7G6WUeEgBabpK" %}
[Web Hook Verification](/developer/web-hooks/web-hook-verification.md)
{% endcontent-ref %}

### Notification

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

[Payment Web Hook Specification](https://apireference.inqud.com/#tag/payment-webhooks/operation/user_payment_create-webhook)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.inqud.com/developer/web-hooks/payment-web-hook.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.