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

# Ramp sessions

> The conceptual model behind on/off-ramp sessions for moving between fiat and crypto.

# Ramp sessions

Ramp sessions are part of <Tooltip headline="Atomic Money" tip="Sumvin's payments umbrella: ramps, card issuing, x402, and payment links." cta="Glossary →" href="/glossary">Atomic Money</Tooltip>, Sumvin's payments umbrella — the on/off-ramp path between fiat and crypto.

<Snippet file="product-term-disambiguation.mdx" />

A **ramp session** moves value between fiat and crypto. In Sumvin, ramp sessions are backed by an on/off-ramp provider — the partner creates a session through the Platform API, and the user completes the flow in the provider's hosted widget. The settlement lands on a Sumvin-managed wallet (for buy flows) or on a connected off-ramp destination (for sell / off-ramp flows).

## The three kinds

| Kind         | Direction                   | Landing                                             |
| ------------ | --------------------------- | --------------------------------------------------- |
| **Buy**      | Fiat → crypto               | A user wallet on the chosen chain                   |
| **Sell**     | Crypto → fiat               | A connected account registered during the flow      |
| **Off-ramp** | Crypto → fiat (generalised) | Roadmap — settlement rails beyond the MVP sell flow |

## Session lifecycle

1. **Created** — partner creates a session via the Platform API with the user's scoped authorisation.
2. **Client-configured** — the partner embeds the provider's hosted widget (Meld) using session-level credentials, pre-filled with the authorised amount and asset.
3. **User completes in the widget** — the user authorises payment or crypto movement in the hosted widget.
4. **Settlement** — the provider returns the settlement result; Sumvin records the transaction against the user and delivers the settled value to the landing wallet or account.

A session carries the scope envelope that authorised it (typically `sr:us:pint:spend:ramp` with `max`, `asset`, `currency` parameters). The widget and the settlement are both scoped to those parameters.

## See also

* [Ramps & banking](/products/ramps/overview) — product-level framing
* [Buy and sell](/products/ramps/buy-sell) — buy and sell configuration
* [Off-ramp](/products/ramps/off-ramp) — the off-ramp flow

## Referenced from

* [KYC passthrough](/products/ramps/kyc-passthrough)
* [Scopes reference](/identity/scopes)
* [App developer persona](/overview/personas/app-developer)