> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onstacks.io/llms.txt
> Use this file to discover all available pages before exploring further.

# User flow

> Every screen a user sees on the Ramp Checkout, in order.

The Ramp Checkout is a single-page flow. Steps that a returning user has already completed are skipped.

<Steps>
  <Step title="Quote">
    The user picks an asset (USDC, USDT, or CNGN), the network they want to receive on or send from (Ethereum, Polygon, BSC, or Base), a currency, and an amount. The page shows the rate, fees, and the amount they will receive.
  </Step>

  <Step title="Order summary">
    A review screen with the quote, the provider that will settle the fiat leg, and the expiry.
  </Step>

  <Step title="Email">
    The user enters an email address. This is the account identifier on the Ramp Checkout.
  </Step>

  <Step title="One-time code">
    A code is sent to the email and verified on the page.
  </Step>

  <Step title="Identity verification">
    First-time users complete KYC on the page. The result is stored on their Ramp Checkout account, so this happens once.
  </Step>

  <Step title="Local identity check">
    Where the payout market requires it, the user provides a local identity number (for example a BVN in Nigeria). It is used to verify the account holder and is not shown again.
  </Step>

  <Step title="Checkout">
    Onramp: the page shows the bank account to pay and waits for the transfer. Offramp: the page shows the deposit address for the ramp wallet, or moves tokens from the user's existing ramp wallet, then pays out to the saved bank account.
  </Step>

  <Step title="Status">
    The page shows pending, processing, then completed or failed. See [Transaction statuses](/ramps/reference/transaction-statuses).
  </Step>
</Steps>

## Wallets on the Ramp Checkout

Each Ramp Checkout user gets a ramp wallet that spans the supported networks. Onramp purchases land in it, and offramp sales are funded from it or from an external deposit. Users can also send tokens out to an address they save as a beneficiary.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.