fleblanc's account

There was a solution to this problem that was posted here: https://community.onespan.com/forum/cookie-issues-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.

Thank you Duo. This is not critical but thanks in advance for your help in submitting issue reports internally!

Yes, data such as <FieldId1> will be injected in the template's document before sending the transaction for signature. To make this happen, put a label (if you want a read-only field) or a text field (if you want to allow the signer to edit the field) on your document and give a name, e.g. "MyField". Then in your CSV file, put a column with the same name.

Please reply if that does not work or if you have any clarifying questions.

In order to get audit data from a transaction, you need to issue a GET request to https://{onespansign}/api/packages/{packageId}/audit

For instance, GET https://sandbox.esignlive.com/api/packages/KpbteuYB0jQoRrFOp1ugyOcpYCI=/audit

Don't forget to include your API key in the appropriate header, e.g.

Authorization: Basic {your_api_key_here}

You should get back a JSON payload.

I am assuming you are familiar with PHP and issuing RESTful calls in PHP however please reply if you are hitting any issue.

Previous comment was actually from Manoj but received via secure email and copied here for ease of reference.