AI Powered SaaS: Stripe + Auth + Billing + Deploy · レッスン

カスタマーポータルと請求履歴

Stripe Customer Portalを統合し、ユーザーがサブスクリプションを管理したり、請求履歴を直接確認したりできるようにします。

「カスタマーポータルと請求履歴」はCoddyKit上の無料AI Powered SaaS: Stripe + Auth + Billing + Deployレッスンです。これはレッスン3/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはAI Powered SaaS: Stripe + Auth + Billing + Deploy学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 AI Powered SaaS: Stripe + Auth + Billing + Deployコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Meet the Stripe Customer Portal

Welcome! In this lesson, we'll integrate the Stripe Customer Portal. This powerful tool empowers your users to manage their own billing information and subscriptions directly.

Think of it as a self-service hub for their payment details.

Empowering Your Users

The Customer Portal provides a secure, Stripe-hosted page where your users can:

Update payment methods: Change credit cards or add new ones.
Change subscription plans: Upgrade, downgrade, or cancel their subscription.
View billing history: Access past invoices and receipts.
Update billing information: Change their address or tax IDs.

This reduces support requests and improves user experience.

Quick Setup in Stripe Dashboard

Before writing code, you enable and configure the Customer Portal in your Stripe Dashboard. Go to Settings > Customer Portal.

Customize your branding (logo, colors).
Choose which actions users can perform (e.g., allow plan changes, cancel subscriptions).
Set a return URL for when users finish.

These settings define the user experience.

Creating a Portal Session

To send a user to the Customer Portal, your backend needs to create a Portal Session with Stripe. This generates a unique, temporary URL for that specific customer.

The process is:

User clicks a 'Manage Billing' button in your app.
Your frontend calls your backend API.
Your backend calls the Stripe API to create a billing_portal.Session.
Stripe returns a URL, which your backend sends to your frontend.
Your frontend redirects the user to that URL.

Backend: Generate Portal Link

Here's how your backend might create a Stripe Customer Portal session. Remember to replace YOUR_SECRET_KEY and customerId with actual values.

This example uses Java, but the logic is similar for other languages.

import com.stripe.Stripe;
import com.stripe.exception.StripeException;
import com.stripe.model.billingportal.Session;
import com.stripe.param.billingportal.SessionCreateParams;

public class Main {
  public static void main(String[] args) {
    // Set your secret key. Use your test key during development.
    Stripe.apiKey = "sk_test_YOUR_SECRET_KEY";

    // This customer ID should come from your database
    // associated with the logged-in user.
    String customerId = "cus_N5fK1ZlW2X3Y4Z"; // Example ID
    String returnUrl = "https://your-app.com/settings/billing";

    try {
      SessionCreateParams params =
          SessionCreateParams.builder()
              .setCustomer(customerId)
              .setReturnUrl(returnUrl)
              .build();

      Session portalSession = Session.create(params);

      System.out.println("Customer Portal URL: " + portalSession.getUrl());
    } catch (StripeException e) {
      System.err.println("Error creating portal session: " + e.getMessage());
    }
  }
}

Frontend: Directing Users

Once your backend provides the Customer Portal URL, your frontend simply redirects the user's browser to that link. This snippet shows a basic HTML button and JavaScript to handle the redirection.

In a real app, /api/create-portal-session would be your backend endpoint.

<!DOCTYPE html>
<html>
<head>
    <title>Billing Portal</title>
</head>
<body>
    <h1>My SaaS Dashboard</h1>
    <p>Click below to manage your subscription.</p>
    <button id="manageBilling">Manage My Billing</button>

    <script>
        document.getElementById('manageBilling').addEventListener('click', async () => {
            try {
                // Call your backend to get the portal URL
                const response = await fetch('/api/create-portal-session', {
                    method: 'POST',
                    headers: { 'Content-Type': 'application/json' }
                    // You might send a user ID or token here
                });
                const data = await response.json();
                
                if (data.url) {
                    window.location.href = data.url; // Redirect!
                } else {
                    alert('Failed to get portal URL.');
                }
            } catch (error) {
                console.error('Error opening portal:', error);
                alert('Error connecting to billing portal.');
            }
        });
    </script>
</body>
</html>

Tailoring the User Portal

The SessionCreateParams used in the backend call offers customization options:

setReturnUrl(): The URL Stripe redirects the user to after they finish in the portal. Make sure it's a valid URL in your app.
setConfiguration(): For advanced control over what features are available in the portal, overriding dashboard settings.

Carefully configure these to match your application's flow.

Listening for Portal Changes

When users make changes in the Customer Portal (e.g., update their plan, change payment method), Stripe emits webhooks.

You can listen for events like customer.subscription.updated or customer.source.updated to keep your application's database in sync. This was covered in the previous lesson!

Ensure your webhook handler can process these events to reflect changes in your app.

Testing Your Portal

Always test your Customer Portal integration thoroughly:

Use Stripe's test mode API keys and test customer IDs.
Simulate various user actions: updating cards, changing plans, viewing invoices.
Verify that your application correctly redirects to and from the portal.
Check that webhooks are received and processed correctly after portal actions.

This ensures a smooth experience for your users.

Portal Link Logic

You want to provide a 'Manage Billing' button in your SaaS application. When a user clicks it, what is the correct flow to open the Stripe Customer Portal?

Recap: Self-Service Success

Great job! You've learned how to integrate the Stripe Customer Portal.

It empowers users to manage their billing and subscriptions.
You create a session URL from your backend via the Stripe API.
Your frontend redirects users to this secure, Stripe-hosted page.
Webhooks keep your app updated on portal changes.

This integration significantly enhances user experience and reduces your support overhead.

よくある質問

「カスタマーポータルと請求履歴」レッスンは無料ですか？

はい。「カスタマーポータルと請求履歴」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、AI Powered SaaS: Stripe + Auth + Billing + Deployコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 AI Powered SaaS: Stripe + Auth + Billing + Deployコースには全4レッスンが含まれています。

「カスタマーポータルと請求履歴」で何を学びますか？

Stripe Customer Portalを統合し、ユーザーがサブスクリプションを管理したり、請求履歴を直接確認したりできるようにします。ブラウザで直接実行するハンズオンコードでAI Powered SaaS: Stripe + Auth + Billing + Deployを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

AI Powered SaaS: Stripe + Auth + Billing + Deployを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのAI Powered SaaS: Stripe + Auth + Billing + Deployは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン3/4です。

「カスタマーポータルと請求履歴」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このAI Powered SaaS: Stripe + Auth + Billing + Deployレッスンでコードを書いて実行できますか？

はい。すべてのAI Powered SaaS: Stripe + Auth + Billing + Deployレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← AI Powered SaaS: Stripe + Auth + Billing + Deployに戻る