Unique identifier for the object.
String representing the object's type. Objects of the same type share the same value.
Amount (in the currency specified) of the invoice item. This should always be equal to unit_amount * quantity.
Three-letter ISO currency code, in lowercase. Must be a supported currency.
The ID of the customer to bill for this invoice item.
The ID of the account to bill for this invoice item.
Time at which the object was created. Measured in seconds since the Unix epoch.
OptionaldeletedAlways true for a deleted object
An arbitrary string attached to the object. Often useful for displaying to users.
If true, discounts will apply to this invoice item. Always false for prorations.
The discounts which apply to the invoice item. Item discounts are applied before invoice discounts. Use expand[]=discounts to expand each discount.
The ID of the invoice this invoice item belongs to.
Has the value true if the object exists in live mode or the value false if the object exists in test mode.
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.
Optionalnet_The amount after discounts, but before credits and taxes. This field is null for discountable=true items.
The parent that generated this invoice item.
The pricing information of the invoice item.
Whether the invoice item was created automatically as a proration adjustment when the customer switched plans.
Optionalproration_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.
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.
ID of the test clock this invoice item belongs to.
Invoice Items represent the component lines of an invoice. When you create an invoice item with an
invoicefield, it is attached to the specified invoice and included as an invoice line item within invoice.lines.Invoice Items can be created before you are ready to actually send the invoice. This can be particularly useful when combined with a subscription. Sometimes you want to add a charge or credit to a customer, but actually charge or credit the customer's card only at the end of a regular billing cycle. This is useful for combining several charges (to minimize per-transaction fees), or for having Stripe tabulate your usage-based billing totals.
Related guides: Integrate with the Invoicing API, Subscription Invoices.