I'm curious if we are checking the box regarding demonstrable consent with our E-Sign solution. (Wolters Kluwer)

Banker creates an electronic package to be delivered to the customer. This package consists of PDF documents.
Customer receives an email that an electronic package is available for e-signature, but first must register.
Upon registering user ID/password, next step is consent with all the applicable language etc. This consent is provided web-based, not as a PDF. Customer can click on "I consent" or "I do not consent."
Upon consent, the customer MUST view the electronic package before 'e-signing' the document.

During testing, some users can click on the electronic package and view through a pdf viewer on the webpage (in google chrome for example), while others click on the document and then have to open the document as a PDF. Clearly this is based on user settings, which we have no control.
My question is, since the consent is web-based in all instances, but the documents are sometimes opened via Adobe, are we missing the demonstrable consent piece?

Seems to be lacking to me: consents electronically, or confirms his or her consent electronically, in a manner that reasonably demonstrates that the consumer can access information in the electronic form that will be used to provide the information that is the subject of the consent;

This is precisely why Congress added the "test drive" requirement to ESIGN. If there's any possibility that the customer's equipment and applications could fail to open e-documents containing federal disclosures that must be delivered "in writing", then that equipment and the necessary applications should be tested as a part of the consent process.