Handling external subscription acquisitions
Gain a better understanding of how to do acquisitions and manage recurring billing with a third-party subscription service
Last updated
Gain a better understanding of how to do acquisitions and manage recurring billing with a third-party subscription service
Last updated
If you're not using , you can still use the Digital River APIs and to handle recurring billing, display and acquire acceptance of a subscription's terms, and comply with mandates.
Integrations that use a third-party subscription service can:
Supply an upstream
Use to maintain SCA compliance
Flag a subscription as a
Use the to ensure that appropriate payment methods are displayed
Persist a subscription's
Specify a subscription's .
During subscription acquisitions, you need to:
Customers can create a new source or authenticate a saved source to fund a recurring transaction.
Before , a subscription acquisition must contain:
A customerId
that references an existing .
A that is and saved to the referenced .
A that is , thereby indicating that the customer actively participates in the acquisition process.
In addition, each in the that has :
Can use or to represent a
Must set to true
Must contain the subscription's
During acquisitions, you must disclose a subscription's terms and then acquire the customer's active acceptance of them. How you do this depends on whether you're using or .
For more details on required disclosures, refer to the article (refer to for access information).
In , set each subscription line item's to true
. In the method's configuration , set to true
.
These settings prompt to display the combined autorenewal and save payment agreement.
If customers click the without agreeing to the terms, Drop-in prevents the transaction from proceeding.
If the customer consents and a is successfully created, then the event's data
contains the agreed-upon terms (mandate.terms
) and the time the customer accepted those terms (mandate.signedTime
).
If you're using DigitalRiver.js, you can present our standardized subscription terms and save the payment agreement by calling the , retrieving autorenewalPlanTerms.localizedText
and then displaying that text with an appropriate acceptance control. Your code should be written so customers can accept these terms before the checkout can proceed.
You should then pass autorenewalPlanTerms.localizedText
to mandate.terms
in the method's configuration object.
If you configure your workflow correctly, then the customer-accepted autorenewal terms are returned in the event's data
or the response to the method.
In either case, retrieve mandate.terms
and use this value to set each of the . This ensures that the subscription's terms are added to the .
For details, refer to the on the page.
Once the checkout's is , and all are met, . At that point, Digital River generates a and returns its billingAgreementId
in the response.
When the is , notify customers that their subscription acquisition has been successfully processed. In the article (refer to for access information), you can find a complete list of what is required in this notification.‌
For details on auto-renewals and updates, refer to .