Subscriptions
Gain a better understanding of Digital River's subscription service along with how to define a business model and set up free trials
Last updated
Gain a better understanding of Digital River's subscription service along with how to define a business model and set up free trials
Last updated
Digital River offers a PSD2 and SCA-compliant subscription management service that automatically schedules and processes recurring payments. The service allows you to offer customers free trials and numerous ways to fund recurring transactions.
On this page, you'll find information on:
How you do subscription acquisitions depends on the checkout solution(s) you've selected. Use the following table to access the appropriate article:
| Checkout solution | Article |
|---|---|
Once the acquisition order containing the subscription is created, you'll also need to activate the subscription, fulfill the goods, and manage renewals. For details on how to handle these and other processes, refer to the Managing a subscription page.
You can share digital products among plans in the subscription service. We recommend not relying on SKUs to model subscription entitlements. We also suggest using different plans for your offerings since they can be used to model cohorts for reporting purposes.
Digital River's subscription service models recurring billing. It's not intended to model subscription access or entitlements. As a result, you cannot call the service to determine a customer's current access level.
Subscription metadata and client data linked to the subscription are useful for modeling details irrelevant to Digital River and within the plan's terms.
With Digital River's subscription service, you can either use SKUs or productDetails to define the basic and compliance data of any digital product you intend to offer on a subscription basis.
For more details, refer to Managing SKUs and Using product details.
Once you've built a product catalog, you should set up plans that define the behavior of your subscriptions.
At a minimum, you should specify a plan's name and terms, designate its contract length and billing frequency, set up renewal reminders, and configure its billing offset days and collection period days.
The following diagram shows how plans define the behavior of subscriptions that belong to them.
In a POST /plans request, you can set state to draft or active. If you're using Digital River as the system of record before deployment, you may decide creating draft plans is beneficial. We generate one for you if you don't specify a unique id in the create plan request.
A 201 Created response contains a unique plan identifier. The request also triggers an event with a type of plan.created. If the plan's state is draft when you're ready to launch, send its identifier as a path parameter in a POST /plans/{planId} and use the request's body to set state to active.
The plan must be active before you can add subscriptions to it. For details, refer to the Lifecycle of a plan and the Lifecycle of a subscription.
Subscriptions on discontinued plans continue to be renewed. Deactivating a plan, however, terminates all of its active subscriptions on their nextInvoiceDate.
When you want to discontinue or deactivate a plan, specify the desired state in the payload of a POST /plans/{planId} request.
If you attempt to create subscriptions that belong to discontinued or deactivated plans, an error is thrown during the acquisition checkout.
Refer to the Lifecycle of a plan and the Lifecycle of a subscription for details on how discontinuing or deactivating a plan affects its associated subscriptions.
You can configure a customer's subscription to start with a free trial period. This section provides information on defining trial and paid plans before deployment. How you handle subscription acquisitions that involve free trials depends on the checkout solution(s) you've selected. Use the following table to access the relevant content:
Once the acquisition order containing the subscription is created, you must convert it from trial to paid. For details, refer to Trial subscription management on the Subscription management page.
To offer free trials, you must configure plans for your trial subscriptions before deployment.
Refer to Defining plans for general information on plans and their relationship to subscriptions.
For each subscription you intend to offer on a trial basis, you should define a trial and paid period plan. The following diagram shows how you might set up two plans that result in a seven-day free trial period followed by a monthly, recurring billing cycle:
Your trial period plan controls the subscription's behavior during its first billing cycle.
The plan's interval and intervalCount determine the trial period's length. If, for example, you want to offer a 31-day free trial period, set interval to day and intervalCount to 31 .
For free trial plans, set billingOffsetDays to 0. This configuration results in a subscription whose initial billing cycle has the same nextInvoiceDate and currentPeriodEndDate, thereby ensuring that the first payment capture attempt occurs after the trial period ends.
The value you give reminderOffsetDays determines when the subscription.reminder event is created. For example, a reminderOffsetDays of 3 results in creating a subscription.reminder event three days before the trial period's conclusion.
Use collectionPeriodDays to define the number of days when Digital River will attempt to capture payment. Once the trial period ends, Digital River will initially attempt to charge the customer's designated payment source. If this proves unsuccessful, our billing optimization service will continue making capture attempts for the number of days you specify.
You must also define a paid period plan that governs the subscription after its trial conversion. The following plan bills customers monthly, and in every billing cycle, Digital River makes the first payment capture attempt three days before the end period date.
When setting up a payment in acquisitions or modifying a subscription's payment source, customers must select the payment methods they want to use for recurring transactions.
Refer to the Supported payment methods page for a complete list of such payment methods.
In acquisition checkouts, you can combine a reusable primary source with one or more secondary sources. Refer to the Managing sources page for details on combining primary and secondary payment sources.
To learn more about how you interact with subscriptions during checkouts, use the following table to access the appropriate article:
| Checkout solution | Article |
|---|---|
| Checkout solution | Article |
|---|---|
