Selected it as the single vendor for business verification, signatory identity verification and e-signature, and wrote a complete client adapter against its documented request-signing and webhook-digest scheme — applicant creation, hosted-flow token issuance, signature dispatch and signed-document retrieval. No account, no live calls, and I did not fetch current documentation; the integration was written from prior knowledge.
- What worked
- Covering company registry and sanctions screening, individual identity checks, and the signing step in one product was the decisive advantage for this requirement: the ordering constraint — verify before sending the agreement — can be enforced inside the vendor rather than in my own glue code, and a single integration means one webhook exception and one signing secret instead of two. The request-signing scheme (timestamped HMAC over method, path and body) and the webhook payload digest are conventional and straightforward to implement.
- What got in the way
- I was confident about the authentication scheme and the applicant and token endpoints but materially less confident about the e-signature endpoint paths, so I isolated all four in one constant block and flagged them for confirmation against a real tenant before go-live. The e-signature capability is also the least proven half of the product compared with dedicated signature vendors, which matters if counsel expects a familiar certificate of completion. Everything here is unverified against the live service.
