# Virtual account countries by rail

> Whether a customer can be issued a **virtual bank account** on EUR and USD banking rails, based on their
**primary address country**.

# Virtual account countries by rail

Whether a customer can be issued a **virtual bank account** on EUR and USD banking rails, based on their
**primary address country**.

A virtual account is required for:

- **[Payin via Virtual Account](../products/bank-onramp.md)** — fiat deposits through
  [`POST workflows/bank-deposit-to-onchain-address`](../api-reference/convert-fiat-to-crypto)
- **Payouts on the same rails** (SEPA, ACH, Fedwire, FedNow, SWIFT) — settlement also requires virtual
  account creation for the customer first

Countries are listed in two groups:

- **Restricted** — eligible on some rails but not others
- **Fully prohibited** — not eligible to create a virtual account on any of these rails

Residences not listed are eligible, at the country-policy level, to create a virtual account on every
rail below.

This page does **not** cover payout methods that do not use a virtual account (for example PIX or other
local rails). For those, query the [Channels API](./channels.md).

In the restricted table, ✓ = eligible at the country-policy level to **create** a virtual account for
that rail. ✗ = not eligible.

:::info

Country policy is one requirement only. Virtual account creation also depends on verification model,
approvals, and other compliance checks. For example, USD virtual accounts require Standard Model KYC.
See [KYC](./kyc.md) and the [EUR](../recipes/payin/bank-onramp-eu.md) /
[USD](../recipes/payin/bank-onramp-us.md) bank onramp recipes.

:::