---
title: "Many applications from shared parts."
url: "https://platformdocs.coinme.com/#/explainers/platform"
markdown: "https://platformdocs.coinme.com/pages/explainers/platform.md"
summary: "A layered platform for building crypto applications on top of Coinme. The transactional core is built once, decomposed into versioned parts, and composed at runtime into whatever a market or a partner needs."
---

# Many applications from shared parts.

A layered platform for building crypto applications on top of Coinme. The transactional core is built once, decomposed into versioned parts, and composed at runtime into whatever a market or a partner needs.

**Building internally and enabling a partner are the same act.** A new kind of integration is a matter of composition and configuration, not a new codebase.

<a id="stack"></a>

## A stack you can enter at any layer

Six layers, each building on the one beneath it. **Select a layer to see what it holds.** Then pick an integration tier to see how far up a given consumer starts.

The stack, top to bottom. The last column names the integration tiers that use each layer.

| Layer | Tag | Summary | Used by tiers |
| --- | --- | --- | --- |
| Ramps | output | A complete, deployable application produced by an Orchestrator instance, aimed at a market, partner, or use case. | Ramp deployment |
| Orchestrator | engine | The composition engine. Selects flows, wires their props, and assembles them at runtime into one experience. | Ramp deployment |
| Flows | features | Feature-complete modules, each a self-contained package: KYC, buy, sell, send, cash pickup, history, account. | Ramp deployment |
| Platform services | cross-cutting | Configuration, localization and monitoring, handled by Coinme for the layers above. | Ramp deployment |
| SDK components | raw materials | The partner-facing SDKs, such as Risk, Vault and Onboarding. Usable on their own. | Ramp deployment, Bespoke SDK build |
| Backend | Coinme as a Service | Coinme's services, exposed through standard interfaces rather than re-implemented per app. | Ramp deployment, Bespoke SDK build |

### What each layer holds

- **Ramps**: The output of the platform. A ramp is a complete, deployable application produced by an Orchestrator instance and targeted at a specific market, partner, or use case. Four different ramps are four compositions, not four codebases.
- **Orchestrator**: The composition engine. It reads the ramp's configuration and localization, selects the flows a ramp calls for, and assembles them into one experience.
- **Flows**: Feature-complete modules, each self-contained with its own UI, state, and localization. The same flow runs unchanged in every ramp that offers it.
- **Platform services**: Cross-cutting capabilities the layers above rely on: configuration, localization and monitoring are handled by Coinme.
- **SDK components**: The raw materials, usable on their own with or without the rest of the platform: the partner-facing SDKs listed in the Library, such as Risk, Vault and Onboarding.
- **Backend (Coinme as a Service)**: Coinme's services, holding the business logic and data, exposed to everything above through standard interfaces rather than re-implemented per application.

### Integration tier

- **Enter at any layer**: A partner can build on the SDKs or deploy a finished ramp. The tiers are where each consumer enters the same stack.

Each tier enters the stack at its topmost layer and uses every layer beneath it; the layers above its entry point are outside it.

| Tier | Enters at | Layers it uses | Layers outside it | About |
| --- | --- | --- | --- | --- |
| Bespoke SDK build | SDK components | SDK components, Backend | Ramps, Orchestrator, Flows, Platform services | Bespoke SDK build: a partner brings their own UI and consumes the lower layers directly, taking only the capabilities they need. |
| Ramp deployment | Ramps | Ramps, Orchestrator, Flows, Platform services, SDK components, Backend | none | Ramp deployment: a partner takes a finished, Orchestrator-composed application, differing from any other ramp by configuration. |

<a id="compose"></a>

## One engine, many apps

Different apps are different selections of the same flows under the same engine. Pick a preset and watch the same catalog compose into a different product.

Flow catalog: KYC, Cash buy, Debit buy, Sell, Send / Receive, Cash pickup, Readycode offramp, Transaction history, Account.

Each preset is one app composed by Orchestrator from that catalog. The table states the flows each preset composes and the catalog flows it leaves out.

