Erasing Captured Signature on GuestLogin/Passcode entry/Emailclick in SignatHome

Hi Vijay, As you may have known, in order to erase the existing capture signature for a signer, you'd call:

GET /api/packages/{packageId}/roles/{roleId}

and grab all the response, and set the "signers"--"signatures"--"handdrawn" attribute as an empty string, then make a PUT request to the same API carrying this changed JSON, to update the signer information. But there're few technical challenges achieving your use case: (1)in order to make any API calls updating a package/signer, you have to first change the package status to DRAFT, after updates, you'd resend the package. This will break your workflow -- user will see "Package not accessible" error page during the package updating (2)there's no callback notification triggered by email click, guest login or QA/SMS code input So a potential solution is: change the URL behind the "Go to document" button in email, to an interface of your internal resource (you can use signer level message/ signing link as part of your url path to identify which package and which signer is trying to sign). As you can notify your application by email clicking now, you can update package as mentioned above and redirect the page to the actual signing ceremony, or simply embed the page into an iFrame for better control. If you think the workaround took too much code changes, you can consider set the package setting "enforceCaptureSignature": true, in which case, it forces signers to hand drawn every capture signatures. Duo