Add Stripe Payments to an AI-Built App (One Connector)

To add Stripe payments to an AI-built app, connect the Stripe connector in Zugo: paste your publishable and secret keys, describe what to charge for, and the builder wires checkout into the generated app. You test with Stripe's test keys first, then switch to live keys when you're ready to take real payments.

That is the whole loop. No payment SDK to read, no server code to write by hand. The rest of this post covers what you need before you start, the exact steps, what the generated app can and cannot charge for, and — honestly — the parts of running a paid product that no AI app builder handles for you.

What does the Stripe connector actually do?

Zugo is an AI builder: you describe an idea in plain language and it assembles a working app, landing site, 2D game, or multi-page platform with a database, auth, and payments. Simple builds arrive in about a minute; a complex platform takes a few minutes. Stripe is one of the built-in connectors, alongside Supabase for database and auth, Google Analytics, Resend for email, and Vercel for deploying to your own account.

When Stripe is connected, the code Zugo generates can create real checkout flows: a pricing page whose buttons open Stripe Checkout, a paywall in front of premium content, a "buy now" button on a product page. The payment itself runs on Stripe's hosted checkout, which means card data never touches your generated app. Money goes to your Stripe account, not to Zugo. Zugo never sits between you and your revenue.

Every build is verified in a sandbox — "verified" means the app actually loaded and rendered in front of you, not that someone eyeballed the code. For deeper multi-page builds you also get checkpoints and a live process log, so you can watch the payment pages come together instead of waiting on a spinner.

What do you need before you start?

Three things, and only one of them takes real time:

1. A Stripe account. Free to create at stripe.com. Stripe will ask for business details before it lets you accept live payments, and that verification is between you and Stripe.
2. Your API keys. In the Stripe dashboard under Developers → API keys you get two pairs: test keys (they start with pk_test_ and sk_test_) and live keys (pk_live_ and sk_live_). Start with test keys. Always.
3. A clear idea of what you're selling. One-time purchase or subscription? One price or three tiers? The more specific your prompt, the fewer follow-up edits you'll make.

On the Zugo side you need nothing but an account — free starter credits, no card required. If you have never built with an AI builder before, how to build an app with AI walks through the general workflow; this post assumes payments are the goal.

How do you add Stripe payments, step by step?

A concrete example. Say you type:

"Build a landing page for my resume-review service. One offer: a $49 one-time review. Add a checkout button that charges through Stripe and a thank-you page after payment."

Zugo assembles the page, and once your keys are in the connector, the button opens a real Stripe Checkout session for your $49 product. Change your mind about the price or want to add a $99 rush option? Say so in the chat — it's an edit, not a rebuild. If you want to plan the structure before generating anything, Plan mode lets you review the build plan first.

What can the generated app charge for?

Anything Stripe Checkout supports, in practice:

• One-time payments — digital products, services, bookings, event tickets, a "pay what's owed" invoice page.
• Subscriptions — monthly or yearly tiers, the standard SaaS pricing-page pattern.
• Gated content — combine Stripe with the Supabase connector (or Zugo Cloud, the built-in database) and the app can check who paid before showing premium pages.

The pattern matters more than the niche. A paid newsletter signup, a booking deposit for a photography studio, a $5 tip jar on a game you built — the checkout mechanics are identical. Zugo ships 25 templates across 5 categories if you'd rather start from a working layout than a blank prompt, and the showcase has live examples of what people have published.

Test mode vs live mode: what's the difference?

Stripe keeps two parallel worlds. Test mode uses pk_test_/sk_test_ keys and fake cards; no money moves, ever. Live mode uses pk_live_/sk_live_ keys and charges real cards. The generated code doesn't change between the two — only the keys in the connector do.

The safe workflow: build and iterate entirely on test keys, run through the full purchase with the test card, check that the success page and any post-payment logic behave, and only then paste live keys. If something is broken, you find out with a fake card instead of a customer's real one.

What does Zugo not handle?

This part matters, because "AI app builder with Stripe" can sound like it makes you a finished business. It doesn't. Zugo builds the software; the commerce around it is yours:

• Taxes. Sales tax, VAT, GST — collecting and remitting them is your responsibility. Stripe has a Tax product you can enable in your Stripe dashboard, but configuring it, registering where you owe tax, and filing returns is on you.
• Refund policy and disputes. Zugo doesn't write your refund terms, and chargebacks are handled between you and Stripe. Issue refunds from the Stripe dashboard.
• Stripe account approval. Stripe decides what businesses it supports and verifies your identity. Zugo can't speed that up or route around it.
• Payout timing. When money lands in your bank account is a Stripe setting, not a Zugo one.
• Legal pages. Terms of service and privacy policy for a paid product need real review, not just generated placeholder text.

None of this is unusual — it's true of any stack, hand-coded or generated. The difference is that with Zugo the software part collapses from weeks to minutes, so the checklist above becomes the actual work.

What happens after checkout works?

Publishing is one click to your-slug.zugo.run. Free publishes carry a "Made with Zugo" badge; paid plans unlock custom domains, so the checkout lives at your own address — which is where you want it once real money is involved.

You're also not locked in. Zugo exports to GitHub as a real repository — src/, package.json, vite.config — so the payment code is yours to read, audit, or hand to a developer later. Details in exporting an AI app to GitHub.

Cost to build: the free tier's starter credits are enough to try the full loop with test keys. Pro is $25/month — 200 credits, roughly 16 full platforms or 33 quick builds, plus custom domains. Business is $99/month. So the realistic path is: prototype the paid app free, verify checkout in test mode, and upgrade when you're ready to put it on your own domain and flip the keys to live.