> This is Payabli documentation. For a complete page index, fetch https://docs.payabli.com/llms.txt — append .md to any page URL for lightweight markdown. For section-level indexes, query parameters, and other AI-optimized access methods, see https://docs.payabli.com/ai-agents.md

# Bank account functions and account IDs

> Understand how deposit, withdrawal, and remittance accounts work and how account IDs route transactions

When you board a paypoint, you connect one or more bank accounts to it. Each account carries one or more functions that tell Payabli how to move money to and from it. Each account also has an account ID that identifies it when you transact. Understand both before you complete boarding. This matters most when your paypoint uses more than one account.

## Bank account functions

You can assign three distinct functions to the bank accounts on a paypoint. Each function maps to a Payabli product area:

| Function       | Vertical | Description                                                                                                                                                                                                  |
| -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Deposit**    | Pay In   | When you accept payments, Payabli uses your deposit account to route the funds collected from payers to you. A paypoint can have only one account assigned for deposits during boarding.                     |
| **Withdrawal** | Pay Ops  | Payabli uses your withdrawal account to collect fees, returns, and other negative amounts related to a paypoint's processing. A paypoint can have only one account assigned for withdrawals during boarding. |
| **Remittance** | Pay Out  | Remittance accounts fund payables from the paypoint to its vendors. A paypoint can have any number of accounts assigned for remittance.                                                                      |

### Assignment rules

These rules govern how you assign functions across a paypoint's accounts:

* You can assign **remittance** to any bank account, including accounts that also carry the deposit or withdrawal function.
* You can assign **deposit** to only one bank account at a time.
* You can assign **withdrawal** to only one bank account at a time.

Because deposit and withdrawal are each exclusive to one account, any configuration that assigns either function to more than one account is invalid. The following table shows the valid combinations:

| Scenario                      | Account 1                       | Account 2              | Account 3  |
| ----------------------------- | ------------------------------- | ---------------------- | ---------- |
| Single account, all functions | Deposit, Withdrawal, Remittance | —                      | —          |
| Split deposit and withdrawal  | Deposit, Remittance             | Withdrawal, Remittance | —          |
| Dedicated remittance account  | Deposit, Withdrawal             | Remittance             | —          |
| Fully separated               | Deposit                         | Withdrawal             | Remittance |

After boarding, you can direct transactions to specific accounts with [fund routing](/guides/pay-in-developer-routing-multiple-accounts).

## Account IDs

An account ID identifies a bank account so Payabli knows which account handles a payment when a paypoint has more than one account configured. Any account assigned the remittance function automatically receives an account ID you can use to transact payouts.

You can retrieve a paypoint's account IDs from its account data with the [Get paypoint details](/developers/api-reference/paypoint/get-paypoint-details) endpoint.

### Route a transaction to a specific account

When a paypoint has more than one account set up for a payment method, you choose where the funds go. To do so, pass the account's account ID in the transaction request. For Pay In, this is Payabli's fund routing feature. The Payabli team enables and configures fund routing for your paypoint, so contact them before you rely on it. For setup steps, examples, and error behavior, see [Route funds from a transaction](/guides/pay-in-developer-routing-multiple-accounts).

For payouts, provide the remittance account's account ID when you [authorize a payout](/developers/api-reference/moneyout/authorize-a-transaction-for-payout) to choose which account funds the payout.

### How account IDs are generated

If you don't provide an account ID when you create or update an account, Payabli generates one in the format `acct-{first_digit}xxxxx{last_4_digits}` based on the account number. The mask always uses five `x` characters, regardless of the account number's length. For example, account number `123456789` produces `acct-1xxxxx6789`.

If a duplicate exists within the same service at the paypoint, Payabli appends a numeric suffix, such as `acct-1xxxxx6789-2`. Payabli also uses this value as the identifier for the bank account's associated payment connector.

## Related resources

See these related resources to help you get the most out of Payabli.

* **[Merchant application tips](/guides/pay-ops-boarding-application-tips)** - Learn how to avoid common merchant application problems
* **[Boarding overview](/guides/pay-ops-boarding-overview)** - Learn how merchant boarding works in Payabli
* **[Manage payouts with the API](/guides/pay-out-developer-payouts-manage)** - Learn how to use the Payabli API to create, capture, and cancel payout transactions
* **[Route funds from a transaction](/guides/pay-in-developer-routing-multiple-accounts)** - Route funds from transactions to different bank accounts for a single paypoint