pub struct SubscriptionSchedule {Show 18 fields
pub application: Option<Expandable<Application>>,
pub billing_mode: SubscriptionsResourceBillingMode,
pub canceled_at: Option<Timestamp>,
pub completed_at: Option<Timestamp>,
pub created: Timestamp,
pub current_phase: Option<SubscriptionScheduleCurrentPhase>,
pub customer: Expandable<Customer>,
pub default_settings: SubscriptionSchedulesResourceDefaultSettings,
pub end_behavior: SubscriptionScheduleEndBehavior,
pub id: SubscriptionScheduleId,
pub livemode: bool,
pub metadata: Option<HashMap<String, String>>,
pub phases: Vec<SubscriptionSchedulePhaseConfiguration>,
pub released_at: Option<Timestamp>,
pub released_subscription: Option<String>,
pub status: SubscriptionScheduleStatus,
pub subscription: Option<Expandable<Subscription>>,
pub test_clock: Option<Expandable<TestHelpersTestClock>>,
}Expand description
A subscription schedule allows you to create and manage the lifecycle of a subscription by predefining expected changes.
Related guide: Subscription schedules.
For more details see <https://stripe.com/docs/api/subscription_schedules/object>.
Fields§
§application: Option<Expandable<Application>>ID of the Connect Application that created the schedule.
billing_mode: SubscriptionsResourceBillingMode§canceled_at: Option<Timestamp>Time at which the subscription schedule was canceled. Measured in seconds since the Unix epoch.
completed_at: Option<Timestamp>Time at which the subscription schedule was completed. Measured in seconds since the Unix epoch.
created: TimestampTime at which the object was created. Measured in seconds since the Unix epoch.
current_phase: Option<SubscriptionScheduleCurrentPhase>Object representing the start and end dates for the current phase of the subscription schedule, if it is active.
customer: Expandable<Customer>ID of the customer who owns the subscription schedule.
default_settings: SubscriptionSchedulesResourceDefaultSettings§end_behavior: SubscriptionScheduleEndBehaviorBehavior of the subscription schedule and underlying subscription when it ends.
Possible values are release or cancel with the default being release.
release will end the subscription schedule and keep the underlying subscription running.
cancel will end the subscription schedule and cancel the underlying subscription.
id: SubscriptionScheduleIdUnique identifier for the object.
livemode: boolHas the value true if the object exists in live mode or the value false if the object exists in test mode.
metadata: Option<HashMap<String, String>>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.
phases: Vec<SubscriptionSchedulePhaseConfiguration>Configuration for the subscription schedule’s phases.
released_at: Option<Timestamp>Time at which the subscription schedule was released. Measured in seconds since the Unix epoch.
released_subscription: Option<String>ID of the subscription once managed by the subscription schedule (if it is released).
status: SubscriptionScheduleStatusThe present status of the subscription schedule.
Possible values are not_started, active, completed, released, and canceled.
You can read more about the different states in our behavior guide.
subscription: Option<Expandable<Subscription>>ID of the subscription managed by the subscription schedule.
test_clock: Option<Expandable<TestHelpersTestClock>>ID of the test clock this subscription schedule belongs to.
Trait Implementations§
Source§impl Clone for SubscriptionSchedule
impl Clone for SubscriptionSchedule
Source§fn clone(&self) -> SubscriptionSchedule
fn clone(&self) -> SubscriptionSchedule
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more