Which statement best defines a webhook in Stripe?

Which statement best defines a webhook in Stripe?

• A. Url endpoints that are dedicated towards listening to and responding to API events.
• B. A database that stores event logs.
• C. A user interface component for dashboards.
• D. A background task scheduler.

Answer: (A)

Webhooks are HTTP callbacks that Stripe uses to notify your system about events happening in your account. You configure a webhook endpoint URL in Stripe, and Stripe will POST event data to that URL whenever something occurs (for example, a payment succeeds or a customer is created). Your server listens for these requests, verifies the payload using a signing secret to ensure it came from Stripe, and then reacts accordingly (like updating order status or fulfilling a service). They’re asynchronous and push-based, not something you pull on a schedule. This is why a webhook is not a database of logs, a UI component, or a scheduler—their purpose is to deliver real-time events to your app so you can respond automatically.

Webhooks are HTTP callbacks that Stripe uses to notify your system about events happening in your account. You configure a webhook endpoint URL in Stripe, and Stripe will POST event data to that URL whenever something occurs (for example, a payment succeeds or a customer is created). Your server listens for these requests, verifies the payload using a signing secret to ensure it came from Stripe, and then reacts accordingly (like updating order status or fulfilling a service). They’re asynchronous and push-based, not something you pull on a schedule. This is why a webhook is not a database of logs, a UI component, or a scheduler—their purpose is to deliver real-time events to your app so you can respond automatically.