Types of events

This is a list of all the types of events we currently send. We may add more at any time, so in developing and maintaining your code, you should not assume that only these types exist.

Note that the events follow a sort of pattern in its naming: resource.event. Our goal is to have a consistent system so it feels intuitive and easy for you to use.

🚧
The link.created is the only event that cannot be listened using a Webhook Endpoint. To receive said event, you need to pass the URL of your backend that you want to send the event to when configuring the widget.

Event type	`data.object`	Description	WebhookEndpoint
`link.created`	`link`	Triggers when a `Link` is created
`link.credentials_changed`	`link`	Triggers when the credentials corresponding to a `Link` change and the `Link` needs to be reconnected	✅
`link.refresh_intent.succeeded`	`refresh_intent`	Triggers when a `Link` has been completely updated. For now, it is only triggered for electronic invoices	✅
`account.refresh_intent.succeeded`	`refresh_intent`	Triggers when an `Account` is updated with the latest available movements from the bank	✅
`account.refresh_intent.failed`	`refresh_intent`	Triggers when an update of the movements of a specific `Account` fails. Only available for "Refresh On Demand" plans	✅
`account.refresh_intent.rejected`	`refresh_intent`	Triggers when an update of the movements of a specific `Account` fails because the `Link`credentials are invalid. Only available for "Refresh On Demand" plans	✅
`account.refresh_intent.movements_removed`	`refresh_intent`	Triggers when the Link's bank deletes transactions. To enable these notifications, activate them from your dashboard. Then, send an email to [email protected] to register your organization for this webhook event.	✅
`checkout_session.finished`	`checkout_session`	Triggers when a customer has completed a payment. The webhook contains information about the Payment including its final status.	✅
`checkout_session.expired`	`checkout_session`	Triggers when a customer leaves the payment flow before finishing	✅
`payment_intent.succeeded`	`payment_intent`	Triggers when a `Payment Intent` finishes successfully	✅
`payment_intent.rejected`	`payment_intent`	Triggers when a user rejects a `Payment Intent`	✅
`payment_intent.expired`	`payment_intent`	Triggers when a user doesn't complete a `Payment Intent`	✅
`payment_intent.failed`	`payment_intent`	Triggers when a `Payment Intent` fails due	✅
`payment_intent.pending`	`payment_intent`	Triggers when the final status of the payment is not available yet. A future webhook will be sent with the final status once it's determined.	✅
`payout.created`	`payout`	Triggers when a `Payout` is created and starts processing	✅
`payout.succeeded`	`payout`	Triggers when a `Payout` is successfully transferred to your bank account	✅
`payout.canceled`	`payout`	Triggers when a `Payout` is canceled and will not be sent to your bank account	✅
`refund.in_progress`	`refund`	Triggers when a `Refund` starts processing.	✅
`refund.succeeded`	`refund`	Triggers when a `Refund` is successfully processed	✅
`refund.failed`	`refund`	Triggers when a `Refund` fails	✅
`subscription_intent.succeeded`	`subscription_intent`	Triggers when a subscription intent is validated as successful. The `subscription_intent` includes the resulting `subscription` object.	✅
`subscription_intent.failed`	`subscription_intent`	Triggers when a subscription intent fails due to a problem with the bank or Fintoc.	✅
`subscription_intent.rejected`	`subscription_intent`	Triggers when a subscription intent is rejected by the user. This may happen when the user rejects the MFA step or if it is entered incorrectly.	✅
`subscription.activated`	`subscription`	Triggers when the bank has confirmed that the subscription is ready to accept charges.	✅
`subscription.canceled`	`subscription`	Triggers when the bank informs Fintoc that the subscription has been canceled.	✅
`charge.succeeded`	`charge`	Triggers when a charge is validated as successful.	✅
`charge.failed`	charge	Triggers when a charge fails due to insufficient funds, the charged amount being higher than the authorized amount, or the user disabling the authorization.	✅
`transfer.outbound.succeeded`	transfer	Triggers when the transfer successfully settles.	✅
`transfer.outbound.returned`	transfer	🇲🇽 In Mexico: Triggers when either Banco de Mexico or the counterparty institution has rejected the transfer. 🇨🇱 In Chile: Triggers when the counterparty institution has rejected the transfer.	✅
`transfer.outbound.failed`	transfer	Triggers when the transfer has not been able to reach its destination account, due to an error during the process.	✅
`transfer.inbound.succeeded`	transfer	Triggers when a Transfer is successfully received in your account.	✅