# DocuSign # DocuSign An electronic-signature vendor, integrated at the connector layer for signing ceremonies. DocuSign carries the signing ceremony: the document set, the signer order, and the certificate of completion. The integration exists as connector evidence, so the transport is written and the vendor sits under Connection. Signing order is declared rather than inferred, because some documents require a specific sequence between borrower, coborrower and settlement agent, and a ceremony that allows any order produces a package a closer has to reject. ## Products it serves - Connection ## How this integration is built - **connection configuration** — The wire protocol. One repository per vendor API call, not per vendor. - **language configuration** — The field mapping between the vendor's vocabulary and the canonical model. - **flow file** — The four-way translation: canonical request, vendor request, vendor response, canonical response. - **waterfall priority** — One line naming where this vendor sits in the vertical's ordering. - **status call** — Activating the vendor for a lender, optionally with the lender's own credentials. ## Evidence This vendor is on the roster because each of the following resolves to a committed artifact. - `docu-sign-product` - `leadoff-site-docusign-data`