> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/v1/releases/releases-notes-bank-account-details-ocr.md).

# Bank Account Details OCR

## Bank Account Details OCR

Keep track of the changes and updates for the Bank Account Details OCR API.

## Version 2

### ⚡️ Feature: Second Release (June 19, 2023)

Increased accuracy for all fields.

New field and changes in the field's name:

* New: \*\*BBAN \*\*including: Bank code, Branch code, account number and key.
* **Account holders names**: the field has been renamed from account\_holder\_name to account\_holders\_names

## Version 1

### ⚡️ Feature: First Release (May 10, 2022)

Extracted fields:

* Account holder name
* IBAN
* Swift


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mindee.com/v1/releases/releases-notes-bank-account-details-ocr.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.