Products and prices guide

Learn about products and prices.

Products and Prices are core resources for Stripe Billing. They’re closely associated with Customers, Invoices, and Subscriptions. These resources, along with the resources described in the table below, are the building blocks for creating and managing recurring payments in Stripe. This guide explains how to create, modify, and update products and prices.

For more information about managing payment methods, read the overview and see the integration options.

Resource definitions

Working with products and prices

You can create and update products and prices in the Dashboard or through the API.

Some advanced use cases, like creating ad-hoc prices, require you to use the API. If you have a large number of products and prices or if you’re building a custom integration with Elements, you need to use the API.

Use the Dashboard to create and manage products, prices, and other core Billing resources if you want to avoid writing code or if you only have a few products and prices. Set up your pricing model in test mode and click the Copy to live mode button on the product details page.
Use the API or the Stripe CLI to create and manage products, prices, and other core Billing resources with code. The API is a direct method that you use for production implementations. The Stripe CLI is a developer tool that helps you build, test, and manage your integration with Stripe directly from your terminal. The following API steps use Togethere, a SaaS collaboration tool, as an example, where the basic product is a project management dashboard.

Create a product

Create a product and price

You can type “product.new” into the address bar of any browser to jump straight to the Product Editor.

Create a product

To create a product in the Dashboard:

Go to the Products tab.
Click +Add product.
Enter the Name of your product.
(Optional) Add a Description. The description appears at checkout, on the customer portal, and in quotes.
(Optional) Add an Image of your product. Use a JPEG or PNG file that’s smaller than 2MB. The image appears at checkout.
(Optional) If you’re using Stripe Tax, select a Tax code for your product. See tax codes for more information about the appropriate code for your product.
(Optional) Enter a Statement descriptor. This descriptor overrides any account descriptors for recurring payments. Choose something that your customers would recognize on a bank statement.
(Optional) Enter a Unit label. This describes how you sell your product. For example, if you charge by the seat, enter “seat” so the line item includes “per seat” for the price. Unit labels appear at checkout, and in invoices, receipts, and the customer portal.

Create a price for the product

To save a product in the Dashboard, you must also add at least one price. You can create multiple prices for a product. To add a price for your product:

Select a Pricing model. For more details about each model, read the pricing model guide.
- Standard pricing—Charge the same price for each unit. If you use this option, select One time or Recurring.
- Package pricing—Charge by the package, or group of units, like charging $25.00 for every 5 units. Purchases are rounded up by default, so a customer buying 8 units would pay $50.00.
- Graduated pricing—Use pricing tiers that may result in a different price for some units in an order. For example, you might charge $10.00 per unit for the first 100 units and then $5.00 per unit for the next 50. If you use this option, select the currency for the price and fill in the tier table.
- Volume pricing—Charge the same price for each unit based on the total number of units sold. For example, you might charge $10.00 per unit for 50 units, and $7.00 per unit for 100 units. If you use this option, select the currency for the price and fill in the tier table.
Select a Billing period for recurring prices. You can add a custom period if none of the drop-down options are what you want.
(Optional) Check the box under Billing period if you’re using metered billing.
Select whether to Include tax in price. Learn more about taxes and subscriptions.
(Optional) Enter a Price description. Customers don’t see this description.
(Optional) Click Add another price if you want to create multiple prices for your product.
Click Save product to save the product and price. You can edit both later. Click Save and add more if you want to create another product and price.

Edit a product

To modify a product in the Dashboard:

Go to the Products tab.
Find the product you want to modify, click the overflow menu (), then click Edit product.
Make your changes to the product.
Click Save product.

You can also edit products from within the product information page by clicking the overflow menu (

) or Edit.

Archive a product

If you want to disable a product so that it can’t be added to new invoices or subscriptions, you can archive it. If you archive a product, any existing subscriptions that use the product remain active until they’re cancelled. You can’t delete products that have an associated price, but you can archive them.

To archive a product:

Go to the Products tab.
Find the product you want to modify, click the overflow menu (), then click Archive product.

To unarchive a product:

Go to the Archived tab in the Products > Overview page.
Find the product you want to modify, click the overflow menu (), then click Unarchive product.

You can also unarchive a product from the product information page.

Delete a product

You can only delete products that have no prices associated with them. If a product has a price associated with it, you have to delete or archive the price before you can delete the product. Alternatively, you can archive a product.

