---
title: "Agent primer: the Coinme App Platform"
url: "https://platformdocs.coinme.com/agents/primer.md"
markdown: "https://platformdocs.coinme.com/agents/primer.md"
summary: "Orientation for a coding agent new to Coinme: what the Coinme App Platform is, which of its two surfaces and which SDKs apply, the vocabulary the site uses, what an integrator touches versus internal architecture, what is shipped today, and which page answers which kind of question."
---

# Agent primer: the Coinme App Platform

## What the Coinme App Platform is

The Coinme App Platform is how other companies put regulated crypto buying, selling and moving inside their own products. Coinme is the licensed money transmitter and carries the licences, compliance and reporting.

There are two ways to build on it. In the **Widget / Ramp** integration a transactional partner embeds the Coinme Widget, a complete crypto application (a Ramp) that Coinme composes from reusable flows; the transaction is the partner's and the end user is onboarded as a Coinme customer inside the widget. In the **Coinme-as-a-Service (CaaS)** integration a partner with its own users composes Coinme services into its own app with the Onboarding, Compliance, Vault and Risk SDKs, and its backend calls the CaaS API, directly or through the CaaS API clients, server-side convenience wrappers for Node.js; the users stay the partner's customers.

What a Ramp offers is configuration, not code: it resolves at session start from the Ramp's remote configuration (keyed by its Ramp ID), the compliance rules of the user's region, and the session intent the partner sends.

## Which surface, which SDKs

