> For the complete documentation index, see [llms.txt](https://developers.hyp.co.il/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.hyp.co.il/enterprise/payment-page-integration/webhooks.md).

# Receiving Notifications via Webhooks

In addition to handling the [payment completion redirect](https://developers.hyp.co.il/enterprise/payment-page-integration/integrating-hyps-payment-page-and-accepting-payment.md#handle-payment-completion-redirect), you may want to use webhooks as a transaction status delivery mechanism.

Webhooks provide a reliable server-to-server fallback in case the client-side redirect doesn't return a response due to connectivity issues or the user closing their browser too early. They are sent asynchronously (usually within seconds with a retry mechanism) for all transaction results.

Hyp Enterprise push notifications are powered by Amazon SNS (Simple Notification Service). When you register a webhook endpoint in the Hyp Console, Amazon SNS starts sending POST requests that deliver transaction notifications to your receiver application.

## Prerequisites

Before you enable webhooks, **set up a receiver application** — either a custom application or a third-party webhook service — that exposes an endpoint prepared to handle the POST requests sent by Amazon SNS. The receiver application must meet the following requirements:

* **HTTPS**: Your receiver application must use a server certificate signed by a trusted Certificate Authority (CA). Amazon SNS will not send messages to endpoints with self-signed or untrusted certificates.
* **Initial confirmation**: Your receiver application must be able to receive and process the initial `SubscriptionConfirmation` message sent by Amazon SNS when you register a webhook subscription.
* **Response status and timeout**: Your receiver application must respond to every notification with a successful status code in the 200–4xx range within 15 seconds. If the connection times out or returns an error, Amazon SNS will consider the delivery attempt failed and will retry according to its [retry policy](https://docs.aws.amazon.com/sns/latest/dg/SendMessageToHttp.prepare.html).
* **Firewall settings**: The firewall protecting your receiver application's endpoint must allow traffic from Amazon SNS. If you use a service like Cloudflare, you may need to whitelist the `Amazon Simple Notification Service Agent` User-Agent.

There are two approaches that you can use to fulfill these prerequisites.

### Approach 1: Third-party webhook services (best for testing)

During development or sandbox testing, you can route traffic to an external webhook monitoring service like [webhook.site](https://webhook.site/).

* **How it handles confirmations:** Webhook services **do not automatically confirm the subscription**. You must open the service's dashboard, locate the `SubscriptionConfirmation` JSON payload, and manually copy/paste the `SubscribeURL` into your browser to activate it.
* **How it handles notifications:** Once manually confirmed, subsequent transaction notifications will appear in your third-party dashboard for visual inspection and debugging. Webhook services will normally automatically reply to Amazon SNS with a `200 OK` status code.

### Approach 2: Custom receiver application (best for production)

You deploy a dedicated endpoint within your own software stack (e.g., an Express.js, Python, or .NET backend).

* **How it handles confirmations:** Your application code needs to intercept the initial `SubscriptionConfirmation` notification, extract the `SubscribeURL`, and programmatically send a GET request to it to activate the subscription.
* **How it handles notifications:** Once confirmed, your receiver application needs to automatically parse incoming transaction notifications, auto-reply to them, and update your internal database or order status.

When developing a custom receiver application, follow Amazon's [guidelines on preparing to process SNS messages](https://docs.aws.amazon.com/sns/latest/dg/SendMessageToHttp.prepare.html). In addition, mind the following:

* You can use the `x-amz-sns-message-type` header of the POST requests that Amazon SNS sends to your endpoint to determine the message type without having to parse the body of the HTTPS request. The possible values are:
  * `SubscriptionConfirmation` – sent for one-time subscription confirmation.
  * `Notification` – sent for each Hyp Enterprise transaction.
  * `UnsubscribeConfirmation` – sent when you choose to unsubscribe from webhook notifications.
* You can use the `x-amz-sns-message-id` header to compare the IDs of the messages you have already processed with incoming messages. This will help you determine whether a message is new or represents a retry attempt.
* For guidance on parsing POST requests from Amazon SNS, see [Parsing Amazon SNS message formats](https://docs.aws.amazon.com/sns/latest/dg/sns-message-and-json-formats.html).
* To ensure message authenticity and integrity and prevent spoofing, Amazon's best practice recommendation is that you verify every SNS message. For an up-to-date verification guide, see [Verifying the signature of an Amazon SNS message when using HTTP query-based requests](https://docs.aws.amazon.com/sns/latest/dg/sns-verify-signature-of-message-verify-message-signature.html).

## Setting up webhooks

Setting up webhooks is a two-part process: first, you create a new webhook subscription in your Hyp Console, and then you confirm the subscription.

### Creating a webhook subscription

1. In your Hyp Console, click **Manage** in the sidebar.
2. Under **Webhook Service Management**, select **Payment page**: ![Hyp Console sidebar](https://3255314327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQDmIAW4sQ20lCItJGzcS%2Fuploads%2Fgit-blob-adb3f46c1bf462cad48f595ebe616172fa8a1937%2Fwebhooks-sidebar.png?alt=media)
3. Click **New Subscription**.
4. In the **Receiving Automatic Updates via WEBHOOK** form, fill in the following details:
   * **Subscription Name**: A descriptive name for this webhook (e.g., "Production Webhook").
   * **ENDPOINT Address**: The full HTTPS URL of your receiver application's endpoint where you want to receive notifications.
   * **Alert Format**: Select whether you want to receive the transaction data in **JSON** or **XML** format.
   * **Terminal Selection**: Choose whether to receive notifications for **All Terminals** or select specific terminals from the list.
5. Click **Register for Service**.

The new subscription will be created in the *Pending Approval* status. Meanwhile, an Amazon SNS confirmation request will be sent to your defined endpoint.

### Confirming your subscription

Look for a message of type `SubscriptionConfirmation` from Amazon SNS:

<details>

<summary>Show a SubscriptionConfirmation message example</summary>

```json
{
  "Type" : "SubscriptionConfirmation",
  "MessageId" : "3ceeb8a2-7aac-4344-b311-4065b54aecbc",
  "Token" : "2336412f37fb687f5d51e6e2425929f52bf0d75a00d118b115e89615be18a144306a6a40a41ab14cc11fca4ca40073113a12149f5734dcbaaf616f4890ff5a476d0f552b7d797e3321f41d89ee0b4421ee7166c426a9fba48dba12f270e732c6c60e57f1c178d19ddbea99b903c99cb17483c5e87062475362ce7bec6fc28df55684bc7fe9ca99bacd1c653cc4d478c86cdeafdd7d50d3386ebcd6a9b8041f94c507913bcda0ff0ae2f576e82403f08928ed2220a8997d3b3465c583ea72517f",
  "TopicArn" : "arn:aws:sns:eu-north-1:154299021161:systemId_cg_environment_uat_eventType_mpiTransaction_cgServerId_157_merchantId_CG-02487",
  "Message" : "You have chosen to subscribe to the topic arn:aws:sns:eu-north-1:154299021161:systemId_cg_environment_uat_eventType_mpiTransaction_cgServerId_157_merchantId_CG-02487.\nTo confirm the subscription, visit the SubscribeURL included in this message.",
  "SubscribeURL" : "https://sns.eu-north-1.amazonaws.com/?Action=ConfirmSubscription&TopicArn=arn:aws:sns:eu-north-1:154299021161:systemId_cg_environment_uat_eventType_mpiTransaction_cgServerId_157_merchantId_CG-02487&Token=2336412f37fb687f5d51e6e2425929f52bf0d75a00d118b115e89615be18a144306a6a40a41ab14cc11fca4ca40073113a12149f5734dcbaaf616f4890ff5a476d0f552b7d797e3321f41d89ee0b4421ee7166c426a9fba48dba12f270e732c6c60e57f1c178d19ddbea99b903c99cb17483c5e87062475362ce7bec6fc28df55684bc7fe9ca99bacd1c653cc4d478c86cdeafdd7d50d3386ebcd6a9b8041f94c507913bcda0ff0ae2f576e82403f08928ed2220a8997d3b3465c583ea72517f",
  "Timestamp" : "2026-06-17T10:24:02.222Z",
  "SignatureVersion" : "2",
  "Signature" : "SCXTCcw43r7rj3KwSd83Zai7X5S9SBPsZ/5k75uJ7HUyt7l5FTw2wQxmkXwO7rBITgw3HmL6c/pcIPmXmhjGHytZcSzUihDvrhZ3Wrt/f5Y3JzOtkxtdVTSfDK9TYXkBqMzsgdBcwgd7/Zt48eCb1YSb2Ia0ISxWM3DXax8PqI/O6RQnq2cOoBnQa0LvNn4ZpU3MEjjBfuW2WZGgqV5Oe+SCaG3U3gfrXtTgVAshege6TxLMs1ZncLP+v/GunmsKobS27/95a1X5ilZeAy3d6hytmoR647kG+7+dUBfc4BRIU2v3MTyldRubANi6Keh+x7zj8esq9jSYzWPewSUm5w==",
  "SigningCertURL" : "https://sns.eu-north-1.amazonaws.com/SimpleNotificationService-7506a1e35b36ef5a444dd1a8e7cc3ed8.pem"
}
```

</details>

To start receiving notifications, your receiver application must:

1. Extract a URL from the `SubscribeURL` field of the request body.
2. Perform an HTTP GET request to that URL to confirm the subscription.

Once confirmed, the endpoint subscription in your Hyp Console will be marked as active, and Amazon SNS will begin sending transaction notifications to the endpoint.

## Processing transaction notifications

When a transaction occurs, Amazon SNS sends a `Notification` message:

<details>

<summary>Show a transaction notification example</summary>

```json
{
  "Type" : "Notification",
  "MessageId" : "76b18d53-0dc9-584a-ad30-efff941d92c2",
  "TopicArn" : "arn:aws:sns:eu-north-1:154299021161:systemId_cg_environment_uat_eventType_mpiTransaction_cgServerId_157_merchantId_CG-02487",
  "Message" : "PHRyYW5zYWN0aW9uPjxzdGF0dXM+MDAwPC9zdGF0dXM+PHN0YXR1c1RleHQ+UGVybWl0dGVkIHRyYW5zYWN0aW9uPC9zdGF0dXNUZXh0PjxleHRlbmRlZFN0YXR1cy8+PGV4dGVuZGVkU3RhdHVzVGV4dC8+PGV4dGVuZGVkVXNlck1lc3NhZ2UvPjx0ZXJtaW5hbE51bWJlcj4wODgyODE4MDEyPC90ZXJtaW5hbE51bWJlcj48Y2FyZElkPjEwNzgzNDQyMTA2MzM0MzE8L2NhcmRJZD48Y2FyZEJpbj40NTU3NDM8L2NhcmRCaW4+PGNhcmRNYXNrPjQ1NTc0MyoqKioqKjM0MzE8L2NhcmRNYXNrPjxjYXJkTGVuZ3RoPjE2PC9jYXJkTGVuZ3RoPjxjYXJkTm8+eHh4eHh4eHh4eHh4MzQzMTwvY2FyZE5vPjxjYXJkTmFtZS8+PGNhcmRFeHBpcmF0aW9uPjEyMjY8L2NhcmRFeHBpcmF0aW9uPjxjYXJkVHlwZSBjb2RlPSIwMCI+TG9jYWw8L2NhcmRUeXBlPjxleHRlbmRlZENhcmRUeXBlIGNvZGU9IjAiPkNyZWRpdDwvZXh0ZW5kZWRDYXJkVHlwZT48Y3JlZGl0Q29tcGFueSBjb2RlPSIxIj5Jc3JhY2FyZDwvY3JlZGl0Q29tcGFueT48Y2FyZEJyYW5kIGNvZGU9IjIiPlZpc2E8L2NhcmRCcmFuZD48Y2FyZEFjcXVpcmVyIGNvZGU9IjEiPklzcmFjYXJkPC9jYXJkQWNxdWlyZXI+PHNlcnZpY2VDb2RlLz48dHJhbnNhY3Rpb25UeXBlIGNvZGU9IjAxIj5SZWd1bGFyRGViaXQ8L3RyYW5zYWN0aW9uVHlwZT48Y3JlZGl0VHlwZSBjb2RlPSIxIj5SZWd1bGFyQ3JlZGl0PC9jcmVkaXRUeXBlPjxjdXJyZW5jeSBjb2RlPSIxIj5JTFM8L2N1cnJlbmN5PjxiYXNlQ3VycmVuY3kvPjxiYXNlQW1vdW50Lz48dHJhbnNhY3Rpb25Db2RlIGNvZGU9IjUyIj5JbnRlcm5ldDwvdHJhbnNhY3Rpb25Db2RlPjx0b3RhbD4xMTQwMDwvdG90YWw+PGZpcnN0UGF5bWVudC8+PHBlcmlvZGljYWxQYXltZW50Lz48bnVtYmVyT2ZQYXltZW50cz4wPC9udW1iZXJPZlBheW1lbnRzPjxjbHViSWQvPjx2YWxpZGF0aW9uIGNvZGU9IjQiPkF1dG9Db21tPC92YWxpZGF0aW9uPjxpZFN0YXR1cyBjb2RlPSIwIj5BYnNlbnQ8L2lkU3RhdHVzPjxjdnZTdGF0dXMgY29kZT0iMyI+Tm90VmFsaWRhdGVkPC9jdnZTdGF0dXM+PGF1dGhTb3VyY2UgY29kZT0iMiI+Q3JlZGl0Q29tcGFueTwvYXV0aFNvdXJjZT48YXV0aE51bWJlcj42ODY0MjQxPC9hdXRoTnVtYmVyPjxmaWxlTnVtYmVyPjQ4PC9maWxlTnVtYmVyPjxzbGF2ZVRlcm1pbmFsTnVtYmVyPjAwMzwvc2xhdmVUZXJtaW5hbE51bWJlcj48c2xhdmVUZXJtaW5hbFNlcXVlbmNlPjA4NDwvc2xhdmVUZXJtaW5hbFNlcXVlbmNlPjxlY2k+NzwvZWNpPjxjbGllbnRJcC8+PGVtYWlsLz48Y2F2diBjb2RlPSIiLz48dXNlci8+PGFkZG9uRGF0YS8+PHN1cHBsaWVyTnVtYmVyPjcxNTA2PC9zdXBwbGllck51bWJlcj48aWQ+MDA4MzM2MTc0PC9pZD48c2hpZnRJZDEvPjxzaGlmdElkMi8+PHNoaWZ0SWQzLz48c2hpZnRUeG5EYXRlLz48Y2dVaWQ+MTI3NDk4NDY1PC9jZ1VpZD48Y2FyZEhhc2gvPjxjdXN0b21lckRhdGE+PHVzZXJEYXRhMT5KZW5ueSBQYXJraW5ndG9uPC91c2VyRGF0YTE+PC9jdXN0b21lckRhdGE+PGFjcXVpcmVyRGF0YT48YWNxdWlyZXJSZXNwb25zZUlkPjczODUwNjYyMTA4MjwvYWNxdWlyZXJSZXNwb25zZUlkPjxhY3F1aXJlclJlc3BvbnNlRGF0YS8+PHdhbGxldFN1cHBsaWVySWQvPjxtY2M+NDEyMTwvbWNjPjwvYWNxdWlyZXJEYXRhPjxhc2hyYWl0RW12RGF0YT48bXRpPjEwMDwvbXRpPjwvYXNocmFpdEVtdkRhdGE+PGV4dGVuZGVkVHJhbkNvZGUvPjxzZW5kTm90aWZpY2F0aW9uLz48bWVzc2FnZT5QZXJtaXR0ZWQgdHJhbnNhY3Rpb248L21lc3NhZ2U+PHVzZXJNZXNzYWdlPlBlcm1pdHRlZCB0cmFuc2FjdGlvbjwvdXNlck1lc3NhZ2U+PG1waVRyYW5zYWN0aW9uPjE8L21waVRyYW5zYWN0aW9uPjxtcGlUcmFuc2FjdGlvbklkPmZlZTNjY2M0LWQ3ODgtNDhkNC1hMGM3LTkyMGRhZmFiNjVmYjwvbXBpVHJhbnNhY3Rpb25JZD48ZmluYW5jaWFsU3RhdHVzPkNhcHR1cmVkPC9maW5hbmNpYWxTdGF0dXM+PHRyYW5JZD4xMjc0OTg0OTY8L3RyYW5JZD48c2hvdmFyPjAwMzA4NDwvc2hvdmFyPjx0cmFuc2FjdGlvbkRhdGU+MjAyNi0wNi0xNyAxNTo0ODoxOTwvdHJhbnNhY3Rpb25EYXRlPjwvdHJhbnNhY3Rpb24+",
  "Timestamp" : "2026-06-17T12:48:20.638Z",
  "SignatureVersion" : "2",
  "Signature" : "HS/dwfMSiOh5LNwSIN9PLErGhGGV5RmEg7eThgGaaNaBESLiSrGmNkJkvU025QmJWKq5hAZU1XTQuWdeESRKiFR6cQVQQO1FkKG0KXlYB/KDuulLxv1FrIoB2UYSVlzVTbVRJWzfjhmMw2sa/Ysl/UGXbdwJ2ch5N7tmdRBO53CyOYWd0tK10UQB+2GH2KrZeqnfdc4OMPCRxAIwqECYIMH5VTrC6wzt1LNMEA/u+lidvv5s6r1N8a50zdQRkOD2Mv+buSd+31zH0qpIJhvctsnVWAtgOwHdRCoawHasNvm2ufuXq9szoVJQ6/UbtmiGsTjJdpSVEF89wh8k3F2d+w==",
  "SigningCertURL" : "https://sns.eu-north-1.amazonaws.com/SimpleNotificationService-7506a1e35b36ef5a444dd1a8e7cc3ed8.pem",
  "UnsubscribeURL" : "https://sns.eu-north-1.amazonaws.com/?Action=Unsubscribe&SubscriptionArn=arn:aws:sns:eu-north-1:154299021161:systemId_cg_environment_uat_eventType_mpiTransaction_cgServerId_157_merchantId_CG-02487:e60bf0ed-8b36-4d98-977d-dac57f9fd82c",
  "MessageAttributes" : {
    "result" : {"Type":"String","Value":"000"},
    "terminalNumber" : {"Type":"String","Value":"0882818012"},
    "total" : {"Type":"String","Value":"11400"},
    "jcode" : {"Type":"String","Value":"4"},
    "posTransaction" : {"Type":"String","Value":"0"},
    "cardType" : {"Type":"String","Value":"00"},
    "financialStatus" : {"Type":"String","Value":"4"},
    "tranCode" : {"Type":"String","Value":"52"},
    "userData1" : {"Type":"String","Value":"Jenny Parkington"},
    "tranType" : {"Type":"String","Value":"01"}
  }
}
```

</details>

The actual transaction data is contained within the `Message` field of the JSON body. This field contains a **Base64-encoded string** that you should decode to retrieve the raw transaction data.

Once decoded, the result is a JSON or XML document describing the transaction. When structured as XML, this document follows the exact same structure as a [transaction inquiry response](https://developers.hyp.co.il/enterprise/inquiring-transactions/overview.md):

<details>

<summary>Show an XML document decoded from the Message field</summary>

```xml
<transaction>
    <status>000</status>
    <statusText>Permitted transaction</statusText>
    <extendedStatus/>
    <extendedStatusText/>
    <extendedUserMessage/>
    <terminalNumber>0882818012</terminalNumber>
    <cardId>1078344210633431</cardId>
    <cardBin>455743</cardBin>
    <cardMask>455743******3431</cardMask>
    <cardLength>16</cardLength>
    <cardNo>xxxxxxxxxxxx3431</cardNo>
    <cardName/>
    <cardExpiration>1226</cardExpiration>
    <cardType code="00">Local</cardType>
    <extendedCardType code="0">Credit</extendedCardType>
    <creditCompany code="1">Isracard</creditCompany>
    <cardBrand code="2">Visa</cardBrand>
    <cardAcquirer code="1">Isracard</cardAcquirer>
    <serviceCode/>
    <transactionType code="01">RegularDebit</transactionType>
    <creditType code="1">RegularCredit</creditType>
    <currency code="1">ILS</currency>
    <baseCurrency/>
    <baseAmount/>
    <transactionCode code="52">Internet</transactionCode>
    <total>11400</total>
    <firstPayment/>
    <periodicalPayment/>
    <numberOfPayments>0</numberOfPayments>
    <clubId/>
    <validation code="4">AutoComm</validation>
    <idStatus code="0">Absent</idStatus>
    <cvvStatus code="3">NotValidated</cvvStatus>
    <authSource code="2">CreditCompany</authSource>
    <authNumber>6864241</authNumber>
    <fileNumber>48</fileNumber>
    <slaveTerminalNumber>003</slaveTerminalNumber>
    <slaveTerminalSequence>084</slaveTerminalSequence>
    <eci>7</eci>
    <clientIp/>
    <email/>
    <cavv code=""/>
    <user/>
    <addonData/>
    <supplierNumber>71506</supplierNumber>
    <id>008336174</id>
    <shiftId1/>
    <shiftId2/>
    <shiftId3/>
    <shiftTxnDate/>
    <cgUid>127498465</cgUid>
    <cardHash/>
    <customerData>
        <userData1>Jenny Parkington</userData1>
    </customerData>
    <acquirerData>
        <acquirerResponseId>738506621082</acquirerResponseId>
        <acquirerResponseData/>
        <walletSupplierId/>
        <mcc>4121</mcc>
    </acquirerData>
    <ashraitEmvData>
        <mti>100</mti>
    </ashraitEmvData>
    <extendedTranCode/>
    <sendNotification/>
    <message>Permitted transaction</message>
    <userMessage>Permitted transaction</userMessage>
    <mpiTransaction>1</mpiTransaction>
    <mpiTransactionId>fee3ccc4-d788-48d4-a0c7-920dafab65fb</mpiTransactionId>
    <financialStatus>Captured</financialStatus>
    <tranId>127498496</tranId>
    <shovar>003084</shovar>
    <transactionDate>2026-06-17 15:48:19</transactionDate>
</transaction>
```

</details>

<details>

<summary>Show a JSON document decoded from the Message field</summary>

```json
{
  "transaction": {
    "status": "000",
    "statusText": "עסקה תקינה",
    "extendedStatus": "",
    "extendedStatusText": "",
    "extendedUserMessage": "",
    "terminalNumber": "0882819014",
    "cardId": "1030912641231699",
    "cardBin": "601178",
    "cardMask": "601178******1699",
    "cardLength": "16",
    "cardNo": "xxxxxxxxxxxx1699",
    "cardName": "",
    "cardExpiration": "1125",
    "cardType": {
      "text": "Foreign",
      "code": "99"
    },
    "extendedCardType": "Credit",
    "creditCompany": {
      "text": "Foreign",
      "code": "0"
    },
    "cardBrand": {
      "text": "Discover",
      "code": "7"
    },
    "cardAcquirer": {
      "text": "Visa",
      "code": "2"
    },
    "serviceCode": "",
    "transactionType": {
      "text": "AuthCredit",
      "code": "53"
    },
    "creditType": {
      "text": "RegularCredit",
      "code": "1"
    },
    "currency": {
      "text": "ILS",
      "code": "1"
    },
    "baseCurrency": "",
    "baseAmount": "",
    "transactionCode": {
      "text": "Phone",
      "code": "50"
    },
    "total": "500",
    "firstPayment": "",
    "periodicalPayment": "",
    "numberOfPayments": "",
    "clubId": "",
    "validation": {
      "text": "AutoComm",
      "code": "4"
    },
    "idStatus": {
      "text": "Absent",
      "code": "0"
    },
    "cvvStatus": {
      "text": "NotValidated",
      "code": "3"
    },
    "authSource": {
      "text": "CreditCompany",
      "code": "2"
    },
    "authNumber": "3225081",
    "fileNumber": "",
    "slaveTerminalNumber": "675",
    "slaveTerminalSequence": "825",
    "eci": "",
    "clientIp": "",
    "email": "",
    "cavv": "",
    "user": "",
    "addonData": "",
    "supplierNumber": "7007245",
    "id": "",
    "shiftId1": "",
    "shiftId2": "",
    "shiftId3": "",
    "shiftTxnDate": "",
    "cgUid": "8071874",
    "cardHash": "",
    "invoice": "",
    "acquirerData": "",
    "ashraitEmvData": "",
    "extendedTranCode": "",
    "sendNotification": "1",
    "message": "עסקה תקינה",
    "userMessage": "עסקה תקינה",
    "financialStatus": "Captured",
    "tranId": "8071880",
    "shovar": "675825",
    "transactionDate": "2024-12-05 15:53:15"
  }
}
```

</details>

## Unsubscribing from notifications

If you want to unsubscribe and stop receiving webhook notifications to your endpoint, you can do this in one of two ways:

1. In your Hyp Console (recommended):
   1. Click **Manage** in the sidebar.
   2. Select **Webhook Service Management**, then **Payment Page**.
   3. In the list of webhook subscriptions, click the three-dot menu next to the subscription you want to unsubscribe from.
   4. Click **Remove Subscription**.
2. Perform a GET request to the URL provided in the `UnsubscribeURL` property of any transaction notification you've received before.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.hyp.co.il/enterprise/payment-page-integration/webhooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
