Disclosures, compliance statements, and emails
Learn more about the standards related to displaying Digital River policies, notices, and terms.
Last updated
Learn more about the standards related to displaying Digital River policies, notices, and terms.
Last updated
The and in this section cover how to display the Digital River policies, notices, and terms necessary to maintain compliance. This includes displaying the proper localized text and links on various pages in your integration and doing the same in customer email notifications.
Click any checklist item to see more detail on how to meet the integration standard.
These integration standards relate to disclosures and compliance statements:
Your integration must have a that automatically retrieves and renders the required links to Digital River's policies, notices, and terms in the footer of all checkout pages.
When you pass this compliance element to the method, you can include two parameters: locale and entity. By specifying these parameters, the compliance element returns localized text and hyperlinks.
In some regions and locales, additional disclosures may be required. For your convenience, they are also returned by the compliance method.
On the review order page of your checkout flow, use resellerDisclosure.localizedText and resellerDisclosure.url to both display and provide a link to Digital River's reseller disclosure.
On the same page, use confirmDisclosure.localizedText to provide Digital River's terms and display a checkbox control to acquire the customer's active acceptance of those terms.
The optional locale sets the language of the disclosure information presented to the customer. The required entity should be the Digital River that is facilitating the transaction. During the checkout process, retrieve the and sellingEntity.id returned by the and then passed these values to the createElement() method.
In the footer of all your checkout pages, you should use the to render the required links to Digital River's policies, notices, and terms. Each url returned by this method is contained within an easily identifiable hash table (such as termsOfSale, privacyPolicy or legalNotice) that simplifies placement.
At certain stages in the order life cycle, your integration should respond to by sending email notifications to the customer. At a minimum, you should email the customer when the order is confirmed, cancelled, shipped, and refunded. Either or in , you can configure webhooks to detect these events, and then your integration can respond by emailing the customer.
Customer emails must also contain the required disclosures, similar to those in the , that you retrieve with the
The article (click for access information) provides a complete list of the required and recommended subscription-related notifications and what should be included in each.
When customers purchase an auto-renewing subscription, you must disclose the terms and acquire the customer's active acceptance of them. For more information on the specific disclosures that are required, refer to the article (click for access information).