Today, the Bank data API (links, connections, accounts, balances, transactions and the change feed) is available for sandbox applications with the Didit Test Bank, and live access with real banks opens country by country.
Bank Verification inside verification workflows (bank sign-in and the account check) already runs with real banks.
Open banking API pricing: pay as you go
- Bank sign-in from $0.45 per completed sign-in and the account check from $0.45 per answered check, in USD, on the pricing page.
- You pay per completed or answered check, and a link nobody completes is free.
- The Free plan is $0 a month at list prices, and an annual contract is only for Enterprise, from $15,000 a year. See Pricing.
- Every sandbox price is $0 charged.
- Ongoing access is charged per active connection per month, and live prices are published with live access.
Bank account verification API
The account check confirms that a bank account belongs to the name you send, before a payout or a mandate, with no sign-in. A link with ownership comparison goes further: the person signs in at the bank and Didit compares the holder with a person or company verified in Didit. See Verify a bank account before a payout.Bank data API: accounts, balances and transactions
The Bank data API connects a bank with a hosted Bank Link, then serves accounts, balances and transactions, a change feed with a durable cursor, sync on demand and webhooks. It is available for sandbox applications with the Didit Test Bank today. Start with the quickstart.Coverage in numbers
- Bank sign-in in 33 countries.
- The account check in 47 countries.
- 23 countries with both methods, and 57 with at least one.
- Each country is listed with its flag on the coverage page.
- The Bank data API’s coverage operation returned 31 countries on 22 November 2026, for sandbox applications. Real banks through the Bank data API are not open yet.
One account for identity, AML and bank checks
Didit is one open API with 25+ modules: identity verification, business verification, AML screening, transaction monitoring and bank data share one API key, one console and one record. You do not need a second vendor to check who a person is before you read their bank.Start without a call
- Create a sandbox application and a key in the Business Console, then follow the quickstart.
- Every operation is documented with request and response examples in the API reference.
- Webhooks, a change feed with a durable cursor and sync on demand are part of the API.