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

# The LigdiCash merchant account

> Structure of the LigdiCash merchant account: sub-accounts per operator, inbound and outbound flows, Cashin, Cashout, and balance management.

When you sign a LigdiCash contract, you receive a **merchant account**. This is the central entity that gathers all your financial flows: payments received from your customers (payin) and transfers you make (payout). Understanding its structure is essential to anticipate where your money sits and why some operations may fail.

## One sub-account per operator

Your merchant account is not a single account with a global balance. It is made up of **distinct sub-accounts** — one per operator activated in your contract.

```
MyApp merchant account
├── Orange Burkina sub-account    → balance: 125,000 XOF
├── Moov Burkina sub-account      → balance:  48,500 XOF
├── Wave Senegal sub-account      → balance:  12,000 XOF
└── ...
```

These sub-accounts are independent. There is no automatic pooling of balances between them.

<Note>
  A sub-account is created automatically upon the first transaction received via that operator — not when the project is activated.
</Note>

## Inbound flows — payin

When a customer pays with Orange Burkina, the funds are credited to your **Orange Burkina sub-account**. If they pay with Moov Burkina, the funds go to your **Moov Burkina sub-account**. Each payin exclusively feeds the sub-account matching the operator used.

You can also fund a sub-account manually via a **Cashin**: you send a request to LigdiCash specifying the code of the sub-account to credit and the amount, then you make a bank transfer to the LigdiCash account. Once the transfer is verified, LigdiCash credits your sub-account.

<Note>
  The code of each sub-account is available at any time from the LigdiCash Dashboard. It is required for any Cashin or Cashout request.
</Note>

## Outbound flows — payout

During a payout, the funds leave the **sub-account matching the operator of the recipient number**. If you send money to an Orange Burkina number, the funds are debited from your Orange Burkina sub-account.

<Warning>
  Balances are not pooled across operators. A payout to Orange Burkina cannot be funded by your Moov Burkina sub-account. If the sub-account of the recipient's operator is insufficient, the payout fails — even if your other sub-accounts are well funded.
</Warning>

You can withdraw funds from a sub-account via a **Cashout**: you send a request to LigdiCash specifying the code of the sub-account to debit, the amount, and your bank details. LigdiCash deducts the amount and makes a transfer to your bank account.

By combining a Cashout from one sub-account and a Cashin to another, you can **rebalance your balances** across operators — useful before a large payout to a specific operator.

<Note>
  Cashin and Cashout requests are made by email to the LigdiCash team. There is no API endpoint for these operations.
</Note>

## Withdrawing funds from the dashboard

In addition to Cashout (bank transfer via the LigdiCash team), you can initiate a withdrawal directly from the dashboard without going through support.

From the dashboard: **Merchants → Accounts → Actions → New merchant withdrawal**.

Two withdrawal modes are available:

**Mobile transfer** — you send funds to a mobile money number. The number must be entered with country code + number, no spaces (`22670XXXXXXX`). The recipient number must belong to the **same monetary zone** as the operator of the sub-account: you cannot send funds from an Orange Burkina sub-account to a Guinean number, which is not in the WAEMU zone. However, a Moov Burkina or Orange Mali number will be accepted from an Orange Burkina sub-account.

**Bank transfer** — you send funds to a bank account. In the "Bank details" field, enter the information needed for the transfer: account holder name, bank name, account number, or IBAN.

In both cases, a summary displays the amount received, any fees, and the amount debited before confirmation.

<Note>
  The dashboard lists all your merchant sub-accounts (API projects and PayLink projects combined). You can filter by operator or by project to find the account to debit.
</Note>

## Checking your balances

Balance checking is done exclusively from the **LigdiCash Dashboard**. There is no API endpoint to read the balance of a sub-account. Plan for manual monitoring or alerts based on your own transaction logs if you need to monitor your balances in real time.

## What this means for your integration

**On the payin side** — you have nothing to manage: funds arrive automatically in the correct sub-account based on the customer's operator.

**On the payout side** — always check that the sub-account of the recipient's operator is sufficiently funded before initiating a payout. If you regularly make payouts to several operators, monitor your balances per operator, not globally.

## Related pages

* [Payment API overview](/en/payment-api/overview)
* [Payout to LigdiCash wallet](/en/payment-api/payout/to-ligdicash-wallet)
* [Payout to mobile money](/en/payment-api/payout/to-mobile-money)