BoldSign Blogs

  If a signer uploads an ID document during BoldSign identity verification flow, you can later download that same image through the Identity Verification APIs. This is for developers building KYC, onboarding, healthcare, or legal workflows who must access uploaded ID documents, even when automated verification fails. In this guide, you’ll see exactly how to get the fileId from the Identity Verification Report and then use it with the Identity Verification Image API to download the image stream, with code samples in multiple languages. What is BoldSign identity verification and when is it useful? BoldSign Identity Verification is a signer authentication feature that adds an identity check to your eSignature workflows. It: Validates whether a signer is who they claim to be before they can access or sign a document. Works with flows where verification requests are delivered via email, SMS, or WhatsApp delivery modes. Lets signers upload government-issued IDs for proof-of-identity ch...

  The real problem is not switching platforms. It is switching safely. If you are running Docusign in production today, you already know migration is not a weekend project. Your codebase does not just call Docusign. It relies on a connected set of behaviors such as signing flows, template and field mappings, webhook based status updates, and downstream logic triggered by document lifecycle events. If any of those behaviors change during migration, problems can surface quietly. Signatures may be delayed. Webhook handlers may stop firing. Downstream systems may receive events they do not recognize. The challenge was never “can we build a BoldSign integration?” It’s “can we replace Docusign without disrupting what already works?” That is exactly what the Docusign to BoldSign Migration Skill is designed to help with. In this blog post, we will walk through how it supports a safer migration. Why teams are migrating now Docusign’s pricing has become a growing concern for teams, especial...