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

Stripe Webhooksの処理

Stripe Webhooksを設定・処理し、決済の成功、失敗、キャンセルなどの非同期イベントに応答します。

レッスン 2/411 ステップ

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

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

What are Webhooks?

Imagine you're waiting for a package. You could constantly call the delivery company (polling) to ask for updates, or they could simply call you (webhook) when the package arrives. Webhooks are automated messages sent by one system to another when a specific event occurs.

They act like a notification system, allowing applications to communicate in real-time about changes or events.

Why Stripe Webhooks?

Payment processing is often asynchronous. This means an action, like a payment, might not complete instantly. It could take time, or even fail, after your user initiates it.

Stripe uses webhooks to notify your application about these crucial asynchronous events. Instead of constantly asking Stripe for updates, Stripe tells your app when a payment succeeds, a subscription renews, a refund is issued, or a failure occurs.

Key Stripe Event Types

Stripe sends different types of webhook events depending on what happened. Each event type has a unique identifier.

  • checkout.session.completed: A customer finished a Stripe Checkout session.
  • invoice.payment_succeeded: A payment for an invoice (often related to subscriptions) was successful.
  • customer.subscription.updated: A subscription changed status (e.g., from active to canceled).
  • payment_intent.succeeded: A payment intent successfully captured funds.

These are just a few; there are many more to cover various scenarios.

Your Webhook Endpoint

To receive Stripe webhooks, your application needs a publicly accessible HTTP endpoint (a URL) that can accept POST requests. This endpoint will be the listener for all incoming Stripe events.

Here's a basic Python Flask example of what such an endpoint might look like:

from flask import Flask, request, jsonify

app = Flask(__name__)

@app.route('/stripe-webhook', methods=['POST'])
def stripe_webhook():
    # Stripe will send event data here
    payload = request.get_data(as_text=True)
    print(f"Received webhook: {payload[:100]}...") # Log first 100 chars
    return jsonify(success=True), 200 # Always respond with 200 OK

if __name__ == '__main__':
    # Run on a port for local testing. In production, use a server like Gunicorn.
    app.run(port=4242, debug=True)

Register with Stripe

