Skip to main content
The BillingPlan object describes the amount and schedule for recurring charges. Product objects describe the products or services that you sell. Both objects can include a Price. Note: An AutoBill object includes a BillingPlan, and an array of AutoBillItems. An AutoBillItem includes a Product, and the number of cycles the Product is to be included on the AutoBill. For more information, see the AutoBillItem Subobject in the Subscribe API Guide. For example, a business that sells access to online magazines—which cover different topics and are supported by different websites, but offer a standard subscription plan—might want to create a single BillingPlan that offers a one-month free trial, followed by a recurring bill of US19.95orC19.95 or C22.40 per year. Note: Although multiple Billing Plans can be created dynamically, as shown in the following example, our best practice recommendation is to create stable BillingPlan objects that can be used when individual customers subscribe. The Subscribe Portal allows you to create and manipulate BillingPlan objects through a user interface. See the Subscribe User Guidefor details.

Create a Billing Plan with a one-month free trial, followed by a recurring bill of US19.95orC19.95 or C22.40 per year

Note: Once subscriptions have been activated in the system (that is, an AutoBill object that uses a particular BillingPlan object becomes active), do not make changes to the underlying BillingPlan object, other than to change the BillingPlan Cycle amounts. For all other changes, create a new BillingPlan object. The BillingPlan object supports several information-only attributes, such as endOfLifeTimestamp and status. These attributes can be used to sort or categorize your customers. For example, you can fetch all BillingPlan objects, and display only those objects for active customers, or for customers whose end-of-life time stamp has not yet passed. Note: Billing Plans can be processed in currency or tokens, but not in both. For example, you might set up your environment to support several token types (such as downloads and storage) and charge 50 downloads per month for access to the system. For details on how the BillingPlan object affects entitlements, see Creating Entitlements. Billing Plans can also be used to grant Seasonal Entitlements, using the SeasonSet object. For example, Create a 4-installment seasonal Billing Plan for the next 3 summers. The initial purchase must result in 2 free weeks, but subsequent years should not include a free period. (This is controlled using “skipInitialFreeWhenRepeating.”)

Create a Billing Plan with an attached Season Set

Parent topic:Working with Billing Plans