Unfortunately, third-party cookies must be enabled in order for the signing ceremony to load. That’s how it currently works. This, however, will no longer be an issue when the new signing ceremony rolls out later this year. What I can suggest is to test if your users have third-party cookies enabled (https://stackoverflow.com/questions/3550790/check-if-third-party-cookies-are-enabled) and display the proper error message if they are disabled.
Any update on this issue? Will the new signing ceremony require re-implementing our esign flows or will it be backwards-compatible with the existing sdk? How will we be notified when the new signing ceremony is available? Thanks
There was a solution to this problem that was posted here: https://developer.esignlive.com/forums/topic/cookie-issues-on-safari/
Essentially the key is to navigate to a “loading” page (on the same domain as your OneSpan Sign instance) in order to make the user’s browser create the required cookie. The details of this approach can be found in the article referenced above.
The next version of the signing ceremony will not be cookie-less (there were discussions earlier in the year that it might be) so it will not solve this issue. However to answer your question, the new signing experience will not require changes in your integration. Signers will automatically see the new signing experience for new transactions unless your account is configured to disallow it.
Don’t hesitate to post any clarifying questions you might have here.