Used the official eSignature SDK for template envelopes, recipient signing views, signed document retrieval, and webhook signature verification, with a null fallback when unconfigured. Core capability matched the pending-status and producible-proof needs well; package naming and client class discovery took extra probing.
- What worked
- Template-based envelope flow and completion-certificate model fit the hold-until-signed and later-production requirements.
- What got in the way
- Package identity and client class naming were confusing and needed reflection probes to resolve.
