---
title: "Crypto payments, inside your app."
url: "https://platformdocs.coinme.com/#/"
markdown: "https://platformdocs.coinme.com/pages/landing.md"
summary: "Turnkey, compliant, regulated on and off ramps that live inside your product, so you focus on your business. Size the integration surface yourself: as loose as a hosted web frame, as tight as a native bridge."
---

# Crypto payments, inside your app.

Turnkey, compliant, regulated on and off ramps that live inside your product, so you focus on your business. Size the integration surface yourself: as loose as a hosted web frame, as tight as a native bridge.

## Two ways in, one widget

The same Orchestrator widget, the same configuration payload, the same events. Only the container differs. Pick the one that matches where your users are.

The page shows one integration at a time behind a toggle. Both are listed here.

### Inside a native app: Native bridges for iOS and Android

The widget runs in a WebView your app owns, with a two-way messaging bridge. Your app opens it, pre-fills the session, and listens for events.

- **Coupling**: Tight
- **You ship**: A view controller or fragment from our SDK, wired to your navigation.
- **You own**: The surrounding app, the moment of entry, and any reaction to events.
- **Effort**: About fifteen minutes to a first embed; you polish your app as you desire.
- **Guide**: [Native bridges for iOS and Android](https://platformdocs.coinme.com/pages/build/native/ios/overview.md)

### On the web: Framekit for the web

An iframe pointed at the Orchestrator, with the same bridge protocol running over postMessage. Drop a React component or a plain script into your page; theming, prefill, and events all work the same as native.

- **Coupling**: Loose
- **You ship**: One component and a Content Security Policy entry for our origin.
- **You own**: The page around the frame and what happens after a session completes.
- **Effort**: About 15 minutes to start; an afternoon including the CSP change.
- **Guide**: [Framekit for the web](https://platformdocs.coinme.com/pages/build/web/overview.md)

\* A third path, the Bridge Proxy, needs no front-end work at all: a REST call returns a hosted session URL and webhooks report completion. Its build guide is not yet on this site.

## What arrives with the widget

Everything a regulated crypto purchase needs is inside the frame. Your product supplies the user and the moment; the platform supplies the rest.

- **Regulated**: Coinme is a licensed money transmitter. The licenses, the audits, and the reporting are ours to carry.
- **Compliance included**: KYC, risk, and per-region rules run inside the flows. A restricted state changes what the widget offers; it does not change your code.
- **Cash, debit, & more**: Cash at 40,000+ retail locations, any US debit card, and more. Each rail is a feature the ramp can allow or withhold.
- **Multi-asset**: Bitcoin, Ethereum, Polygon, and more, delivered to the wallet the session names or, on Coinme's own ramp, to a custodial balance.
- **Localized**: Translations are delivered separately from the code. A new language is a content change, not a release.
- **Yours to theme**: Light or dark, pinned by your config. The widget takes the shape of the app around it.

## One widget, many experiences.

**Configuration, not code.** Which features, which assets, which regions, which theme: all of it resolves when the widget loads. Adding you as a partner is configuration on our side, not a deploy. Changing your mind later is the same.

- **Go live**: A ramp ID and a config payload.
- **Add a market**: Regional rules are applied for you.
- **Change a rail**: Flip features on or off, no release.

## Go deeper

The widget is the front of a layered platform. When you want the mechanism, it is all here.

- **[The platform, explained](https://platformdocs.coinme.com/pages/explainers/index.md)** (For everyone): Interactive explainers for the platform, one part at a time. No code required to follow.
- **[Build guides](https://platformdocs.coinme.com/pages/build/index.md)** (For engineers): Framekit for the web, CoinmeBridge for iOS and Android, and the whole SDK library. Fifteen minutes to a first embed.

Screens shown are from the Coinme demo app running the widget in [simulated transaction mode](https://platformdocs.coinme.com/pages/explainers/faq.md#simulated-transaction-mode). Live demos are not available in [sanctioned or otherwise restricted jurisdictions](https://platformdocs.coinme.com/pages/explainers/faq.md#sanctioned-jurisdictions) due to regulation. Building with a coding agent? This site is also published as plain text at [llms.txt](https://platformdocs.coinme.com/llms.txt), one Markdown file per page, so an agent can read every guide directly.
