Testing Business Accounts

Overview

There are two ways to test business verification in Glide. The path you use depends on whether your financial institution (FI) has received access to its own Middesk dashboard.

• Build Your Own Test Profiles: For FIs with their own Middesk dashboard. Create sample businesses and choose their verification results in Settings → Sandbox Configuration.

• Legacy Sandbox Credentials: For FIs that have not received their own Middesk dashboard and are still using the legacy sandbox. Use the existing test values in the table below.

1. Build Your Own Test Profiles

Use this path if your FI has received access to its own Middesk dashboard and Glide staging is connected to that account’s enhanced sandbox.

A test profile is a simulated business record with the information and results you choose. These are test application values, not dashboard usernames or passwords. Create profiles in your FI’s own sandbox before using them; the examples below are recommendations and are not automatically installed in every account. Do not assume that the legacy names or TINs in section 2 will produce the same results here.

Step 1: Sign in and select Sandbox

Sign in to Middesk with your individual dashboard login. Check that you are in your FI’s account, then change the environment selector from Live to Sandbox. Use your Glide staging application for testing.

Step 2: Open Sandbox Configuration

Open Settings, select Sandbox Configuration, and click Create configuration. On a narrow screen, open the navigation menu first. If the tab or create button is unavailable, contact your FI’s Middesk administrator or your Glide team.

Step 3: Enter the business information

Enter a unique Business name and a complete Office address. Choose an Entity type and enter a test TIN. Add a DBA or associated person if your scenario needs one. Record the exact values so other testers can reuse the profile.

For the example below, use Glide Demo Verified LLC, 123 Main St, San Francisco, CA 94103, entity type LLC, and TIN 987651001. These are synthetic sandbox inputs only.

Step 4: Choose the TIN and registration results

Next to the TIN, click Select outcome. Select Found for a business TIN match; Person match is available for person-based scenarios. Choose the Domestic SOS registration state and Registration status. For this example, select California and Active. Add a foreign registration or formation date if needed.

Step 5: Add address risk flags, if needed

Click Add risk flags beside the office address. Options include CMRA (Commercial Mail Receiving Agency), PO box, Registered agent, Virtual mailbox, and Undeliverable. Leave these unset for the successful-verification example. Start with one risk flag at a time so the result is easy to interpret.

Step 6: Select the attributes to simulate

Click Next step. On Select attributes, choose the findings you want to simulate for the business or associated people. The screen includes adverse media, bankruptcy, litigations, liens, watchlists, and industry classification. Leave all attributes unchecked for the successful-verification example. For a business watchlist scenario, select Business under Watchlists and complete any additional list-selection prompts.

Selecting an attribute does not enable or order the corresponding service. The service must also be available on your account and included in the test order.

Step 7: Save the profile

Click Create registration. If a People Data step appears for your selected person attributes, complete the required synthetic person details and finish the remaining prompts. Confirm that the business appears in the Sandbox Configuration list before testing.

Step 8: Run and review a test

Submit a new business application in your FI’s Glide staging environment using the saved profile’s exact business name, address, TIN, and relevant person details. Follow the intentional name difference described below only when testing a TIN/name mismatch.

Review the KYB checks in Glide and, when enabled, select Open in Middesk to inspect the associated sandbox report. You can also use Place order directly in Middesk’s Sandbox to check a profile; that alone does not test the complete Glide application flow. Include any additional service required for your scenario.

Verify the individual checks you intended to test. A successful business verification does not guarantee automatic application approval; other checks and your FI’s review rules still apply. If results differ, confirm the account, Sandbox selection, saved input values, enabled services, and Glide staging connection with your Glide team.

Five recommended test profiles

Create these profiles separately in your FI’s Sandbox Configuration. Unless stated otherwise, use 123 Main St, San Francisco, CA 94103, entity type LLC, a California / Active domestic registration, TIN outcome Found, no address risk flags, and no selected attributes. Use a unique TIN for each profile. Add the test signer as an associated person if you also want to test that person’s link to the business.

1. Successful verification — Glide Demo Verified LLC
   TIN: 987651001. Use the default setup above and submit the same business details. Expected: matching business name, address, and TIN, with an active registration and no configured watchlist hit. Use this as the baseline before testing exceptions.

2. Business watchlist hit — Glide Demo Watchlist LLC
   TIN: 987651002. Under Watchlists, select Business and choose the SDN list when prompted. Submit the saved business details. Expected: a business watchlist finding. Use it to practice investigation and the dismissal/comment workflow for a simulated false positive, then check the corresponding result in Glide.

3. TIN/name mismatch — Glide Demo TIN Reference LLC
   TIN: 987651003. Save this reference business with outcome Found. In the test application, intentionally submit Orchid Bicycle Repairs LLC with the same TIN and address; do not create a second configuration for that submitted name. Expected: the TIN is associated with the reference business, producing a TIN/name mismatch. Other name checks may also require review.

4. Address risk — Glide Demo CMRA LLC
   TIN: 987651004. Select CMRA under Add risk flags; keep the other defaults. Submit the saved business details. Expected: a CMRA address-risk finding. Use it to practice reviewing a business that uses a mail-receiving address.

5. Inactive registration — Glide Demo Inactive LLC
   TIN: 987651005. Set the California domestic registration status to Inactive; keep the other defaults. Submit the saved business details. Expected: an inactive domestic Secretary of State registration requiring review.

Start with one exception per profile. Once you have confirmed the individual outcomes, create additional profiles that combine the conditions your team needs to practice.

2. Legacy Sandbox Credentials

Use this path if your FI has not received access to its own Middesk dashboard and your Glide staging environment still uses the legacy sandbox. These are the existing sandbox test values. Enter one or more of the values below in a staging application to generate the corresponding scenario. They are not a setup checklist for Sandbox Configuration.

Applicant and signer identity verification

For the applicant, use the Leslie Knope test credentials to pass Plaid Identity Verification. The existing sandbox guidance uses ZIP code 46001 to pass identity verification for signers. Plaid identity verification is separate from the Middesk business profile; use test identities only in staging.

Example Sandbox Business Attributes

You can combine legacy values to create a scenario with multiple outcomes. For example, use 423 Grand St., New York, NY 10013 for an approximate address match and J Doe for an unverified person. Additional services, such as liens, must be included in the order package to return results.

If your FI moves to its own enhanced sandbox, follow Build Your Own Test Profiles above instead of relying on this table. Contact your Glide team if you are unsure which path applies.