---
title: "One widget runs the whole customer experience."
url: "https://platformdocs.coinme.com/#/explainers/orchestrator"
markdown: "https://platformdocs.coinme.com/pages/explainers/orchestrator.md"
summary: "Orchestrator is the application behind the Coinme Widget. It runs everything your customer does with Coinme, from identity verification to buying, selling and sending, as one experience. What it offers is set by your Ramp, a configuration Coinme sets up for you and identifies by a Ramp ID. A Ramp is a configuration, not a codebase. Pick one below and watch the same widget become a different application."
---

# One widget runs the whole customer experience.

Orchestrator is the application behind the Coinme Widget. It runs everything your customer does with Coinme, from identity verification to buying, selling and sending, as one experience. What it offers is set by your **Ramp**, a configuration Coinme sets up for you and identifies by a Ramp ID. A Ramp is a configuration, not a codebase. Pick one below and watch the same widget become a different application.

## The same widget, different ramps

The page opens with a ramp assembler: pick a ramp, choose a custody model and apply a region overlay, and the exposed flows change. It offers 3 example ramps, every one drawn from the one shared flow library below. The table states what each exposes.

| Ramp | Ramp ID | Flows in any custody model | Flows added only when custodial | About this ramp |
| --- | --- | --- | --- | --- |
| Coinme | `‹coinme ramp›` | KYC, GreenDot cash, Transact, Debit, Readycode, Transaction history, Discover, Account management, Payment methods, EDD | Swaps, Send, Receive, Wallet management † | Coinme's own consumer ramp, running on the platform as a tenant like any partner. A rich composition drawn from the same shared library, not a special case in the code. |
| Cash partner (illustrative) | `‹assigned per ramp›` | KYC, GreenDot cash, Transact, Readycode, Transaction history, Discover, Account management | Wallet management †, Send, Receive | A retail composition spanning cash buy, digital transact, cash pickup, and location discovery. Wallet management, send, and receive appear only while the ramp operates custodially; flip custody to watch them drop. |
| Digital partner (illustrative) | `‹assigned per ramp›` | KYC, Transact, Debit, Transaction history, Account management, Payment methods, EDD | Swaps, Send, Receive, Wallet management † | A buy and sell composition. Debit, payment methods, account management, and EDD stand regardless of custody; wallet management, swaps, send, and receive join only when the ramp operates custodially. |

Custody is a configuration choice: any ramp, including Coinme's, can operate custodially or non-custodially*. Wallet management, swaps, send, and receive apply to custodial operation.

\* Custodial partner ramps are not implemented at this time.

† Wallet management is in development.

### Region overlay

A region overlay is the compliance layer applied on top of the base ramp. Overlays only further restrict, never grant.

| Overlay | Effect |
| --- | --- |
| no cash onramp | Removes GreenDot cash from any ramp that exposes it. |
| no cash offramp | Removes Readycode from any ramp that exposes it. |
| no onboarding | Removes every flow. |

### The shared flow library

- KYC
- Transact
- Swaps, custodial only
- Send, custodial only
- Receive, custodial only
- GreenDot cash
- Debit
- Readycode
- Wallet management, custodial only, in development
- Transaction history
- Discover
- Account management
- Payment methods
- EDD

<a id="why"></a>

## Why it exists

If Coinme shipped a single use application, every new market, partner, or product would mean another codebase to build, staff, and keep in sync with the last one. Compliance logic, risk instrumentation, and transaction handling would need to be re-implemented or forked each time, and a fix in one place would not reach the others. This would be unsustainable.

Orchestrator changes what a new application costs. Different Ramps are different selections and configurations of the same flows running under the same engine. A custodial cash experience, a non-custodial digital experience, and the standalone Coinme app are not three codebases; they are three compositions. Adding a partner is, in the ideal case, authoring a configuration payload rather than forking an application. New product offerings are efforts at new flows, not new applications. Composability reduces cost, complexity, and time to market.

