---
title: "What a user can do is composed, not coded."
url: "https://platformdocs.coinme.com/#/explainers/configuration"
markdown: "https://platformdocs.coinme.com/pages/explainers/configuration.md"
summary: "Three inputs decide what any given person sees and can do in a session. None of them live in a branch inside the app. Change one input and the behavior changes with it, with no new build and no new code."
---

# What a user can do is composed, not coded.

Three inputs decide what any given person sees and can do in a session. None of them live in a branch inside the app. Change one input and the behavior changes with it, with no new build and no new code.

<a id="model"></a>

## Two sources, three inputs

Everything that shapes a session comes from one of two places, and resolves into three inputs the engine composes.

At session start the widget reads Coinme's remote configuration for your Ramp, keyed by the Ramp identifier. It carries two of the three inputs. The base Ramp config says what the Ramp offers to everyone. The compliance overlay says what a given region takes away or requires. The third input arrives from the embedding partner over the Bridge, and it describes what this one session is for. Orchestrator composes all three and offers the user exactly the capabilities that survive.

| Source | About the source | Inputs it yields |
| --- | --- | --- |
| Remote configuration (SOURCE · KEYED BY RAMP ID) | Static for the ramp. Maintained by Coinme. | INPUT 1 · BASE RAMP CONFIG: What the Ramp offers everyone. INPUT 2 · COMPLIANCE OVERLAY: What a region takes away. |
| Bridge / Bridge Proxy (SOURCE · FROM THE PARTNER) | Delivered per session or transaction. | INPUT 3 · SESSION INTENT: What this session is for. |

**Orchestrator** composes all three inputs into: What the user can do.

- **What the Ramp offers** (Input 1 · Base config): The flows, rails, payment methods, assets, regions, and languages a Ramp exposes by default, to everyone, regardless of where they are. Source: **Coinme's remote configuration for your Ramp**. Same for every session of the Ramp.
- **What a region requires or removes** (Input 2 · Compliance): Region-matched rules layered on top of base config: excluded rails, excluded assets, required consents and disclosures, receipt formats. Source: **Coinme's remote configuration for your Ramp**. Applies to the user's region after identity verification.
- **What this session is for** (Input 3 · Session): Pre-filled amounts and assets, locked fields, a destination wallet, a language. The one input that differs between two people at once. Source: **The partner**, over the Bridge. Changing it: a new session.

These three inputs are a curated subset of what the platform can do. The configuration surface exposes the settings a Ramp needs to select and shape existing flows, rails, assets, and rules. The platform holds more capability than any single config payload names, and configuration chooses from it.

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

## Compose it yourself

Set the three inputs on the left. The panel on the right resolves what a user in this session can actually do, and shows how each input contributed.

On the page this is an interactive sandbox. The full set of input combinations is too large to list, so the tables below give each input on its own, then what every region and direction resolve to with the full base config and an open session, then what a requested asset and a narrower base config change.

### Input 1 · Base Ramp config (Remote configuration)

What this Ramp offers everyone. Toggle a capability off and no region can bring it back.

By default the base config offers every rail and asset below.

| Rails | Direction |
| --- | --- |
| Buy with cash | `buy` |
| Buy with card | `buy` |
| Sell for cash | `sell` |
| Sell to card | `sell` |
| Send crypto | `transfer` |
| Receive crypto | `transfer` |

Assets: `POL`, `BTC`, `ETH`, `USDC`.

### Input 2 · Compliance overlay (Remote configuration)

The user's region. Its rules can only take away from what base offers or add steps before the user proceeds, and they apply only after identity verification. The regions here are illustrative.

Each region the sandbox offers, with the full base config:

| Resolved region | Removes | Assets they can pick | Gates before they proceed | What it means |
| --- | --- | --- | --- | --- |
| None yet (before identity verification) | none | None until identity verification completes | none | Until the user completes identity verification, the only available action is verifying, and no regional rules apply yet. |
| Unrestricted region | none | POL, BTC, ETH, USDC | none | A region with no rules of its own. Base config passes through in full: nothing is removed and nothing is added. |
| Region A | Buy with cash, Sell for cash | POL, BTC, ETH, USDC | none | Removes cash buy and cash sell. Card rails and transfers still work. |
| Region B | ETH | POL, BTC, USDC | none | Removes one asset. A session that requests it meets a notice before the flow opens. |
| Region C | none | POL, BTC, ETH, USDC | One-time consent (once, before the app opens), Disclosure on every transaction (per transaction) | Removes nothing. The user accepts a one-time consent before the app opens and sees a disclosure on every transaction. |
| Region not in this Ramp | none | None | none | The Ramp is not offered in this region, so no regional rules are evaluated and the Ramp does not operate here. |

### Input 3 · Session intent (Bridge)

