subscriptionInfo
.subscriptionInfo
can be used to hold data on:subscriptionInfo
configurations are autoRenewal
set to true
, the subscriptionId
that you may have provided during the acquisition and the billingAgreementId
from the acquisition order. You should also set the checkout's chargeType
to merchant_initiated
.autoRenewal
indicates whether subscriptions renew automatically or manually. During the acquisition of auto-renewing subscriptions, customers need to actively consent to automatic recurring billing. So, when autorenewal
is true
, customers must agree to have their payment information stored on file and then charged at the start of every billing cycle.‌freeTrial
to true
. To satisfy our reseller of record requirements, Digital River needs to know that payment details are being collected, even when no charge authorization occurs.‌freeTrial
also needs to be true
. For more information, refer to Using free trials.terms
hold the subscription's contractual agreement. These should be the Digital River approved terms displayed to customers during acquisitions. Prior to creating a subscription, your integration must acquire the customer's active acceptance of them. They define the subscription, provide links to Digital River's terms of sale and privacy policy, and stipulate that the customer agrees to store their payment information for use in renewals.subscriptionInfo
, we create a billing agreement and return its billingAgreementId
in the POST/orders
response.subscriptionInfo
(i.e., both are subscriptions), then Digital River generates two separate billing agreements and returns two billing agreement identifiers.‌billingAgreementId
is sent in all renewal requests. For those using a third-party subscription service, you need to retrieve billingAgreementId
from the acquisition order and pass it in all renewal requests.subscriptionId
. If you don't, we generate an identifier for you. In either case, the value uniquely identifies the subscription in our system.subscriptionId
. You must send your own value during the checkout process. In this case, whenever you process a renewal, its best practice to provide us the same subscriptionId
you sent during the acquisition.startTime
and endTime
. This data helps Klarna's risk engine make an accurate assessment of a transaction's validity, thereby improving conversion and acceptance rates.‌startTime
and endTime
, make sure you adhere to the date/time standard used in the Digital River APIs. If either value is improperly formatted, you receive a 400 Bad Request
with an error code
of invalid_parameter
.startTime
as the current date. The endTime
should be the startTime
+ the subscription duration, also known as the payment schedule. The payment schedule is how often customers pay for their subscription. As an example, customers might have a year-long subscription that they pay monthly. We treat the subscription duration and payment schedule as equivalent.‌startTime
of an annually billed subscription is 2021-07-07T13:47:13Z
then set endTime
to 2022-07-07T13:47:12Z
. For a monthly recurring subscription with the same startTime
, you would set endTime
to 2021-08-07T13:47:12Z
.‌startDate
and endDate
in each request, until the customer cancels.‌