Can you mix-and-match remote authenticated signing with in-person signing within a single signature package?Monday, March 27, 2023 at 09:11am
Hello, we currently are using e-signature packages (created using the RESTful API) where all signers are fully remote e-signers. Signers must be authenticated by the combination of access to the e-mail address we specify for them plus SMS-based code authentication at the cell phone number we specify.
This, of course, requires that all signers have a verified, private e-mail account and verified, private cell phone number that we have on file for them.
I am interested in using a mix-and-match approach within a single signature package where some signers use the remote authenticated signing approach above and some are able to use in-person signing.
This would allow one or more in-person signers to either come into one of our locations or one of our staff be with the signer in person at their business or home and we do in-person identity verification before handing the signer a phone or tablet with this signer's custom URL (with this URL containing this signer's URL auth token code we have generated) to complete their signing event. In this case, there are no e-mail or SMS messages involved at all for this signer.
I have been examining this OneSpan blog post, which is the best reference I have found for in-person signing:
However, this page only describes the case where all signers in a signature package are in-person.
In addition, the setting to use "eSigning" or "In-Person eSigning" (pic below) is set at the package level, not at a per-signer level. This suggests a single package can only be all of one approach or all of the other.
I would like to ask if OneSpan supports creating a single signature package where some signers using the fully remote/e-mail/SMS authentication signing path and some signers use the in-person authentication signing path?
And are there any documentation pages on doing this?
Pic: UI for creating a new signing package