Cycle Charged Event
This event is triggered when a subscription’s billing cycle is successfully charged.
A unique identifier for this specific event. This ensures that each event can be tracked and processed individually.
Describes the type of event. In this case, it signifies that a subscription billing cycle has been successfully charged.
The timestamp when the event was generated, typically in milliseconds since the Unix epoch (January 1, 1970). This value can be used to track when the event occurred.
A unique identifier for the specific subscription that was charged for the current billing cycle.
A unique identifier for the payment intent associated with this charge. This ID can be used to track the payment process and its status.
The amount charged for the current billing cycle, expressed in the smallest unit
of the currency. Here, 1500
represents 15.00 USD (as USD typically uses two decimal
places).
The currency used for the subscription payment. In this case, it is United States Dollars (USD).
A timestamp indicating the date and time of the next scheduled payment, expressed in milliseconds since the Unix epoch.
The number of billing cycles remaining for the subscription. For instance, if the
total cycle count is 6 and 2 cycles have been completed, the remaining cycle count
will be 4
.
A collection of key-value pairs that were provided when the object was created. These metadata values are echoed back in the response, allowing you to store and retrieve custom information such as context-specific attributes, references, or tags. This can be useful for correlating records in your system or attaching meaningful context to transactions.
Was this page helpful?