# plan

From **Stripe API**.

You can now model subscriptions more flexibly using the [Prices API](https://stripe.com/docs/api#prices). It replaces the Plans API and is backwards compatible to simplify your migration.

Plans define the base price, currency, and billing cycle for recurring purchases of products.
[Products](https://stripe.com/docs/api#products) help you track inventory or provisioning, and plans help you track pricing. Different physical goods or levels of service should be represented by products, and pricing options should be represented by plans. This approach lets you change prices without having to change your provisioning scheme.

For example, you might have a single "gold" product that has plans for $10/month, $100/year, €9/month, and €90/year.

Related guides: [Set up a subscription](https://stripe.com/docs/billing/subscriptions/set-up-subscription) and more about [products and prices](https://stripe.com/docs/billing/prices-guide).

- Type: `object`

## Properties

### `active`

- Required: true
- Type: `boolean`

Whether the plan can be used for new purchases.

### `aggregate_usage`

- Required: false
- Type: `string`
- Nullable: true
- Allowed values: `"last_during_period"`, `"last_ever"`, `"max"`, `"sum"`

Specifies a usage aggregation strategy for plans 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`.

### `amount`

- Required: false
- Type: `integer`
- Nullable: true

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

### `amount_decimal`

- Required: false
- Type: `string`
- Format: `decimal`
- Nullable: true

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`.

### `billing_scheme`

- Required: true
- Type: `string`
- Allowed values: `"per_unit"`, `"tiered"`

Describes how to compute the price per period. Either `per_unit` or `tiered`. `per_unit` indicates that the fixed amount (specified in `amount`) will be charged per unit in `quantity` (for plans with `usage_type=licensed`), or per unit of total usage (for plans 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`

- Required: true
- Type: `integer`
- Format: `unix-time`

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

### `currency`

- Required: true
- Type: `string`

Three-letter [ISO currency code](https://www.iso.org/iso-4217-currency-codes.html), in lowercase. Must be a [supported currency](https://stripe.com/docs/currencies).

### `id`

- Required: true
- Type: `string`
- maxLength: `5000`

Unique identifier for the object.

### `interval`

- Required: true
- Type: `string`
- Allowed values: `"day"`, `"month"`, `"week"`, `"year"`

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

### `interval_count`

- Required: true
- Type: `integer`

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

### `livemode`

- Required: true
- Type: `boolean`

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

### `metadata`

- Required: false
- Type: `object`
- Nullable: true

Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format.

### `nickname`

- Required: false
- Type: `string`
- Nullable: true
- maxLength: `5000`

A brief description of the plan, hidden from customers.

### `object`

- Required: true
- Type: `string`
- Allowed values: `"plan"`

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

### `product`

- Required: false
- Nullable: true

The product whose pricing this plan determines.

### `tiers`

- Required: false
- Type: `array`

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`

- Required: false
- Type: `string`
- Nullable: true
- Allowed values: `"graduated"`, `"volume"`

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_usage`

- Required: false
- Nullable: true

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

### `trial_period_days`

- Required: false
- Type: `integer`
- Nullable: true

Default number of trial days when subscribing a customer to this plan using [`trial_from_plan=true`](https://stripe.com/docs/api#create_subscription-trial_from_plan).

### `usage_type`

- Required: true
- Type: `string`
- Allowed values: `"licensed"`, `"metered"`

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`.

## JSON Schema

```json
{"description":"You can now model subscriptions more flexibly using the [Prices API](https://stripe.com/docs/api#prices). It replaces the Plans API and is backwards compatible to simplify your migration.\n\nPlans define the base price, currency, and billing cycle for recurring purchases of products.\n[Products](https://stripe.com/docs/api#products) help you track inventory or provisioning, and plans help you track pricing. Different physical goods or levels of service should be represented by products, and pricing options should be represented by plans. This approach lets you change prices without having to change your provisioning scheme.\n\nFor example, you might have a single \"gold\" product that has plans for $10/month, $100/year, €9/month, and €90/year.\n\nRelated guides: [Set up a subscription](https://stripe.com/docs/billing/subscriptions/set-up-subscription) and more about [products and prices](https://stripe.com/docs/billing/prices-guide).","properties":{"active":{"description":"Whether the plan can be used for new purchases.","type":"boolean"},"aggregate_usage":{"description":"Specifies a usage aggregation strategy for plans 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`.","enum":["last_during_period","last_ever","max","sum"],"nullable":true,"type":"string"},"amount":{"description":"The unit amount in %s to be charged, represented as a whole integer if possible. Only set if `billing_scheme=per_unit`.","nullable":true,"type":"integer"},"amount_decimal":{"description":"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`.","format":"decimal","nullable":true,"type":"string"},"billing_scheme":{"description":"Describes how to compute the price per period. Either `per_unit` or `tiered`. `per_unit` indicates that the fixed amount (specified in `amount`) will be charged per unit in `quantity` (for plans with `usage_type=licensed`), or per unit of total usage (for plans 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.","enum":["per_unit","tiered"],"type":"string"},"created":{"description":"Time at which the object was created. Measured in seconds since the Unix epoch.","format":"unix-time","type":"integer"},"currency":{"description":"Three-letter [ISO currency code](https://www.iso.org/iso-4217-currency-codes.html), in lowercase. Must be a [supported currency](https://stripe.com/docs/currencies).","type":"string"},"id":{"description":"Unique identifier for the object.","maxLength":5000,"type":"string"},"interval":{"description":"The frequency at which a subscription is billed. One of `day`, `week`, `month` or `year`.","enum":["day","month","week","year"],"type":"string"},"interval_count":{"description":"The number of intervals (specified in the `interval` attribute) between subscription billings. For example, `interval=month` and `interval_count=3` bills every 3 months.","type":"integer"},"livemode":{"description":"Has the value `true` if the object exists in live mode or the value `false` if the object exists in test mode.","type":"boolean"},"metadata":{"additionalProperties":{"maxLength":500,"type":"string"},"description":"Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format.","nullable":true,"type":"object"},"nickname":{"description":"A brief description of the plan, hidden from customers.","maxLength":5000,"nullable":true,"type":"string"},"object":{"description":"String representing the object's type. Objects of the same type share the same value.","enum":["plan"],"type":"string"},"product":{"anyOf":[{"maxLength":5000,"type":"string"},{"$ref":"#/components/schemas/product"},{"$ref":"#/components/schemas/deleted_product"}],"description":"The product whose pricing this plan determines.","nullable":true,"x-expansionResources":{"oneOf":[{"$ref":"#/components/schemas/product"},{"$ref":"#/components/schemas/deleted_product"}]}},"tiers":{"description":"Each element represents a pricing tier. This parameter requires `billing_scheme` to be set to `tiered`. See also the documentation for `billing_scheme`.","items":{"$ref":"#/components/schemas/plan_tier"},"type":"array"},"tiers_mode":{"description":"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.","enum":["graduated","volume"],"nullable":true,"type":"string"},"transform_usage":{"anyOf":[{"$ref":"#/components/schemas/transform_usage"}],"description":"Apply a transformation to the reported usage or set quantity before computing the amount billed. Cannot be combined with `tiers`.","nullable":true},"trial_period_days":{"description":"Default number of trial days when subscribing a customer to this plan using [`trial_from_plan=true`](https://stripe.com/docs/api#create_subscription-trial_from_plan).","nullable":true,"type":"integer"},"usage_type":{"description":"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`.","enum":["licensed","metered"],"type":"string"}},"required":["active","billing_scheme","created","currency","id","interval","interval_count","livemode","object","usage_type"],"title":"Plan","type":"object","x-expandableFields":["product","tiers","transform_usage"],"x-resourceId":"plan"}
```