Ryan_Coleman

Notary Handdrawn values question

0 votes
Guys, I am seeing some weird results when trying to change the notary capture signature. Can you please fill me in on each of these items and if they are working as intended. 1. Notary Capture Signature not using the most current capture signature after being updated. EX: I updated the Notary capture signature value to look like a script signature. I then uploaded a package with that Notary on it. I then updated the Notary signature again to something different and proceeded to upload another document package with the same Notary. Since I updated the notary in OS with a new handdrawn value, both packages, which haven't been signed at this point, should have the same Notary capture signature value. I went in and sign the first package that was created with the script looking signature and it shows the script looking signature. Then I went into the second package that was created with a different signature and that different signature was on the page. Since I updated the Notary after I sent both packages, should both packages have the exact same signature as they were not signed prior to updating the Notary? Below are the examples of the two packages in our sandbox. First PackageID: EcY2ow_VENDSTAzfdyrUK0CpbMQ= Second PackageID : NdUNhrxhWdMN7lndnbbCtRdvK0U= 2. If the Notary Capture Signature is blank in the system and I upload a handdrawn value for the Notary is my JSON package, why is this not overriding what is currently in the system? EX. I cleared out the value of the Notary Capture Signature. I then uploaded a package with the handdrawn value of the Notary set. When I logged in as the Notary, the signature was not uploaded. When I tried to sign the document as the Notary, the signature capture was also blank. Isn't this value suppose to override what is in the system, for this specific package?

Reply to: Notary Handdrawn values question

0 votes
Hey Ryan, This only happens with the notary? If you do any of these changes with a regular signer, everything works as intended?

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: Notary Handdrawn values question

0 votes
Right now this is only happening with Notaries because we do not have the ability to change account settings for a user that isn't created. Since we do not create accounts for the other signers, we cannot update their info.

Reply to: Notary Handdrawn values question

0 votes
I guess I should have asked this in two ways. One would be for the sender on your account signing in a transaction that's not a notary, if you are experiencing the same as a notary within your account (sounds like you don't have these). And the second would be when you provide the handdrawn data for an individual signer within a particular transaction (don't have to have a user in your account to provide sample signature data for any signer). You've tested neither of those outside the notary then, I'll take it, based on your last post?

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: Notary Handdrawn values question

0 votes
That is correct. I've tested neither of those two situations only because we do not use the sender/owner accounts for signing and all other accounts should be notaries.

Reply to: Notary Handdrawn values question

0 votes
Okay. I'll test this and get back to you. :)

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: Notary Handdrawn values question

0 votes
Okay. For scenario 1, above, the signer in the package, even if it's a person on your account is created with the signature that existed at the time that the transaction was created. That's why you're seeing this. It's consistent with all senders. I doubt this will be considered a bug because of the ability to upload a particular signature for a signer when you create a package. Unfortunately, the only way to get around this would seem to update the signer on any transaction created prior to updating a signature. You could submit an enhancement request with [email protected]. For scenario 2, it should sign the transaction with whatever data is associated with the signer in your JSON. If you updated the handdrawn property of the signature for the signer (not the package owner info) this should show in the signing of the transaction, but would not update the sender's profile. I think I am understanding this correctly. If you're seeing something different, could you please upload some sample JSON that shows how you're adding the data to the transaction? Thanks,

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: Notary Handdrawn values question

0 votes
Michael, Scenario 1 - I expected these results so it isn't really that big of a deal to work around, for our purposes. Confirmation is always good. For Scenario 2, yes I am seeing different results. I am going to run more test samples today but I will contact support soon as I can give good examples where I empty the signature capture for one of our Notary users, upload a package with a handdrawn value, then sign the documents with no capture signature. Thanks for the help.

Reply to: Notary Handdrawn values question

0 votes
Sounds good. Let me know what you find. If I find any other info on this, I'll post it here, as well.

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


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