To permanently delete a product:

Go to the Products tab.
Find the product you want to modify, click the overflow menu (), then click Delete product.

Create price

You can create multiple prices for a product. For example, Togethere may have a “starter” level offered at 10 USD per month, 100 USD per year, or 9 EUR as a one-time purchase.

After you create a price, you can only update its metadata, nickname, and active fields.

To create a price in the Dashboard, you have to create a product first. Then you can create a price:

Select a Pricing model. For more details about each model, read the pricing model guide.
- Standard pricing—Charge the same price for each unit. If you use this option, select One time or Recurring.
- Package pricing—Charge by the package, or group of units, like charging $25.00 for every 5 units. Purchases are rounded up by default, so a customer buying 8 units would pay $50.00.
- Graduated pricing—Use pricing tiers that may result in a different price for some units in an order. For example, you might charge $10.00 per unit for the first 100 units and then $5.00 per unit for the next 50. If you use this option, select the currency for the price and fill in the tier table.
- Volume pricing—Charge the same price for each unit based on the total number of units sold. For example, you might charge $10.00 per unit for 50 units, and $7.00 per unit for 100 units. If you use this option, select the currency for the price and fill in the tier table.
Select a Billing period for recurring prices. You can add a custom period if none of the drop-down options are what you want.
(Optional) Check the box under Billing period if you’re using metered billing.
Select whether to Include tax in price. Learn more about taxes and subscriptions.
(Optional) Enter a Price description. Customers don’t see this description.
(Optional) Click Add another price if you want to create multiple prices for your product.
Click Save product to save the product and price. You can edit both later. Click Save and add more if you want to create another product and price.

Edit a price

To modify a price in the Dashboard:

Go to the Products tab.
Find the product for the price you want to modify, click the overflow menu (), then click Edit product.
Make your changes to the price. You can add another price at this point.
Click Save product.

You can also edit products from within the product information page by clicking the overflow menu (

) next to the price you want to change.

Archive a price

If you want to disable a price so that it can’t be added to new invoices or subscriptions, you can archive it. If you archive a price, any existing subscriptions that use the price remain active until they’re cancelled.

To archive a price through the Dashboard:

Go to the Products tab.
Find the product you want to modify, click the overflow menu ().
In the product information page, find the price you want to modify, then click the overflow menu () next to it and click Archive price.

To unarchive a price:

Go to the Products tab.
Find the product you want to modify, click the overflow menu ().
In the product information page, find the price you want to modify, then click the overflow menu () next to it and click Unarchive price.

Delete a price

To permanently delete a price in the Dashboard:

Go to the Products tab.
Find the product you want to modify, click the overflow menu ().
In the product information page, find the price you want to modify, then click the overflow menu () next to it and click Delete price.

Ad-hoc prices

In some cases, you might want to use a custom price that hasn’t been preconfigured. For example, you may want to allow customers to specify a donation amount, or you may manage your product catalog outside of Stripe.

You can only create ad-hoc prices through the API.

To facilitate these ad-hoc price use cases, you can pass in price_data instead of a price_id when you create a subscription. For example, to subscribe a customer to a monthly subscription with an ad-hoc price:

Terminal

curl https://api.stripe.com/v1/subscriptions \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -d customer="{{CUSTOMER_ID}}" \
  -d "items[0][price_data][unit_amount]=5000" \
  -d "items[0][price_data][currency]=usd" \
  -d "items[0][price_data][product]="{{PRODUCT_ID}}"
" \
  -d "items[0][price_data][recurring][interval]=month"

This creates a monthly recurring price of 50 USD for the basic service offering. By default, prices created with price_data are effectively archived (e.g., they are marked as active=false) so that they can’t be reused for other customers or subscriptions. You can’t update or reuse ad-hoc prices after you create them.

You can also use price_data with these APIs:

Lookup keys

Most businesses display pricing information on their website. If these prices are hard-coded and you want to change them, the process is often manual and requires you to deploy new code. To better manage these scenarios, you can use the lookup_key attribute on the Price object. This key allows you to:

Render different prices in your frontend.
Use the rendered price to bill customers.

You can pass a lookup_key when you create a price:

Terminal

curl https://api.stripe.com/v1/prices \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -d "product"="{{PRODUCT_ID}}" \
  -d "unit_amount"=1000 \
  -d "currency"="usd" \
  -d "recurring[interval]"="month" \
  -d "lookup_key"="standard_monthly"

