Stripe Payments & SaaS Billing Systems · レッスン

従量課金システムの実装

サービスやリソースの利用量に応じて顧客に課金する従量課金を設計・統合します。

「従量課金システムの実装」はCoddyKit上の無料Stripe Payments & SaaS Billing Systemsレッスンです。これはレッスン1/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはStripe Payments & SaaS Billing Systems学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Stripe Payments & SaaS Billing Systemsコースには全4レッスンが含まれています。

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

What is Usage-Based Billing?

Usage-based billing, also known as metered billing, charges customers based on how much they use a product or service.

Instead of a fixed monthly fee, customers pay only for their actual consumption. This model is popular for services like cloud storage, API calls, or data processing.

It offers flexibility and fairness, aligning costs directly with value received.

Core Concepts: Meters & Events

At the heart of usage-based billing are meters and events.

Meter: This is the specific resource or action you track. Examples include "API calls," "GB stored," or "minutes used."
Event: A single occurrence that increments your meter. Every time a user makes an API call, stores a file, or uses a minute, an "event" happens.

Your system needs to record and report these events.

Designing Your Usage Meter

When designing your usage-based system, first decide what to meter. What defines "usage" for your service?

Example: For a cloud storage service, your meter could be "gigabytes stored."
Granularity: How often do you report usage? Instantly? Hourly? Daily? Stripe typically aggregates usage over a billing cycle.

Clearly defining your meter ensures accurate billing.

Stripe's Metered Billing

Stripe supports usage-based billing through metered prices.

You define a product (e.g., "API Access") and then a price that specifies a cost "per unit" (e.g., $0.01 per API call). Instead of setting a fixed quantity for a subscription item, you report usage records to Stripe.

Stripe then aggregates these usage records over the billing period and charges the customer accordingly.

Product & Price Setup (Conceptual)

To set up usage-based billing in Stripe, you'd typically:

Create a Product: This represents the service itself (e.g., "Cloud Storage").
Create a Price: Link this price to your product. Crucially, set its recurring.usage_type to 'metered' and specify the unit_amount (cost per unit) or tiers for graduated pricing.

This tells Stripe that the price is based on reported usage.

Reporting Usage via API

Once your customer is subscribed to a metered price, you'll need to report their usage to Stripe using the API.

You'll send a Usage Record for a specific Subscription Item, indicating the quantity used. Stripe then adds this quantity to the customer's current billing cycle total.

This is usually done server-side from your application as usage events occur.

Code: Reporting Usage

Here's a simplified Java example showing how you might report usage to Stripe. You'd replace placeholders with your actual keys and IDs.

This example reports '10' units of usage for a specific subscription item.

import com.stripe.Stripe;
import com.stripe.exception.StripeException;
import com.stripe.model.UsageRecord;
import com.stripe.param.UsageRecordCreateParams;

public class Main {
  public static void main(String[] args) {
    Stripe.apiKey = "sk_test_YOUR_SECRET_KEY"; // Replace with your secret key

    String subscriptionItemId = "si_YOUR_SUBSCRIPTION_ITEM_ID"; // Get this from your subscription
    Long quantityToReport = 10L; // The amount of usage to report

    try {
      UsageRecordCreateParams params = UsageRecordCreateParams.builder()
        .setQuantity(quantityToReport)
        .setTimestamp(System.currentTimeMillis() / 1000L) // Current time in seconds
        .setAction(UsageRecordCreateParams.Action.INCREMENT) // Add to existing usage
        .build();

      UsageRecord usageRecord = UsageRecord.createOnSubscriptionItem(
        subscriptionItemId, params
      );

      System.out.println("Usage reported successfully: " + usageRecord.getId());
    } catch (StripeException e) {
      System.err.println("Error reporting usage: " + e.getMessage());
    }
  }
}

Billing Cycles & Aggregation

Stripe aggregates all usage records for a specific subscription item within a billing cycle.

When the billing cycle ends, Stripe calculates the total usage based on the configured aggregate_usage for that price. This total is then multiplied by the unit price (or applied to tiers) to determine the final charge for that period.

The invoice is then generated and finalized.

Different Aggregation Types

Stripe offers different ways to aggregate usage for a metered price:

sum: (Default) Adds up all reported usage quantities over the billing period. Perfect for API calls or data transfer.
max: Uses the highest reported usage quantity during the period. Useful for "peak usage" models, like concurrent users.
last_ever: Uses the last reported usage quantity. Great for "snapshot" billing, like storage used at the end of the period.

Choose the type that best fits your service.

Quick Check: Usage Billing

Which of the following scenarios is best suited for a 'last_ever' aggregation type in Stripe's usage-based billing?

Recap: Usage-Based Billing

You've learned how to design and implement usage-based billing with Stripe!

We covered the core concepts of meters and events.
Explored how Stripe uses metered prices and usage records.
Saw a code example for reporting usage via the API.
Understood different aggregation types like sum, max, and last_ever.

This model offers great flexibility for both you and your customers.

よくある質問

「従量課金システムの実装」レッスンは無料ですか？

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

「従量課金システムの実装」で何を学びますか？

サービスやリソースの利用量に応じて顧客に課金する従量課金を設計・統合します。ブラウザで直接実行するハンズオンコードでStripe Payments & SaaS Billing Systemsを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Stripe Payments & SaaS Billing Systemsを始めるのに経験は必要ですか？

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

「従量課金システムの実装」レッスンにはどのくらい時間がかかりますか？

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

このStripe Payments & SaaS Billing Systemsレッスンでコードを書いて実行できますか？

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

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

← Stripe Payments & SaaS Billing Systemsに戻る