--- title: Connect webhooks subtitle: Learn how to use webhooks with Connect to be notified of Stripe activity. route: /connect/webhooks --- # Connect webhooks Learn how to use webhooks with Connect to be notified of Stripe activity. Stripe uses *webhooks* (A webhook is a real-time push notification sent to your application as a JSON payload through HTTPS requests) to notify your application when an event happens in your account. All *Connect* (Connect is Stripe's solution for multi-party businesses, such as marketplace or software platforms, to route payments between sellers, customers, and other recipients) integrations should establish a [webhook endpoint](https://dashboard.stripe.com/account/webhooks) to listen for Connect events. ## Connect webhooks A Connect platform uses two types of webhooks: - *Account* webhooks are for activity on your own account (for example, most requests made using your API keys and without [authenticating as another Stripe account](https://stripe.com/connect/authentication)). This includes all types of charges, except those made directly on a connected account. - *Connect* webhooks are for activity on any connected account. We send all events on the connected account (including account updates and direct charges) to the Connect webhooks. When you create a Connect webhook, you must configure it to receive Connect webhook events. When creating it in [the Dashboard](https://dashboard.stripe.com/test/webhooks), for **Listen to**, select **Events on Connected accounts**. When creating it using the API, set the [connect parameter](https://stripe.com/api/webhook_endpoints/create#create_webhook_endpoint-connect) to true. ![Webhook settings in the Stripe Dashboard](https://b.stripecdn.com/docs-statics-srv/assets/webhooks.ac3d6c19a5281fbbd2b85a335cd887b3.png) For Connect webhooks, your development webhook URLs receive only test webhooks, but your production webhook URLs receive both live and test webhooks. This is because you can perform both live and test transactions under a production application. We recommend that you check the `livemode` value when receiving an event webhook to determine whether users need to take action. Each event for a connected account contains a top-level `account` property that identifies the connected account. Because the connected account owns [the object that triggered the event](https://stripe.com/api/events/object#event_object-data-object), you must make API requests for that object [as the connected account](https://stripe.com/connect/authentication). ```json { "id": ""{{EVENT_ID}}"", "livemode": true, "object": "event", "type": "customer.created", "account": ""{{CONNECTED_ACCOUNT_ID}}"", "pending_webhooks": 2, "created": 1349654313, "data": {...} } ``` The following table describes some of the most common and important events related to connected accounts: | Event | data.object type | Description | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `account.application.deauthorized` | `application` | Occurs when a connected account disconnects from your platform. You can use it to trigger cleanup on your server. Available for connected accounts with access to the Stripe Dashboard, which includes [Standard accounts](https://stripe.com/connect/standard-accounts). | | `account.external_account.updated` | An external account, such as `card` or `bank_account` | Occurs when [a bank account or debit card attached to a connected account is updated](https://stripe.com/connect/payouts-bank-accounts), which can impact payouts. Available for connected accounts that your platform controls, which includes Custom and Express accounts, and Standard accounts with [platform controls](https://stripe.com/connect/platform-controls-for-stripe-dashboard-accounts) enabled. | | `account.updated` | `account` | Allows you to monitor changes to connected account requirements and status changes. Available for all connected accounts. | | `balance.available` | `balance` | Occurs when your Stripe balance has been updated. For example, when [funds you’ve added from your bank account](https://stripe.com/connect/add-and-pay-out-guide?dashboard-or-api=dashboard#add-funds-to-your-balance) are available for transfer to your connected account. | | `payment_intent.succeeded` | `payment_intent` | Occurs when a payment intent results in a successful charge. Available for all payments, including [destination](https://stripe.com/connect/destination-charges) and [direct](https://stripe.com/connect/direct-charges) charges. | | `payout.failed` | `payout` | Occurs when [a payout fails](https://stripe.com/connect/payouts-connected-accounts#webhooks). When a payout fails, the external account involved is disabled, and no automatic or manual payouts can be processed until the external account is updated. | | `person.updated` | `person` | Occurs when a `Person` associated with the `Account` is updated. If you [use the Persons API to handle requirements](https://stripe.com/connect/handling-api-verification#verification-process), listen for this event to monitor changes to requirements and status changes for individuals. Available for connected accounts that your platform controls, which includes Custom and Express accounts, and Standard accounts with [platform controls](https://stripe.com/connect/platform-controls-for-stripe-dashboard-accounts) enabled. | #### Event - account.application.deauthorized #### Event - account.updated #### Event - person.updated #### Event - payment_intent.succeeded, direct charge #### Event - payment_intent.succeeded, non-direct charge #### Event - balance.available #### Event - account.external_account.updated #### Event - payout.failed ## Test webhooks locally You can test webhooks locally with the Stripe CLI. 1. If you haven’t already, [install the Stripe CLI](https://stripe.com/stripe-cli#install) on your machine. 1. Log in to your Stripe account and set up the CLI by running `stripe login` on the command line. 1. Allow your local host to receive a simulated event on your connected account by running `stripe listen --forward-to localhost:{PORT}/webhook` in one terminal window, and running `stripe trigger {{EVENT_NAME}}` in another. For Connect webhooks, use [--forward-connect-to](https://stripe.com/cli/listen#listen-forward-connect-to) with `stripe listen` and [--stripe-account](https://stripe.com/cli/trigger#trigger-stripe_account) with `stripe trigger`. ## See also - [Webhook documentation](https://stripe.com/webhooks) - [Event object reference](https://stripe.com/api#events)