> For the complete documentation index, see [llms.txt](https://docs.gobtcpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gobtcpay.com/api-reference/pos-api/gobtc-pay-pos-api/webhooks.md).

# Webhooks

Instead of polling **Get payment**, register a webhook endpoint in the **merchant dashboard** and GoBTC Pay will notify you when a payment's status changes. The `payment.status.updated` event is delivered as an HTTP `POST` wrapped in a thin envelope — `{ eventId, type, createdAt, data }` — where `data` matches the **Get payment** response.

Each delivery is signed. Verify the `X-GoBTCPay-Signature: t=<unix>,v1=<hmac>` header, where `v1 = HMAC-SHA256(signingSecret, "{t}.{rawBody}")` and the `signingSecret` is shown once when you create the endpoint. Delivery is at-least-once, so de-duplicate on `eventId`. Respond with any `2xx` to acknowledge; non-2xx responses are retried.

***

This is the **POS terminal** surface of the GoBTC Pay API. Backwards compatibility is preserved across published versions.

Found an error in the docs? Email <support@gomining.com>.


---

# 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.gobtcpay.com/api-reference/pos-api/gobtc-pay-pos-api/webhooks.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.