# Test webhooks in account 
Testing webhooks helps to ensure the correct setup of the project both on your side and on Xsolla side.
If webhooks are <a href="/webhooks/overview/#section/Set-up-webhooks-in-account">set up</a> successfully, a webhooks testing section is displayed below the webhooks setup section.
![Webhooks testing section](https://cdn.xsolla.net/developers/current/images/api_docs/webhooks/testing-section.svg)
The testing section in the account varies depending on the webhook receiving option.
If you registered in the account after January 22, 2025, you receive combined webhooks:
<table>
<thead>
<tr>
<th>Tab name for webhook testing</th>
<th>Webhook name and type</th>
</tr>
</thead>
<tbody>
<tr>
<td><b>Payments and store</b></td>
<td>User validation > <a href="/webhooks/operation/user-validation/">User validation</a> (<code>user_validation</code>)</td>
</tr>
<tr>
<td></td>
<td>Game services > Combined webhooks > <a href="/webhooks/operation/successful-order-payment">Successful payment for order</a> (<code>order_paid</code>)</td>
</tr>
<tr>
<td></td>
<td>Game services > Combined webhooks > <a href="/webhooks/operation/order-cancellation">Order cancellation</a> (<code>order_canceled</code>)</td>
</tr>
<tr>
<td><b>Subscriptions</b></td>
<td>User validation > <a href="/webhooks/operation/user-validation/">User validation</a> (<code>user_validation</code>)</td>
</tr>
<tr>
<td></td>
<td>Payments > <a href="/webhooks/operation/payment">Payment</a> (<code>payment</code>)</td>
</tr>
</tbody>
</table>
If you registered in Publisher Account on or before January 22, 2025, you receive separate webhooks:
<table>
<thead>
<tr>
<th>Tab name for webhook testing</th>
<th>Webhook name and type</th>
</tr>
</thead>
<tbody>
<tr>
<td><b>Store</b></td>
<td>Game services > Separate webhooks > <a href="/webhooks/operation/successful-order-payment-separate">Successful payment for order</a> (<code>order_paid</code>)</td>
</tr>
<tr>
<td></td>
<td>Game services > Separate webhooks > <a href="/webhooks/operation/order-cancellation-separate">Order cancellation</a> (<code>order_canceled</code>)</td>
</tr>
<tr>
<td><b>Payments</b></td>
<td>User validation > <a href="/webhooks/operation/user-validation/">User validation</a> (<code>user_validation</code>)</td>
</tr>
<tr>
<td></td>
<td>Payments > <a href="/webhooks/operation/payment">Payment</a> (<code>payment</code>)</td>
</tr>
<tr>
<td><b>Subscriptions</b></td>
<td>User validation > <a href="/webhooks/operation/user-validation/">User validation</a> (<code>user_validation</code>)</td>
</tr>
<tr>
<td></td>
<td>Payments > <a href="/webhooks/operation/payment">Payment</a> (<code>payment</code>)</td>
</tr>
</tbody>
</table>
<div lang="en" class="note">
<p><strong>Note</strong></p>
<p>If a warning that the test has not passed appears in the testing section, check the webhook response settings in your <a href="/webhooks/overview/#section/Webhook-listener">webhook listener</a>. The reasons for the errors in testing are indicated in the test results.</p>
<p><b>Example:</b></p>
<p>You use the specialized site <a href="https://webhook.site/#!/">webhook.site</a> for testing.</p>
<p>An error is displayed in the <b>Testing response to invalid signature</b> section.</p>
<p>This happens because Xsolla sends a webhook with an incorrect signature and expects your handler to respond with a <code>4xx</code> HTTP code specifying the <code>INVALID_SIGNATURE</code> error code.</p>
<p><a href="https://webhook.site/#!/">webhook.site</a> sends a <code>200</code> HTTP code in response to all webhooks, including a webhook with an incorrect signature. The expected <code>4xx</code> HTTP code cannot be obtained, so an error is displayed in the test result.</p>
</div>
The process of testing for the scenario with combined webhooks is described below.