Prepaid subscriptions

After enabling prepaid subscriptions, you will be able to use all prepaid endpoints to control the prepaid subscription

Prepaid subscriptions data

The field called prepaid_subscription_context is present on subscription objects. It represents the information about the subscription the customer prepaid. In cases where the subscription is not a prepaid subscription, this field will be null.

Those are the additional fields in a prepaid subscription:

  • prepaid_orders_remaining: An integer value representing the number of shipments the customer is still owed before their prepaid subscription should renew. For example, if the value of this field is 0, the next order placed that contains an item for this subscription will renew the prepaid subscription.
  • prepaid_orders_per_billing: An integer value representing the length of the prepaid subscription cycle in terms of number of shipments the customer will receive per instance they are billed. For example, if the value of this field is 3, that means they are billed for 3 shipments every time they are charged and will receive 2 shipments free of charge for each occasion they are charged.
  • renewal_behavior: A string field representing what action will occur when the customer has received their last free shipment. Currently, the only possible values for this field are “autorenew” and “cancel”.
    • autorenew: Renew and bill the customer a full prepaid cycle after all orders are placed. This happens when the first order of the next cycle is placed.
    • cancel: Cancel subscription when all orders are placed.
    • downgrade: Turns the prepaid subscription to a normal subscription when all orders are placed. The next order placed for the subscription will have the price of a single shipment.