The DigiFi platform includes a built-in integration with DocuSign, a leading electronic signature provider.
You can set up this integration to use DigiFi's e-sign feature, which lets you trigger e-sign processes from the "Documents" tab of applications. This causes DocuSign to start an email-based signature flow with the borrower. Once that flow is complete, the signed file is automatically retrieved and stored as a document in the DigiFi platform.
To integrate DocuSign's API, you'll need both a regular account and a developer account.
To generate your developer account credentials, start by signing in to your DocuSign developer account.
Select "Settings" from the top menu, scroll down until you see the "Integrations" section and then choose the "Apps and Keys" option. You'll be navigated to that page.
On the "Apps and Keys" page, click the "ADD APP AND INTEGRATION KEY" button. In the popup window that appears, enter "App Name" and click "CREATE APP".
You should now be able to see your app with the generated Integration Key.
To do this, first construct a URL value matching the following syntax:
The text fields "UPDATE1" and "UPDATE2" should be updated by you per the instructions below.
- UPDATE1 (client_id): Put your integration key here (from Step 1).
- UPDATE2 (redirect_uri): The address you want DocuSign to redirect your users for their e-signature consent.
You can check to make sure the the redirect_uri (from UPDATE2) is set up properly by:
- Clicking "Actions" and choosing "Edit" from the dropdown list.
- Scrolling down and finding the "Additional Settings" section.
- Ensuring that you redirect_uri (above) is on the list of "Redirect URIs".
If it's not there, add it to the list using the "+ ADD URI" button.
After you constructed the link with the corresponding values, copy it into your web browser's address bar and press "Enter" on your keyboard. You will see the page where you need to accept the consent. After pressing “Accept” the system redirects you to the "redirect_uri" address you put into the initial link.
In this step, you'll add your DocuSign credentials to the DigiFi platform. To get started, open DigiFi and navigate to Company Settings > Developers > DocuSign.
To update your credentials:
- Click the "Edit Credentials" button.
- Add your DocuSign credentials (details below).
- Click the "Save Changes" button.
Form fields details:
- "DocuSign Environment" is either "Developer Mode" or "Production Mode". For now, select "Developer Mode".
- Account Base URL should be set to "https://demo.docusign.net" for testing.
- Integration Key should be from DocuSign.
- User ID should be from DocuSign.
- API Account ID should be from DocuSign.
- RSA Private Key should be from DocuSign.
Your DocuSign Integration Key, User ID and API Account ID can all be found from the "Apps and Keys" page.
Your RSA Private Key must be generated. To generate it:
- Click the "Actions" button and select "Edit" from the list of options. You will be navigated to a new page.
- Scroll down until you find the "Service Integration" section and click on the "+ GENERATE RSA" button.
- A popup window will open that contains the RSA Private Key. Copy it into the DigiFi platform.
Create DocuSign Templates.
For this, open your DocuSign account and navigate to “Templates” on the navigation bar. Customize a new template by adding fields you require for the e-signature process.
Use Custom “Text” field type in DocuSign
Only the custom “Text” field type can be used for “Field Mapping” in DigiFi. You can assign different types of variables to “Text” fields (ex. Number, Date, Text, Phone, Email). The format will be automatically recognized and applied to your template.
After you’ve created e-sign templates within your DocuSign account, you can import them into DigiFi.
To import a template to DigiFi:
- Navigate to the "Templates" tab of the DigiFi platform.
- Click the "Import Templates" button.
- Select which templates you want to import to DigiFi from DocuSign.
- Click the "Import Templates" button.
After you’ve imported templates, you need to map DocuSign recipients to DigiFi entities and the DocuSign data fields to variables (i.e. data fields). This lets the DigiFi platform know what data to pass into the DocuSign integration when it runs.
If your DocuSign integration requires the borrower's name, you can map the "Borrower First Name" and "Borrower Last Name" variables to the template.
To map your DocuSign template, click on it in the table. You'll then see two sections:
- In the "Recipient Mapping" section, choose who should receive the e-signature request when it is sent. This section lets you map DigiFi entities (e.g. borrower, co-borrower, intermediary) to the recipients that you set up in DocuSign.
- In the "Field Mapping" section, choose which variables should be populated from DigiFi into the DocuSign template.
Once you have completed this mapping process, toggle the activation button (beside the page title) to "Activated" to make the template available for use in the DigiFi platform!
After completing Step 4, your DocuSign integration should now be working (using your "developer" credentials).
Please refer to the How To Use DocuSign E-Signature section for details on using DocuSign once it is configured. This process can be followed to test DocuSign for a specific loan application.
After you have successfully tested your DigiFi-DocuSign integration, you need to go through the following steps to activate your production account:
- Log in to your full DocuSign account.
- Complete the DocuSign go-live process instructions, which you can find here.
- Get user consent for the production account. To do this repeat Step 2 from the Test Environment section but replace the base URL with "https://account.docusign.com/oauth/auth".
- Change the "DocuSign Environment" field in DigiFi to "Production Mode" and update the "Account Base URL" field to the specific value that will be displayed on the "App and Keys" page of your DocuSign account after finishing the go-live process.
Updated 4 months ago