> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Bank Data API: Connect Banks and Read Transactions

> Connect a customer's bank once with Bank Link, verify who owns the account, and keep reading balances and transactions with one API and one price.

Didit's Bank data API lets your product connect a person's or company's bank account through Bank Link, check who owns the account, and read its balances and transactions for as long as the bank and the person allow.
You use one API key, one webhook endpoint and one price list, the same ones you use for identity verification, business verification and AML screening.

> [!NOTE]
>
> **Availability.** Bank data is available for sandbox applications.
> A live application's calls answer `404` until live access is announced, and nothing is charged in sandbox.
> Start with the [quickstart](https://docs.didit.me/core-technology/bank-verification/quickstart.md).
> The [coverage page](https://docs.didit.me/core-technology/bank-verification/coverage.md) and the [institutions endpoint](https://docs.didit.me/standalone-apis/bank-institutions-list.md) show what each bank supports.

## One idea in one sentence

A **link** creates a **connection**, a connection has **accounts**, and an account has **balances** and **transactions**.

| Object | What it is | How long it lives |
| - | - | - |
| Link | One run of [Bank Link](https://docs.didit.me/core-technology/bank-verification/bank-link.md) for one person: connect a bank, or renew a connection. | Minutes to hours, then it expires. |
| Connection | The person's permission for your application to read one bank. It carries the consent, the sync state and the status. | One-time access: until collection ends. Ongoing access: until the consent ends, renewed as often as the person agrees. |
| Account | One account inside a connection, with an id that never changes while the connection exists. | As long as the connection. The id stays the same after every renewal. |
| Balance | A typed amount of an account at a reference date. | Replaced at each sync. |
| Transaction | One movement of an account, with a stable id. | As long as the connection exists. |

## Two ways to get bank data, and two other bank checks

| You want to | Use | Price in one line |
| - | - | - |
| Read balances and transactions once | A link with `access: one_time` | Per check, see [pricing](https://docs.didit.me/getting-started/bank-verification-pricing.md#bank-data-and-ongoing-access) |
| Keep reading balances and transactions for months | A link with `access: ongoing` | Per active connection per month |
| Confirm that a bank account belongs to a name before you pay it | [Account check](https://docs.didit.me/standalone-apis/bank-account-check.md), no sign-in | Per answered check |
| Confirm that the person who signs in owns the account | A link with `ownership.compare`, or the [Bank Verification step](https://docs.didit.me/core-technology/bank-verification/verification-methods.md) of a verification session | Per completed sign-in |

## What makes it different

* **One platform.** Identity verification, business verification, AML screening and bank data share one API key, one contract and one console.
* **One link for one-time or ongoing access.** The same hosted Bank Link serves both.
* **The holder comparison is optional.** Compare the account holder with a Didit-verified person or company, or skip the comparison when you only need data.
* **Public pay-per-use prices.** See the [pricing page](https://docs.didit.me/getting-started/bank-verification-pricing.md).
* **Stable ids and a change feed.** Accounts and transactions keep their ids across renewals, and a change feed with a durable cursor gives you only what changed.
* **A sandbox that covers the hard cases.** The Didit Test Bank and its test customers include business accounts, long history, pending transactions and one-time-only banks.

## Pick your path

> [card] [Quickstart](https://docs.didit.me/core-technology/bank-verification/quickstart.md)
>
> Copy-paste requests from zero to your first transactions, with a sandbox key.

> [card] [Continuous feed for accounting](https://docs.didit.me/use-cases/bank-data-for-accounting.md)
>
> A daily feed of balances and transactions for each of your clients.

> [card] [Verify an account before a payout](https://docs.didit.me/use-cases/verify-a-payout-account.md)
>
> Check the account holder with no sign-in.

> [card] [Show Bank Link](https://docs.didit.me/core-technology/bank-verification/bank-link.md)
>
> Send the person to the hosted link and return them to your site.

## Where to go next

* [Connections](https://docs.didit.me/core-technology/bank-verification/connections.md): ongoing access, consent, renewal and the statuses of a connection.
* [Accounts, balances and transactions](https://docs.didit.me/core-technology/bank-verification/accounts-balances-transactions.md): the data model and which fields each bank sends.
* [Webhooks](https://docs.didit.me/core-technology/bank-verification/webhooks.md): the `bank.*` events and how to use them.
* [Sandbox](https://docs.didit.me/core-technology/bank-verification/sandbox.md): the Didit Test Bank and its test customers.
* [Data, consent and deletion](https://docs.didit.me/core-technology/bank-verification/data-consent-and-deletion.md): what the person agrees to, how to stop access, and what deletion removes.
* [Pricing](https://docs.didit.me/getting-started/bank-verification-pricing.md): every price as text.
* [API reference](https://docs.didit.me/standalone-apis/bank-data.md): every endpoint.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.