Accéder directement au contenu
Créez un compte
ou
connecter-vous
Logo de la documentation Stripe
/
Demander à l'assistant IA
Créez un compte
Connectez-vous
Démarrer
Paiements
Revenus
Plateformes et places de marché
Gestion de fonds
Ressources pour les développeurs
Aperçu
Billing
PrésentationÀ propos des API Billing
Abonnements
Invoicing
Facturation à la consommation
    Choisir une configuration de facturation à l'usage
      Utiliser des produits et des tarifs
        Gérer votre configuration de facturation
        Transformer les quantités
      Utiliser des grilles tarifaires
    Enregistrer la consommation en vue de la facturation
    Proposer des crédits de facturation
    Surveiller l'utilisation
    Modèles de tarification à l'usage
Devis
Gestion des clients
Billing with other products
Recouvrement de revenus
Automatisations
Comptabilisation des revenus
Tester votre intégration
Tax
Présentation
Use Stripe tax
Manage compliance
Rapports
Présentation
Sélectionner un rapport
Configure reports
API de rapport
Rapports sur plusieurs comptes
Comptabilisation des revenus
Données
PrésentationSchéma
Rapports personnalisés
Data Pipeline
Gestion des données
AccueilRevenusUsage-based billingChoose a usage-based billing setupUse products and prices

Remarque

Cette page n'est pas encore disponible dans cette langue. Nous faisons tout notre possible pour proposer notre documentation dans davantage de langues et nous vous fournirons la version traduite dès qu'elle sera disponible.

Manage your usage-based billing setup

Learn how to handle billing-related tasks for your usage-based billing model.

After you create your usage-based billing model, you can modify different parts of your billing setup. For example, you can update a subscription item’s price during a billing cycle, backdate a subscription to include usage in the next invoice, or cancel usage-based subscriptions.

Update prices mid-cycle

You can update a subscription item’s price during a billing cycle.

However, limitations apply when switching from one meter price to another.

On future invoices, we reflect only usage that occurs after the update. For example, say you have a monthly subscription that you switch from price A to price B on January 16. At the end of the month, the invoice includes usage from January 16 to January 31 at price B. Usage from January 1 to January 16 isn’t billed.

An exception exists if you use billing thresholds and have a threshold invoice already generated at the old price. For example, say you generate a threshold invoice on January 10 using price A. That threshold invoice is still charged to the customer. At the end of the month, the invoice includes usage from January 16 to January 31 at price B. The earlier threshold invoice doesn’t offset any usage for this end-of-month invoice.

Similar restrictions apply if you add a new subscription item with a billing meter price in the middle of the subscription cycle. For example, say you add a new subscription item with price C on January 16. At the end of the month, the invoice includes usage from January 16 to January 31 at price C for that subscription item.

To capture previously reported usage when changing prices, choose one of these options:

  • Report the aggregated usage again to capture it in the cycle on the new price.
  • Reset the billing_cycle_anchor parameter to now, applying the old price to previously reported usage.

These workarounds address the current limitation.

To update the price for a subscription item:

Command Line
cURL
curl https://api.stripe.com/v1/subscription_items/{{SUBSCRIPTION_ITEM_ID}} \ -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:"
\ -d price={{NEW_PRICE_ID}}

To delete a subscription item:

Command Line
cURL
curl -X DELETE https://api.stripe.com/v1/subscription_items/{{SUBSCRIPTION_ITEM_ID}} \ -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:"

After deletion, the invoice doesn’t reflect any usage from that item.

Create a backdated subscription

You can record usage for a customer even before creating a subscription for them. After recording usage for a customer, use the backdate_start_date to create a subscription before the first report.

This allows you to include usage in the next subscription invoice.

Command Line
cURL
curl https://api.stripe.com/v1/subscriptions \ -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:"
\ -d customer={{CUSTOMER_ID}} \ -d "items[0][price]"={{PRICE_ID}} \ -d backdate_start_date=1710000000

Cancel usage-based subscriptions

With usage-based billing, the bill the customer pays varies based on consumption during the billing cycle. When changing the billing cycle results in a subscription interval ending early, you charge the customer for the usage accrued during the shortened billing cycle.

Remarque

We don’t support proration with usage-based billing.

You can’t reactivate canceled subscriptions. Instead, you can collect updated billing information from your customer, update their default payment method, and create a new subscription with their existing customer record.

If you use cancel_at_period_end to schedule the cancellation of a subscription, you can reactivate the subscription at any time up to the end of the period. To do so, update cancel_at_period_end to false.

For subscriptions that cancel at the end of the period, the final invoice at the end of the cycle includes metered usage from the last billing cycle.

Cette page vous a-t-elle été utile ?
OuiNon
Besoin d'aide ? Contactez le service Support.
Rejoignez notre programme d'accès anticipé.
Consultez notre log des modifications.
Des questions ? Contactez l'équipe commerciale.
LLM ? Lire llms.txt.
Propulsé par Markdoc