> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Embedded signing functional process flow

> **Note**
>
> This page describes functionality for the older eSignature SOAP API. See [How to request a signature through your app](/docs/esign-rest-api/how-to/request-signature-in-app-embedded) for more information on this topic in the more actively-supported eSignature REST API documentation.

This overview of a typical embedded document-signing transaction should familiarize Docusign Connect API users with terms and process. It is not a faithful reproduction of how the process is implemented on the web site or in the API. In this use case, a web user applies for credit from an online lending source that provides an instant credit decision and also electronic signature services.

![Embedded Signer Example Diagram](/_fern-files/_img/f6531b2d845ab9230283b4467fd3ab15b2205528e8965826e34f52eb8bc89bce.webp)