StripeAPI.Types.Invoiceitem

amount: Amount (in the `currency` specified) of the invoice item. This should always be equal to `unit_amount * quantity`.

currency: Three-letter ISO currency code, in lowercase. Must be a supported currency.

customer: The ID of the customer who will be billed when this invoice item is billed.

date: Time at which the object was created. Measured in seconds since the Unix epoch.

description: An arbitrary string attached to the object. Often useful for displaying to users.

Constraints:

• Maximum length of 5000

discountable: If true, discounts will apply to this invoice item. Always false for prorations.

discounts: The discounts which apply to the invoice item. Item discounts are applied before invoice discounts. Use `expand[]=discounts` to expand each discount.

id: Unique identifier for the object.

Constraints:

• Maximum length of 5000

invoice: The ID of the invoice this invoice item belongs to.

livemode: Has the value `true` if the object exists in live mode or the value `false` if the object exists in test mode.

metadata: Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format.

period:

price: The price of the invoice item.

proration: Whether the invoice item was created automatically as a proration adjustment when the customer switched plans.

quantity: Quantity of units for the invoice item. If the invoice item is a proration, the quantity of the subscription that the proration was computed for.

subscription: The subscription that this invoice item has been created for, if any.

subscription_item: The subscription item that this invoice item has been created for, if any.

Constraints:

• Maximum length of 5000

tax_rates: The tax rates which apply to the invoice item. When set, the `default_tax_rates` on the invoice do not apply to this invoice item.

test_clock: ID of the test clock this invoice item belongs to.

unit_amount: Unit amount (in the `currency` specified) of the invoice item.

unit_amount_decimal: Same as `unit_amount`, but contains a decimal value with at most 12 decimal places.

active: Whether the price can be used for new purchases.

billing_scheme: Describes how to compute the price per period. Either `per_unit` or `tiered`. `per_unit` indicates that the fixed amount (specified in `unit_amount` or `unit_amount_decimal`) will be charged per unit in `quantity` (for prices with `usage_type=licensed`), or per unit of total usage (for prices with `usage_type=metered`). `tiered` indicates that the unit pricing will be computed using a tiering strategy as defined using the `tiers` and `tiers_mode` attributes.

created: Time at which the object was created. Measured in seconds since the Unix epoch.

currency: Three-letter ISO currency code, in lowercase. Must be a supported currency.

custom_unit_amount: When set, provides configuration for the amount to be adjusted by the customer during Checkout Sessions and Payment Links.

id: Unique identifier for the object.

Constraints:

• Maximum length of 5000

livemode: Has the value `true` if the object exists in live mode or the value `false` if the object exists in test mode.

lookup_key: A lookup key used to retrieve prices dynamically from a static string. This may be up to 200 characters.

Constraints:

• Maximum length of 5000

metadata: Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format.

nickname: A brief description of the price, hidden from customers.

Constraints:

• Maximum length of 5000

object: String representing the object's type. Objects of the same type share the same value.

product: The ID of the product this price is associated with.

recurring: The recurring components of a price such as `interval` and `usage_type`.

tax_behavior: Specifies whether the price is considered inclusive of taxes or exclusive of taxes. One of `inclusive`, `exclusive`, or `unspecified`. Once specified as either `inclusive` or `exclusive`, it cannot be changed.

tiers: Each element represents a pricing tier. This parameter requires `billing_scheme` to be set to `tiered`. See also the documentation for `billing_scheme`.

tiers_mode: Defines if the tiering price should be `graduated` or `volume` based. In `volume`-based tiering, the maximum quantity within a period determines the per unit price. In `graduated` tiering, pricing can change as the quantity grows.

transform_quantity: Apply a transformation to the reported usage or set quantity before computing the amount billed. Cannot be combined with `tiers`.

type: One of `one_time` or `recurring` depending on whether the price is for a one-time purchase or a recurring (subscription) purchase.

unit_amount: The unit amount in %s to be charged, represented as a whole integer if possible. Only set if `billing_scheme=per_unit`.

unit_amount_decimal: The unit amount in %s to be charged, represented as a decimal string with at most 12 decimal places. Only set if `billing_scheme=per_unit`.

maximum: The maximum unit amount the customer can specify for this item.

minimum: The minimum unit amount the customer can specify for this item. Must be at least the minimum charge amount.

preset: The starting unit amount which can be updated by the customer.

aggregate_usage: Specifies a usage aggregation strategy for prices of `usage_type=metered`. Allowed values are `sum` for summing up all usage during a period, `last_during_period` for using the last usage record reported within a period, `last_ever` for using the last usage record ever (across period bounds) or `max` which uses the usage record with the maximum reported usage during a period. Defaults to `sum`.

interval: The frequency at which a subscription is billed. One of `day`, `week`, `month` or `year`.

interval_count: The number of intervals (specified in the `interval` attribute) between subscription billings. For example, `interval=month` and `interval_count=3` bills every 3 months.

usage_type: Configures how the quantity per period should be determined. Can be either `metered` or `licensed`. `licensed` automatically bills the `quantity` set when adding it to a subscription. `metered` aggregates the total usage based on usage records. Defaults to `licensed`.

divide_by: Divide usage by this number.

round: After division, either round the result `up` or `down`.