> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.middesk.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.middesk.com/_mcp/server.

# Verify business in Docusign

> Verify a signer's business name, address, and TIN against official records in real time, before a document is signed.

The Middesk app for Docusign verifies a signer's business name, address, and Taxpayer Identification Number (TIN) against official records while they complete an envelope. Middesk returns a pass or fail result to Docusign, so you can require valid business details before a document is signed.

This guide covers the one-time setup: install the app, connect your Middesk API key, and add verification fields to an envelope.

> **Note**
>
> This app supports US businesses. It requires a Middesk account and a Docusign eSignature account with the Premium DV add-on, or a Docusign IAM CX plan. Installing Docusign apps generally requires admin permissions.

## How it works

When a signer fills in the Middesk fields on an envelope, Docusign sends the values to the app. The app runs a single business lookup with Middesk and returns one of two outcomes to the signing session—pass or fail—usually within a few seconds. There is no partial result.

The signer can correct any issues by referring to the message highlighting checks that passed or failed.

The app decides pass or fail by applying an acceptance policy associated with the [verification levels](#understanding-verification-levels) you choose to the review tasks Middesk returns.

### Understanding review tasks

Middesk returns a review task for each verification with its own unique success, warning, and failure statuses that may require additional review.

| Review task                         | Success          | Warning                                            | Failure                                      |
| ----------------------------------- | ---------------- | -------------------------------------------------- | -------------------------------------------- |
| **Business Name**                   | Verified         | Similar Match, DBA Match                           | Unverified, Alternate Name                   |
| **Business Address**                | Verified         | Similar Match, Approximate Match, Incomplete Match | Unverified                                   |
| **TIN**                             | Found            | N/A                                                | Mismatch, Not Found, Duplicate, Unavailable  |
| **Secretary of State Registration** | Submitted Active | Submitted Unknown                                  | Submitted Inactive, Submitted Not Registered |

### Understanding verification levels

The app offers three verification levels. They use the same fields but apply progressively stricter rules for what counts as verified. Choose the level that matches your risk tolerance. Standard and Strict require a TIN; Flexible does not.

| Level        | Conditions required to pass                                                                              | Use case                                                                 |
| ------------ | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| **Flexible** | The TIN is confirmed, or both business name and address match.                                           | Low-friction flows where any one strong proof of the business is enough. |
| **Standard** | An active registration exists, and either the business name matches or the TIN is confirmed.             | The balanced default—a real, registered entity plus one identity match.  |
| **Strict**   | The business name matches, the TIN is confirmed, the address matches, and an active registration exists. | High-assurance flows where every detail must line up.                    |

> **Note**
>
> You may also see two older options, Businesses (Full Address) and Businesses with TIN (Full Address). For new envelopes, use one of the three levels above.

## How to set up Middesk with Docusign

#### Install the app from the Docusign App Center

Sign in to Docusign at [apps.docusign.com](https://apps.docusign.com), search for **Middesk**, and open the listing. Select **Install**, accept the permissions and terms if prompted, then choose the account to install into and confirm. The verification fields then become available in the envelope editor.

![Middesk app listing in the Docusign App Center](/_fern-img/42973c7525c45e0ad3d6160d101abb5c92ae1ea1b49ec44c1a6a2ef600602f25.webp)

#### Connect your Middesk API key

The first time you use the app, Docusign opens a **Connect Middesk** window.

To find your key, sign in to the Middesk Dashboard at [app.middesk.com](https://app.middesk.com) and go to **Settings → Credentials → API Keys**. Create a new key or copy an existing one. Live keys begin with `mk_live_` and verify against real records; sandbox keys begin with `mk_test_` and are available in the sandbox environment for testing.

![Creating an API key in the Middesk Dashboard](/_fern-img/2ab04005b00b7e1abec77570773564931c0a143d0fcb7a613ea09a11d808d5e6.webp)

Paste the key into the **Middesk API key** field, then select **Continue to Docusign**. Middesk encrypts the key at rest and reuses it until you disconnect or rotate it.

![The Connect Middesk window in Docusign](/_fern-img/8f9a27b7fb06a78d3a9c97762d25b10e939cca1a338f6dae758d88170ae65e7f.webp)

#### Add verification fields to an envelope

Start a new envelope, add your documents and recipients, and continue to the tagging screen. In the fields panel, open **Custom Fields**, select **Middesk**, and choose a verification type. Drag each field onto the document, assign it to the recipient who enters the business details, and send the envelope as usual.

The available fields are:

* Business name
* Full address
* TIN (labeled **TIN** in Docusign)

![Middesk verification fields added to an envelope](/_fern-img/27e45b4b0af9c6e5757c86af4774b2f93128d354d59093883fca839c431a5890.webp)

#### Choose a verification level

Set the field to Flexible, Standard, or Strict, depending on your risk tolerance. See [verification levels](#understanding-verification-levels) for the rules that have to be satisfied for each level.

#### Set what happens when verification does not pass

Configuration of the field in Docusign determines the behavior when a verification fails. When you place the field, you can either require the recipient to pass verification before they finish signing, or let them complete signing even when the business data was not verified so you can follow up later. Set this to match your policy.

![Data Verification settings for a Middesk field in Docusign](/_fern-img/192230fbb637394d4c40fc469ed4d425dc7efa02a8fee0f4718b1b34b2c49996.webp)

> **Get a demo**
>
> Contact your account manager or [contact sales](https://www.middesk.com/contact-sales) to inquire about access.