swethabalda | Posts: 5

Signature is captured on one package is being applied to another package

Wednesday, March 7, 2018 at 12:51am
0 votes
Hello, We have a scenario where we load one package after other. While doing this, the signature captured in package 1 is being applied in the package 2. Can I know why it is happening so? Sample packages: package1 : rh10fIWXhqHYGr57RPJRHv62qoQ= package2 : 92C5fjhfr2GVDMz3AmY7YQRABQQ=
harishaidary | Posts: 1812

Reply to: Signature is captured on one package is being applied to another package

Wednesday, March 7, 2018 at 05:01am
0 votes
Hi there, Looking at both packages, I'll assume this is happening for the buyer. Looking at the package json, it seems that the "handdrawn" value is being passed when defining this signer, which should be empty if you want to capture the signature. Your colleague Nadiya recently emailed me about how to auto sign for senders and I showed her a workaround that uses this handdrawn value. Please verify your workflow with her.
swethabalda | Posts: 5

Reply to: Signature is captured on one package is being applied to another package

Wednesday, March 7, 2018 at 06:33am
0 votes
Are there any changes happened for the account. This was not the case previously.
harishaidary | Posts: 1812

Reply to: Signature is captured on one package is being applied to another package

Wednesday, March 7, 2018 at 07:20am
0 votes
I'm not aware of any changes for your account no. If not explicitly asked to our support team from your team, then there shouldn't have been any modifications.

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

LoginSign Up