Instead of hard-coding text like $10/month on your pricing page and using a price ID on your backend, you can query for the price using the standard_monthly key and then render that in your frontend:

Terminal

curl https://api.stripe.com/v1/prices \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -d "lookup_keys[]"="standard_monthly" \
  -G

To optimize performance, you might want to add a caching layer to only reload the price occasionally.

When a customer clicks your subscribe or pay button, you pass the price from the GET request above into the Subscriptions API.

Now that you can render different prices, if you decide that you want to start charging new users 20 USD per month rather than 10 USD per month, you only need to create a new price and transfer the lookup key to that new price using transfer_lookup_key=true:

Terminal

curl https://api.stripe.com/v1/prices \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -d "product"="{{PRODUCT_ID}}" \
  -d "unit_amount"=2000 \
  -d "currency"="usd" \
  -d "recurring[interval]"="month" \
  -d "lookup_key"="standard_monthly" \
  -d "transfer_lookup_key"="true"

Decimal amounts

Decimal pricing is useful if you need to create pricing amounts that are not whole numbers. For example, if you are running a cloud storage SaaS business, you can create a price that charges 0.05 cents for each MB used per month. Based on usage, the quantity of MB is then multiplied by 0.05 cents and rounded to the nearest whole cent.

Creating objects with decimal amounts

To create prices with decimal amounts, specify unit_amount_decimal instead of unit_amount. unit_amount_decimal allows you to set the amount in the minor unit of the currency you are charging in. For example, you can set unit_amount_decimal = 105.5 in USD to represent 105.5 cents, or $1.055. unit_amount_decimal accepts decimals up to 12 decimal places.

If you plan to use tiers, you can specify unit_amount_decimal instead of unit_amount. You can also create invoice items with unit_amount_decimal instead of unit_amount.

In API responses, the integer unit_amount field is not populated if the object is created with a decimal value. For example, if you create a price with unit_amount_decimal = 0.05, the response contains unit_amount = null and unit_amount_decimal = 0.05. You can still pass integer values into unit_amount_decimal, in which case unit_amount is populated in the response. For instance, if you create a price with unit_amount_decimal = 5, the response contains unit_amount = 5 and unit_amount_decimal = 5.0.

If your integration has event handling that uses unit_amount values and you begin using decimal amounts, you need to use unit_amount_decimal instead. This is important because unit_amount will be returned as null if the decimal amounts cannot be converted into integers, which could cause errors in your integration.

Rounding

Rounding occurs on the line item level of your invoices. For example, if you create a price with unit_amount_decimal = 0.05 and a monthly subscription for that [price] with quantity = 30, rounding occurs after the quantity is multiplied by the decimal amount. In this case, the calculated amount for the line item would be 0.05 * 30 = 1.5, which is then rounded up to 2 cents. If you have multiple line items, each will be rounded before summing up the total amount for the invoice. This ensures that customers are still charged an integer minor unit amount, as decimal amounts only apply for pricing.

Tiered pricing

Use tiers if you need non-linear pricing when quantity or usage changes. Tiered pricing can also be combined with base fees or other pricing models to create complex subscriptions.

When you create a price with billing_scheme=per_unit, the unit_amount is the same regardless of how many units a customer buys. This amount is multiplied by the quantity to determine the total cost. For example, a unit_amount of $5 creates this billing structure:

Quantity/Usage at end of period	Total cost
1	5 USD
5	25 USD
6	30 USD
20	100 USD
25	125 USD

When you create a price with billing_scheme=tiered, the unit cost varies depending on how many units your customer buys. Here’s an example tier structure:

Tier	Amount (unit cost)
1-5 (`up_to=5`)	5 USD (`unit_amount=500`)
6-10 (`up_to=10`)	4 USD (`unit_amount=400`)
10-15 (`up_to=15`)	3 USD (`unit_amount=300`)
15-20 (`up_to=20`)	2 USD (`unit_amount=200`)
20+ (`up_to=inf`)	1 USD (`unit_amount=100`)

Multiplication happens at the start of the billing period for Price objects with recurring.usage_type = licensed, and at the end of the billing period for Price objects with recurring.usage_type = metered.

With tiered billing, you also set the tiers_mode to one of volume or graduated, and create a tiers array to represent the tiers structure. See also the volume-based and graduated pricing examples.

Volume

