Say what you sell. Get a link that takes money.
Your agent stands up a real Stripe account in your business's name, creates the product, the price and the checkout link, and then answers questions about your money. You own the account. We take 0% of your revenue today, because we are not in the fee path at all.
mode: subscription — picked from the price, not by you
Week two was supposed to be launch week.
You built the thing. Then payments arrived, and it turned out not to be one job — it was products, prices, a checkout session, a webhook endpoint, signature verification, staging keys, and the small nagging question of whether this user is actually paid.
is a product yet
Those are the two prices the market normally asks: a week of your life, or a slice of everything that comes after. The next section is about why that is a false choice.
Everyone who made this easy did it by becoming the merchant.
We made it easy by designing ourselves out of the money entirely. Your agent does the setup. The account is yours. Nothing we run sits between your customer and your bank.
one of them is ours
That posture is not a policy we describe — it is read back out of Stripe's own response on every account we create, and a mismatch throws posture_mismatch and the account is never handed to you. We take 0% of your revenue today. Stripe bills your account directly at your own Stripe rates. Present tense, deliberately: this is what the code does now, not a forever promise dressed up as one.
Four calls. Real Stripe. No forms.
Not three — four, and here they are by name. Each one is something you say in a sentence, and each one returns a real Stripe object on an account that belongs to you.
before any onboarding
They are two accounts and a switch. which_account tells you which one your calls are pointed at — and it resolves the account from your project, never from an argument you could get wrong. Try the guard:
the account is resolved from the project. It is never an argument, so it can never be the wrong one.
Forty questions become three.
Stripe's own signup has nobody to fill it in for you. A platform does — Accounts v2 lets us submit the business record on your behalf, so the requirements list arrives already answered except for the parts only you can supply.
the residue is 3
Live accounts today are US single-member LLCs. go_live submits country: "US", entity_type: "company", structure: "single_member_llc", and anything else is refused. More entity types and countries are on the way. The sandbox works for anyone — going live does not yet.
Two-tenths of a cent, exactly.
A dollars string goes in; the right Stripe price comes out. Whole dollars, cents, or sub-cent amounts a cents-only price list simply cannot hold.
or usage-metered
exact, aggregate-then-round $0.00
what a cents-only floor forces $0.00
Same usage. The cents-only version overcharges your customer five times over, or you eat the difference — and those are the only two options a price list that stops at one cent gives you.
What is not here: per-seat pricing. There is no seat model, no usage_type: "licensed" handling, and no tool that changes a subscription's quantity after purchase — create_checkout takes a fixed quantity between 1 and 999 and that is the whole of it. If your model is "$10 per user per month and the count changes," this is not the tool for it yet.
"Who owes me money?"
The difference between owning a dashboard and being able to ask a question. Both of these tools are read-only, both run scoped to your account, and neither needs a Stripe login.
real return shapes
| id | customer | dueDate | amountDue |
|---|---|---|---|
| in_1S4bQ… | cus_TQ8kM… | 2026-08-14 | $1,250.00 |
| in_1S4c7… | cus_TR2pV… | 2026-08-18 | $480.00 |
| in_1S4dK… | cus_TS9wB… | 2026-08-29 | $2,000.00 |
| in_1S4eF… | cus_TT4nL… | 2026-09-02 | $450.00 |
| total | $0.00 | ||
Most people find out an invoice went overdue by accident. outstanding takes no arguments at all — it is one sentence to your agent, and it returns every open invoice with id, customer, amountDue, dueDate, a hosted invoice URL, and the total. explain_payment with no arguments gives you the recent list instead of one payment.
Your agent cannot refund. By construction.
Stripe enforces no confirmation of its own, and a call arriving on a public channel resolves as the project owner. So we never gave the agent a refund button — we gave it the ability to ask a human for one.
single use
Other Stripe agent tooling will execute a refund in a single tool call, which is why a lot of teams turn that tool off entirely. Ours cannot execute one, so you can leave it on. An earlier version of this code omitted the amount from the idempotency key and a second partial refund silently did nothing while the row said refunded — we are telling you that because a bug you can read about is worth more than a guarantee you cannot check.
- explain_payment
- outstanding
- which_account
- read the console
- refund_payment
- go_live
- switch_mode
- cancel_subscription
- set_cap
- submit business PII
Stripe's own screens, inside yours.
For the moments that are not a conversation. Three embedded Stripe components, a summary strip, and your full Stripe dashboard one click away — because the account is genuinely yours.
never paywalled
| payment | status | method | created | amount |
|---|---|---|---|---|
| pi_3S4bH… | succeeded | card | 22 Aug 09:14 | $1,250.00 |
| pi_3S4aQ… | succeeded | card | 21 Aug 16:02 | $29.00 |
| pi_3S48V… | disputed | card | 19 Aug 11:47 | $480.00 |
| pi_3S47B… | succeeded | card | 18 Aug 08:30 | $29.00 |
| payout | status | arrival | destination | amount |
|---|---|---|---|---|
| po_1S4d2… | in transit | 25 Aug | ••••4471 | $3,120.00 |
| po_1S3xR… | paid | 18 Aug | ••••4471 | $2,480.00 |
| po_1S3kL… | paid | 11 Aug | ••••4471 | $1,905.00 |
In sandbox mode there is no Stripe dashboard to link to, so the console says so rather than offering a link that bounces. In live mode, Open in Stripe goes straight to dashboard.stripe.com for your account.
Every extra business costs $0.00.
A project is a boundary, not a line item: its own data, its own members, its own spend caps, and its own Stripe account. Add as many as you have businesses — and one for personal.
free, on the one plan
it is an account-level subscription, not a per-project one
A second business here is a second row, not a second subscription — the subscription is account-level, not per project or per workspace. Each project keeps its own sell-side account — live and sandbox are separate rows because they are separate Stripe accounts — and the console's project switcher moves between them without a second login.
Ten sell-side tools, in your Claude.
There is nothing to install and no key to paste. One MCP connection is minted for you at sign-in, and every tool below arrives in whatever assistant you already use.
uncapped and unbilled
the profile decides which tools appear
“Make a $49 one-off called Teardown and give me the link.”
“Who owes me money?”
“Refund $125 of that payment.”
The same connection carries every other Parsons product you have turned on — email, CRM, storage, scheduling, deploys — so "set up a $29 plan, then email the link to the three people on the waiting list" is one conversation rather than three tabs. Tool calls are metered and uncapped, and they are not billed.
Including the three rows we lose.
You have three tabs open, so here is the comparison done for you. Three of these rows go against us, and they are printed in the same weight as the ones that do not.
own published pages
| Decision | Parsons Payments | Merchant-of-record platforms | Stripe direct | Closed-loop POS |
|---|---|---|---|---|
| Whose name is on the account | yours | theirs | yours | theirs |
| Cut of your revenue to the tool | 0% today | 5% + 50¢ standard, +1.5% on international cards — some charge less on a paid tier (as low as ~3.4% + 30¢) | none — there is no tool | none — there is no tool |
| What the tool itself costs | $15/mo flat ($150/yr) — and it carries every other Parsons product too | nothing up front; you pay it as 5% of everything you sell, which passes $15 at $300/mo of sales | nothing — there is no tool | a monthly software fee, varies by vendor |
| Card processing rate | your own Stripe rate, billed to you | bundled into the 5% | your own Stripe rate | their rate |
| Who owns the customer record | you | they do | you | they do |
| Sales tax / VAT filed for you | no | yes — it is the whole point of the model | no | varies by vendor |
| Setup | four tool calls | a signup form | your week | in store |
| An agent can drive it | all of it, 10 tools | no | partially | no |
| An agent can refund unsupervised | no, structurally | n/a | yes, in one tool call | n/a |
| If you stop paying the tool | the account is still yours | subscribers re-enter cards elsewhere | n/a | n/a |
| Countries | US only today | many | many | many |
| Entity types for going live | single-member LLC today | most | most | most |
If you sell to consumers across the EU and would rather not think about VAT, a merchant of record is the right answer and we are not it. You will pay roughly five percent for that at the standard published rate — less on some vendors' paid tiers — and your customers will belong to them. If you would rather own the account and keep the percentage, keep reading.
Printed here, not discovered after you pay.
Every refusal you could run into, written down. A page that prints its own constraints is a page you can check.
says so too
go_live submits country: "US", entity_type: "company", structure: "single_member_llc". Other shapes are refused. The sandbox is open to anyone, anywhere.bad_refund_amount; a payment that has not succeeded is refused with not_refundable. Card money rounds to the cent, so the tool does too.beta and every other Parsons surface shows that pill. It is live, it moves real money, and it is still early.$15 buys the account. Nothing comes off the top.
Monthly or yearly — a year costs exactly two months less than twelve months do. No per-seat price, no enterprise tier, no free tier. Payments is not an upsell: the one plan carries it, and the Revenue console is never behind the paywall.
monthly or yearly
- All 10 sell-side tools — sandbox, catalog, checkout, explain, outstanding, refund ceremony, go-live
- The Revenue console with Payments, Payouts and Account embedded from Stripe
- Unlimited projects, each with its own Stripe account, at $0 per connected account
- MCP tool calls are uncapped and unbilled
The ones people actually ask.
All open. An accordion in a section about money would be a small dishonesty.
behind a click
- Whose Stripe account is it?
- Yours. A full-dashboard Accounts v2 account in your business's name, with
acct_…yours to keep. You can log into Stripe directly and we cannot stop you — that is the point. - What do you take?
- 0% of your revenue today. Direct charges settle on your account and Stripe bills you at your own Stripe rates; we are not in the fee path. Present tense on purpose — we are not going to dress today's fact up as a permanent guarantee.
- What if I stop paying Parsons?
- The Stripe account is yours and stays yours. The Revenue console is one of two consoles exempt from the paywall, so an unpaid account can always reach its own money. We do not hold revenue hostage.
- Can I use it outside the US?
- The sandbox, yes. Going live today is US single-member LLCs —
go_livehardcodes that shape and anything else is refused. - Do you handle sales tax or VAT?
- No. If that is your main problem, a merchant of record is the right tool and we would rather say so here than after you have paid.
- Can the AI refund my customers without asking?
- No. It can only mint a 15-minute, single-use confirmation link. A human opens it and clicks, or nothing happens. Two clicks at once execute exactly once.
- How long does going live take?
- Prefill takes about forty requirements down to three. Stripe then verifies on its own clock and we do not control it — so there is no number here, deliberately.
- What happens to my test products when I go live?
- They copy across — products, prices including sub-cent decimals, and the billing meters metered prices hang on. Your sandbox work is already there at the moment you need it.
- Can I sell one-off products as well as subscriptions?
- Yes.
create_checkoutreads the price and picksmode: subscriptionormode: paymentfor you. - Is this locked behind a higher tier?
- No — there is no higher tier. It works on the one $15/mo subscription. There is no plan check anywhere on the sell side, and the console is never paywalled.
- Is the trial really free? Do I need a card?
- 14 days free, and yes — checkout collects a payment method, because it opens the subscription that starts on day 15. Cancel any time before then. The trial is first-subscription-only: cancelling and resubscribing does not start a second one.
- I run three businesses. Three subscriptions?
- One. Projects are unlimited and free — three separate Stripe accounts with separate data, members and spend caps, on the one $15.
- Is there an annual price?
- Yes. $150/yr — exactly two months free against paying by the month ($180). You pick the interval at checkout, and the 14-day trial is the same either way.
- Can I bring a Stripe account I already have?
- Not today.
go_livecreates a new account rather than adopting an existing one, and sandbox is never promoted into live. - Where does the MCP connection come from?
- It is minted for you at sign-in — one hub connection covering Payments and every other product you have on. There is nothing to install and no key to paste.
Say what you sell. Get a link that takes money.
14-day free trial, then $15/mo — or $150 a year, two months free — covering every Parsons product, on unlimited projects.