The gate defaults to closed. Everything else follows.
Last updated: September 24, 2026
Most point of sale (POS) compliance is procedural: a checklist somebody has to remember to follow. We made it structural. The platform physically can’t disclose past an unclean file, can’t show a borrower math it didn’t compute, and can’t pull credit without the named person’s authorization. We built the architecture for zero-defect files.
Required-to-disclose services
In the loan officer workspace, four service orders have to clear before disclosures can launch: soft credit, hard credit, flood determination and the automated compliance review. The launch control names what’s outstanding and stays disabled until the list is empty. Closing costs gate the same file a second way: the Loan Estimate’s escrow figures come from an ordered fee schedule, and that calculation fails closed when there’s no schedule. On the borrower self-serve journeys, cash-out and purchase alike, flood, fees, escrow readiness and the compliance review all have to clear before the platform orders any disclosure.
Fail-closed compliance review
Where the review gates a file, it has to affirmatively clear. A failed review holds the file. A pending review holds the file. An errored review holds the file. We treat an error as a hold, never a shrug.
Deterministic math, one engine
The payment on the borrower’s workbench, the review screen, the disclosure package and the file in your loan origination system (LOS) all come from one deterministic calculation library. Same inputs, same outputs, and you can replay it after the fact. You can always reproduce a disclosed scenario exactly.
Consent, per person
We capture e-consent, credit authorization under the Fair Credit Reporting Act (FCRA), and e-signature for each person individually, including co-borrowers on their own devices. The records carry who, what and when. No pull, no signature and no disclosure happens on someone’s behalf.
Locked disclosure surfaces
A visual contract locks the screens where consent and disclosure happen, so re-branding, theming and white-labeling can’t restyle them. A regulator sees the same surface every borrower saw, in every tenant and every brand.
Append-only evidence
We write attribution and milestone records once and never rewrite them. Service orders keep durable transaction references. So when someone asks “what did the borrower see, and when?”, you can reconstruct the answer.
Honest recommendations are a compliance feature
We built the journey to only recommend a product where the borrower’s own numbers win. It shows the losing option next to the winning one and lets the borrower open the math and check it. That’s a conversion strategy, and it’s also exactly the posture you want the record to show. See how the journey behaves →
And no model is anywhere near any of it
Every gate on this page is deterministic code. No artificial intelligence (AI) or machine learning (ML) model produces, influences, or ranks any output that determines a regulated outcome: credit decisioning, pricing, valuation, adverse action, disclosure content or timing, or a servicing action. A continuous integration (CI) gate enforces that. It fails our build if a model endpoint ever becomes reachable, by import, from a regulated module. Since Fannie Mae Lender Letter (LL) 2026-04 took effect and Freddie Mac Guide §1302.8 came into force, your risk committee has to answer this about every vendor, so we answer it in full. The AI governance posture, including what the gate cannot see →
Apsis Line is a software platform, and we aren’t a lender. Nothing here is legal advice. Your compliance team owns policy, and our job is to make your policy structurally enforceable.
One note applies to everything above. The gate logic is real, built and tested, but the vendor services it orchestrates (credit, address verification, flood, fees and the compliance review) run simulated until a lender provisions live credentials for its deployment, and we label every simulated result that way. The same is true of the LOS connection: we built loan create and field read/write to the published contracts of Intercontinental Exchange (ICE), and none of it has run against a live Encompass instance yet. We never present a simulated service as live, on this page or anywhere else.
Bring your compliance officer. Seriously.
Watching the gate refuse an unclean file is the best thirty seconds of the demo.