Vibe Coding · 课时

添加支付功能

使用 Stripe 和人工智能为您的产品收费。

添加支付功能 是 CoddyKit 上的免费 Vibe Coding 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Vibe Coding 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Vibe Coding 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Getting Paid

A validated product that people love can become a business — the moment you let them pay. Charging money is also the ultimate validation: nothing proves value like a credit card.

The good news: you don't need to be a payments expert. Stripe handles the hard, scary parts (cards, security, taxes), and AI can wire it into your app step by step. In this lesson you'll add payments the vibe-coding way.

Why Stripe

Stripe is the default choice for indie makers. It's developer-friendly, handles cards from around the world, manages security and compliance, and has world-class docs that AI tools know deeply.

You'll work with a few core ideas: Products (what you sell), Prices (how much, one-time or recurring), Checkout (the payment page), and webhooks (Stripe telling your app a payment happened).

You don't memorize these — you ask AI to set them up.

Start with a Payment Link

The absolute fastest way to get paid needs zero code: a Stripe Payment Link. You create a product in the Stripe dashboard, get a URL, and put it behind a button.

This is perfect for an early MVP — validate that people will actually pay before you build real billing into the app.

I want the simplest possible way to charge $9/month for my web app's Pro plan.

- Walk me through creating a Stripe Payment Link in the dashboard (no coding)
- Show me how to add it as an 'Upgrade to Pro' button in my HTML
- Explain what happens after the user pays and how I'd know they paid

Keep it shippable today; I'll add automation later.

One-Time vs Subscription

Decide how you charge before you build. One-time payments suit a single purchase (a template, a course, lifetime access). Subscriptions charge on a recurring schedule (monthly or yearly) — the model behind most SaaS.

Subscriptions give predictable, recurring revenue but add complexity: renewals, cancellations, failed payments. For a first paid product, many makers start with a simple monthly plan plus a discounted yearly option.

Add Stripe Checkout with AI

When you outgrow Payment Links, move to Stripe Checkout: a secure, Stripe-hosted page your app sends users to. Your server creates a "checkout session," and Stripe handles the rest.

Ask AI to scaffold both the backend route and the frontend button. Be specific about your stack so the code fits.

Add Stripe Checkout to my app (Node.js + Express backend, plain JS frontend).

1. A backend route POST /create-checkout-session that creates a subscription Checkout session for my $9/month price.
2. A frontend 'Upgrade' button that calls it and redirects the user to Stripe.
3. Use my Stripe secret key from an environment variable, never hardcoded.
4. Explain each part as you go.

Confirm Payments with Webhooks

How does your app know a payment succeeded? Stripe sends a webhook — an automatic message to your server when events happen (like checkout.session.completed).

This is where you flip a user to "Pro." Here's the shape of handling a webhook event in JavaScript — simplified so you can see the logic AI generates.

function handleStripeEvent(event) {
  if (event.type === 'checkout.session.completed') {
    const userId = event.data.object.client_reference_id;
    upgradeToPro(userId);
    return 'upgraded ' + userId;
  }
  return 'ignored ' + event.type;
}

function upgradeToPro(userId) {
  console.log('User', userId, 'is now Pro');
}

const fakeEvent = {
  type: 'checkout.session.completed',
  data: { object: { client_reference_id: 'user_42' } }
};
console.log(handleStripeEvent(fakeEvent));

Test Mode First, Always

Stripe has a test mode with fake API keys and fake cards (like 4242 4242 4242 4242). Never test with real money on yourself.

Build and verify the entire flow in test mode: checkout, webhook, the upgrade, and cancellation. Only switch to live keys once it all works. Ask AI for the test card numbers and how to trigger test webhooks.

I've added Stripe Checkout. Help me test it safely before going live.

- Confirm I'm using TEST keys, not live keys
- Give me Stripe's test card numbers for success and for a declined card
- Show me how to test that my webhook actually upgrades the user
- Give me a checklist to verify before flipping to live mode

Guard Your Keys

Your Stripe secret key can move real money — treat it like a password. It belongs only on your server, loaded from an environment variable, never in frontend code, never in a Git commit, and never pasted into a public prompt.

The frontend may use the publishable key (safe to expose). If a secret key ever leaks, roll it immediately in the Stripe dashboard. Ask AI to audit your code for accidentally exposed keys.

Gate Pro Features

Once a user is Pro, your app needs to unlock the right things. The pattern: store an isPro flag on the user, then check it before showing premium features or running paid actions.

Always enforce the check on the server too — a frontend-only gate can be bypassed. Ask AI to add the flag and the checks consistently across your app.

After a successful Stripe payment, my webhook sets user.isPro = true.

Now help me gate Pro features:
- Show the pattern for checking isPro before allowing a premium action
- Make sure the check runs on the SERVER, not just hidden in the UI
- Add a friendly 'Upgrade to unlock' message for free users
- Where should I store the isPro flag in my database?

Handle the Messy Cases

Real billing has edges: cards get declined, users cancel, subscriptions lapse, people ask for refunds. A trustworthy product handles these gracefully.

Plan for: failed renewals (downgrade after a grace period), cancellations (keep access until the period ends), and refunds (revoke Pro). Stripe sends webhooks for each. You don't have to handle every case on day one — but ask AI which ones matter most for your model and tackle those first.

Payments, the Indie Way

Your path to getting paid:

1. Start with a no-code Payment Link to validate willingness to pay.
2. Upgrade to Stripe Checkout when ready.
3. Confirm payments with webhooks and flip users to Pro.
4. Test everything in test mode first.
5. Guard your secret key on the server only.
6. Gate features and handle cancellations.

AI writes most of this for you — your job is to understand the flow and keep it secure.

Quick Check

Where should your Stripe secret key live?

Recap: Charge with Confidence

You learned to add payments with Stripe and AI:

Start with a no-code Payment Link to validate demand.
Choose one-time vs subscription pricing.
Use Stripe Checkout and webhooks for the full flow.
Always test in test mode before going live.
Keep your secret key server-side and gate Pro features.
Plan for cancellations, failed payments and refunds.

You can now make money. Final lesson: launching your SaaS to the world.

常见问题解答

「添加支付功能」课时是免费的吗？

是的 — 「添加支付功能」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Vibe Coding 课程的其余内容，请升级到 CoddyKit PRO。 Vibe Coding 课程共包含 4 节课。

「添加支付功能」这节课中我会学到什么？

使用 Stripe 和人工智能为您的产品收费。你通过在浏览器中直接运行的动手代码来练习 Vibe Coding，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Vibe Coding 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Vibe Coding 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「添加支付功能」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Vibe Coding 课中编写并运行代码吗？

能。每节 Vibe Coding 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Vibe Coding