Skip to main content
A loan origination system (LOS) integration lets loan teams order and monitor verifications from the loan file while borrowers complete the required payroll or banking connections. Loan origination systems integrate with Argyle.

​
Verification workflow

  1. The loan officer orders the required verification products for the borrower.
  2. Payroll and banking orders send or launch the appropriate user session.
  3. The borrower connects the requested accounts at their direction, or the loan team uploads documents for Doc VOI.
  4. The integration tracks each verification independently.
  5. Completed reports and supported source documents are routed to the loan file.
Use the Verifications Guides for the API lifecycle.

​
Product status

Each requested product can complete, require action, or fail independently. Do not combine payroll, banking, and Doc VOI into one status when the LOS supports product-level status. Use the verification status object to determine the next action:
  • Continue waiting while processing is active.
  • Return the borrower to the existing active verification when connection steps are incomplete.
  • Surface verification errors and their current remediation.
  • Retrieve the report when the verification is complete.

​
Reports and documents

When a verification reaches completed or completed_with_errors:
  • Retrieve the report PDF from report.file_url.
  • Retrieve report JSON from report.json_url when available.
  • Retrieve supported payroll documents through the Payroll Documents API.
  • Retrieve uploaded source files through the User Uploads API.
Route files to the LOS document categories required by the integration rather than relying on report names alone.

​
Re-verification

Use Re-verification for updated payroll, banking, or Doc VOI results. An active connection can support a refreshed verification without borrower action. When updated authentication is required, create the appropriate new session and return the borrower to the existing account.

​
Notifications

Use the LOS event model for loan-team notifications and Argyle webhooks for backend lifecycle state. Keep these responsibilities separate:
  • LOS events notify operators inside the loan system.
  • The verifications.updated webhook updates the verification record and report readiness.
  • Account and resource webhooks support direct-data workflows.

​
Supported integrations

For another LOS, confirm ordering, status mapping, report routing, and document mapping requirements before implementation.