Disclaimer / IPO
Disclaimer
IPO
When a company is about to be listed on the stock market the process for this is called IPO (Initial Public Offering), which means that the company offers their shares to the public for new investors.
On the company's website there is usually an IPO page which holds information and documents regarding the offer.
During the IPO-process there are certain rules and regulations, where one of them is that they are obligated to put certain information behind a Disclaimer wall on the website to prevent the information to directly be accessed. This falls into the MFN press releases, where certain press releases must be behind a wall.
Disclaimer wall
The disclaimer is a simple HTML form, often containing two dropdown menus where the user selects the country they reside in and the country that they're currently in.
After they've selected the country and continue, the next step will show important information which the user needs to confirm to be able to then be obligated to access the release.
When the user has confirmed they are either redirected to the IPO-page (which holds the release PDF) or directly to the single press release page.
Disclaimer information and structure
How the disclaimer is structured and which options and information it includes can differ depending on the project. We do not provide this information as this is maintained by the IR-representative of the company.
Technical implementation
There are no specific "has too's" regarding the technical implementation so there's no need for any complicated logic, just that the data needs to be hidden from view on the website until the user has clicked through and confirmed the Disclaimer.
To simplify the implementation of the disclaimer, we ask the customer to add a custom "disclaimer"-tag to the releases that needs to be behind a disclaimer (In the MFN API the custom tag is called cus:disclaimer).By doing this it is possible to pick up the tag in the integration and to show the disclaimer for the certain releases that has the tag, but still allow direct access to regular releases.
Additionally, we've added logic to some of our integration methods to support the disclaimer tag and redirect to a specified disclaimer url depending on the custom tag - For example we've added support in our MFN Loader. However for pure API integrations the disclaimer "redirect logic" needs to be built and managed outside of MFN.
MFN Loader redirect-configuration for Disclaimer
We've added two parameters to the MFN Loader config.
disclaimer_redirect_tag: 'cus:disclaimer',
disclaimer_redirect_url: 'disclaimer.html'
In the MFN Loader-package we provide an example disclaimer HTML-form (disclaimer.html) that shows how the disclaimer could be implemented, to make it easier to getting started.
Summary
So when it comes to the integration of the disclaimer we do not have a complete solution as it differs from integration to integration. However we try to make the process as smooth as possible and we provide help and guidance on how it works and should be implemented.
Last updated
