# `Stripe.Params.SubscriptionCreateParams`
[🔗](https://github.com/jeffhuen/tiger_stripe/blob/main/lib/stripe/params/subscription_create_params.ex#L2)

Parameters for subscription create.

# `t`

```elixir
@type t() :: %Stripe.Params.SubscriptionCreateParams{
  add_invoice_items:
    [Stripe.Params.SubscriptionCreateParams.AddInvoiceItems.t()] | nil,
  application_fee_percent: map() | nil,
  automatic_tax: Stripe.Params.SubscriptionCreateParams.AutomaticTax.t() | nil,
  backdate_start_date: integer() | nil,
  billing_cycle_anchor: integer() | nil,
  billing_cycle_anchor_config:
    Stripe.Params.SubscriptionCreateParams.BillingCycleAnchorConfig.t() | nil,
  billing_mode: Stripe.Params.SubscriptionCreateParams.BillingMode.t() | nil,
  billing_thresholds: map() | nil,
  cancel_at: map() | nil,
  cancel_at_period_end: boolean() | nil,
  collection_method: String.t() | nil,
  currency: String.t() | nil,
  customer: String.t() | nil,
  customer_account: String.t() | nil,
  days_until_due: integer() | nil,
  default_payment_method: String.t() | nil,
  default_source: String.t() | nil,
  default_tax_rates: map() | nil,
  description: String.t() | nil,
  discounts: map() | nil,
  expand: [String.t()] | nil,
  invoice_settings:
    Stripe.Params.SubscriptionCreateParams.InvoiceSettings.t() | nil,
  items: [Stripe.Params.SubscriptionCreateParams.Items.t()] | nil,
  metadata: map() | nil,
  off_session: boolean() | nil,
  on_behalf_of: map() | nil,
  payment_behavior: String.t() | nil,
  payment_settings:
    Stripe.Params.SubscriptionCreateParams.PaymentSettings.t() | nil,
  pending_invoice_item_interval: map() | nil,
  proration_behavior: String.t() | nil,
  transfer_data: Stripe.Params.SubscriptionCreateParams.TransferData.t() | nil,
  trial_end: map() | nil,
  trial_from_plan: boolean() | nil,
  trial_period_days: integer() | nil,
  trial_settings: Stripe.Params.SubscriptionCreateParams.TrialSettings.t() | nil
}
```

* `add_invoice_items` - A list of prices and quantities that will generate invoice items appended to the next invoice for this subscription. You may pass up to 20 items.
* `application_fee_percent` - A non-negative decimal between 0 and 100, with at most two decimal places. This represents the percentage of the subscription invoice total that will be transferred to the application owner's Stripe account. The request must be made by a platform account on a connected account in order to set an application fee percentage. For more information, see the application fees [documentation](https://stripe.com/docs/connect/subscriptions#collecting-fees-on-subscriptions).
* `automatic_tax` - Automatic tax settings for this subscription.
* `backdate_start_date` - A past timestamp to backdate the subscription's start date to. If set, the first invoice will contain line items for the timespan between the start date and the current time. Can be combined with trials and the billing cycle anchor. Format: Unix timestamp.
* `billing_cycle_anchor` - A future timestamp in UTC format to anchor the subscription's [billing cycle](https://docs.stripe.com/subscriptions/billing-cycle). The anchor is the reference point that aligns future billing cycle dates. It sets the day of week for `week` intervals, the day of month for `month` and `year` intervals, and the month of year for `year` intervals. Format: Unix timestamp.
* `billing_cycle_anchor_config` - Mutually exclusive with billing_cycle_anchor and only valid with monthly and yearly price intervals. When provided, the billing_cycle_anchor is set to the next occurrence of the day_of_month at the hour, minute, and second UTC.
* `billing_mode` - Controls how prorations and invoices for subscriptions are calculated and orchestrated.
* `billing_thresholds` - Define thresholds at which an invoice will be sent, and the subscription advanced to a new billing period. When updating, pass an empty string to remove previously-defined thresholds.
* `cancel_at` - A timestamp at which the subscription should cancel. If set to a date before the current period ends, this will cause a proration if prorations have been enabled using `proration_behavior`. If set during a future period, this will always cause a proration for that period.
* `cancel_at_period_end` - Indicate whether this subscription should cancel at the end of the current period (`current_period_end`). Defaults to `false`.
* `collection_method` - Either `charge_automatically`, or `send_invoice`. When charging automatically, Stripe will attempt to pay this subscription at the end of the cycle using the default source attached to the customer. When sending an invoice, Stripe will email your customer an invoice with payment instructions and mark the subscription as `active`. Defaults to `charge_automatically`. Possible values: `charge_automatically`, `send_invoice`.
* `currency` - 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). Format: ISO 4217 currency code.
* `customer` - The identifier of the customer to subscribe. Max length: 5000.
* `customer_account` - The identifier of the account representing the customer to subscribe. Max length: 5000.
* `days_until_due` - Number of days a customer has to pay invoices generated by this subscription. Valid only for subscriptions where `collection_method` is set to `send_invoice`.
* `default_payment_method` - ID of the default payment method for the subscription. It must belong to the customer associated with the subscription. This takes precedence over `default_source`. If neither are set, invoices will use the customer's [invoice_settings.default_payment_method](https://docs.stripe.com/api/customers/object#customer_object-invoice_settings-default_payment_method) or [default_source](https://docs.stripe.com/api/customers/object#customer_object-default_source). Max length: 5000.
* `default_source` - ID of the default payment source for the subscription. It must belong to the customer associated with the subscription and be in a chargeable state. If `default_payment_method` is also set, `default_payment_method` will take precedence. If neither are set, invoices will use the customer's [invoice_settings.default_payment_method](https://docs.stripe.com/api/customers/object#customer_object-invoice_settings-default_payment_method) or [default_source](https://docs.stripe.com/api/customers/object#customer_object-default_source). Max length: 5000.
* `default_tax_rates` - The tax rates that will apply to any subscription item that does not have `tax_rates` set. Invoices created will have their `default_tax_rates` populated from the subscription.
* `description` - The subscription's description, meant to be displayable to the customer. Use this field to optionally store an explanation of the subscription for rendering in Stripe surfaces and certain local payment methods UIs. Max length: 500.
* `discounts` - The coupons to redeem into discounts for the subscription. If not specified or empty, inherits the discount from the subscription's customer.
* `expand` - Specifies which fields in the response should be expanded.
* `invoice_settings` - All invoices will be billed using the specified settings.
* `items` - A list of up to 20 subscription items, each with an attached price.
* `metadata` - Set of [key-value pairs](https://docs.stripe.com/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to `metadata`.
* `off_session` - Indicates if a customer is on or off-session while an invoice payment is attempted. Defaults to `false` (on-session).
* `on_behalf_of` - The account on behalf of which to charge, for each of the subscription's invoices.
* `payment_behavior` - Only applies to subscriptions with `collection_method=charge_automatically`.

Use `allow_incomplete` to create Subscriptions with `status=incomplete` if the first invoice can't be paid. Creating Subscriptions with this status allows you to manage scenarios where additional customer actions are needed to pay a subscription's invoice. For example, SCA regulation may require 3DS authentication to complete payment. See the [SCA Migration Guide](https://docs.stripe.com/billing/migration/strong-customer-authentication) for Billing to learn more. This is the default behavior.

Use `default_incomplete` to create Subscriptions with `status=incomplete` when the first invoice requires payment, otherwise start as active. Subscriptions transition to `status=active` when successfully confirming the PaymentIntent on the first invoice. This allows simpler management of scenarios where additional customer actions are needed to pay a subscription’s invoice, such as failed payments, [SCA regulation](https://docs.stripe.com/billing/migration/strong-customer-authentication), or collecting a mandate for a bank debit payment method. If the PaymentIntent is not confirmed within 23 hours Subscriptions transition to `status=incomplete_expired`, which is a terminal state.

Use `error_if_incomplete` if you want Stripe to return an HTTP 402 status code if a subscription's first invoice can't be paid. For example, if a payment method requires 3DS authentication due to SCA regulation and further customer action is needed, this parameter doesn't create a Subscription and returns an error instead. This was the default behavior for API versions prior to 2019-03-14. See the [changelog](https://docs.stripe.com/upgrades#2019-03-14) to learn more.

`pending_if_incomplete` is only used with updates and cannot be passed when creating a Subscription.

Subscriptions with `collection_method=send_invoice` are automatically activated regardless of the first Invoice status. Possible values: `allow_incomplete`, `default_incomplete`, `error_if_incomplete`, `pending_if_incomplete`.
* `payment_settings` - Payment settings to pass to invoices created by the subscription.
* `pending_invoice_item_interval` - Specifies an interval for how often to bill for any pending invoice items. It is analogous to calling [Create an invoice](https://docs.stripe.com/api#create_invoice) for the given subscription at the specified interval.
* `proration_behavior` - Determines how to handle [prorations](https://docs.stripe.com/billing/subscriptions/prorations) resulting from the `billing_cycle_anchor`. If no value is passed, the default is `create_prorations`. Possible values: `always_invoice`, `create_prorations`, `none`.
* `transfer_data` - If specified, the funds from the subscription's invoices will be transferred to the destination and the ID of the resulting transfers will be found on the resulting charges.
* `trial_end` - Unix timestamp representing the end of the trial period the customer will get before being charged for the first time. If set, trial_end will override the default trial period of the plan the customer is being subscribed to. The special value `now` can be provided to end the customer's trial immediately. Can be at most two years from `billing_cycle_anchor`. See [Using trial periods on subscriptions](https://docs.stripe.com/billing/subscriptions/trials) to learn more.
* `trial_from_plan` - Indicates if a plan's `trial_period_days` should be applied to the subscription. Setting `trial_end` per subscription is preferred, and this defaults to `false`. Setting this flag to `true` together with `trial_end` is not allowed. See [Using trial periods on subscriptions](https://docs.stripe.com/billing/subscriptions/trials) to learn more.
* `trial_period_days` - Integer representing the number of trial period days before the customer is charged for the first time. This will always overwrite any trials that might apply via a subscribed plan. See [Using trial periods on subscriptions](https://docs.stripe.com/billing/subscriptions/trials) to learn more.
* `trial_settings` - Settings related to subscription trials.

---

*Consult [api-reference.md](api-reference.md) for complete listing*