Stripe Payments & SaaS Billing Systems · Lección

Implementación de prorrateos y facturación por uso

Comprenda y aplique prorrateos para cambios a mitad del ciclo y configure la facturación por uso para modelos de suscripción basados en el consumo.

Lección 2 de 411 pasos

Implementación de prorrateos y facturación por uso es una lección gratuita de Stripe Payments & SaaS Billing Systems en CoddyKit. Esta es la lección 2 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Stripe Payments & SaaS Billing Systems, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Stripe Payments & SaaS Billing Systems incluye 4 lecciones en total.

Partes de esta lección aún no han sido traducidas y se muestran en inglés.

Flexible Billing: Intro

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.

What are Prorations?

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.

Stripe's Proration Logic

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.

Implementing Prorated Changes

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:

import com.stripe.Stripe;
import com.stripe.param.SubscriptionUpdateParams;

public class Main {
  public static void main(String[] args) {
    // In a real app, you'd set Stripe.apiKey and handle exceptions.
    // This snippet focuses on the update parameters.

    String subscriptionItemId = "si_EXISTING_ITEM_ID";
    String newPriceId = "price_NEW_PLAN_ID";

    SubscriptionUpdateParams params =
      SubscriptionUpdateParams.builder()
        .addItem(
          SubscriptionUpdateParams.Item.builder()
            .setId(subscriptionItemId) // ID of the existing subscription item
            .setPrice(newPriceId)     // The new price for the subscription
            .build()
        )
        .setProrationBehavior(SubscriptionUpdateParams.ProrationBehavior.CREATE_PRORATIONS)
        .build();

    System.out.println("Subscription update parameters created:");
    System.out.println("- New Price ID: " + newPriceId);
    System.out.println("- Proration Behavior: CREATE_PRORATIONS");
    System.out.println("Stripe will automatically calculate and apply prorations.");
  }
}

What is Metered Billing?

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.

Setting Up Metered Products

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.

Reporting Usage to Stripe

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:

import com.stripe.Stripe;
import com.stripe.param.UsageRecordCreateParams;

public class Main {
  public static void main(String[] args) {
    // In a real app, you'd set Stripe.apiKey and handle exceptions.
    // This snippet focuses on creating a usage record.

    String subscriptionItemId = "si_METERED_ITEM_ID"; // The ID of the metered subscription item
    long quantityUsed = 10L; // The amount of usage to report

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

    System.out.println("Usage record creation parameters created:");
    System.out.println("- Subscription Item ID: " + subscriptionItemId);
    System.out.println("- Quantity Reported: " + quantityUsed);
    System.out.println("- Action: INCREMENT (adds to previous usage)");
    System.out.println("This usage will be billed at the end of the current billing cycle.");
  }
}

How Metered Usage is Billed

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.

Prorations vs. Metered: Recap

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.

Quick Check: Flexible Billing

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

Recap: Prorations & Metered

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!

Gratis para empezar

Aprende Stripe Payments & SaaS Billing Systems con un tutor de IA — gratis

Escribe y ejecuta código real en tu navegador, obtén ayuda instantánea de un tutor de IA disponible 24/7 y continúa donde lo dejaste en la web o en la aplicación.

Cursos
12
Lecciones
48

Preguntas frecuentes

¿La lección «Implementación de prorrateos y facturación por uso» es gratis?

Sí — el texto completo de «Implementación de prorrateos y facturación por uso» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Stripe Payments & SaaS Billing Systems, actualiza a CoddyKit PRO. El curso de Stripe Payments & SaaS Billing Systems incluye 4 lecciones en total.

¿Qué aprenderé en «Implementación de prorrateos y facturación por uso»?

Comprenda y aplique prorrateos para cambios a mitad del ciclo y configure la facturación por uso para modelos de suscripción basados en el consumo. Practicas Stripe Payments & SaaS Billing Systems con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.

¿Necesito experiencia previa para empezar Stripe Payments & SaaS Billing Systems?

No se requiere experiencia previa. Stripe Payments & SaaS Billing Systems en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 2 de 4.

¿Cuánto tiempo toma la lección «Implementación de prorrateos y facturación por uso»?

La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.

¿Puedo escribir y ejecutar código en esta lección de Stripe Payments & SaaS Billing Systems?

Sí. Cada lección de Stripe Payments & SaaS Billing Systems incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.

Todas las lecciones de este curso

  1. Gestión de períodos de prueba y mejoras de plan
  2. Implementación de prorrateos y facturación por uso
  3. Gestión del ciclo de vida y los eventos de las suscripciones
  4. Cupones, descuentos y códigos promocionales
← Volver a Stripe Payments & SaaS Billing Systems