Stripe Financial Connections deactivation webhook events
Introduced 2026-07-29 · score 0.91
HOW TO USE IT
If the integration needs advance warning of Financial Connections deactivation, subscribe the webhook endpoint to the four deactivation events. Handle each event’s `data.object` and prepare for deactivation, such as by prompting users to relink when appropriate.
curl https://api.stripe.com/v1/webhook_endpoints \
-u "<YOUR_SECRET_KEY>:" \
-d "enabled_events[]=financial_connections.account.expected_deactivation_date_updated" \
-d "enabled_events[]=financial_connections.account.upcoming_deactivation" \
-d "enabled_events[]=financial_connections.authorization.expected_deactivation_date_updated" \
-d "enabled_events[]=financial_connections.authorization.upcoming_deactivation" \
--data-urlencode "url=https://<YOUR_DOMAIN>/<WEBHOOK_PATH>"WHY THIS HELPS
When maintaining an integration that needs to respond to Financial Connections account or authorization deactivation, subscribe to the new webhook events and handle their payloads.
REQUIREMENTS AND LIMITATIONS
- url (required): HTTPS URL for the webhook endpoint.
- enabled_events (required): Event types enabled for this endpoint; specify each event as an array entry. The four deactivation event types were added for webhook endpoint creation and updates.
- financial_connections.account.expected_deactivation_date_updated: Event sent when an Account’s expected deactivation date is set or updated; payload contains the updated Account object.
- financial_connections.account.upcoming_deactivation: Event sent 30 days before an Account is expected to become inactive; payload contains the Account object.
- financial_connections.authorization.expected_deactivation_date_updated: Event sent when an Authorization’s expected deactivation date is set or updated; payload contains the updated Authorization object.
- financial_connections.authorization.upcoming_deactivation: Event sent 30 days before an Authorization is expected to become inactive; payload contains the Authorization object.
- Prerequisite: Provide a publicly accessible HTTPS URL for the registered webhook endpoint.
- Prerequisite: Authenticate the API request with a Stripe secret key.
- Upcoming deactivation events are sent 30 days before an Account or Authorization is expected to become `inactive`.
- Expected deactivation date updated events are sent when the expected deactivation date is set or updated.
- Event payloads contain the relevant updated Account or Authorization object.
FIRST-PARTY EVIDENCE
- https://docs.stripe.com/changelog/dahlia/2026-07-29/financial-connections-deactivation-event-notifications
- https://docs.stripe.com/api/webhook_endpoints/create
- https://docs.stripe.com/webhooks
Check the installed version and the source before using it. Entry JSON