> For the complete documentation index, see [llms.txt](https://customer-api-docs.ibanera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://customer-api-docs.ibanera.com/terminology/payees.md).

# Payees

In the realm of finance and banking, payees are essential components that facilitate transactions. On the Ibanera banking platform, the concept of payees is built into the system, allowing customer users to designate and enroll trustworthy bank accounts—either individual accounts or pool accounts—to work alongside their subledger accounts. Here are some key aspects of managing payees on the platform:

1. **Payee Registration**: Customers can register payees in a couple of ways—either via Plaid, which links to an external bank account, or through Visa Direct, connecting to a debit card account. For business customers, there's also the provision to add payees by submitting a form with the bank account details.
2. **Funds Transfer**: Once a payee account is registered and associated with a customer’s subledger account, the customer is positioned to transfer funds out to the payee account.
3. **Asset Exchange**: Customers can nominate registered payees for use during a crypto to fiat sell exchange, streamlining the process where fiat cannot be held in subledger accounts indefinitely. This is critical for asset exchanges: once such a trade reaches the payee transfer stage, the resulting fiat is transferred out to the selected payee.
4. **Funds Pull**: If a payee account is added through Plaid, customers have the ability to initiate ACH pull transfers. This means they can draw funds from the payee account into their Ibanera subledger account.

Through these mechanisms, the platform ensures that customer subledger accounts remain primarily for asset management and not for the long-term storage of fiat funds, maintaining clear lines between different types of transactions and accounts


---

# 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://customer-api-docs.ibanera.com/terminology/payees.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.