Didit’s Bank Link is the single flow in which a person connects a bank account to your product, whether you want a one-time read or ongoing access.
You create a link on your server and send the person to its hosted page.
Show it
Send the person to the link url, or put it in an email or a message: Didit hosts every screen.
See Hosted Bank Link, and Return to your site to bring the person back to your page.
Your server confirms the result with GET /v3/bank/links/{id}/ or the bank.link.completed webhook.
What the person sees
- Consent. Who will read the data (your name and logo), what (accounts, balances, transactions back to a date), for how long, how often it is refreshed, and how to stop.
- Personal or business. Only when the bank separates them and your request said
any.
- Bank. The picker lists the banks that can do what the link asks. With ongoing access it lists only banks that can keep access open.
- Sign-in at the bank. On the bank’s own page, never inside Didit’s screens.
- Accounts. All eligible accounts are preselected and each can be unticked, with at least one left.
- Success. The accounts linked and, for ongoing access, until when.
See Data, consent and deletion for what the person agrees to and how access stops.
The bank hop
A bank’s own sign-in page cannot run inside a frame, so Bank Link sends the person to the bank and brings them back.
The state of a link lives on Didit’s servers, so closing a tab never loses a consent the person already gave.
At the end the person goes to your redirect_url when the link has one: see Return to your site.
Security
- The API key never reaches a browser or an app.
redirect_url is checked when you create the link: in a sandbox application only a localhost address works today, see Return to your site.
- Events carry ids only: no names, no account numbers and no tokens.
Next steps
Last modified on November 22, 2026