Skip to main content
Didit sends bank webhooks when a link ends, a connection changes, the consent is about to end, or a sync stores new data. They use the same envelope, signing and retries as every other Didit webhook, and carry ids and statuses only: you fetch the object to read it.
Bank webhook events are sent for live and sandbox applications. Choose the events per destination with the destination’s event filter, as for other events. See Webhooks for the envelope, the signature headers and retries.

Events

Every event also carries the common fields event_id, webhook_type, timestamp, created_at, application_id and environment. bank.link.* events carry their fields under data; the connection, data and sync events carry theirs at the top level. ended_by is end_user, bank, customer or unknown. The exact schema of every event is in the API reference.

Example

How to use them

  • New data. bank.data.updated is a signal only: nothing is pushed. Call the change feed with your stored cursor. Use bank.sync.completed only if you want to see every sync, including those that changed nothing.
  • Onboarding. Wait for bank.connection.created before you read accounts, and for bank.connection.history_complete before you rely on the full history.
  • Consent. On bank.connection.consent_expiring ask the person to renew. On bank.connection.renewal_required data is still readable but no longer synced.
  • Stop. On bank.connection.revoked stop your own feed for that connection and decide whether to delete the stored data.
  • Duplicates. Treat every event idempotently: key on the event id, and expect the same event twice now and then.
  • Never trust the browser. Confirm a link with bank.link.completed or GET /v3/bank/links/{id}/, not with a link id sent by a page.

Next steps

Last modified on November 22, 2026