- **Will the end users become Coinme customers, with Coinme's app doing sign-in, KYC and payment?** Then it is a Widget / Ramp integration ([details](https://platformdocs.coinme.com/agents/surfaces.md#ramp)):
  - On a website: Framekit, `@coinme/coinme-bridge-framekit`. Skill: [coinme-widget-web](https://platformdocs.coinme.com/skills/coinme-widget-web/SKILL.md).
  - In an iOS app: CoinmeBridge for iOS. Skill: [coinme-widget-ios](https://platformdocs.coinme.com/skills/coinme-widget-ios/SKILL.md).
  - In an Android app: CoinmeBridge for Android. Skill: [coinme-widget-android](https://platformdocs.coinme.com/skills/coinme-widget-android/SKILL.md).
  - Backend only, no front-end channel: the Bridge Proxy. It is described in [the bridge explainer](https://platformdocs.coinme.com/pages/explainers/bridges.md); its build guide is not on this site.
  - You do not need the Onboarding, Vault or Risk SDK for the widget itself.
- **Will the users stay your customers, in your own app and UI?** Then it is a CaaS integration ([details](https://platformdocs.coinme.com/agents/surfaces.md#caas)), and you pick the services you need:
  - To onboard a customer, run non-documentary KYC and verify their phone afterwards: the Onboarding SDK (`@coinme-security/onboarding-sdk-react` for React and JavaScript web apps, `@coinme-security/onboarding-sdk-react-native` for React Native and Expo apps). Skills: [coinme-onboarding-react](https://platformdocs.coinme.com/skills/coinme-onboarding-react/SKILL.md) and [coinme-onboarding-react-native](https://platformdocs.coinme.com/skills/coinme-onboarding-react-native/SKILL.md).
  - To apply Coinme's regional compliance rules in your own screens (which states to offer, what a region excludes, which consents and disclosures to show, and recording what the customer accepted): the Compliance SDK, `@coinme-security/compliance-sdk-react`, for React and JavaScript web apps. Its release on this site is 1.1.3, in **beta** (published and installable, not generally available), and it is **advisory**: Coinme's backend still enforces every rule. Skill: [coinme-compliance-react](https://platformdocs.coinme.com/skills/coinme-compliance-react/SKILL.md). For React Native and Expo apps, `@coinme-security/compliance-sdk-react-native` is also in **beta** (release 1.0.2), with the same rules, provider and hooks; skill: [coinme-compliance-react-native](https://platformdocs.coinme.com/skills/coinme-compliance-react-native/SKILL.md). Every page in [llms-compliance.txt](https://platformdocs.coinme.com/llms-compliance.txt).
  - To capture card details without them touching your code: the Vault SDK (JavaScript, iOS, Android, React Native). Skills: [skills/index.json](https://platformdocs.coinme.com/skills/index.json), names `coinme-vault-*`.
  - To send the device and behavioural signals Coinme requires before transactional calls: the Risk SDK (web, iOS, Android, React Native). Skills: names `coinme-risk-*` in the same index.
  - To call the CaaS API (quotes, buy and sell, history, sends, onboarding and payment methods): the CaaS API clients, `@coinme/*-api-client`. They are **server-side convenience wrappers** over the CaaS REST API, for your Node.js 20+ backend only: `AuthService` holds your partner ID and client secret, so your web and mobile front ends call your backend, never CaaS directly. Overview: [CaaS API clients](https://platformdocs.coinme.com/docs/caas-api-clients.md); skill: [coinme-caas-api-clients](https://platformdocs.coinme.com/skills/coinme-caas-api-clients/SKILL.md); every page in [llms-api.txt](https://platformdocs.coinme.com/llms-api.txt).
  - You do not embed the Coinme Widget.
- **Does your app collect a wallet address, on either integration?** Check it with the wallet address validator, `@coinme/wallet-address-validator` (release 1.2.0, for browsers, Node.js 18+ and React Native 0.74+ with Hermes). It works on **both** surfaces ([details](https://platformdocs.coinme.com/agents/surfaces.md#both)): it is offline and format-only, calls no Coinme service and needs no credential beyond the registry token. A Widget partner checks an address before passing it to the widget as `walletAddress`; a CaaS partner checks the send or withdrawal addresses its own screens collect. `true` means well-formed, not safe to send to. Skill: [coinme-wallet-address-validator](https://platformdocs.coinme.com/skills/coinme-wallet-address-validator/SKILL.md); every page in [llms-wallet.txt](https://platformdocs.coinme.com/llms-wallet.txt).
- **Not sure which?** Ask your Coinme integration contact; the side-by-side comparison is in [agents/surfaces.md](https://platformdocs.coinme.com/agents/surfaces.md).

## Glossary

| Term | Meaning | Defined in |
| --- | --- | --- |
| Ramp | A complete, deployable crypto application that Orchestrator composes from shared flows for a market, partner or use case. A Ramp is a configuration, not a codebase. | [source](https://platformdocs.coinme.com/pages/explainers/orchestrator.md) |
| Ramp ID (`rampId`) | The key Orchestrator resolves the Ramp's configuration by and attributes transactions to. Coinme issues it at onboarding. | [source](https://platformdocs.coinme.com/pages/build/index.md#config) |
| `partnerKey` | Identifies your app to the Widget in the bridge handshake. Native integrations need it; a wrong or empty value means the session never becomes ready. Keep it in runtime configuration with your `rampId`. | [source](https://platformdocs.coinme.com/pages/build/index.md#config) |
| Orchestrator | The Coinme Widget: one web app that runs the whole customer experience, configured per Ramp ID. | [source](https://platformdocs.coinme.com/pages/explainers/orchestrator.md) |
| Coinme Widget | An Orchestrator Ramp running inside a partner's iframe or WebView, reached through the Widget SDK. | [source](https://platformdocs.coinme.com/pages/build/index.md) |
| Flow | One customer journey inside the widget (identity verification, buy, sell, send, cash pickup, history, account); your Ramp decides which run. | [source](https://platformdocs.coinme.com/pages/explainers/flows.md) |
| Bridge (Messaging Bridge) | The live two-way postMessage channel between a partner's app and the widget: handshake, one configuration, then events out and updates in for as long as the container lives. | [source](https://platformdocs.coinme.com/pages/explainers/bridges.md) |
| Bridge Proxy | The backend-only alternative to the bridge: the partner's backend posts a configuration and receives a widget URL with a short-lived token, and backend webhooks report completion. There is no live channel. | [source](https://platformdocs.coinme.com/pages/explainers/bridges.md) |
| Framekit | The web Widget SDK, `@coinme/coinme-bridge-framekit`: a React component or plain script that mounts the widget in an iframe and runs the bridge. | [source](https://platformdocs.coinme.com/pages/build/web/overview.md) |
| CoinmeBridge | The native Widget SDKs for iOS (Swift) and Android (Kotlin): the widget in a WebView with the same configuration and events as Framekit. | [source](https://platformdocs.coinme.com/pages/build/native/ios/overview.md) |
| `CoinmeConfig` (session intent) | The one configuration object the SDK sends across the bridge: identity, theme, language, pre-filled transaction values and locks, wallet, location and tracking ids. It overlays the Ramp's configuration for one session without redefining it. Every `updateConfig` reaches the widget at once, but only theme and language should change while a transaction is under way; transaction fields set up the next one. | [source](https://platformdocs.coinme.com/pages/build/index.md#config) |
| Compliance overlay | The rules for the user's region in Coinme's remote configuration for your Ramp, applied on top of its base configuration. They can only take away from what the base offers or add steps before the user proceeds, never grant. Coinme sets them, and they can change. | [source](https://platformdocs.coinme.com/pages/explainers/configuration.md) |
| Remote configuration | Coinme's remote configuration for your Ramp: what the Ramp offers and the rules for each region, keyed by Ramp ID. Coinme authors it. | [source](https://platformdocs.coinme.com/pages/explainers/configuration.md) |
| GreenDot | The cash on-ramp: buying crypto with cash at retail locations. | [source](https://platformdocs.coinme.com/pages/explainers/configuration.md) |
| Readycode | The cash off-ramp: selling crypto for cash picked up at an ATM. | [source](https://platformdocs.coinme.com/pages/explainers/configuration.md) |
| Bridge events | The typed events the Widget SDKs deliver, such as `sessionReady`, `transactionComplete`, `barcodeGenerated` and `closeRequested`. Which events your app receives depends on your Ramp's configuration. | [source](https://platformdocs.coinme.com/pages/build/web/how-to-use.md) |
| Simulated transaction mode | The widget runs its full path without moving real funds: crypto on testnets, card payments with test cards, real but unusable barcodes. | [source](https://platformdocs.coinme.com/pages/explainers/faq.md#simulated-transaction-mode) |
| CaaS (Coinme-as-a-Service) | Coinme's services for partners that keep their own users: onboarding and KYC, vaulting, risk and transactions, reached through the CaaS SDKs in the partner's app and the CaaS API from the partner's backend. | [source](https://platformdocs.coinme.com/agents/surfaces.md) |
| CaaS API clients (`@coinme/*-api-client`) | Server-side convenience wrappers: typed TypeScript packages for calling the CaaS REST API from a Node.js backend, one package per area of the API (core, quotes, transactions, history, send and more), installed from a private registry. Not for browsers or apps. | [source](https://platformdocs.coinme.com/docs/caas-api-clients.md) |
| `AuthService` | The class in `@coinme/core-api-client` that exchanges a partner ID and client secret for a bearer token and refreshes it; it holds the client secret, so it runs only in the backend, and it throws if created in a browser, WebView or React Native app. | [source](https://platformdocs.coinme.com/docs/caas-api-clients.md) |
| `customerId` | The id of a customer onboarded to CaaS, returned by the Onboarding SDK once the customer is onboarded. | [source](https://platformdocs.coinme.com/docs/coinme-onboarding-sdk.md) |
| Region status (Compliance SDK) | Where a region stands with Coinme: `onboardable` (operating, and new customers can onboard), `operating` (no new customers; whether anything can be transacted there depends on its rail exclusions), `notOperating` (listed, but Coinme does not operate there) or `unknown` (an ISO code Coinme does not list). Every region is an ISO 3166-2 code (`US-NY`); a short code or a name throws `invalidRegion` rather than being treated as unknown, and unknown fails closed. | [source](https://platformdocs.coinme.com/docs/compliance-sdk-react.md) |
| Attestation | A record that an onboarded customer accepted a consent or a transactional disclosure, with the region, the `policyVersion` in force and the exact text they saw (`locale`, `contentHash`). Recorded through the Compliance SDK after onboarding; not available in the Compliance SDK beta at this time. | [source](https://platformdocs.coinme.com/docs/compliance-sdk-react.md) |
| Non-documentary KYC | Identity verification from the details the customer types (email, name, address, phone, date of birth, SSN), with no document upload. | [source](https://platformdocs.coinme.com/docs/coinme-onboarding-sdk.md) |
| Transient Auth Token (onboarding token) | A 10-minute token the partner's backend mints with `POST /services/browserAuth` for one customer and one kind of call: the Vault SDK's payment-method submit (`payment-methods` scope) or the Onboarding SDK's onboarding submit (`onboarding` scope, minted for the sign-up session) and its phone verification calls (`onboarding` scope, minted for the `customerId` onboarding returned, from the partner's own record and never from the client; it is the only thing binding the send and the check to that customer, with no challenge ID or session to pass between them; the partner builds the backend route that mints it, which looks up the signed-in user and mints for the `customerId` saved when onboarding succeeded, so customer IDs cannot be mixed up), or the Compliance SDK's attestation reads and records (`attestations` scope, minted for the onboarded customer; not available in the beta at this time). The client sends it as `Authorization: Bearer`; it is never stored. Never pass the partner access token to any of these SDKs in its place. The Risk SDK takes no token at all. | [source](https://platformdocs.coinme.com/docs/transient-auth-token.md) |
| Partner access token | The token a partner's backend gets from `POST /services/authorize` with its API client ID and client secret. It authorizes every CaaS endpoint, mints Transient Auth Tokens, and never leaves the backend. Never pass it to any Coinme SDK. | [source](https://platformdocs.coinme.com/docs/transient-auth-token.md) |
| Secure field (hosted field) | An input rendered by the vault provider in an iframe, so sensitive values such as a card number or SSN go straight to Coinme's vault without passing through the partner's code. | [source](https://platformdocs.coinme.com/docs/coinme-vault-sdk.md) |
| Risk session tag | The `webSessionID` the Risk SDK's session-tag call returns (`getSessionTag()` on the web, `getPartnerSessionTag()` on iOS, Android and React Native, neither taking an auth token); it becomes the session key for later risk calls, and the Vault SDK's payment-method submit requires it as `webSessionId`. A tag lives 30 minutes from when it was issued, so it is fetched right before each add-payment-method call and each order. | [source](https://platformdocs.coinme.com/docs/using-the-coinme-risk-sdk-for-web.md) |
| `clientId` (Risk) | Identifies an integration to the Risk Engine; the Risk SDK refuses to initialise without it. One per environment. | [source](https://platformdocs.coinme.com/pages/build/agents.md) |
| Wallet address validation (`validateAddress`) | A format-only check, offline, that an address is well-formed for an asset and chain: its length and characters, network prefix and checksum. It comes from `@coinme/wallet-address-validator` and works on both surfaces. `true` does not mean the address exists, is the customer's or is safe to send to, and an unsupported asset or chain throws rather than returning `false`. | [source](https://platformdocs.coinme.com/docs/wallet-address-validator.md) |
| `chainType` | The chain a wallet address is on, passed to `validateAddress` as a chain id or alias (`stellar`, `tron`, `erc20`). Strict mode requires it for assets on more than one chain, such as `usdc` and `usdt`, and throws when the chain does not use the currency's address format. | [source](https://platformdocs.coinme.com/docs/wallet-address-validator.md#chains-and-chaintype) |
| Embed allowlist | The list of web hostnames Coinme lets the widget render inside. A deployed site must be added; local development hosts work against the stage Widget without an allowlist entry. | [source](https://platformdocs.coinme.com/pages/build/web/how-to-use.md) |

## What you touch, and what is internal

The explainers describe how the platform is built, including detail no integrator configures. Use this table to tell the two apart.

| Concept | For an integrator | What it is to you |
| --- | --- | --- |
| `rampId`, `partnerKey`, `orchestratorUrl` | you set or handle it | Identity of a Widget integration, issued by Coinme. |
| `CoinmeConfig` and `updateConfig` | you set or handle it | Session intent: pre-fill, locks, theme, language, tracking ids. Change transaction fields between transactions, not during one. |
| Bridge events | you set or handle it | What your app reacts to: session ready, transaction outcomes, barcodes, close. |
| Onboarding, Compliance, Vault and Risk SDK APIs and their tokens | you set or handle it | The CaaS integration surface in your app. |
| CaaS API clients, `AuthService`, partner ID and client secret | you set or handle it | The CaaS integration surface in your backend. |
| The wallet address validator (`validateAddress`, `isSupported`) | you set or handle it | A format check for the wallet addresses your app collects, on either surface; it calls no Coinme service. |
| Your Ramp's configuration and compliance overlays | internal: understand, do not configure | Coinme authors them; they explain why a user sees what they see. |
| How the Widget is built and configured inside Coinme | internal: understand, do not configure | Coinme operates it; nothing here is a partner setting. |

## What exists today

Pages mark capabilities in beta (published and installable, fine for development builds, not generally available: check with your Coinme integration contact before production), or in development; do not build against an in-development capability as present. Anything not listed here is not documented on this site; ask your Coinme integration contact rather than assuming it exists.

| Capability | Status | Stated in |
| --- | --- | --- |
| Widget SDK on web, iOS and Android | shipped | [source](https://platformdocs.coinme.com/pages/build/index.md) |
| Onboarding SDK for JavaScript & React | shipped | [source](https://platformdocs.coinme.com/docs/onboarding-sdk-react.md) |
| Onboarding SDK for React Native | shipped | [source](https://platformdocs.coinme.com/docs/onboarding-sdk-react-native.md) |
| Compliance SDK for JavaScript & React (1.1.3, published but not generally available) | beta | [source](https://platformdocs.coinme.com/docs/coinme-compliance-sdk.md) |
| Compliance SDK for React Native (1.0.2, published but not generally available) | beta | [source](https://platformdocs.coinme.com/docs/compliance-sdk-react-native.md) |
| Vault SDK on JavaScript, iOS, Android, React Native | shipped | [source](https://platformdocs.coinme.com/docs/coinme-vault-sdk.md) |
| Risk SDK on web, iOS, Android, React Native | shipped | [source](https://platformdocs.coinme.com/docs/coinme-risk-sdk.md) |
| Wallet address validator 1.2.0 (browsers, Node.js 18+, React Native 0.74+ with Hermes; both surfaces) | shipped | [source](https://platformdocs.coinme.com/docs/wallet-address-validator.md) |
| Phone verification after onboarding (part of the Onboarding SDK in the releases on this site, 1.7.1 on the web and 1.2.1 on React Native; KYC is not complete until the customer's phone is verified) | shipped | [source](https://platformdocs.coinme.com/docs/onboarding-sdk-react.md#phone-verification) |
| CaaS API clients 2.0.0 (1.x is deprecated; until 2.0.0 is published the registry serves 1.x) | in development | [source](https://platformdocs.coinme.com/docs/caas-api-clients.md) |
| Custody and cash ramp API clients (not yet published; they publish with the 2.0.0 release, as version 0.1.0) | in development | [source](https://platformdocs.coinme.com/docs/caas-api-clients.md) |
| Design-token theming (light / dark via `theme`) | shipped | [source](https://platformdocs.coinme.com/pages/explainers/platform.md) |

<a id="not-covered"></a>

## Not covered on this site

Newcomers ask about these, and this site does not answer them. Say so, and send the question to the right place, rather than guessing or inferring an answer from examples.

| Topic | What this site says | Where the answer is |
| --- | --- | --- |
| Supported assets, chains, countries and US states | No list of what Coinme offers. The [wallet address validator's list](https://platformdocs.coinme.com/docs/wallet-address-validator-supported-assets.md) is the assets and chains it can check addresses for, not what Coinme lets a customer buy, sell or send. For a CaaS integration, the [Compliance SDK](https://platformdocs.coinme.com/docs/compliance-sdk-react.md#regions) returns the regions Coinme lists, with whether it operates and onboards in each, at runtime (in beta). Assets appear only in examples (`BTC`, `ETH`, `POL`, `USDC`); [the configuration explainer](https://platformdocs.coinme.com/pages/explainers/configuration.md) uses illustrative regions only. What a given Ramp offers is in its configuration. The [sanctioned-jurisdictions list](https://platformdocs.coinme.com/pages/explainers/faq.md#sanctioned-jurisdictions) is about where the demo apps run, not where you may operate. | Ask your Coinme integration contact. Coverage is per Ramp and per region. |
| Fees and pricing | Nothing. | Ask your Coinme integration contact. |
| Support and bug reporting | No support channel, issue tracker or status page. For a web embed that does not load, [framekit-doctor](https://platformdocs.coinme.com/pages/build/web/doctor.md) diagnoses the integration. | Ask your Coinme integration contact. |
| Changelog and release notes | None. The current release of each SDK is in [skills/index.json](https://platformdocs.coinme.com/skills/index.json) and in each SDK page's front matter (`version`). | Ask your Coinme integration contact. |
| Webhooks (registration, payload, signing, retries) | Named as the way the Bridge Proxy reports completion, in [the bridge explainer](https://platformdocs.coinme.com/pages/explainers/bridges.md); not specified anywhere. | Ask your Coinme integration contact. |
| Server-side transaction status | Nothing. A Widget integration learns outcomes in the client, from bridge events such as `transactionComplete` and `barcodeGenerated` ([How to use (web)](https://platformdocs.coinme.com/pages/build/web/how-to-use.md)). | Ask your Coinme integration contact. |
| The Bridge Proxy API | Described as a pattern in [the bridge explainer](https://platformdocs.coinme.com/pages/explainers/bridges.md): your backend posts a configuration and receives a widget URL with a short-lived token. Its build guide is not on this site. | Ask your Coinme integration contact. |

## Where to find the answer

| If the question is | Read |
| --- | --- |
| What is the platform, which surface am I on, which SDKs do I need? | [The agent primer](https://platformdocs.coinme.com/agents/primer.md), then [agents/surfaces.md](https://platformdocs.coinme.com/agents/surfaces.md). |
| How do I integrate SDK X on platform Y? | Its skill: [skills/index.json](https://platformdocs.coinme.com/skills/index.json) lists every skill with its surface, platform, package and version. |
| Did my call succeed? What does this error code mean: fix, retry, or stop and ask? | [Reading results](https://platformdocs.coinme.com/agents/results.md): HTTP 200 is not success, the error envelope, common codes by what to do, lifetimes and limits, and what to send when something fails. |
| Every document for one SDK | The [Library](https://platformdocs.coinme.com/pages/build/library.md), or that SDK's `llms-<family>.txt` slice. |
| Which `CoinmeConfig` fields exist, which are required, which can change mid-session? | The field table on [Build](https://platformdocs.coinme.com/pages/build/index.md#config). |
| Which widget events will my app receive? | [Build](https://platformdocs.coinme.com/pages/build/index.md) for the four that need an answer; [How to use (web)](https://platformdocs.coinme.com/pages/build/web/how-to-use.md) for the typed set and forwarding. |
| Bridge or Bridge Proxy? | [The bridge explainer](https://platformdocs.coinme.com/pages/explainers/bridges.md). |
| Why does a user see (or not see) a rail, asset or disclosure? | [The configuration explainer](https://platformdocs.coinme.com/pages/explainers/configuration.md): base config, compliance overlay, session intent. |
| In my own CaaS screens, which states can I offer, and which rails, assets, consents and disclosures apply in a region? | The [Compliance SDK](https://platformdocs.coinme.com/docs/coinme-compliance-sdk.md): its [JavaScript & React guide](https://platformdocs.coinme.com/docs/compliance-sdk-react.md) covers region status, the rule helpers, consents and disclosures, localized copy and attestations, with an end-to-end walkthrough. It is in beta and advisory. For a React Native app, its [React Native guide](https://platformdocs.coinme.com/docs/compliance-sdk-react-native.md) covers the same SDK, also in beta. |
| How do I check a wallet address before sending, or before passing it to the widget? | The [wallet address validator](https://platformdocs.coinme.com/docs/wallet-address-validator.md) on either surface: `validateAddress` with `strict: true` and the asset's `chainType`, trimmed input, and the three outcomes (valid, invalid, unsupported) handled apart. [Supported assets and chains](https://platformdocs.coinme.com/docs/wallet-address-validator-supported-assets.md) lists every asset and chain it can validate; its skill is [coinme-wallet-address-validator](https://platformdocs.coinme.com/skills/coinme-wallet-address-validator/SKILL.md). |
| What does a Ramp contain, and how is a new one stood up? | [The Orchestrator explainer](https://platformdocs.coinme.com/pages/explainers/orchestrator.md). |
| Which credentials do I need from Coinme, and how do I get them? | The integrator reference for your surface: [Widget / Ramp](https://platformdocs.coinme.com/agents/ramp-reference.md) or [CaaS](https://platformdocs.coinme.com/agents/caas-reference.md). |
| Which environments and hosts are there, and what do I set for each? | The integrator reference: [Widget / Ramp](https://platformdocs.coinme.com/agents/ramp-reference.md#environments) or [CaaS](https://platformdocs.coinme.com/agents/caas-reference.md#environments). |
| Which version of an SDK is current, and is it released yet? | [SDK versions](https://platformdocs.coinme.com/pages/build/versions.md) lists every SDK's current release, generally available or beta (published, fine for development builds, not generally available), and the SDKs still in development; [versions.json](https://platformdocs.coinme.com/versions.json) has the same list as JSON. Each skill's front matter, and each page's, carries the same version and a `status: "beta"` where it applies. |
| Which platform and framework versions are supported? | The integrator reference: [Widget / Ramp](https://platformdocs.coinme.com/agents/ramp-reference.md#platform-requirements) or [CaaS](https://platformdocs.coinme.com/agents/caas-reference.md#platform-requirements). |
| What must change before going live? | The go-live checklists: [Widget / Ramp](https://platformdocs.coinme.com/agents/ramp-reference.md#go-live-checklists) or [CaaS](https://platformdocs.coinme.com/agents/caas-reference.md#go-live-checklists). |
| How do I create a verified test customer in the stage Widget, and which test identities can I use? | [Creating Widget test accounts in stage](https://platformdocs.coinme.com/docs/widget-test-accounts.md) and [Test identities for Coinme KYC](https://platformdocs.coinme.com/docs/widget-test-identities.md); [Expected behavior in stage](https://platformdocs.coinme.com/docs/widget-stage-behavior.md) covers failed verification, test cards, cash locations and testnet use. The identities are fake and work wherever Coinme performs identity verification (KYC): in the Widget and in Coinme onboarding for CaaS partners (the Onboarding SDK's sandbox environment and the onboarding API). |
| My web embed is deployed but does not load | [Doctor](https://platformdocs.coinme.com/pages/build/web/doctor.md) and the allowlist callout in [How to use (web)](https://platformdocs.coinme.com/pages/build/web/how-to-use.md). |
| How does my backend get the token the Vault, Onboarding or Compliance SDK sends? | [Transient Auth Token](https://platformdocs.coinme.com/docs/transient-auth-token.md): exchange the API client ID and secret for a partner access token, then mint a 10-minute token per customer or sign-up session, with the scope of the call (`payment-methods`, `onboarding` or `attestations`, the last not available in the Compliance SDK beta at this time). Never pass the partner access token to the SDK; the `Authorization` header carries only the Transient Auth Token from `POST /services/browserAuth`. |
| How does my backend link an onboarded customer to its own sign-up session? | [Example: linking onboarding to your backend session](https://platformdocs.coinme.com/docs/onboarding-sdk-session-example.md), a complete example of the two backend routes and the checks; the concepts are in the [Onboarding SDK guide](https://platformdocs.coinme.com/docs/onboarding-sdk-react.md#how-do-i-associate-an-onboarding-with-my-own-backend-session). |
| Is there a REST API? How do I call CaaS from my backend? | [CaaS API clients](https://platformdocs.coinme.com/docs/caas-api-clients.md) for Node.js, one reference page per package, all in [llms-api.txt](https://platformdocs.coinme.com/llms-api.txt); the API reference itself is on docs.coinme.com, linked from that page. |
| Pricing, supported assets or states, webhooks, support, release notes? | Not covered on this site: see [what is not covered](https://platformdocs.coinme.com/agents/primer.md#not-covered) and ask your Coinme integration contact. |
| Is this a real transaction? Can I use it from my country? | [The FAQ](https://platformdocs.coinme.com/pages/explainers/faq.md). |
