BoltBolt ships full-stack apps from a prompt. The missing piece is always the same: a merchant account that doesn't take a week. That's the piece we removed.
In Bolt, the agent reads paas.build/agents and calls our API directly — no setup. When you continue in an MCP client (Cursor, Windsurf, Claude Code, Cline, VS Code), point it at our server to get identify_business, go_live and create_checkout.
Registry name: io.github.UNIPaaS/paas-build-mcp. Full per-client configs are on the docs page.
Bolt’s Stripe path runs through Supabase edge functions — the prototype is instant, the payment plumbing isn’t.
with paas.build: Checkout is one component + one API call — the backend is ours, not yours.
Builders report the frontend flies, then backend + database + deploy for payments eats the rest of the day.
with paas.build: One prompt → account + checkout mounted in the same session.
Flipping to live still means account activation and business verification at your PSP — days, not minutes.
with paas.build: A real capped account the same day; verification completes in the background.
Paste the prompt below in Bolt. It reads our agent docs and adds the payment flow — component, API call, success page.
At paas.build, click Open my account, tell us who you are (or paste your site) — a real account, sandbox + production, is created in the same session.
Set the two env vars from your welcome email. Test with our sandbox cards, flip the toggle to production, and you're selling.
Individuals: the same session — a capped, real account (≈£1,500) until verification finishes in the background. No week-long review.
3.9% flat per transaction. Compare: Paddle is 5% + $0.50 — roughly 41% more expensive on a $30 sale.
Yes — the checkout is a drop-in component (or a hosted link). Works in any Node/React app Bolt produces.