> For the complete documentation index, see [llms.txt](https://docs.avici.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avici.money/getting-started/virtual-accounts/blockchains-currencies-and-payment-rails.md).

# Blockchains, Currencies and Payment Rails

### Blockchain and Stablecoin Support Overview

| Blockchain   | USDT | USDC | EURC |
| ------------ | :--: | :--: | :--: |
| **Solana**   |   ✅  |   ✅  |   ✅  |
| **Ethereum** |   ✅  |   ✅  |   ✅  |
| **Polygon**  |   ✅  |   ✅  |   ✅  |
| **Base**     |   -  |   ✅  |   ✅  |
| **Arbitrum** |   -  |   ✅  |   ✅  |

### Currencies

These currencies support both onramp (fiat to crypto) and offramp (crypto to fiat) for Business-to-Business (B2B), Business-to-Individual (B2C), and Individual-to-Individual (I2I) transactions.

| Currency | Payment Method                          | Average Delivery Speed                |
| -------- | --------------------------------------- | ------------------------------------- |
| **USD**  | ACH, FedWire                            | Same Day (T+1 if outside cutoff time) |
| **EUR**  | SEPA Instant (SEPA Credit if 100k+ EUR) | Real-time                             |

{% hint style="info" %}
Settlement timelines may not be
 instant. (This is due to the applicable jurisdiction, payment rail used, cross-border nature
 of a transaction, settlement protocols, processing windows, and banking infrastructure
 involved, and may take up to seven days).
{% endhint %}

### Payment Rails

The following table outlines our supported payment methods.

<table data-header-hidden><thead><tr><th></th><th width="432.199951171875"></th><th align="center"></th></tr></thead><tbody><tr><td><strong>Payment Method</strong></td><td><strong>Description</strong></td><td align="center"><strong>Availability</strong></td></tr><tr><td><strong>SEPA (Instant)</strong></td><td>Instant EEA transactions sub €100k</td><td align="center">✅</td></tr><tr><td><strong>SEPA (Credit)</strong></td><td>Usually 24 hours for transactions greater than €100k</td><td align="center">✅</td></tr><tr><td><strong>ACH</strong></td><td>Common for domestic transfers within the US</td><td align="center">✅</td></tr><tr><td><strong>Wire</strong></td><td>Common for domestic transfers within the US</td><td align="center">✅</td></tr></tbody></table>

#### Third Party Payments

**Use Case**

* **Onramp**: Accept fiat payments from external bank accounts as a third-party source.
* **Offramp:** Disburse fiat payouts to external bank accounts that are not owned by the initiating end customer (e.g., vendor, beneficiary, or third party).

Key use case is for users to be able to **offramp / send stablecoins into third party bank accounts**:

* Crypto companies paying suppliers (USDC to EURO)
* Payroll originating in USDC to get delivered as USD or EUR into bank accounts
* Companies pay with stablecoins, freelancers receive fiat.
* Cross border payments

{% hint style="info" %}
Customers from the USA can’t enable EURO 3rd party accounts.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avici.money/getting-started/virtual-accounts/blockchains-currencies-and-payment-rails.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.