arathore

How to Add Remote Signing with the existing Imperson Signing process Using API

0 votes
Hello, We are using Impersonate Signing process with eSignLive for one of our client, now client needs to use both Impersonate and Remote Signing (use anyone of for a particular transaction) for same Account. to achieve this we need documentation or examples how to achieve following: For Remote Signing:
  • How to activate the RemoteSigning using API using .Net.
  • How did a Platform(sent the packet to eSignLive) get notified in case of any person got eSign complete, is there any service URL need for client.
  • Any changes required in current eSignLive account.
Please help us in this update. Thanks, A. Rathore

Reply to: How to Add Remote Signing with the existing Imperson Signing process Using API

0 votes
Hi Aniket, For #1, when you say "Remote Signing", do you mean that signer receive email notification and get access from email link vs signing through sender's account and be in person(imperson signing)? If so, you don't need to activate it, that's a default way OneSpan Sign will deal with the transaction. When you use imperson signing, I believe you are currently using .WithInPerson()in your setting like below, so you can simply remove that and it's a remote signing.
 DocumentPackage package = PackageBuilder.NewPackageNamed("Test - Signing Ceremony Customization - " + DateTime.Now)
                                        ...
                                        .WithSettings(DocumentPackageSettingsBuilder.NewDocumentPackageSettings()
                                            .WithInPerson()
                                            )
                                        .Build();
For #2, you can use our callback notification to have your platform informed. You can have an url monitoring callback notifications(POST request) sending from OneSpan Sign. There’s an event named “Recipient completed signing”, you can select this event in your Web Portal and the below is the body of the request you will receive:
{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"SIGNER_COMPLETE","sessionUser":"44aafb7c-97b9-40e1-bb59-eb76c7d2a484","packageId":"5n4obeO8jYoPp126Cm-Y3fxdfbo=","message":null,"documentId":null,"createdDate":"2018-06-30T20:12:12.272Z"}
If you want to follow this path, I can share with you more related documents and examples. For #3, as we discussed above, the remote signing method is a default way OSS deal with packages, so you don't need to do specific setting to your account. If I misunderstood your point, please let me know. And hope this could help you! Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: How to Add Remote Signing with the existing Imperson Signing process Using API

0 votes
Hi Duo, Thanks for quick reply, please see updates below. 1# Yes, Remote signing means signer receive email notification and get access from email link. 2# Please provide more details about eSignLive callback notification, so that we can setup Notifications for packets. Thanks, A. Rathore

Reply to: How to Add Remote Signing with the existing Imperson Signing process Using API

0 votes
Hi Aniket, Sure, with pleasure. You can set up your callback url, callback key and the events you want to monitor at your web portal interface or using code to have these set. (guidance here) So once the monitored events are triggers, "Recipient completed signing" for example, OneSpan Sign will send a POST request to your listener url with your callback key as "Authorization" attribute in request header if it's set. The request body will be like below:
Create a new Package:
{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_CREATE","sessionUser":"18EZDL44xgsX","packageId":"wVdZEaPD2igwUnFGJBjDD0dpO7k=","message":null,"documentId":null,"createdDate":"2018-06-30T20:04:55.384Z"}

Send a package
{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_ACTIVATE","sessionUser":"18EZDL44xgsX","packageId":"5n4obeO8jYoPp126Cm-Y3fxdfbo=","message":null,"documentId":null,"createdDate":"2018-06-30T20:09:50.425Z"}


Signer 1 accept consent document
{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"DOCUMENT_SIGNED","sessionUser":"44aafb7c-97b9-40e1-bb59-eb76c7d2a484","packageId":"5n4obeO8jYoPp126Cm-Y3fxdfbo=","message":null,"documentId":"default-consent","createdDate":"2018-06-30T20:10:51.002Z"}


Signer 1 sign a signature block
{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"DOCUMENT_SIGNED","sessionUser":"44aafb7c-97b9-40e1-bb59-eb76c7d2a484","packageId":"5n4obeO8jYoPp126Cm-Y3fxdfbo=","message":null,"documentId":"7caf46cdd75f7a411bf8c22793b84fa79d8d180becc40691","createdDate":"2018-06-30T20:12:12.256Z"}


Signer 1 finish his part
{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"SIGNER_COMPLETE","sessionUser":"44aafb7c-97b9-40e1-bb59-eb76c7d2a484","packageId":"5n4obeO8jYoPp126Cm-Y3fxdfbo=","message":null,"documentId":null,"createdDate":"2018-06-30T20:12:12.272Z"}


Package Complete:
{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_COMPLETE","sessionUser":"e00696ec-d6f5-4feb-89c5-a5ce002a6c66","packageId":"5n4obeO8jYoPp126Cm-Y3fxdfbo=","message":null,"documentId":null,"createdDate":"2018-06-30T20:15:01.038Z"}


Signer 1 opt out:
{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_OPT_OUT","sessionUser":"b5381b13-991e-4179-9f9b-d4e1ec9d06bb","packageId":"J5tyJalzG49hmDho5b9JdG61T7M=","message":"the personal info is not correct","documentId":null,"createdDate":"2018-06-30T20:16:29.763Z"}
There's also a blog where you can find example codes for building a controller with url exposed and handling with callback body. Hope this could help you! Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off