Payments
Take payments with Stripe. Test your checkout in a sandbox, connect your live account, sell pricing plans, and handle refunds and cancellations.
Take payments with Stripe. Your agent sets up Stripe for your company, builds and tests your checkout in a sandbox that charges no one, and takes real payments once you connect your live Stripe account.
Check Where Things Stand
Your agent starts with cofounder payments get. It shows whether the
company has a test sandbox, whether you've claimed it, whether a live
account is connected, and how far your app's payment setup has progressed.
Try It in a Test Sandbox
Your agent creates a Stripe test account for the company, for the country your business is in. Nothing in the sandbox charges real cards. To own it, you open a link in your browser and claim it under your own Stripe login. Your agent can give you the link again any time.
Connect Your Live Stripe Account
When you're ready for real payments, your agent gives you a link to approve the Cofounder Stripe App on your existing Stripe account. You don't need a sandbox first. Connecting doesn't turn on payments in your app by itself.
These links point to Cofounder, not Stripe, because Stripe's own claim and dashboard links open only in your signed-in browser. Never paste Stripe keys into chat or command arguments.
Test or Live
Plans are always edited in the test sandbox. Publishing is the only step that copies them to your live account. Customer lookups, revenue, refunds, and cancellations use your live account as soon as one is connected, and the test sandbox until then. Once live, those hit your real Stripe account and real customers.
If a refund or cancellation fails partway, your agent can retry it without Stripe doing it twice, for about 24 hours. After that, it checks whether the first try went through before retrying.
Read Your Revenue
Ask your agent how the business is doing. In one check it reports:
- Monthly recurring revenue per currency.
- Gross, refunded, and net charges over the last 30 days.
- Your Stripe balance (available and pending).
- The five most recent payouts.
To keep watching cheaply, your agent passes the previous answer's
next_since as --since and gets only the charges and refunds since then.
Nothing is skipped or repeated across checks, though items can arrive out of
order. The first check returns the starting point and no new items.
Sell a Pricing Plan
Your agent sets the plans your app shows on its pricing page. A plan has monthly and yearly prices, for example a Pro plan at $29 a month or $290 a year. One-time prices aren't supported yet. Your agent can preview a change before making it, or reuse a price you already have in Stripe.
The app shows active Stripe prices whose lookup keys match
plan_<key>_month or plan_<key>_year. Amounts are in the currency's
smallest unit: 2900 in usd is $29.00.
Removing a plan archives its prices and product. Existing subscribers keep paying.
Check Stripe Reaches Your App
Before you go live, your agent runs cofounder payments setup --method sync in test
mode. It checks your deployed app's Stripe wiring:
- The app has the right test keys.
- The billing section and plans load.
- Stripe's webhook points at the app.
- A test subscription, created directly in Stripe, reaches the app's webhook and is processed.
That proves Stripe's notifications arrive and are accepted. It doesn't test checkout, entitlements, or the billing portal. It always cancels the test subscription and never returns a checkout link.
Go Live With Your Plans
Publishing puts real prices in front of real customers, so your agent does it in two steps. First it previews what would be created, updated, and archived to make live match test. Then it applies exactly those changes. It refuses if test or live plans changed in between. If live already matches test, there's nothing to publish.
Help a Customer
Your agent finds a customer by email or Stripe customer ID and shows their 10 most recent subscriptions and charges (an email can match up to 10 customers, and the result says when more were cut off). It looks the customer up before every refund or cancellation and passes along what it saw. A refund needs the charge's amount, amount already refunded, and currency. A cancellation needs the subscription's status and customer.
- A refund covers everything refundable unless you name an amount.
- A cancellation takes effect at the end of the billing period unless you ask to cancel now.
- Your agent refunds or cancels only when you ask. Once a live account is connected, these act on it and move real money.
Watch for Money Problems
Once you're live, your agent also watches for what costs you money if ignored: disputes needing a response, past-due subscriptions, and failed or paused payouts. It acts on every critical notice. Each notice has a deadline or next step. For a dispute, you get a link to it in Stripe. Your agent can draft evidence but never submits it. You respond in Stripe yourself.
Commands
| MCP | CLI | API |
|---|---|---|
| then | ||
manual_keys returns a link to the dashboard Payments settings page, where
you enter the keys yourself; they never pass through your agent.