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 Starter.

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.
• Enabling does not let you charge yet: a new account must finish Stripe verification first (see below).

Turn off and on

You can turn payments off at any time. Turning them off unbinds the app from the Stripe account and nothing else: your Stripe account, its products, prices and sales history stay as they are, and you can enable payments again later, with the same account or another one. A version of the app that is already running stops being able to charge right away and loses its payment keys on the next deploy. One thing to know: an account you never started and no app uses is removed after 30 days (see Your Stripe accounts). The general rule for every feature is in the overview.

Test before you charge anyone

Payments can run in test mode: checkout opens Stripe's test checkout, only Stripe's test cards work (4242 4242 4242 4242, any future date, any CVC), nobody is charged, and every page of your app shows a Test payments bar. The test account is ready about a minute after you turn it on, with no forms to fill in; your catalog is the same as in live mode, so what you test is what you will sell.

• Start in test mode when you enable payments, or switch an app to it later from the Payments tab. An app that already has real customers cannot go back to test mode, because test mode would take away access from people who paid real money; test on a copy of the app instead.
• Switch to live payments when you are ready. Test purchases do not carry over: people who paid with a test card lose access the moment you switch, and real cards start to work. The app restarts for a few seconds so the bar goes away. Stripe asks for your business details before the first real sale.
• A connected agent can make a test purchase for you (simulate_test_purchase) and check that your paywall opens, without a browser.

Your Stripe accounts

Stripe accounts belong to you, not to any one app, so one account can serve several apps. Open Payment accounts in the dashboard to see them all, finish verification, and manage payouts and documents.

• An account you never started is reused before a new one is created. When you ask for a new account and you already have one in the same country where you never submitted your details to Stripe and that serves no app, that account is handed back to you instead of creating another.
• An account you never started and no app uses is removed after 30 days. If you never submitted your details to Stripe for an account, and no app has been connected to it for 30 days, the platform removes it. The dashboard shows the removal date next to the account; submitting your details or connecting an app to it cancels the removal. An account you submitted details for is never removed, whether or not an app uses it.

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

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 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

An agent connected over MCP can enable payments (in test or live mode), switch between the two, create products and prices, make a test purchase, 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 for what a write token can do.