It’s vital that you establish a webhook endpoint that responds to our requests and other account activity. Failure to watch for, and promptly respond to, these notifications will lead to delays in money being transferred.

You’ll use webhooks to be notified about events that happen in a Stripe account. Your webhook URLs, which receive the event notifications, are configured in your webhook settings.

Note that there are a few types of webhooks:

• Account webhooks are for activity on your own account (e.g., most requests made using your API keys and without authenticating as another Stripe account).
• Connect webhooks are for activity on any connected account. This includes the important account.updated event for any connected accounts.
• Person webhooks are for activity on any person associated with a connected account. This includes the person.updated event which provides important verification information. You only receive this webhook if you use the Persons API.

For Connect webhooks, it’s important to note that while only test webhooks will be sent to your development webhook URLs, both live and test webhooks will be sent to your production webhook URLs. This is due to the fact that you can perform both live and test transactions under a production application. For this reason, we recommend you check the livemode value when receiving an event webhook to know what action, if any, should be taken.

In addition to the documented response properties in the event object reference, each event for a connected account will also contain a top-level account property. It identifies the user for whom the webhook is being sent.

{
  "id": "evt_xiMUBZKjfRAna7",
  "livemode": true,
  "object": "event",
  "type": "customer.created",
  "account": "acct_NBDeHbe4ytv1gF",
  "pending_webhooks": 2,
  "created": 1349654313,
  "data": {...}
}

For more information about webhooks, see the webhook documentation or event object reference.