subscriptionInfo hash table. As reseller of record, Digital River is required to collect the basic information contained in this data structure. subscriptionInfo in the LineItem array. You can add subsciptionInfo to the POST/carts, POST /line-items, or POST /line-items/{lineItemsId} requests. The following POST/carts request includes the subscription parameters related to auto renewals, free trials, and the terms displayed to the customer. You can also provide the subscription and the billing agreement identifiers. POST /carts/active, POST /line-items, POST /line-items/{lineItemsId}, and POST /submit-cart , and GET /orders (if available). To get the billingAgreementId, submit the cart.billingAgreementId and a chargeType of merchant_initiated in the POST /carts request. transaction (MIT) to add a subscription would look like this:autoRenewal parameter to tell us whether the subscription is automatically or manually renewed. If true, customers must have agreed to have their card information stored on file and charged at the start of every billing cycle. To do this, you must, at a minimum, attach a Source to the payment option associated with the subscription and make sure the Source is reusable. false, then the customer needs to manually renew the subscription by resupplying payment date. You can facilitate this by creating a new instance of Drop-in to collect the payment source. freeTrial attribute to true. Digital River needs to know that credit card details are being collected, even when a charge does not occur.terms parameter to provide the subscription's auto renewal terms that are displayed to the customer at the point of acquisition.subscriptionId and passes the value in a POST/carts request. subscriptionId you provided at the point of acquisition. If the values don't match, we treat the request as a subscription acquisition rather than a renewal. subscriptionId attribute will be deprecated. For this reason, and to ensure you are PSD2 compliant, we recommend you use the billing agreement identifier to process subscription renewals. subscriptionInfo hash table in a POST/apply-shopper request and include billingAgreementId. billingAgreementId in the POST /submit-cart response.POST/submit-cart request contains two line items and both have a subscriptionInfo hash table, then Digital River creates two separate billing agreements and returns two billing agreement identifiers.billingAgreementId that is returned in the response. This is so that you can later provide the value when renewing the subscription. billingAgreementId you persisted with that subscription. Then, you should include the value in the subscriptionInfo hash table of a POST Cart request. billingAgreementId when renewing the subscription, even if the customer is using a different credit card to pay for the transaction. billingAgreementId for future renewals.commitmentPrice hash table appears when you get a product by identifier. A commitmentPrice is the committed purchase price for a loan or subscription.