The questions lenders ask first.
Is Apsis Line a lender?
No. Apsis Line is a software platform — a mortgage origination point of sale and workspace. It does not originate, broker, or fund loans, and it does not make credit decisions. Your institution remains the lender; your LOS remains the system of record.
Does it replace our LOS?
No — the opposite. Apsis Line is an intelligent middleware layer built above the LOS you already run. It pushes complete MISMO 3.4 applications into the LOS, orders vendor services through the LOS’s service channels, and generates disclosures through it. It maximizes the investment you already made in the LOS rather than duplicating it.
We don’t run Encompass — can we still use Apsis Line?
Yes. The platform is LOS-agnostic by architecture: it speaks MISMO 3.4, the industry-standard interchange every major LOS accepts, and every vendor connection is an adapter seam. The integration is deepest today on ICE Encompass — application push, Partner Connect service orders, disclosure generation — and other LOS platforms wire through the same seams. If you run something else, that is an integration conversation, not a disqualifier.
How does the compliance gate actually work?
Disclosures hard-gate on six required services: credit authorization and pulls, address verification, flood determination, closing fees, and an automated compliance review. The review must affirmatively clear — a failed, pending, or errored review holds the file. There is no code path where an ambiguous result passes through. The same gate holds on the borrower self-serve journey and the loan officer workspace.
What does the borrower actually see?
A self-guided journey that feels like a conversation with a seasoned loan officer: their real numbers (live home-value estimate, soft-credit balances with consent), an honest side-by-side of their options, math they can open and check, and e-sign disclosures at the end. A borrower who wants a human at any point gets one, with the file intact.
Can it run white-label under our brand?
Yes. Tenancy is configuration, not code: your brand, palette, program overlays, and vendor connections resolve from a registry entry, and borrower traffic runs under your domain. The disclosure and consent surfaces are deliberately excluded from theming — those stay visually frozen for every tenant.
Where do vendor credentials live?
Server-side only, in managed environment configuration and vaults. No API key or OAuth secret ever ships to the browser. Every vendor result is labeled with its source, and the server — never the client — decides whether a call is simulated or live.
What happens to a self-serve application that stalls?
It appears in the loan officer workspace pipeline with everything intact — entries, consents, service results. The LO continues the file rather than restarting it. Stalled journeys can also be re-engaged automatically with the context the borrower left behind.
How long does an evaluation take?
A first walkthrough is about thirty minutes: the borrower journey end-to-end, the workspace, the compliance gate refusing an unclean file, and the push to the LOS. Deeper integration evaluation — field mappings, service orders, security review — is typically run under NDA with your team.
Something we didn’t cover? Ask us directly →