تنفيذ التوزيعات النسبية والفوترة حسب الاستخدام

Welcome to advanced subscription features! Many businesses need more flexible billing than just a fixed monthly or yearly fee.

Today, we'll dive into two powerful concepts: prorations and metered billing. These allow you to handle mid-cycle changes and usage-based pricing with ease.

Imagine a customer upgrades their subscription plan halfway through their billing cycle. What happens to the money they already paid for the cheaper plan?

Proration is the process of proportionally adjusting charges when a subscription changes mid-cycle. Stripe automatically calculates this for you.

• Credit: For the unused portion of the old plan.
• Charge: For the new plan's usage up to the end of the current cycle.

When you modify a subscription in Stripe (e.g., changing the price or quantity of a subscription item), Stripe automatically calculates the proration.

It creates line items on the customer's invoice: a credit for the unused time on the old plan and a charge for the new plan from the change date to the end of the current billing period.

This ensures fairness and accuracy for both you and your customers.

When updating a subscription via the Stripe API, prorations are typically handled by default. You can also explicitly control this behavior using the proration_behavior parameter.

CREATE_PRORATIONS ensures that proration items are added to the invoice immediately or at the end of the cycle.

Try running this conceptual Java code:

Metered billing (or usage-based billing) charges customers based on how much of a service they actually use, rather than a fixed amount.

Think of utility bills (electricity, water) or cloud services (data storage, API calls). Customers only pay for what they consume.

• Examples: API requests, GB of storage, minutes of video streaming, number of active users.

To implement metered billing, you first need to define a Product and a Price in Stripe with a usage_type set to metered.

This tells Stripe that the quantity for this price will be reported by your application, not fixed at subscription creation.

You'll also define the billing scheme (e.g., per_unit or tiered) and optional aggregation method.

For metered billing, your application needs to track customer usage and report it to Stripe periodically, usually as it occurs or at regular intervals (e.g., daily).

This is done using the Usage Record API. You report the quantity of usage for a specific subscription_item.

Here's a conceptual Java example:

Stripe aggregates all usage records reported for a specific metered subscription item within a billing period.

At the end of the billing cycle (or when an invoice is finalized), Stripe calculates the total usage and applies the corresponding price, adding it to the customer's invoice.

You can define how usage is aggregated (e.g., sum, last_ever, max) when creating the price.

It's important to distinguish between prorations and metered billing:

• Prorations: Adjust charges for changes to fixed-price subscription items mid-cycle (e.g., upgrading from Basic to Pro plan).
• Metered Billing: Charges based on actual consumption of a service, with usage reported over time (e.g., paying per API call or GB of data).

Both offer powerful ways to make your billing more flexible and customer-friendly.

Which of the following scenarios would typically involve metered billing in Stripe?

Great job! You've learned how to handle flexible billing scenarios with Stripe:

• Prorations: Automatically adjust charges when subscriptions change mid-cycle, ensuring fair billing.
• Metered Billing: Charge customers based on their actual consumption, requiring you to report usage via the Stripe API.

These features are crucial for building dynamic and scalable SaaS platforms. Keep exploring to master more advanced Stripe capabilities!