> For the complete documentation index, see [llms.txt](https://docs.ledgity.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ledgity.finance/overview/how-to-use-ledgity/deposit-eur-or-stablecoin.md).

# Deposit EUR or Stablecoin

Ledgity.finance supports **two primary funding routes**:

#### **Fiat Funding (EUR/USD → EURC/USDC)**

Investors can fund in EUR (and USD where available). Funds are converted into stablecoins and credited to the investor’s account environment.

**i) Instant Funding via MoonPay Virtual Account Service**

1. The investor receives a dedicated virtual IBAN,
2. The investor executes a SEPA transfer,
3. EUR is converted to EURC,
4. EURC is credited to the investor’s account environment.

***

#### **Direct Stablecoin Deposits (Stablecoin → Product)**

Investors who already hold stablecoins can deposit **EURC/USDC directly**, without fiat conversion:

1. The investor sends EURC/USDC from their wallet to the Ledgity.finance deposit address / designated contract,
2. Stablecoins are credited to the investor’s account environment,
3. The investor can subscribe to a yield strategy immediately.

This route is intended for investors seeking a faster subscription workflow.


---

# 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.ledgity.finance/overview/how-to-use-ledgity/deposit-eur-or-stablecoin.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.