# Best Practices

Webhooks provide an effective method to track the state of transactions and to take appropriate actions within your Globaltopup account. Take a look at these best practices to ensure your webhooks remain secure and function seamlessly with your integration.

### Delivery Attempts and Retries <a href="#delivery-attempts-and-retries" id="delivery-attempts-and-retries"></a>

Every event that receives a non-2xx response is considered an event delivery failure by Globaltopup's system. If there is a delivery failure, we retry the delivery in exponential backoff policy for 24 hours after the event creation timestamp.

**Watch Out!**

Webhooks are delivered in near real-time and are asynchronous. For business-critical, synchronous use cases, you may choose to poll out APIs as well.

#### Disable Logic <a href="#disable-logic" id="disable-logic"></a>

A webhook is retried at progressive intervals of time on failure, defined in the exponential backoff policy, for 24 hours. If the webhooks continue to fail for 24 hours, the webhook is disabled. You need to enable the webhook from the Globaltopup Dashboard after fixing the errors at your end.

Whenever a webhook is disabled, you are notified on your **Verified Email Address** as configured during webhook setup. In case you have not provided an **Alert Email Address** during webhook setup, we send a mail to the email address configured under **Account & Settings** on the Globaltopup Dashboard.


---

# Agent Instructions: 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:

```
GET https://docs.globaltopup.in/developer-tools/best-practices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