With tiers_mode=volume, the entire quantity is multiplied by the unit cost of the tier.

Quantity/Usage at end of period	Total for volume tiered pricing
1	5 USD
5	25 USD
6	24 USD
20	40 USD
25	25 USD

Because the tier price applies to the entire quantity or usage, the total can decrease when calculating the final cost.

Graduated

With tiers_mode=graduated, the quantity is multiplied by the amount that falls into that tier. Then, the total is summed. For example, the total cost for an amount of 6 is 29 USD: 25 USD for the 5 quantity that falls into the 1–5 tier, plus 4 USD for the single quantity that falls into the 6–10 tier.

Quantity and usage at end of the period	Total for graduated tiered pricing
1	5 USD
5	25 USD
6	29 USD
20	70 USD
25	75 USD

Adding Flat Fees

You can also specify a flat fee (flat_amount) to add to the invoice. This works for both tiers_mode=volume and tiers_mode=graduated. For example, you can have a flat fee that increases when certain usage thresholds are met:

Tier	Amount (unit cost)	Flat fee
1-5 (`up_to=5`)	5 USD (`unit_amount=500`)	10 USD (`flat_amount=1000`)
6-10 (`up_to=10`)	4 USD (`unit_amount=400`)	20 USD (`flat_amount=2000`)
10-15 (`up_to=15`)	3 USD (`unit_amount=300`)	30 USD (`flat_amount=3000`)
15-20 (`up_to=20`)	2 USD (`unit_amount=200`)	40 USD (`flat_amount=4000`)
20+ (`up_to=inf`)	1 USD (`unit_amount=100`)	50 USD (`flat_amount=5000`)

In this example, if the quantity is 12 and the tiers_mode=volume, the total amount to be billed is 12 * 3 USD + 30 USD = 66 USD. If the quantity is 12 and tiers_mode=graduated, the total amount is 5 * 5 USD + 10 USD + 5 * 4 USD + 20 USD + 2 * 3 USD + 30 USD = 111 USD. Note that a tier can have either a unit_amount or a flat_amount, or both, but it must have at least one of the two.

Metered billing

With metered billing, you charge your customers based on their consumption of your service during the billing cycle, instead of explicitly setting quantities. For example, if you run an email SaaS business, you can record how many emails your customers send per month, then bill them for the total number at the end of the month.

Like other subscription models, metered billing is defined by the prices you create for your product or service. You must also record usage, and you can customize how to handle usage records.Prices can be used for one-off and recurring purchases.

Usage types

For recurring purchases, there are two options, called usage_types, that determine how much a customer is charged.

With licensed usage (recurring[usage_type]='licensed'), the quantity for a subscription item is set when creating or updating the subscription. The quantity persists until you or your customer changes it. Every billing interval, the subscription charges the amount × quantity for the item. For example, a customer with three users who subscribes to a 15 USD per-user monthly service is charged 45 USD every month.
With metered usage (recurring[usage_type]='metered'), your customer is billed in arrears based on how much of your service they consume. Their usage is tracked with the Usage API. At the end of the billing period, the total usage is multiplied by the unit_amount to calculate how much the customer owes. For example, if a broadband provider charges 0.50 USD per gigabyte (GB) used, and a customer uses 100 GBs, the customer is charged 50 USD.

Creating a metered billing subscription

When you create a price for metered billing, you specify:

"recurring[usage_type]"=metered
Interval and currency
Amount per unit of consumption

You can also specify a value for aggregate_usage. This parameter determines how usage records are handled.

The default value (passed if you do not specify the parameter) is sum. The total billed is based on the sum of all usage records for the billing period.
last_during_period – the total billed is based on the most recent usage record for the billing period. If no usage is reported for the billing period, the total billed is based on a usage quantity of 0.
last_ever – the total billed is based on the most recent usage record ever provided. If no usage is reported during the current billing period, Stripe looks for a previous usage record. If no usage record is found, the total billed is based on a usage quantity of 0.
max – the total billed is based on the usage record with the largest usage quantity for the billing period. If no usage is reported for the billing period, the total billed is based on a usage quantity of 0.

Which option you choose depends on how you handle usage on your end. You also set the value of the action parameter of the usage records API to reflect how you record usage.

Terminal

