# Payments

Source: /docs/features/payments

Accept payments from your app's end users with Stripe. OrbitOrca runs Stripe for you: your app never holds Stripe keys and never handles webhooks — it just asks the platform whether a customer has paid. Payments are available on every plan, including Free.

## Enable [#enable]

Open the app's **Payments** tab and enable payments. This binds the app to a **Stripe Connect account** — either reuse an account you have already connected, or create a new one. For a new account you choose a business country, and **that country cannot be changed later**.

* One app connects to **one** Stripe account. Apps that share an account share the same catalog.
* Payments can only be turned **off before your first deploy** — after that, they stay on.
* Enabling does not let you charge yet: a new account must finish Stripe verification first (see below).

## Configure [#configure]

**Finish Stripe onboarding.** Complete Stripe's identity verification. The dashboard's account health moves from **Onboarding** to **Active** and flags anything Stripe still needs. You cannot charge customers until the account is **Active**.

**Build your catalog.** Create **Products** and **Prices**:

* A product has a **kind** — one-time or subscription — and a **key**. Both are fixed once the product is created.
* A price is an amount and currency (plus a billing interval for subscriptions).
* **Editing a price changes only the amount.** New buyers pay the new amount right away; existing subscribers move to it on their next billing cycle. Nothing is deleted — the old price is archived, and your app keeps working with no redeploy.

Refunds, transactions, payouts, and tax documents are managed in **Stripe**, not the OrbitOrca dashboard.

## Wire [#wire]

Your app asks the platform whether a customer has paid and sends them to checkout — it never talks to Stripe directly, and the paid state lives on the platform, not in your app.

You don't write this by hand. The **Payments** tab gives you a **wiring prompt** to paste into your coding agent, which edits your code to add checkout and the paywall. A [connected agent](/docs/mcp/overview) can pull the same prompt itself with the `generate_feature_prompt` tool — it includes a live snapshot of your catalog. After wiring, **deploy** to pick it up.

## Through a connected agent [#through-a-connected-agent]

An agent connected over [MCP](/docs/mcp/overview) can enable payments, create products and prices, and pull the wiring prompt for you. It **cannot** create or verify your Stripe account — do that yourself first, then let the agent handle the rest. See the [tool reference](/docs/mcp/tools) for what a write token can do.