> For the complete documentation index, see [llms.txt](https://docs.lyzi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lyzi.io/en/merchant/backoffice/mon-solde-et-virements.md).

# My Balance and Transfers

Receive your payments directly into your Wallet in USDC and EURC, keep full control over your funds and transfer them to your bank account whenever you want.

From your Back Office, the "**My Balance**" page groups together all the crypto funds you receive with Lyzi. Your payments are credited **directly to your Wallet**, and the Lyzi account manager can transfer them to your bank account whenever you wish, in just a few clicks.

No particular knowledge required

## Your funds stay under your control

With **My** **Balance**, you are the sole holder of your funds. Lyzi has no access to it and no control: only the Lyzi account manager can move your money.

{% hint style="warning" %}
Access to your balance and every operation are protected by a **one-time verification code** sent to your email address. Only you can initiate a transfer of funds to your bank account.
{% endhint %}

In practice:

* You **receive** your payments directly to your Wallet.
* You can **check** your crypto balance at any time in the Back Office.
* You **decide** when to send your funds to your bank account.

### Sending USDC to a wallet

Your USDC aren't only for bank transfers: you can also send them to **any wallet**, your own or a third party's. For example to:

* **refund a customer** directly in stablecoins;
* **pay out stablecoins** (payouts) to your users, partners or suppliers;
* **transfer your funds to your own wallets**, to make your payouts yourself or manage your treasury.

Click **"Withdraw"**, enter the amount, then choose one of your approved addresses as the destination.

{% hint style="warning" %}
**Whitelisted address required.** Any new address must first be added under **Withdrawal addresses**, further down the **My Balance** page (**"Add an address"** button, then **"Submit for approval"**). Lyzi screens the address, then approves it manually. You receive an email as soon as it is approved: it then appears among the destinations in the **"Withdraw"** window. Allow for this delay before a first transfer.
{% endhint %}

{% hint style="info" %}
Only **EVM** addresses (0x…) are accepted. The same address works on all your wallet's networks (Ethereum, Polygon, Arbitrum…). Make sure the recipient can receive the token on the chosen network.
{% endhint %}

## Sending my funds to my bank account

When you are ready to retrieve your money, click **"Withdraw"**, enter the amount, then confirm. Your funds are then transmitted to our **payment service provider (PSP)**, which handles the **payout to your bank account**.

{% hint style="info" %}
Transfers to your bank account are only initiated once you have accumulated 1,000 EUR in received payments.
{% endhint %}

{% hint style="info" %}
You can send **USDC or EURC** to the PSP. The amount in **USDC** will be converted into **EURO** by the PSP upon receipt.
{% endhint %}

{% hint style="info" %}
The PSP may charge fees on the transfer of up to **0.5%.** The payment amounts paid out to your wallet cover this fee.
{% endhint %}

### Prerequisite: being integrated with the PSP

Sending funds to your bank account becomes possible once your merchant account is **finalized with our PSP**, which is responsible for the transfer to your bank account.

If your account is not yet integrated, a message will tell you when you try to send funds. In this case, write to <contact@lyzi.fr> to finalize your integration (submission of specific documents), or wait for the verification and validation of your account.

## Tutorial: creating and using my balance

Follow these steps to activate your balance and transfer your funds to your bank account:

{% stepper %}
{% step %}
**Go to the My Balance section of your Back Office.**
{% endstep %}

{% step %}
**Activate your wallet**

A one-time verification code is sent to you by email to secure access.
{% endstep %}

{% step %}
**Once activated, your available balance is displayed.**
{% endstep %}

{% step %}
**To retrieve your money, click "Withdraw"**

Enter the desired amount, then confirm.
{% endstep %}

{% step %}
**Your funds are transmitted to the PSP**

The PSP proceeds with the **payout to your bank account** (automatic transfer from €1,000).
{% endstep %}
{% endstepper %}

### \[VIDEO] Creating your wallet

{% embed url="<https://youtu.be/PoE7ecoofWI>" %}

### \[VIDEO] Sending USDC

{% embed url="<https://youtu.be/R2skaH_b4VU>" %}

### \[VIDEO] Withdrawing your funds

{% embed url="<https://youtu.be/IIbhMihRyE4>" %}

### \[VIDEO] Bridging your funds

{% hint style="warning" %}
**TWO** confirmations are required to move your funds from one network (a blockchain) to another.\
**Stay** on the page until the operation is confirmed.

The operation may take 1-2 minutes.
{% endhint %}

{% embed url="<https://youtu.be/fnPJoWjJu_8>" %}


---

# 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.lyzi.io/en/merchant/backoffice/mon-solde-et-virements.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.
