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

# Receive funds

> Get bank details or crypto deposit addresses and track incoming funds.

You can receive funds into your Ledig balance using a bank account or crypto deposit address. Request the receiving details first, then follow the instructions returned for that account or address.

For sandbox testing, use the funding instructions provided by Ledig. Keep your sandbox and live accounts, addresses and credentials separate.

## Get a bank account

Read an existing receiving account for a currency:

```http theme={null}
GET /v1/virtual-accounts/NGN
```

A `404` response means there is no available account for that currency. To request one, call `POST /v1/virtual-accounts` with an `Idempotency-Key`:

```http theme={null}
POST /v1/virtual-accounts
Idempotency-Key: YOUR_IDEMPOTENCY_KEY
Content-Type: application/json
```

```json theme={null}
{
  "currency": "NGN",
  "accountName": "Example Trading Ltd",
  "intent": "resume"
}
```

Choose a currency available to your business. Save the request body and idempotency key so you can safely retry if the response is lost.

| `intent` | When to use it |
| - | - |
| `resume` | Continue an existing setup or retrieve its completed result. |
| `additional` | Request another account when that option is available. |

Use `resume` for the usual setup flow. Omitting `intent` can request another account after an earlier setup completes. If Ledig asks you to choose between existing accounts, resolve that choice before retrying.

## Follow account setup

| HTTP status | Meaning |
| - | - |
| `200` | The account details are ready. |
| `202` | Setup is still in progress or needs more information. |

For a pending setup, save its `id` and read the returned `status` and `missing` requirements. Status values are `requested`, `manual_review`, `pending_provider` and `completed`. The response includes `accountId` once an account exists.

Complete any requested information. If setup needs review, contact [support@ledig.io](mailto:support@ledig.io) with the request ID. Reuse the original key when retrying the same request.

Once the account is ready, read `GET /v1/virtual-accounts/{currency}` whenever you need its current account number, bank details and payment reference. These responses use `Cache-Control: no-store`; do not put account details in shared caches or logs.

## Discover crypto deposit networks

Call `GET /v1/wallets/options` to see which networks and assets are available for deposits. Each option includes:

| Field | Meaning |
| - | - |
| `network` | The exact network identifier to use in your request. |
| `testnet` | Whether the option uses a test network. |
| `supportedAssets` | The assets accepted on that network. |

Use the returned options to populate your deposit form. An empty list means you cannot create a new address at that time; you can still read existing wallets.

Deposit networks and [recipient networks](https://docs.ledig.io/guides/recipients.md#crypto-destinations) serve different purposes. Use deposit options when receiving funds.

## Create a network address

Call `POST /v1/wallets/network` to request an address for the selected network. Replace `NETWORK_FROM_OPTIONS` with the exact identifier returned by deposit options:

```http theme={null}
POST /v1/wallets/network
Idempotency-Key: YOUR_IDEMPOTENCY_KEY
Content-Type: application/json
```

```json theme={null}
{
  "nickname": "Customer deposits",
  "network": "NETWORK_FROM_OPTIONS"
}
```

Save the body and key before submitting. The response returns `data.requestId`; keep it even if setup is still pending.

| Response | Next step |
| - | - |
| HTTP `201`, `data.status: ready` | Use the returned address for its listed assets. |
| HTTP `202`, `data.status: pending` | Read the setup request using its `requestId`. |

## Check address setup

Call `GET /v1/wallets/network/{requestId}`. It returns HTTP `200` with the current setup result:

| Result | What to do |
| - | - |
| `status: ready` | Show the address and its deposit instructions. |
| `status: pending`, `setupState: processing` | Check again after a short delay, increasing the delay between attempts. |
| `status: pending`, `setupState: review_required` | Contact support with the request ID. |
| `status: pending`, no `setupState` | Keep the same request ID and contact support if setup remains pending. |

A pending result does not contain a usable address. A `404` response means the request was not found for your business. Keep the original request rather than creating a replacement after a timeout.

## Read existing wallets

`GET /v1/wallets` lists your deposit wallets. Use `GET /v1/wallets/{id}` to read one wallet.

You can also create a wallet for a single asset with `POST /v1/wallets`. Send `nickname`, `coin`, `network` and an `Idempotency-Key`, using an asset and network from deposit options.

> [!WARNING]
>
> Send only the asset on the network listed in the receiving instructions. Include
> the memo or tag when one is returned. Using a different network or omitting a
> required memo can prevent your deposit from being credited.

## Confirm funds are available

Creating an account or address does not add funds. After sending a deposit, check [Transactions](https://docs.ledig.io/guides/transactions.md) for its progress and [Balances](https://docs.ledig.io/guides/balances.md) for the amount available to spend.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.