> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.3/pbms/developer-zone/odoo-modules/g2p-registry-bank-details.md).

# G2P Registry: Bank Details

### Module name

g2p\_bank

### Module title

G2P Registry: Bank Details

### Technology base

\<Odoo>

### Functionality

* **Secure Storage**
  * Provides a structured framework for storing and managing bank details.
  * Ensures the confidentiality and security of financial information.
* **Comprehensive Integration**
  * Integrates seamlessly with the "g2p\_registry\_individual" and "g2p\_registry\_group" modules.
  * Allows users to associate bank details with specific individuals and groups.
* **Python Library Integration**
  * Utilizes the "schwifty" Python library for enhanced functionality.
  * Enables the validation and processing of bank-related information.

### Design notes

NA

### Relationships with other entities

**Dependencies**

Module dependencies

* base
* mail
* contacts
* g2p\_registry\_group
* g2p\_registry\_individual

External Python Dependency

* schwifty

### User interface

NA

### Configuration

* No specific configuration steps are required. The module seamlessly integrates with individuals and groups.

### Source code

<https://github.com/OpenG2P/openg2p-registry/tree/15.0-develop/g2p_registry_membership>

### Installation

* Ensure that all module dependencies are installed, including the external Python library "schwifty."
* Install the "G2P Registry: Bank Details" module from the Odoo Apps interface.


---

# 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.openg2p.org/1.3/pbms/developer-zone/odoo-modules/g2p-registry-bank-details.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.