Skip to main content
Bank data is shared on the person’s instruction, and the person can stop sharing at any time. This page says what they see and agree to, how access ends, and what deleting a connection removes.

What the person sees and agrees to

On Didit’s consent screen the person sees:
  • who will read the data: your name and logo;
  • what: accounts, balances and transactions back to a date;
  • for how long: for ongoing access, “until” a date, with a reminder that they can stop at any time;
  • how often it is refreshed;
  • how to stop.
The regulated account information provider behind a route is disclosed on that route’s consent screen where the law requires it. Didit receives the data and passes it to you on the person’s instruction. Bank credentials for sign-in are never seen or stored by Didit on redirect routes.

Who can read the data

  • Stored bank data is protected: it is encrypted at rest, used only for the purpose the person agreed to, and never written to logs.
  • Every Bank data call needs an API key that carries the Bank data permission: full access does not include it. Without it the call answers 403 bank_data_access_denied.

How access ends

Stopping access is not deleting: after revoke_connection the accounts, balances and transactions already read stay readable to you until you delete the connection or consent.retain_until passes. Delete the connection with delete_connection when you want it gone now.

Delete a connection

DELETE /v3/bank/connections/{id}/ stops access at the bank and deletes the connection’s stored accounts, balances and transactions. What is deleted
  • The accounts, balances, transactions, sync history, consent records and ownership results of the connection.
  • Its change feed history.
  • Its access at the bank, which is ended.
  • Every data operation of the connection (refresh, sync runs, accounts, balances, transactions and the change feed) answers 409 connection_not_active.
What is not affected
  • Other connections, even those of the same person: each connection is an independent grant.
  • Charges already settled and credits already consumed.
  • Webhooks already delivered to you, and anything you downloaded or stored in your own systems: that is your own copy.
What to expect
  • Deleting is immediate and irreversible: when the call returns, the connection’s data is deleted.
  • Read afterwards, the connection answers only its id, status (deleted), status_reason, created_at and erasure, the record of the deletion with requested_at, erased_at and status.
  • erasure.status is the confirmation of the deletion, not a stage in which the data is still readable:
    • pending: the deletion is being confirmed, including the end of access at the bank.
    • erased: confirmed, with erased_at.
    • failed: the confirmation has not arrived yet and is repeated automatically. Nothing is needed from you.
  • The data is deleted and not readable in any of the three.
  • Repeating the call is safe.
  • bank.connection.deleted confirms the deletion.
Deleting your organization or application deletes its connections and their data the same way.

Next steps

  • Connections: statuses and renewal.
  • Webhooks: bank.connection.revoked and bank.connection.deleted.
Last modified on November 22, 2026