Webhooks for Stripe Issuing and Stripe Treasury
Learn about webhook events for Stripe Issuing and Stripe Treasury and why they occur.
Stripe uses webhooks to notify your application when an event happens in your account. Webhooks are particularly useful for asynchronous events such as when an Issuing authorization is created or when a user sends an ACH transfer.
Note
To view the Treasury related webhook events, log in to your Stripe account with Stripe Treasury enabled.
Issuing webhook events
The following table lists the webhook events for Issuing and Treasury.
Note
Connect webhooks are for activity on any connected account. All events on the connected account are sent to the Connect webhooks. This includes the events generated by Treasury and Issuing integrations. For more information see Connect Webhooks.
| Event type | Explanation | Note |
|---|---|---|
| issuing_authorization.created | Occurs whenever an authorization is created. | |
| issuing_authorization.request | Represents a synchronous request for authorization, see Using your integration to handle authorization requests. You must create a webhook endpoint that explicitly subscribes to this event type to access it. Webhook endpoints that subscribe to all events won’t include this event type. | |
| issuing_authorization.updated | Occurs whenever an authorization is updated. | |
| issuing_card.created | Occurs whenever a card is created. | |
| issuing_card.updated | Occurs whenever a card is updated. | |
| issuing_cardholder.created | Occurs whenever a cardholder is created. | |
| issuing_cardholder.updated | Occurs whenever a cardholder is updated. | |
| issuing_dispute.closed | Occurs whenever a dispute is won, lost or expired. | |
| issuing_dispute.created | Occurs whenever a dispute is created. | |
| issuing_dispute.funds_reinstated | Occurs whenever funds are transferred to your Issuing balance (usually associated with won dispute status). | |
| issuing_dispute.submitted | Occurs whenever a dispute is submitted. | |
| issuing_dispute.updated | Occurs whenever a dispute is updated. | |
| issuing_transaction.created | Occurs whenever an issuing transaction is created. | |
| issuing_transaction.updated | Occurs whenever an issuing transaction is updated. | |
| topup.created | Occurs whenever a top-up is created. | Only relevant for Issuing-only integrations. |
| topup.canceled | Occurs whenever a top-up is canceled. | |
| topup.failed | Occurs whenever a top-up fails. | |
| topup.reversed | Occurs whenever a top-up is reversed. | |
| topup.succeeded | Occurs whenever a top-up succeeds. | |
| balance_transfer.created | New balance transfer API—transfer funds from acquiring to issuing | |
| balance.available | Reflects the new updated Stripe balance and Issuing balance after the balance transfer |
Treasury webhook events
The following table lists the webhook events for Treasury and when they occur.
| EVENT | DESCRIPTION |
|---|---|
| treasury.credit_reversal.created | Occurs whenever a CreditReversal is created. |
| treasury.credit_reversal.posted | Occurs whenever a CreditReversal post is posted. |
| treasury.debit_reversal.completed | Occurs whenever a DebitReversal is completed. |
| treasury.debit_reversal.created | Occurs whenever a DebitReversal is created. |
| treasury.debit_reversal.initial_credit_granted | Occurs whenever an initial credit is granted on a DebitReversal. |
| treasury.financial_account.closed | Occurs whenever the status of the FinancialAccount becomes closed. |
| treasury.financial_account.created | Occurs whenever a new FinancialAccount is created. |
| treasury.financial_account.features_status_updated | Occurs whenever the statuses of any features within an existing FinancialAccount are updated. |
| treasury.inbound_transfer.canceled | Occurs whenever an InboundTransfer is canceled. |
| treasury.inbound_transfer.created | Occurs whenever an InboundTransfer is created. |
| treasury.inbound_transfer.failed | Occurs whenever an InboundTransfer has failed. |
| treasury.inbound_transfer.succeeded | Occurs whenever an InboundTransfer has succeeded. |
| treasury.outbound_payment.canceled | Occurs whenever an OutboundPayment is canceled. |
| treasury.outbound_payment.created | Occurs whenever a new OutboundPayment is successfully created. |
| treasury.outbound_payment.expected_arrival_date_updated | Occurs whenever the arrival date on an OutboundPayment updates. |
| treasury.outbound_payment.failed | Occurs whenever an OutboundPayment fails. |
| treasury.outbound_payment.posted | Occurs whenever an OutboundPayment posts. |
| treasury.outbound_payment.returned | Occurs whenever an OutboundPayment is returned. |
| treasury.outbound_transfer.canceled | Occurs whenever an OutboundTransfer is canceled. |
| treasury.outbound_transfer.created | Occurs whenever an OutboundTransfer is created. |
| treasury.outbound_transfer.expected_arrival_date_updated | Occurs whenever the arrival date on an OutboundTransfer updates. |
| treasury.outbound_transfer.failed | Occurs whenever an OutboundTransfer has failed. |
| treasury.outbound_transfer.posted | Occurs whenever an OutboundTransfer is posted. |
| treasury.outbound_transfer.returned | Occurs whenever an OutboundTransfer is returned. |
| treasury.received_credit.created | Occurs whenever a received_credit is created as a result of funds being pushed by another account. |
| treasury.received_credit.failed | Occurs whenever a received_credit transitions to a failed state. Only applicable for check deposits. |
| treasury.received_credit.succeeded | Occurs whenever a received_credit transitions to a succeeded state. Only applicable for check deposits. |
| treasury.received_debit.created | Occurs whenever a received_debit is created as a result of funds being pulled by another account. |
Connect onboarding webhook events
The following webhook events can occur during Connect onboarding:
- Account.updated
- Persons.updated
- Capability.updated
For more information, see Making API calls for connected accounts | Stripe Documentation
Financial Connections webhook events (for funding with inboundTransfer)
The following table lists the Financial Connections webhooks and when they occur, these webhooks are relevant when a Connected Account uses Financial Connections to instantly verify an external bank account to enable InboundTransfers.
| EVENT | DESCRIPTION |
|---|---|
| financial_connections.account.created | Occurs when a customer links a new account. If they link multiple accounts, it sends multiple events (one per account). |
| financial_connections.account.deactivated | Occurs when the status of your user’s account moves from active to inactive. An account can move from active to inactive for a number of reasons, including when a user changes their password or if the financial institution was down for maintenance the last time we tried to retrieve data. Data is no longer accessible on accounts that have moved from active to inactive. |
| financial_connections.account.reactivated | Occurs when the status of your user’s account moves from inactive to active. An account might become inactive because of a user changing their password or technical issues with the bank. It’s not possible to refresh data on an inactive account. After an account moves from inactive to active, account data again becomes refreshable. |
| financial_connections.account.disconnected | Occurs when an account is disconnected. See the disconnections guide for further details. |
| financial_connections.account.refreshed_balance | Occurs after a balance refresh is complete. |
| financial_connections.account.refreshed_ownership | Occurs after an ownership refresh is complete. |
| financial_connections.account.refreshed_transactions | Occurs after a transaction refresh is complete. |
Webhook event best practices
To learn more about webhook best practices, see the webhooks best practices .
Loading video content