Skip to main content
This page explains what virtual accounts are, how onramp vs offramp flows work, and when this product is the right choice. For step-by-step integration: Reach out to Meld support to enable virtual accounts / headless rails on your account.

What are virtual accounts?

A virtual account is a dedicated set of receiving details — for example a bank account number, IBAN, or crypto deposit address — used so inbound funds can be attributed to a specific customer and settled to a destination you configured. Meld orchestrates provider integration, KYC, quoting, and settlement tracking so you work with a single API surface regardless of which provider (Noah, Due Network, and similar) handles the underlying rails. You present your own UI — there is no Meld-hosted widget.

Onramp (fiat → crypto)

The customer receives unique bank deposit details (ACH routing + account number, SEPA IBAN, PIX, mobile money, and so on). They send fiat from their bank; the provider converts it and delivers crypto to the destination wallet you registered. For standing virtual accounts, you fetch those bank details once per customer + provider + payment method + currency pair + destination wallet. The user reuses the same details for later deposits — no new order per transfer. → See the Virtual Account Integration Guide.

Offramp (crypto → fiat)

The customer receives a crypto deposit address on each sell order. They send stablecoin (or other supported crypto) from their wallet; the provider converts and pays out fiat to the bank / mobile money details you supplied on the order. In this flow, a standing virtual account is typically not created per business or end user. Fiat payout usually goes from the provider’s funding account directly to the end bank account (or mobile money wallet) on the order — not via a reusable per-customer fiat “VA.” → See the Headless Offramp Integration Guide.

When to use this product

Choose virtual accounts and payouts when you want:
  • Your own UI — no Meld-hosted widget
  • Bank rails for deposits (ACH, SEPA, PIX, mobile money) with automatic attribution to a customer
  • Crypto → fiat payouts with bank / mobile money details supplied at order time
  • One Meld API across multiple VA / payout providers
It is a weaker fit when you need a full hosted checkout widget, card / Apple Pay headless checkout (separate product surface), or non-VA widget ramp flows.

Next steps

  1. Confirm with Meld that headless / virtual-account preferences and providers are enabled on your account.
  2. Integrate the onramp guide and/or offramp guide.
  3. Subscribe to KYC and transaction webhooks before go-live.