curl https://api.stripe.com/v1/prices \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -d "currency"="usd" \
  -d "recurring[interval]"="month" \
  -d "recurring[usage_type]"="metered" \
  -d "product_data[name]"="Gold special" \
  -d "nickname"="Gold special price" \
  -d "unit_amount"=3000

When you create the subscription:

Don’t pass quantity.
Make sure to record the subscription item ID. You pass this value to the Usage Records API to report usage.

Reporting usage

Stripe expects that you maintain your own system for recording customer usage, but you must also provide usage information for subscriptions to Stripe. Note the following:

The default value for the action parameter is increment. This value assumes that the price is configured with aggregate_usage=sum and that you write usage as it occurs, passing it to Stripe with the current timestamp.
A set value for the action parameter supports the case where you aggregate usage yourself, and configure the price with aggregate_usage=last_during_period or aggregate_usage=last_ever.

Reporting usage outside the current billing interval results in an error. Stripe leaves a five-minute window in the default aggregation mode (aggregate_usage=sum) after the period ends to allow for clock drift. For all other aggregation modes the timestamp must be within the current period.

Terminal

curl https://api.stripe.com/v1/subscription_items/{{SUBSCRIPTION_ITEM_ID}}/usage_records \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -X POST \
  -d quantity=100 \
  -d timestamp=1638957090 \
  -d action=increment

Using an idempotency key lets you safely re-report usage in the event of intermittent API errors.

At the end of a subscription period, Stripe automatically totals and invoices for all usage during the billing period. Metered billing invoices respect trials. Note that once the invoice is submitted, it cannot be changed. The usage reporting endpoint is rate-limited, so you might need to exercise caution and avoid making too many separate usage records.

When canceling a subscription at the end of the period, any usage reported before the subscription ends is billed in a final invoice at the end of the period. Canceling a subscription immediately does not bill for any usage accrued during the final billing cycle.

Retrieving current usage

To retrieve total usage for the current period, you can retrieve the upcoming invoice for the subscription. The usage is reflected as the quantity of the invoice item for a subscription_item. The total usage value may not be the most up-to-date quantity because slight processing delays can occur.

Billing thresholds

Billing thresholds allow you to issue an invoice, and to (optionally) reset a subscription’s billing cycle, when a customer’s accrued usage in a subscription cycle reaches a specified monetary or usage threshold. Consider using billing thresholds if you want precautions to limit the amount owed, or to limit the products consumed, between invoices or charges.

Add a monetary threshold to a subscription

You commonly set the amount of a threshold’s value to a multiple of the cost of one unit of the product being sold.

Setting a lower amount threshold causes your customers to receive an invoice for every unit of usage, which can cause confusion.

The value is a positive integer in the smallest currency unit (e.g., 100 cents to charge 1 USD; or 100 to charge 100 JPY, a zero-decimal currency). It must be at least 50 currency units.

You can also set monetary thresholds in the Dashboard, when you create or update a subscription.

Terminal

curl https://api.stripe.com/v1/subscriptions/sub_49ty4767H20z6a \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -d "billing_thresholds[amount_gte]"=10000 \
  -d "billing_thresholds[reset_billing_cycle_anchor]"="false"

Add a usage threshold to a subscription item

As with monetary thresholds, usage thresholds should ideally be greater than one unit of usage, to avoid frequent invoicing. Stripe doesn’t currently support setting usage thresholds via the Dashboard.

Terminal

curl https://api.stripe.com/v1/subscription_items/si_CFhSgkWb0MyTWg \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -d "billing_thresholds[usage_gte]"=2000

Thresholds and billing cycle anchor

When a customer’s usage reaches a threshold, the subscription’s billing cycle anchor won’t change (by default). For example, if a threshold is reached in the middle of a month-long subscription, the subscription resets at the end of the month like a subscription without thresholds.

You can change this behavior so that reaching a threshold resets the billing cycle anchor. Doing this effectively treats reaching a threshold as if the subscription had reached its natural rollover point at the end of the month.

Terminal

curl https://api.stripe.com/v1/subscriptions/sub_49ty4767H20z6a \
  -u sk_test_4eC39HqLyjWDarjtT1zdp7dc
: \
  -d "billing_thresholds[reset_billing_cycle_anchor]"="true"

Be aware that reset_billing_cycle_anchor=true isn’t allowed if a metered subscription has aggregate_usage=last_ever.

Thresholds and tiered pricing