| Preset | About | Flows composed | Catalog flows left out |
| --- | --- | --- | --- |
| Custodial cash ramp | Buy with cash at retail, pick up as cash. | KYC, Cash buy, Cash pickup, Transaction history, Account | Debit buy, Sell, Send / Receive, Readycode offramp |
| Debit-only digital ramp | Buy and sell digitally, no cash rails. | KYC, Debit buy, Sell, Transaction history, Account | Cash buy, Send / Receive, Cash pickup, Readycode offramp |
| Self-custody wallet | Buy and send to the user's own wallet. | KYC, Debit buy, Send / Receive, Transaction history, Account | Cash buy, Sell, Cash pickup, Readycode offramp |
| Full-service platform | Every rail and every flow available. | KYC, Cash buy, Debit buy, Sell, Send / Receive, Cash pickup, Readycode offramp, Transaction history, Account | none |

<a id="runtime"></a>

## Behavior resolves at runtime, from three inputs

What an instance does is not baked into the build. It resolves on load from ramp configuration, the region's compliance rules, and the partner's inbound session. Change the region or the session and watch the effective experience change.

- **Ramp configuration**: What the app **is**
- **Compliance configuration**: What the region allows
- **Inbound transaction**: What the partner wants now

The Ramp configuration input is fixed: Cash buy, Debit buy, Sell, Send, History. The other two change with the chosen region and session; the table states every combination.

| Region | Session | Compliance configuration | Inbound transaction | Effective session |
| --- | --- | --- | --- | --- |
| Standard region | Open session | Cash buy, Debit buy, Sell, Send, Standard disclosures | Amount open, Currency open, Destination open | In a standard region every rail the ramp permits stays available. The session is open, so the user chooses amount, currency, and destination. |
| Standard region | Partner pre-fill | Cash buy, Debit buy, Sell, Send, Standard disclosures | Amount $100 · locked, BTC · locked, Wallet pinned | In a standard region every rail the ramp permits stays available. The partner pre-filled a $100 BTC purchase and pinned the destination wallet, so those fields arrive locked. |
| Restricted region | Open session | Cash buy, Debit buy (removed), Sell, Send, State disclosure added | Amount open, Currency open, Destination open | In this restricted region compliance removes the debit rail and adds a state-specific disclosure, layered on top of the base config. The session is open, so the user chooses amount, currency, and destination. |
| Restricted region | Partner pre-fill | Cash buy, Debit buy (removed), Sell, Send, State disclosure added | Amount $100 · locked, BTC · locked, Wallet pinned | In this restricted region compliance removes the debit rail and adds a state-specific disclosure, layered on top of the base config. The partner pre-filled a $100 BTC purchase and pinned the destination wallet, so those fields arrive locked. |

None of this variation lives in a branch inside a flow; it is data the engine reads at load.

<a id="reach"></a>

## The span it covers

The flows together cover the whole path a unit of value travels: onto a network, across it, and back off. Deliberately the entire path, not a single segment of it.

The path, in order:

1. **Acquire** (Onramp): Cash at retail, debit and card, kiosk
2. **Move** (Network): Send and receive, custodial or self-custody
3. **Convert out** (Offramp): ATM cash pickup, Readycode

- **Across jurisdictions**: Every U.S. state and every country in the footprint is expressed as data, not code. Entering a market is configuration and content, not a rebuild.
- **Across languages**: User-facing content is delivered separately from the code, so a new language reaches a ramp without a new build.

\* Localization delivery and per-ramp language sets are shipped; the breadth of any given ramp's language set is a configuration choice.

<a id="anywhere"></a>

## The same engine runs anywhere

Three placements, one Orchestrator codebase. Standalone on its own domain, embedded in a partner's website, or embedded in a native app through a WebView.

- **Standalone**: A hosted ramp on its own domain, as Coinme's own consumer experiences ship.
- **Web app**: Loaded in an iframe inside a partner's site.
- **Native app**: Loaded in a WebView (iOS, Android, React Native) inside a partner's mobile app.

