Description:
Credit integrations can be added and managed entirely by an Admin (Company, Region, or Branch level). Once an integration is connected, you can tailor credit behavior for your organization by toggling credit settings that apply across all credit integrations. This gives your team control over where and when credit can be ordered, and what borrowers and loan officers can see throughout the process.
Steps to Resolve:
Web:
Who Can Do This:
A user with Company, Region, or Branch Admin privileges. Integrations apply to all regions, branches, and users unless they are overridden at a lower level.
What You’ll Need Before You Start:
Adding a credit integration requires credentials and connection details issued by your credit provider. Have the following on hand before you begin:
- Credit username — the account username provided by your credit vendor
- Password — the account password for that credit vendor
- API Key — the key issued by the credit provider for API access
- URL — the endpoint/service URL for the credit provider
- Any additional required information — some providers require extra fields (e.g., account/branch identifiers). Confirm these with your credit provider ahead of time.
Important: If you don’t have these details, contact your credit provider to obtain them before starting. The integration cannot be completed without valid credentials.
Step 1: Navigate to Integrations
- Open Company Settings from the left navigation.
- Select the Integrations tile (under “Manage integrations”).
- On the Integrations page, locate the Credit tile. This tile shows how many credit integrations are currently enabled. Path: Company Settings → Integrations → Credit
Step 2: Add the Credit Integration
- Open the Credit tile, then select Add Integration (the + Add button is on the Integrations screen).
- In the Add Integration dialog, choose the API Type.
- Select the Vendor (this list populates based on the API Type selected).
- Select Continue.
Enter the connection details you gathered earlier — username, password, API Key, URL, and any additional provider-required fields.
- Save the integration.
Once saved, the Credit tile will reflect the newly enabled integration in its count.
Step 3: Configure Credit Settings
The Settings section on the Credit page applies to all credit integrations. Toggle these on or off based on how you want credit to behave for your company:
| Setting | What It Does |
|---|---|
| Allow Credit Order On Applications | Enables credit ordering on applications. |
| Allow Credit Order On Loans | Enables credit ordering on loans. |
| Enable Credit Liabilities | Enables a loan officer’s ability to view credit liabilities after a credit pull. |
| Run Credit On Loan App Submission | When a borrower or co-borrower submits a loan application with valid credit auth and a credit integration exists, the borrower’s credit report will run automatically. Use Edit to set the pull type (e.g., Soft or Hard). |
Tip: Toggle each setting according to your company’s preference. These settings are independent — for example, you can allow credit ordering on loans without automatically running credit on loan app submission.
Note: The credit Settings section applies to all credit integrations. Integrations apply to all regions, branches, and users unless overridden at a lower level.
Solution:
After completing these steps, your organization will have a fully configured credit integration ready for use across your applications and loans. Admins can control exactly where and when credit can be ordered, whether credit automatically runs upon loan application submission, and whether loan officers can view credit liabilities after a pull. Because these settings are independent of one another, you have the flexibility to configure credit behavior in a way that fits your company’s specific workflow — whether that means requiring manual credit orders or automating the process entirely at submission. Since integrations apply company-wide by default, be sure to coordinate with your Region and Branch Admins if more granular overrides are needed for specific teams.
Published: 11/19/2026 Last Update: 11/19/2026