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

Community User | Posts: 8831

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

Wednesday, March 7, 2018 at 12:51am

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=

March 7 Created

March 20 Last Updated

8 years ago Last Reply

3 Replies

45 Views

1 Users

0 Likes

0 Links

Community User | Posts: 8831

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

Wednesday, March 7, 2018 at 05:01am

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.

Community User | Posts: 8831

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

Wednesday, March 7, 2018 at 06:33am

Are there any changes happened for the account. This was not the case previously.

Community User | Posts: 8831

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

Wednesday, March 7, 2018 at 07:20am

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.