### Native apps are hybrid apps over the platform

A native app on the platform is a native shell hosting an embedded Orchestrator across the bridge, with the transactional core supplied rather than rebuilt. A family of distinct native apps is not a family of distinct transactional codebases: they differ by **configuration**, by **theming**, and by whatever each one chooses to build natively. This is hybrid app development augmented by a platform that supplies the hardest, most regulated part: web3 onramps, offramps, and the transacting in between.

<a id="embed"></a>

## Two ways to embed

A spectrum from tight and real-time to simple and backend-driven. Pick the one that matches a partner's engineering shape.

### Messaging Bridge: tight and real-time

A postMessage channel with a handshake and continuous, two-way communication. Orchestrator auto-detects its host (iOS WKWebView, Android WebView, React Native, or web iframe). This is what enables configuration that changes mid-session and an event stream so the host always knows where the user is. The choice when the integration should feel seamless.

### Bridge Proxy: simple and backend-driven

A server-side REST pattern. The partner's backend posts a configuration and receives a widget URL with a short-lived token; the frontend just loads that URL. No postMessage handlers, no bridge protocol. The choice for backend-heavy teams who want the smallest possible frontend footprint.

### Side by side

| Capability | Messaging Bridge | Bridge Proxy |
| --- | --- | --- |
| Real-time, two-way channel | **Yes** | Backend webhooks only |
| Mid-session config changes | **Yes** | Fixed for the widget URL |
| Frontend integration work | Required | **Minimal** |

\* Both are real options with real tradeoffs. The Proxy has no client-side channel, so the frontend cannot directly know when a user is done; the Bridge provides that at the cost of integration work.

<a id="packages"></a>

## Almost everything is a package

The platform is decomposed into independently versioned units, each delivered in the format native to where it is consumed. The same package serves two masters: an external SDK and internal composition.

| Surface | Package format | What it is |
| --- | --- | --- |
| JS / TS surfaces | `npm` | The JavaScript and React SDKs, including the host-side SDK that embeds the widget on the web. |
| iOS bridge | `SPM` | A Swift package, pulled the same way as any native dependency. |
| Android bridge | `Gradle` | A Kotlin library, in the native ecosystem's own manager. |

- **One package, two consumers**: The same artifact serves a bespoke partner build as a piece of an SDK and a composed product as one of its parts. A fix benefits every consumer at once. The packaging is the reuse.
- **The SDK is the same code**: The partner-facing SDKs are built from the same parts the platform uses. Using one capability and using the whole platform are points on a continuum, not different products.

<a id="theming"></a>

## Themable today

Components read design tokens from a resolved theme rather than hardcoding values. Supply one accent token and the platform threads it everywhere. Try it.

A partner supplies a partial theme: only the tokens they want to change. Everything else resolves to the Coinme default through a deep merge. For embedded ramps, the session chooses light or dark through `theme` in its configuration; individual tokens are not part of that payload.

The page's live preview applies one brand accent token, chosen from preset swatches or any custom colour. Accent threads through the header, the card edge, the button, and the pill from a single token.

\* Design token theming is shipped. Logos, background images, brand strings and custom fonts are not part of it.

## The whole payoff, in one line

**Configuration, not code.** When behavior lives in data the engine reads at runtime, growth stops being an engineering project in the common case.

- **A new partner** is a configuration payload, not a fork of an application.
- **A new market** is compliance configuration and content, not a rebuild.
- **A new language** is a translation set, not a rebuild.
- **A new app** is a selection of existing flows under the same engine.
- **The result**: One Orchestrator codebase supports an open-ended number of application variants.

## Compliance and security travel with it

Two properties inherited automatically rather than integrated per partner.

- **Compliance is a platform property**: Jurisdictional rules are configuration and content, not branches in flow code. Jurisdiction rules and disclosures are maintained by Coinme and apply to your users automatically.
- **Approved hosts only**: The widget only runs inside hosts Coinme has approved for your ramp. Ask your Coinme integration contact to add your hosts.

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