- **An application per need** (Before): A new partner or market is a new build: its own codebase, its own release train, its own copy of compliance and risk logic to maintain and drift from the others.
- **A configuration per need** (With Orchestrator): A new partner or market is a Ramp: a configuration resolved at runtime against a shared engine and a shared flow library. One fix to a flow reaches every Ramp that uses it.

<a id="ramp"></a>

## Configured per Ramp ID

Everything that makes your integration yours lives in your Ramp: the flows it offers, the regions, payment rails, assets and languages it supports, and its default theme. Coinme sets up your Ramp and gives you its Ramp ID. Your app passes your Ramp ID when it opens the widget, and the widget loads your Ramp from it. There is one path for every Ramp: Coinme runs its own consumer app on the platform as a Ramp like any partner.

1. **Your app opens the widget**: It passes your Ramp ID and the settings for this session.
2. **The widget loads your Ramp**: Your Ramp ID selects the configuration Coinme set up for you.
3. **Regional rules apply**: The rules for the customer's region can remove flows your Ramp offers. They never add one.
4. **Your flows open**: The customer sees only the flows your Ramp allows, starting with the one your app asked for.
5. **Your app hears back**: The widget tells your app what happens over the bridge, for as long as the session lasts.

<a id="inputs"></a>

## Two inputs shape each session

What the widget does for one customer in one session is not baked into a build. It comes from two inputs: one Coinme sets for your Ramp, and one your app sends each time it opens the widget.

| Input | What it defines | Who sets it |
| --- | --- | --- |
| Ramp configuration (set by Coinme) | What the application **is**: the flows, regions, rails, assets and languages your Ramp offers, and its default theme. The same for every session. | Coinme, agreed with you and keyed by your Ramp ID. |
| Session configuration (sent by you) | What you want for **this session**: a pre-filled amount or asset, locked fields, a wallet destination, where to start, the theme and language. Varies per session. | Your app, when it opens the widget and while the session runs. |

The regional rules sit between the two. They can only further restrict what your Ramp allows, never grant something it does not. Your session configuration then tailors one session within what remains, so nothing about a single session needs a change to your Ramp. [The configuration explainer](https://platformdocs.coinme.com/pages/explainers/configuration.md) covers them in more detail.

<a id="bridge"></a>

## It talks to your app through the bridge

The widget talks to your app through the bridge. Your app sends the widget its session configuration, and the widget sends your app events as the customer moves through it, such as a completed transaction or a request to close. The Widget SDKs for web, iOS and Android run the bridge for you.

[The bridge explainer](https://platformdocs.coinme.com/pages/explainers/bridges.md) compares the bridge with the Bridge Proxy. [Build](https://platformdocs.coinme.com/pages/build/index.md#bridge) walks through the bridge sequence and the configuration fields.

## One codebase. Many applications.

**The economic fact.** Because a Ramp is configuration resolved at runtime, the platform's reach comes from composition rather than from more code.

- **Deployment**: **One** widget serves every Ramp.
- **Ramps**: **Many**, each a distinct application, all sharing the same flow library and engine.
- **New ramp**: A **configuration** exercise. No rebuild, no redeploy to stand one up.
- **First-party**: Coinme runs its own app on the platform as a **Ramp** like any partner. One path serves first-party and partner alike.

<a id="newramp"></a>

## Getting your ramp

Coinme sets up your Ramp, confirms it in our staging environment, and gives you its Ramp ID. Setting one up is a configuration exercise on our side; there is nothing for you to build or deploy.

1. **Agree what it offers**: Decide with your Coinme integration contact which flows, regions, assets and languages your Ramp offers, and how it looks.
2. **Coinme sets it up**: Coinme configures your Ramp and confirms it in our staging environment.
3. **You receive its Ramp ID**: Pass it whenever your app opens the widget.

This overview sits above the system-specific documents, each authoritative for its own area. Capabilities noted as in development are marked as such and should not be read as present state.