Once you have your endpoint, you need to tell Stripe where to send the events. You do this in the Stripe Dashboard.

  • Go to Developers > Webhooks.
  • Click Add endpoint.
  • Enter your public URL (e.g., https://yourdomain.com/stripe-webhook).
  • Select the event types you want to receive.

For local development, you can use the Stripe CLI's stripe listen command to forward events to your local endpoint.

Receiving Event Data

When an event occurs, Stripe sends a JSON payload to your endpoint. This payload contains all the details about the event, including its id, type, and the data object related to the event (e.g., a checkout.session or invoice object).

Your endpoint will read this JSON and decide what to do next based on the type of event.

from flask import Flask, request, jsonify
import json

app = Flask(__name__)

@app.route('/stripe-webhook', methods=['POST'])
def stripe_webhook():
    event = json.loads(request.get_data())
    
    event_id = event['id']
    event_type = event['type']
    
    print(f"Processing event ID: {event_id}, Type: {event_type}")
    
    # In a real application, you'd perform actions here
    # based on the event_type.
    
    return jsonify(success=True), 200

if __name__ == '__main__':
    app.run(port=4242, debug=True)

Verify Webhook Signatures

This is crucial for security! Anyone could send a fake POST request to your webhook URL. To ensure an event genuinely came from Stripe and hasn't been tampered with, you must verify its signature.

Stripe includes a unique signature in the Stripe-Signature header of each webhook request. You'll use your webhook secret (from the Stripe Dashboard) to verify it.

from flask import Flask, request, jsonify
import stripe
import os

app = Flask(__name__)

# IMPORTANT: Use environment variables for secrets!
# For this example, replace with your actual keys:
stripe.api_key = "sk_test_YOUR_STRIPE_SECRET_KEY"
webhook_secret = "whsec_YOUR_WEBHOOK_SECRET" # Get from Stripe Dashboard

@app.route('/stripe-webhook', methods=['POST'])
def stripe_webhook():
    payload = request.get_data()
    sig_header = request.headers.get('stripe-signature')
    event = None

    try:
        event = stripe.Webhook.construct_event(
            payload, sig_header, webhook_secret
        )
    except ValueError as e:
        # Invalid payload
        print(f"Error: Invalid payload - {e}")
        return "Invalid payload", 400
    except stripe.error.SignatureVerificationError as e:
        # Invalid signature
        print(f"Error: Invalid signature - {e}")
        return "Invalid signature", 400

    # If we reach here, the event is verified and safe to process
    print(f"Verified event type: {event['type']}")
    return jsonify(success=True), 200

if __name__ == '__main__':
    app.run(port=4242, debug=True)

Processing Specific Events

Once an event is verified, your application can then process it based on its type. This typically involves updating your database, sending emails, or triggering other business logic.

It's common to use a switch statement or if/elif chain to handle different event types.

from flask import Flask, request, jsonify
import stripe
import os

app = Flask(__name__)

stripe.api_key = "sk_test_YOUR_STRIPE_SECRET_KEY"
webhook_secret = "whsec_YOUR_WEBHOOK_SECRET"

@app.route('/stripe-webhook', methods=['POST'])
def stripe_webhook():
    payload = request.get_data()
    sig_header = request.headers.get('stripe-signature')
    event = None

    try:
        event = stripe.Webhook.construct_event(payload, sig_header, webhook_secret)
    except Exception as e:
        return str(e), 400

    # Handle the event based on its type
    if event['type'] == 'checkout.session.completed':
        session = event['data']['object']
        print(f"Checkout Session Completed: {session['id']}")
        # TODO: Fulfill purchase, grant user access
    elif event['type'] == 'invoice.payment_succeeded':
        invoice = event['data']['object']
        print(f"Invoice Payment Succeeded: {invoice['id']}")
        # TODO: Update user's subscription status, send receipt
    elif event['type'] == 'customer.subscription.deleted':
        subscription = event['data']['object']
        print(f"Subscription Deleted: {subscription['id']}")
        # TODO: Revoke user access
    else:
        print(f"Unhandled event type: {event['type']}")

    return jsonify(success=True), 200

if __name__ == '__main__':
    app.run(port=4242, debug=True)

Webhook Best Practices

  • Respond Quickly: Stripe expects a 200 OK response within a few seconds. If processing is heavy, do it asynchronously (e.g., send to a queue).
  • Idempotency: Design your event handlers to be idempotent. Stripe might send the same event multiple times, so ensure processing an event twice doesn't cause issues.
  • Error Handling: Implement robust logging and error handling. If your endpoint returns an error, Stripe will retry sending the event.
  • Security: Always use HTTPS for your webhook endpoint.

Webhook Security Check

When setting up a Stripe webhook endpoint, which of the following is the most critical security measure to implement?

対話的なレッスンで答える

Recap: Handling Webhooks

In this lesson, we explored how to handle Stripe webhooks. You learned that webhooks are essential for reacting to asynchronous payment events in real-time.

  • You create a dedicated endpoint in your application.
  • You register this endpoint in the Stripe Dashboard.
  • Crucially, you verify the webhook signature to ensure authenticity and integrity.
  • Finally, you process different event types to keep your application's state synchronized with Stripe's, fulfilling orders, updating subscriptions, and more.
無料で開始

AI チューターと学ぶ AI Powered SaaS: Stripe + Auth + Billing + Deploy — 無料

ブラウザでリアルコードを書いて実行し、24/7 の AI チューターから瞬時にサポートを受け、ウェブまたはアプリで続きから学習できます。

コース
12
レッスン
48
無料で学習を始めるコース全体を表示

よくある質問

「Stripe Webhooksの処理」レッスンは無料ですか？

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

「Stripe Webhooksの処理」で何を学びますか？

Stripe Webhooksを設定・処理し、決済の成功、失敗、キャンセルなどの非同期イベントに応答します。 ブラウザで直接実行するハンズオンコードでAI Powered SaaS: Stripe + Auth + Billing + Deployを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

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

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

「Stripe Webhooksの処理」レッスンにはどのくらい時間がかかりますか？

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

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

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

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

  1. サブスクリプション管理
  2. Stripe Webhooksの処理
  3. カスタマーポータルと請求履歴
  4. 従量課金と使用量ベースの価格設定
← AI Powered SaaS: Stripe + Auth + Billing + Deployに戻る