Plan constructor
- required bool active,
- InvoiceitemPlanAggregateUsage? aggregateUsage,
- int? amount,
- String? amountDecimal,
- required InvoiceitemPlanBillingScheme billingScheme,
- required DateTime created,
- required String currency,
- required String id,
- required InvoiceitemPlanInterval interval,
- required int intervalCount,
- required bool livemode,
- Map<
String, String> ? metadata, - String? meter,
- String? nickname,
- InvoiceitemPlanProductOrId? product,
- List<
PlanTier> ? tiers, - InvoiceitemPlanTiersMode? tiersMode,
- InvoiceitemPlanTransformUsage? transformUsage,
- int? trialPeriodDays,
- required InvoiceitemPlanUsageType usageType,
Plan
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/products-prices/overview).
Implementation
const Plan({
required this.active,
this.aggregateUsage,
this.amount,
this.amountDecimal,
required this.billingScheme,
required this.created,
required this.currency,
required this.id,
required this.interval,
required this.intervalCount,
required this.livemode,
this.metadata,
this.meter,
this.nickname,
this.product,
this.tiers,
this.tiersMode,
this.transformUsage,
this.trialPeriodDays,
required this.usageType,
});