---
title: "Features that travel."
url: "https://platformdocs.coinme.com/#/explainers/flows"
markdown: "https://platformdocs.coinme.com/pages/explainers/flows.md"
summary: "The Coinme Widget is made of flows. A flow is one complete part of the customer experience, such as identity verification, buying with a debit card, sending, or transaction history. Your Ramp decides which flows run. You never build or host a flow yourself."
---

# Features that travel.

The Coinme Widget is made of flows. A flow is one complete part of the customer experience, such as identity verification, buying with a debit card, sending, or transaction history. **Your Ramp decides which flows run.** You never build or host a flow yourself.

<a id="what"></a>

## What a flow is

A flow owns one complete feature from start to finish: its screens, its steps, and the work it does with Coinme behind them. Flows are built and run by Coinme inside the widget; your app never loads one directly.

Because each flow is complete on its own, the same flow behaves the same way in every Ramp that includes it. A Ramp is what you get when the widget puts several flows together into one experience.

A strip under this prose shows identity verification, location discovery, buy & sell and transaction history, with an arrow labelled "compose" pointing to "a Ramp".

<a id="which"></a>

## Which flows run

Your Ramp's configuration decides which flows the widget offers your customers. The rules for a customer's region can remove some of them, never add one. [The Orchestrator explainer](https://platformdocs.coinme.com/pages/explainers/orchestrator.md) shows how a Ramp comes together.

Your app chooses only where a session starts, with `flowId` in the configuration it sends. It defaults to the buy flow; `landing` opens home, where your Ramp decides what renders, and `transactionHistory` opens the transaction history. The full field list is on [Build](https://platformdocs.coinme.com/pages/build/index.md#config).

<a id="catalogue"></a>

## The flow catalogue

| Flow | What it does |
| --- | --- |
| Identity Verification | Verifies who the customer is before they transact. |
| Location Discovery | Finds locations where a user can transact to buy or sell. |
| Transaction History | Lets a user retrieve their transaction history. |
| Cash at Retail | Buy crypto with cash at participating retail locations. |
| Digital Buy & Sell | Buy and sell using debit cards. |
| Cash Buy & Sell | Buy and sell using cash at ATM machines. |
| Send & Receive | Send and receive assets. |

Which of these your customers see depends on your Ramp and their region. Ask your Coinme integration contact which flows your Ramp offers.

<a id="reuse"></a>

## One flow, every Ramp

**Why it matters.** Because a flow is complete and composable, it is written and tested once and then reused wherever it fits. The same KYC flow serves many Ramps and partner integrations with identical behaviour, and a fix in the flow reaches every Ramp that uses it.

- **Speed**: New Ramps are assembled from existing flows in days rather than built from scratch.
- **Consistency**: A flow used in many Ramps gives every one the same behaviour and user experience.
- **Quality**: Each flow is tested once and reused with confidence.
- **The shape of it**: Build a capability once as a flow, then compose it into as many Ramps as the platform needs. The unit of work is the feature, and the feature is portable.

This overview sits above the system documents, each authoritative for its own area.