Tiers are maintained across threshold invoices. As with a subscription without thresholds, tiers reset only at the end of the billing period, or if you configure the subscription to reset the billing cycle anchor when it reaches a threshold.

For example, let’s say you run an ad platform that has a graduated tiering structure for ad impressions:

Tier	Amount (unit cost)
1-10000 (`up_to=10000`)	0.50 USD (`unit_amount=50`)
10000+ (`up_to=inf`)	0.40 USD (`unit_amount=40`)

Because usage is billed after the fact, you set a threshold of 100 USD as a stopgap for new customers. Under this scheme, your customer is effectively billed every 200 impressions for the first 10,000 impressions (200 * 0.50 USD = 100 USD). When the customer exceeds 10,000 impressions, they’re effectively billed every 250 impressions (250 * 0.40 USD = 100 USD). This will continue until the end of the billing period, at which point all un-invoiced usage will be invoiced, and the subscription and tiers will reset.

If you prefer that tiers reset upon reaching a threshold, you must configure the subscription to reset the billing cycle anchor when thresholds are reached.

Volume tiers

Volume tiers define the pricing for all units of usage, as opposed to graduated tiers (used in the example above), which define pricing for a specific amount of usage. Some pricing models use volume tiers that decrease the unit cost at each successive tier. You can use such models to incentivize customers to use more of a product (e.g., ad impressions, or GBs of storage).

When combined with thresholds, these pricing models can lead to invoices with line items for negative amounts, under the following conditions:

A threshold invoice has already been issued.
Subsequent usage is billed at a lower unit cost.

For example, with these tiers:

Tier	Amount (unit cost)
1-10000 (`up_to=10000`)	0.50 USD (`unit_amount=50`)
10000+ (`up_to=inf`)	0.40 USD (`unit_amount=40`)

If a customer uses 10,000 units, the invoice total will be 5,000 USD (10,000 * 0.50 USD = 5,000 USD). Any additional usage will cause all usage to be billed at the lower unit cost of 0.40 USD. So, if the customer uses just one more unit, the invoice total drops to 4,000.40 USD (10,001 * 0.40 USD = 4,000.40 USD).

If the subscription didn’t have thresholds, Stripe would issue an invoice for 4,000.40 USD at the end of the billing period.

However, to see how negative invoicing can happen, let’s assume we have a 5,000 USD monetary threshold. In this scenario, Stripe issues an invoice when the customer reaches 10,000 units of usage.

If the customer uses just one more unit, the invoice total drops to 4,000.40 USD (10,001 * 0.40 USD = 4,000.40 USD). However, if the customer consumes no more units, then the customer is owed 999.60 USD (5,000 USD - 4,000.40 USD = 999.60 USD). At the end of the billing period, Stripe will credit this amount to the customer’s balance, which will be used to pay down future invoices.

Let’s say the customer continues to accrue usage. The cost of this usage will reach 5,000 USD again when the customer has used 12,500 units (5,000 USD / 0.40 USD = 12,500). However, the previous payment of 5,000 USD covers all of this usage, so no invoice will be issued.

Stripe won’t issue an invoice until either the total usage reaches 25,000 units (for a total cost of 10,000 USD), or the end of the billing period arrives—whichever occurs first. The tables below show the line items you should expect to see for the two invoices issued in the case where usage reaches 25,000 units.

Invoice 1

Line Item	Quantity	Amount
Usage (0.50 USD per unit)	10,000	5,000 USD
Total		5,000 USD

Invoice 2

Line Item	Quantity	Amount
Usage (0.40 USD per unit)	25,000	10,000 USD
Amount previously billed (at 0.50 USD per unit)		-5,000 USD
Total		5,000 USD

Limitations and caveats

Thresholds don’t apply to trialing subscriptions.
Monetary thresholds must be greater than the sum of all licensed subscription costs.
Billing thresholds aren’t evaluated during the 24 hours leading up to the end of a subscription. This helps limit confusion for a customer who receives multiple invoices on the same date.
Subscriptions are only allowed a single monetary threshold.
Subscription items are only allowed a single usage threshold.
Given the real-time nature of usage reporting, invoices might not be issued at the exact moment a specified threshold is reached. Invoiced amounts or usage might be slightly higher than the specified thresholds.
The value used to determine whether a monetary threshold has been reached excludes taxes, but includes discounts and applicable prorations.
If a subscription uses the last_ever aggregation mode, you can’t enable the reset_billing_anchor option.