> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/admin/bank-accounts.md).

# Bank Accounts

Administrative endpoints for **bank accounts** — the bank transfer (money order / EFT) accounts a customer can pay into when paying by bank transfer. Each account belongs to a bank and is identified by its IBAN.

### Core Capabilities

**1. Listing & Filtering**

* Retrieve a paginated list of bank accounts, including inactive (soft-deleted) ones.
* Filter by identifier, bank, and IBAN, each an exact match.

**2. Account Lifecycle Management**

* Create a bank account, fully or partially update it, and deactivate it.
* The IBAN is unique across all accounts; an account whose IBAN already belongs to another account is rejected.

### Deletion Semantics

Deleting a bank account is a **soft delete**: the record is not removed, its `is_active` flag is set to `false` instead. A soft-deleted account keeps its IBAN, so the IBAN stays reserved and cannot be reused by a new account. The list endpoint still returns inactive accounts; filter on `is_active` at the client when only active accounts are wanted.

### Error Codes

Requests that are well-formed but conflict with a business rule are answered with `406 Not Acceptable` and carry the following code.

| Code               | Meaning                                                                        |
| ------------------ | ------------------------------------------------------------------------------ |
| `bank_account_100` | An account with the given IBAN already exists. Raised on create and on update. |

### Dynamic Settings & Environment Variables

No dynamic settings (`dj_dynamic_settings`) are read by these endpoints. The dynamic settings registered by the payments module (`THREE_D_SECURE_ENABLED`, `THREE_D_SECURE_RULES`, `INSTALLMENT_FILTERS`, `LOYALTY_MONEY_ENABLED`, `APPLE_PAY_DOMAIN_ASSOCIATION`, `INSTALLMENT_PROVIDERS`, `SUBSCRIPTION_PRODUCT_ATTRIBUTE_KEY`) govern card payments, installments and related storefront flows; none of them affects the bank account endpoints.

**Environment variables:** No environment variables are read directly by these endpoints.


---

# 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://apidocs.akinon.com/commerce-openapis/admin/bank-accounts.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.