What the partner sends for this one session. It focuses and locks; it never grants.

Each option, what it adds to the session pins, and the RampConfig fields it sets. Every payload also carries `partnerId`. With nothing set the session reads: Open session. The user chooses everything.

| Session option | This session pins | RampConfig fields it sets |
| --- | --- | --- |
| Direction: User chooses | none | none |
| Direction: Buy | Direction: buy | none |
| Direction: Sell | Direction: sell | `destinationCurrency: "USD"` |
| Requested asset: User chooses | none | none |
| Requested asset: POL | Asset: POL | `destinationCurrency: "POL"` |
| Requested asset: BTC | Asset: BTC | `destinationCurrency: "BTC"` |
| Requested asset: ETH | Asset: ETH | `destinationCurrency: "ETH"` |
| Requested asset: USDC | Asset: USDC | `destinationCurrency: "USDC"` |
| Pins: Pre-fill $100 | Amount: $100 | `sourceAmount: 100`, `sourceCurrency: "USD"` |
| Pins: Lock fields | Fields locked | `sourceAmountLock: true`, `destinationCurrencyLock: true`, `walletLock: true` |
| Pins: Wallet provided | Wallet provided | `walletAddress` |

### What the user ends up with

Every region against every direction, with the full base config and no asset requested. "Shown as unavailable" lists what base offers but the user cannot use here.

| Resolved region | Direction | Status | Available to this user | Shown as unavailable | Outcome |
| --- | --- | --- | --- | --- | --- |
| None yet (before identity verification) | Any | Identity verification required: Nothing transacts until identity verification completes | Complete identity verification | Buy with cash, Buy with card, Sell for cash, Sell to card, Send crypto, Receive crypto | Until the user completes identity verification, the only available action is verifying. Nothing transacts and no regional rules apply yet. |
| Unrestricted region | User chooses | This user can transact | Buy with cash, Buy with card, Sell for cash, Sell to card, Send crypto, Receive crypto | none |  |
| Unrestricted region | Buy | This user can transact | Buy with cash, Buy with card | none |  |
| Unrestricted region | Sell | This user can transact | Sell for cash, Sell to card | none |  |
| Region A | User chooses | This user can transact | Buy with card, Sell to card, Send crypto, Receive crypto | Buy with cash, Sell for cash |  |
| Region A | Buy | This user can transact | Buy with card | Buy with cash, Sell for cash |  |
| Region A | Sell | This user can transact | Sell to card | Buy with cash, Sell for cash |  |
| Region B | User chooses | This user can transact | Buy with cash, Buy with card, Sell for cash, Sell to card, Send crypto, Receive crypto | none |  |
| Region B | Buy | This user can transact | Buy with cash, Buy with card | none |  |
| Region B | Sell | This user can transact | Sell for cash, Sell to card | none |  |
| Region C | User chooses | This user can transact | Buy with cash, Buy with card, Sell for cash, Sell to card, Send crypto, Receive crypto | none |  |
| Region C | Buy | This user can transact | Buy with cash, Buy with card | none |  |
| Region C | Sell | This user can transact | Sell for cash, Sell to card | none |  |
| Region not in this Ramp | Any | Ramp does not operate here: Region not offered by this Ramp | Nothing available. Ramp inactive in this region | none |  |

### Requesting an asset

A requested asset is checked against the region before direction. Only regions that remove an asset are listed; elsewhere a request only adds the asset to the session pins.

| Resolved region | Requested asset | Lock fields | Status | Result |
| --- | --- | --- | --- | --- |
| Region B | ETH | no | Session blocked · asset not permitted: A notice before the flow opens | ETH is not permitted in Region B. The user clears the notice and picks a different asset. |
| Region B | ETH | yes | Session blocked · asset not permitted: A notice before the flow opens | ETH is not permitted in Region B. Because the session locks the asset, the user is returned to the partner app. |
| Region B | POL | no | This user can transact | Buy with cash, Buy with card, Sell for cash, Sell to card, Send crypto, Receive crypto |

### Narrowing the base config

Representative base edits. A region rule for a rail that base does not offer has no effect.

