Platform
Payments: a Stripe-powered block for real revenue
Checkout, subscriptions and receipts land in your app as real code — with a test mode to rehearse in and a live mode for when you are ready to charge.
The Ciao Payments block adds Stripe-powered payments to an AI-built application: checkout, subscriptions, receipts, and separate test and live modes. Unlike embedded payment widgets on closed platforms, the block installs as real code in your application, connected to your own Stripe account — revenue flows to you, and the integration is yours to inspect, extend and export.
Published 2026-07-03 · Last updated 2026-07-03
Money is where prototypes stop being enough
The gap between an app and a business is a working checkout. It is also where tolerance for bugs drops to zero: double charges, missing receipts and broken subscription states cost trust that a young product cannot spare. Payments code is exactly the plumbing founders should not hand-roll and agencies should not rebuild for every client.
The Payments block adds Stripe-powered payments to a Ciao application in one click: checkout, subscriptions and receipts, with separate test and live modes. It connects to your own Stripe account and installs as real code in your app — inspectable, extendable and yours.
What the block includes
The block covers the revenue plumbing every paid product needs.
Checkout
A Stripe-powered purchase flow wired into your application, handling the part of the transaction you never want to improvise.
Subscriptions
Plans, trials, upgrades and cancellations built on Stripe's subscription model, driven by rules you describe in plain language.
Receipts
Customers get receipts for their charges without anyone building an email pipeline first.
Test and live modes
Rehearse every flow with Stripe test cards before a real card is ever charged; flip to live deliberately, after the gates pass.
From no revenue to first charge
The path from installing the block to charging a real card is deliberately gated.
1. Add the Payments block
One click generates checkout flows, subscription handling and receipts into your codebase, on a branch like any other change.
2. Connect your Stripe account
Your account, your customers, your payouts. Ciao wires the integration; the commercial relationship is between you and Stripe.
3. Describe what you sell
Products, prices and plans in plain language — one-time purchases, monthly tiers, trials — and the flows are built to match.
4. Rehearse in test mode
Run the full journey with Stripe test cards. QA captures the purchase flow as a deterministic replay, so it stays protected from then on.
5. Pass the gates and go live
Smoke gates and the safe-to-publish dashboard apply as usual. When everything is green, flip from test to live and take the first real payment.
6. Keep iterating safely
Pricing changes and new plans are changes to a protected area — Guardrails can require senior review for anything touching payment flows.
Why it matters
Payments as a governed capability changes the risk profile of shipping revenue features. The checkout is covered by deterministic QA replays, access-control probes exercise the boundaries around billing data, and every change near money can require recorded review. That is a different foundation than a widget dropped into a page.
And because it is real code in your application, edge cases stay reachable: a custom upgrade path, seat-based logic, the receipt wording your finance team asks for. You extend code you own instead of negotiating with a plugin.
There is a reason payments is often the first block a team reaches for: it is the clearest test of whether an AI-built application is a real product. A checkout that passes deterministic replays, a subscription flow with recorded review behind it, receipts that arrive without anyone remembering to send them — that is what production-ready means when money is involved.
Who uses the Payments block
- Founders — The first paid version of the product ships with checkout already rehearsed in test mode.
- Agencies — Paid client products stop requiring a bespoke billing build per engagement — the block installs, the client's Stripe account connects.
- SaaS teams — Subscription logic with governed change control, so pricing experiments never bypass review.
- Internal and operations teams — Paid bookings, registrations and orders inside otherwise internal tools, with receipts handled.
Security and governance notes
- ✓ Runs on your own Stripe account — funds settle to you.
- ✓ Card details are handled by Stripe's checkout, not stored in your application's database.
- ✓ Test and live modes are separate; every flow can be rehearsed before a real charge.
- ✓ QA replays cover purchase journeys; smoke gates run before every publish.
- ✓ Guardrails can require senior review for changes to payment flows.
- ✓ Changes near billing land in the append-only audit trail.
Test mode vs live mode
The two modes exist so that nothing about your first real charge is a surprise.
| Test mode | Live mode | |
|---|---|---|
| Cards | Stripe test cards | Real customer cards |
| Money | No funds move | Charges settle to your Stripe account |
| Purpose | Rehearse flows and run QA replays | Serve customers |
| Switching | The default for new payment features | Flipped deliberately, after gates pass |
Frequently asked questions
Do I need my own Stripe account?
Yes — the block connects to your Stripe account, so the customers, the payments and the payouts are yours. Ciao generates and maintains the integration code inside your application.
Can I customize checkout and billing logic?
Yes. The block is real code in your app, so you can change it the way you change anything else — describe the adjustment in Builder, or point at the checkout page with inspect-to-prompt. Changes to payment flows go through the same gates as everything.
How do subscriptions handle upgrades and cancellations?
They are built on Stripe's subscription model, with your policy described in plain language — prorate upgrades, cancel at period end, offer a trial. The resulting flows are captured as QA replays so they keep working as the app evolves.
Is it safe to experiment with payment features?
That is what the structure is for: changes happen on branches, test mode means no real charges, smoke gates run before any publish, and Guardrails can require senior review for payment-flow changes. Experimentation happens; surprises in production do not have to.
What does the Payments block cost?
The block is part of the platform; Stripe's own processing fees are between you and Stripe. Individual builders start self-serve with credits, and serious production programs start at USD 10,000 per year — see the pricing page.