Skip to main content
Question

SIGNATURE_PROVIDER_INVALID_NAME

  • December 13, 2024
  • 3 replies
  • 97 views

Forum|alt.badge.img+2

Dear all, 

We face an issue in Prod which is not existing in our Sandbox env. 

SIGNATURE_PROVIDER_INVALID_NAME The signature provider name specified is not valid. Invalid signature provider name

The name is  intesa_tsp_spid_dev 

Who can confirm what is the correct name for this signature in Production ? 

 

Thank you 

 

olivier 

3 replies

Hengfeng Ge
Rising Star
Forum|alt.badge.img+12
  • Rising Star
  • 511 replies
  • December 13, 2024

Have you add Signature Types in you production account?

you can check the Intesa in you demo account:

https://admindemo.docusign.com/signature-types

then go to production account whether add it. 

https://admin.docusign.com/signature-types

if not added it, you can add it by edit.

https://support.docusign.com/s/document-item?language=en_US&bundleId=xww1594245808169&topicId=pyd1688486325417.html&_LANG=enus

 

FreeLink/甫连信息

🌍 Docusign Partner | Partner Profile

🏆 Docusign 2024 APAC Reseller Growth Partner of the Year

🌟 The only Docusign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant.

📊 Docusign Community Leaderboard Top 5 contributor.

🚀 Expertise in Docusign integrations with on-premises systems for leading enterprises across various industries.


Michael.Rave
Docusign Employee
Forum|alt.badge.img+14
  • Docusign Employee
  • 929 replies
  • December 18, 2024

@Oli.M 

As ​@Hengfeng Ge mentioned, this is probably related to the signature type not being active in production. You need to add the signature type to your production account as described above.

If you don’t see the option to configure the signature types in your production account, it is likely that your current plan does not support the signature type and you may need to purchase an add-on to proceed.

I can also see from the signature type name, that this is pointing to the developer environment. It could be that you added the signature type correctly in production, but provided the wrong signature type name:

intesa_tsp_spid_dev

If you want to find out the correct signature type name in production, you can create a template in production, add a recipient and select the desired signature type. When you download the template and inspect the JSON file, search for “intesa” and you should be able to find the correct signature provider name.


Forum|alt.badge.img+15
  • Community Moderator
  • 2070 replies
  • January 3, 2025

​Hi ​@Oli.M,

 

I hope you are doing well.

I would like to confirm if the suggested solution answers your question?           

If so, please mark it as the best answer by clicking “Select as Best” to make it easier for other users to find. Otherwise, feel free to let me know and I will gladly help you address the situation as soon as possible.

 

Best regards,   

 

Alejandro R. | Docusign Community Moderator   

"Select as Best" below if you find the answer a valid solution to your issue!