| Base offers | Resolved region | Direction | Status | Available to this user | Assets they can pick | Region rules with no effect | Outcome |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Rails: Send crypto, Receive crypto. Assets: POL, BTC, ETH, USDC | Unrestricted region | User chooses | View-only (transaction history): No transacting rail survives for this path | Send crypto, Receive crypto | POL, BTC, ETH, USDC | 0 | No transacting rail survives, so the app opens to transaction history, view-only. |
| Rails: Send crypto, Receive crypto. Assets: POL, BTC, ETH, USDC | Unrestricted region | Buy | View-only (transaction history): No transacting rail survives for this path | View-only, no transacting | POL, BTC, ETH, USDC | 0 | Every buy rail is excluded here, so the session lands on transaction history, view-only. |
| Rails: Buy with cash, Buy with card, Sell for cash, Sell to card, Send crypto, Receive crypto. Assets: none | Unrestricted region | User chooses | This user can transact | Buy with cash, Buy with card, Sell for cash, Sell to card, Send crypto, Receive crypto | No assets available | 0 |  |
| Rails: Buy with card, Sell to card, Send crypto, Receive crypto. Assets: POL, BTC, ETH, USDC | Region A | User chooses | This user can transact | Buy with card, Sell to card, Send crypto, Receive crypto | POL, BTC, ETH, USDC | 2 |  |

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

## Why it is shaped this way

Every session sits where four different demands meet. The configuration model exists to satisfy all four at once, without a code branch for any of them.

Coinme operates in many jurisdictions, and the rules differ between them. At the same time the platform powers many partners, each wanting a different integration, and each of their customers arrives with a different transaction in mind. The combination of partners, jurisdictions, and transactions is far too large to maintain as branches in code, so the variation is expressed as configuration the engine reads at runtime. Each of the four demands lands in a specific place, and one platform serves every partner without forking.

### The four demands, and where each one lands

| The demand | What it pushes for | Where it lands |
| --- | --- | --- |
| What the platform can do | The full set of flows, rails, and assets that could ever be offered | **The capability ceiling**, above config |
| What a partner wants from their integration | A specific selection and look for their own Ramp | **Base Ramp config** (Input 1) |
| What a jurisdiction obligates and allows | Required disclosures, restricted rails and assets, receipt content | **Compliance overlay** (Input 2) |
| What a partner wants for one transaction | A pre-set, focused session for their inbound customer | **Inbound RampConfig** (Input 3) |

These pull in different directions. A partner wants flexibility, a jurisdiction sets limits, and a transaction wants a single narrow path. Expressing the demands as layered configuration is what lets one platform apply the rules a region sets and leave room where a partner needs it, in the same deployment, at the same moment.

## The whole model in one line

**Base config, narrowed by region, tailored per session.**

Each phrase answers a different demand, in the order they compose. Together they are how a heavily regulated business sells into many jurisdictions and many partners from a single platform.

- **Applied for you**: Jurisdiction rules and disclosures are maintained by Coinme and apply to your users automatically.
- **Flexible without forking**: Partners select and shape from shared parts. A new market or a new partner is a configuration effort, not a new codebase.
- **No release on your side**: When a regional rule changes, Coinme updates your Ramp's configuration. Your integration stays as it is.

<a id="interface"></a>

## The real interface

The controls above map onto real shapes. Two of them are worth separating by name.

The Ramp's remote configuration is Inputs 1 and 2. It defines what the Ramp is, it is keyed by Ramp ID, and Coinme maintains it for your Ramp. The inbound **transaction** RampConfig is Input 3. It defines what a single session is for. The partner sends it over the Bridge when their customer comes inbound, and it can only focus and lock the capabilities the first two already allow. It cannot switch a flow on, add a rail, or reach into another partner's session. The first table below describes the kinds of regional rule Coinme can apply, which partners never author; the second is the inbound RampConfig partners send.

### Regional rules · what a region can apply on top of base config (Input 2)

| Rule | What it does to a user in that region |
| --- | --- |
| Region match | Which region the rules apply to, matched against the user's region after identity verification. |
| Removed rails | Ways to buy, sell, or move crypto that are not offered in the region. They drop out of the choices the user sees. |
| Removed assets | Assets not offered in the region. A session that requests one meets a notice before the flow opens. |
| One-time consents | Disclosures the user accepts once before the app opens. |
| Transaction disclosures | Disclosures shown before the user confirms a transaction, on some transactions or on every one. |
| Receipt content | Region-specific content on the user's receipt. It changes what the receipt says, not what the user can do. |
| Additional verification | Extra identity checks a region requires before the user can transact. |

### RampConfig · the inbound, per-session payload the partner sends over the Bridge (Input 3)

| Field | What it does to this session |
| --- | --- |
| `partnerId` | Identifies the embedding partner for this session. |
| `destinationCurrency` | The asset the session targets, for example **POL** for a buy. A value of **USD** resolves the direction to sell; anything else is a buy. |
| `sourceAmount` / `sourceCurrency` | Pre-fills the amount and paying currency so the user starts partway through. |
| `sourceAmountLock` / `destinationCurrencyLock` / `walletLock` | Locks a pre-filled field so the user cannot change it. |
| `walletAddress` | A destination wallet, which lets the flow skip asking the user for one. |

Regions and rules on this page are illustrative. The rules that apply in a given state are set by Coinme and can change.
