> 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 # Loan application use case > See how Docusign for Developers tools and technologies can turn a complex loan application process into a streamlined experience. Lending is a cornerstone of the financial industry and a mission-critical process for many businesses. For developers building solutions in this space, it’s about more than just processing a transaction. It’s about empowering businesses to acquire and retain customers by offering flexible financing options. The customer journey—from the moment a user applies for a loan to managing their account—is deeply integrated with a business’s core systems and customer touch points. This presents an opportunity to build seamless digital experiences that not only expedite the loan process but also enhance customer engagement and trust. The right tools can help you build solutions that turn a complex, regulated process into a streamlined experience that delights both businesses and their customers. These solutions can integrate the loan application process with an organization’s core systems that handle customer relationship management (CRM), loan processing, storage, digital onboarding, marketing, analytics, and compliance. ## The developer challenge Integrating a business’s loan application process with its core systems is a complex project that involves far more than merely creating an online loan application form. Developers must consider the following challenges when creating a truly integrated solution: * **Multiple loan scenarios:** Depending on the business or financial institution and the available loan types, the solution must be able to offer different loan application forms, collect various types of information, include additional forms, and route the completed application package to different personnel for review, approval, and funding. * **Identity verification:** When a financial institution requires a customer to verify their identity during a loan application process, it’s not simply a matter of policy. It’s a fundamental requirement for legal compliance, fraud prevention, and risk management. This process, referred to as Know Your Customer (KYC), is a cornerstone of global Anti-Money Laundering (AML) and Counter-Terrorist Financing (CTF) regulations. Each institution has its own KYC requirements, which are often risk-based. * **Data integrity and validation:** The information the customer enters must be accurate and complete. Information about existing customers may be cross-checked against internal records, and new customer information must be validated against external sources or may require in-person reviews. * **Export of customer information:** Storing the completed form as a static PDF or other file type isn’t enough. The customer’s information and the terms of the loan must be transcribed into the business’s systems of record, such as its CRM platform, core system, and imaging system. The export of this information can trigger downstream services to enable straight-through processing. * **Self-service:** An ideal solution would enable customers in as many scenarios as possible to open accounts, fill out loan applications, and update their personal information without supervision or input from staff. In many cases, business rules can automate loan review and approval. * **Compliance:** Any solution should meet legal requirements for customer signature, document retention, fair lending practice disclosure and adherence, verification of financial means to pay, and audit trails. Building an app that handles all this can be costly and time-consuming. With [Docusign for Developers](https://www.docusign.com/blog/developers/streamline-end-to-end-agreement-management-with-docusign-a-developer), your organization can make use of existing components that meet these requirements. ## How Docusign for Developers can help Docusign for Developers includes a number of technologies that directly address the needs of developers building loan application processes that connect with their internal platforms. Let’s review these technologies and how each of them can be used for this purpose: ### Workflow Builder [Workflow Builder](https://www.docusign.com/products/platform/workflow-builder) is a powerful, no-code orchestration tool that enables you to create customizable workflows to automate any agreement management process. Within a workflow, you can collect data from your user; create branching rules based on that data to collect data for different loan types or set different routing rules for approval and funding; call external systems to share, store, and validate that data; verify the user’s identity; present forms to your user and have the user complete and electronically sign them; and export the final completed application to business systems and cloud storage. The [Workflow Builder API](/docs/workflow-builder-api) gives you programmatic control over your workflows so you can integrate them into your solutions. You can use the Workflow Builder API to trigger, monitor, and manage workflows from your application. ![Loan application workflow](/_fern-files/_img/f3029759b903ca31d8b49cd613fae5823485bc13ea785328071160d2fb437fc8.webp) ### Web Forms and the Web Forms API [Web Forms](https://www.docusign.com/products/web-forms) is a no-code form designer and management tool that lets you build and present online forms to collect information from your users, then use that data as you wish. You can build stand-alone web forms or create them from an eSignature template. Data from template-based forms can be populated automatically in an eSignature envelope that a customer reviews and signs. With the [Web Forms API](/docs/web-forms-api), you can create web form instances to present to your users and get status information on their progress. This enables you to trigger web forms from your application and integrate them into your application’s flow. You can choose to host a web form in your application, redirect the user to Docusign to view the form, or send the form via email for the user to fill out. ![Loan application web form](/_fern-files/_img/29a67f00e0d27a833d2c378527e574eb3f7736ef8cfd8a48951fa404cb54cc4c.webp) ### Private extension apps [Extension apps](/extension-apps) are a way to import your functionality into Docusign itself, enabling Docusign features to access your systems. While many extension apps are public (available to all Docusign users), Docusign also lets you publish extension apps *privately,* only to those Docusign accounts you designate: this lets you build extension apps that access your own internal systems without compromising their security. Extension apps are designed to be triggered at specific steps in Docusign agreement processes, so you can work them into a simple e-signing experience or a sophisticated agreement workflow. So, what can you do with extension apps? A lot: * [Data IO extension](/extension-apps/extension-apps-101/supported-extensions/data-io): This extension connects Docusign with external data sources. With data IO, you can retrieve customer data, say from your CRM platform, and prepopulate web forms with it; take data input from customers and send it back to your CRM platform; and store it for access in later steps in your workflow. * [Connected fields extension](/extension-apps/extension-apps-101/supported-extensions/connected-fields), [data verification extensions](/extension-apps/extension-apps-101/supported-extensions), and [Connected Fields API](/docs/connected-fields-api): These features let you validate user-supplied data against a source of truth. In the context of loan applications, you can use the connected fields extension to validate your customer’s input on their loan application against your system of record. Beyond validating simple data such as their address or phone number, you can use this extension to, for instance, confirm whether they already have an account, live in an area serviced by your business, or belong to a list of blocked individuals or of those who qualify for improved loan terms. The data verification extensions each verify a specific type of value, such as a bank account number or Social Security Number, using a verification service. While the connected fields extension and data verification extensions send data for validation, the Connected Fields API lets you discover which data items in your agreements map to information you can validate against your own or external data sources. * [File output cloud storage extension](/extension-apps/extension-apps-101/supported-extensions/file-output-cloud-storage): This extension can be triggered from a Workflow Builder workflow to automatically write completed loan applications and loan agreements to a cloud storage system. To meet business requirements, the documents can be stored to a specified cloud storage location using an appropriate naming convention. ![File output workflow step](/_fern-files/_img/8547d2473b7c98bf2fde2a12637c63325e1a7128f2e1014db53368cc2376cde9.webp) ### Docusign for Salesforce Docusign has tools to closely integrate your solutions with the leading SaaS CRM platform on the market: * [Docusign eSignature for Salesforce](/docs/salesforce) lets you send, sign, track, and save agreements in Salesforce. * The [Apex Toolkit](/docs/salesforce/salesforce101/apex-toolkit) lets you build Docusign solutions in Apex, Salesforce’s own integration language. * The [Salesforce extension app](https://apps.docusign.com/app-center/app/2d576583-520a-41e2-886b-089fefe733a1) lets you run Docusign agreement processes within your own solution while keeping your Salesforce data current. You can use the Salesforce extension app to enable your workflow to poll Salesforce for existing customer data to prepopulate forms, and then write new or updated customer data back to Salesforce. ![Workflow Salesforce step](/_fern-files/_img/cbe39222f20abfb35b08ec7cc36df891b0f4c40f21937896abcfda3b2a9ef53e.webp) ### Workspaces and the Workspaces API Loan applications are one example of an agreement process with complex procedures, multiple documents, and any number of participants in different roles: the customer, the joint applicant, the sales agent, the loan officer, the underwriters, and more. [Workspaces](https://www.docusign.com/products/workspaces) are designed to simplify complex scenarios like this by creating a single digital interface with all the necessary documents and with participants’ roles defined, enabling you to upload documents, assign tasks, and track the progress of everything in the process. The [Workspaces API](/docs/workspaces-api) gives your application access to all these functions programmatically, enabling you to create workspaces, add and update users, assign roles and tasks, and pull status information. ![Loan application workspace](/_fern-files/_img/3c53fe4d060401b12d7d47d8b584e25aec060654ed818fdb364ed830e991523b.webp) ### Docusign Identity Verification and the ID Evidence API [Docusign Identity Verification](https://www.docusign.com/products/identify) is a suite of tools designed to securely and efficiently confirm the identities of individuals signing documents electronically. It integrates advanced technologies to ensure that the person signing is indeed who they claim to be, thereby enhancing trust and compliance in digital transactions. The [ID Evidence API](/docs/idevidence-api) lets your application track the success of identity verification and retrieve the identity documents the user presents for verification. This is a key element of compliance with the applicable legal requirements for your business, industry, or location. ![Identify verification workflow step](/_fern-files/_img/426fda83e13669b5a5452e6199e5db2eabc69000de042201d9ff62e12de62049.webp) ## Resources for implementing your solution #### High-level overviews * [Workflow Builder overview](https://support.docusign.com/s/document-item?bundleId=yff1696971835267\&topicId=dnx1696972415150.html): Get an introduction to workflows and access educational resources. * [Workflow Builder API overview](/docs/workflow-builder-api): Start here for information about the API that enables your app to trigger and manage workflow instances. * [Web Forms overview](https://support.docusign.com/s/document-item?language=en_US&_gl=1*1u34way*_gcl_au*ODczOTUxNTUwLjE3MjcyOTgwNDc.\&bundleId=gmi1660583110357\&topicId=ofz1660589243255.html): Get the basics about Web Forms and review the documentation. * [Web Forms API overview](/docs/web-forms-api): Find out how your app can call this API to create web form instances and deliver them to your customers. * [Connected fields extension overview](/extension-apps/extension-apps-101/supported-extensions/connected-fields): See how to use connected fields to validate any data you choose against external sources of truth. * [Data IO extension overview](/extension-apps/extension-apps-101/supported-extensions/data-io): Learn about the data input and output flows that can retrieve and update data on an external system. * [File output cloud storage extension overview](/extension-apps/extension-apps-101/supported-extensions/file-output-cloud-storage): See how file output requests function during workflow configuration and execution. * [Apex Toolkit overview](/docs/salesforce/salesforce101/apex-toolkit): Learn how to develop Docusign integrations that work in Salesforce. * [Workspaces overview](https://support.docusign.com/s/document-item?bundleId=bmb1723842049882\&topicId=ovf1725900699633.html): Discover Docusign Workspaces and learn how the UI tool works. * [Workspaces API overview](/docs/workspaces-api): Get your bearings and learn how the Workspaces API can help you create and manage workspaces. * [ID verification overview](https://support.docusign.com/s/document-item?bundleId=ced1643229641057\&topicId=zfu1578456528197.html): Learn about the types of identity verification available in Docusign products. #### Walkthroughs with sample code * [How to trigger a Workflow Builder workflow](/docs/workflow-builder-api/how-to/trigger-workflow): Programmatically initiate a workflow instance populated with customer-specific information from your back-end system. * [How to create and embed a web form instance](/docs/web-forms-api/how-to/create-embed-web-form-instance): Create a web form instance and embed it in your appʼs HTML using the Docusign JS library. * [Seamlessly integrating Workflow Builder with data systems using data IO extensions](https://www.docusign.com/blog/developers/seamlessly-integrating-maestro-with-data-systems-using-data-io-extensions): Integrate external data sources with automated workflows that save time and eliminate errors. * [Reducing manual agreement work, part 1: Automating file export to cloud storage](https://www.docusign.com/blog/developers/automating-file-export-to-cloud-storage): Implement a solution that reliably and securely writes customer files to your cloud storage system. * [Secure, verify, comply: Automate identity checks with Docusign APIs](https://www.docusign.com/blog/developers/automate-identity-checks-with-docusign-apis): Combine workflows, API integrations, and extension apps to create a secure, flexible identity verification flow. #### Example applications with repos * [Workflows sample app](https://workflows.sampleapps.docusign.com/): This app showcases how to get workflow definitions and trigger workflow instances from your integrations. * [Web Forms sample app](https://webforms.sampleapps.docusign.com/): Three loan application scenarios show how to leverage the Web Forms API to collect customer information. * [Data IO reference implementation](https://github.com/docusign/extension-app-data-io-reference-implementation): This repo shows you how a data IO extension app supplies data model information and responds to read and write requests. * [File output cloud storage reference implementation](http://github.com/docusign/extension-app-file-output-cloud-storage-reference-implementation): With this repo, you can review file output requests and responses and see how file output works when invoked from a workflow. * [Salesforce Apex sample app](https://salesforce.sampleapps.docusign.com/s/): This app models how a financial institution can use the Apex Toolkit to build a customer portal hosted through Salesforce. * [Healthcare sample app](https://healthcare.sampleapps.docusign.com): A medical records scenario demonstrates how Docusign ID verification ensures that private information is shared with only authorized parties. #### Videos * [How to trigger and embed Docusign Workflow Builder workflows with Bash & code launcher](https://www.youtube.com/watch?v=ZjvjTIO6B4A): Trigger and embed a workflow using Bash and the Docusign code launcher. * [How to set up a reference implementation](https://youtu.be/_4p7GWK5aoA?list=PLXpRTgmbu4oqnHn6pusz4riseJHKZ42HW): Set up and run an extension app reference implementation. * [Write files to cloud storage from Docusign workflows](https://www.youtube.com/watch?v=OLj2RJtVYLQ): Implement a custom solution that generates agreements and writes them to a cloud storage system. * [Custom data verification for eSignature flows with Connected Fields API](https://www.youtube.com/watch?v=lI1GpCzaO4g): See how to generate agreements and verify their values against a system of record. * [Using the Docusign Salesforce extension app in a workflow](https://www.youtube.com/watch?v=WEs-jGUY1Dw): See how this extension app connects and shares data with Salesforce from your workflows. * [ID verification developer deep dive](https://www.youtube.com/watch?v=E3ztq3erEnw): Learn how Docusign solves identity verification challenges for developers.