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

# Coverage, Limitations & FAQ

> Supported banks, image requirements, accuracy, what Bankbooks does not cover, deployment, pricing and frequently asked questions.

## Image requirements

JPEG or PNG, at least 20 KB and up to 8 MB. Skewed or upside-down photos are rotated automatically. Framing and legibility rules are in the [API reference](/api-reference/bankbooks/extract-data).

## Supported banks

Physical passbooks from all major Thai banks:

* Kasikornbank
* Krungsri (Bank of Ayudhya)
* Bangkok Bank
* Krungthai
* SCB
* TMB/TTB
* UOB
* GSB

## Accuracy and speed

* **92.9%** correct extraction on a 500-document test set.
* **\~10 ms** average model inference.
* Model updates ship without changes to the API contract.

## Not supported

| Not supported | Notes |
| - | - |
| Bankbooks from outside Thailand | `issued_country` other than `TH` returns 400. |
| Credit, debit and virtual cards | Out of scope; usually rejected by the similarity check. |
| Screenshots and digital copies | Flagged by `is_scan` as an anti-fraud measure. |
| Bank statements, utility bills, other documents | Out of scope. |
| Transaction pages | Only the name and account number are extracted; transactions and balances are not parsed. |
| Identity verification | A bankbook proves ownership of an account, not the person's identity. Pair it with [Document Verification](/document-verification/overview) and liveness when you need both. |
| Small, blurry or low-contrast images | Files under 20 KB are rejected; poor photos return a low `confidence_score` or 404. |

## Data handling and deployment

Each check is stateless and isolated. Hosted API, OEM, white-label and on-premises deployments are available, which helps with Thailand's PDPA rules on cross-border transfer of personal data.

## Pricing

Per-verification pricing with a monthly minimum commitment and volume discounts; enterprise terms on request. A free test account is available for evaluation. Contact [service@dataspike.io](mailto:contact@dataspike.io).

## FAQ

> **Do I need to create an applicant or a verification first?**
>
> No. Send the image to the [Extract Data](/api-reference/bankbooks/extract-data) endpoint and use the response directly.

> **Can I match on the English name?**
>
> Prefer the Thai `account_name`. `account_name_en` is a transliteration and spellings vary between documents. See [Matching Thai names](/bankbook-verification/how-it-works#matching-thai-names).

> **Does a bankbook verify the user's identity?**
>
> No. It proves the user holds the account. For identity, combine it with [Document Verification](/document-verification/overview) and liveness.

> **A passbook from a certain bank or design isn't read well. What now?**
>
> Send the check `id` to support. The engineering team handles new designs and edge cases directly and retrains the model when needed.

> **Will model updates break my integration?**
>
> No. Accuracy improvements are rolled out without changes to the request or response format.

> **Can Bankbooks run in our own infrastructure?**
>
> Yes. OEM, white-label and on-premises deployments are available. Contact [service@dataspike.io](mailto:contact@dataspike.io).


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