LendEasy/DocsLMS + Servicing·v1
Start integrating
GuidesSelf-ServiceWhite-label borrower apps

White-label borrower apps

The borrower experience ships white-label: your name, your domain, your palette — with LendEasy's payment integrity, e-sign ceremony, and human-staffed messaging underneath.

The borrower experience ships white-label. Your name in the header, your domain in the address bar, your palette on every screen — and underneath it, the same payment integrity, evidence discipline, and servicing plumbing as the rest of the platform. Tenant branding resolves to design tokens at runtime; per-tenant subdomains and custom domains are first-class, and each tenant’s data lives in its own database.

What borrowers do

Surface What it delivers
Dashboard A triage-ordered home: what needs attention first — a due payment, a document request, an unread reply — before anything decorative.
Loans Each loan with its schedule, activity, statements, and autopay state on URL-addressable tabs.
Payments A deliberate multi-step payment ceremony: amount, method, review, explicit authorization — with idempotent submission so a retry can never double-charge.
Autopay Enrollment and management with the advance-notice language shown where the borrower authorizes, not buried in terms.
Payment methods Bank and card instruments, added and verified before they can move money.
Agreements & e-sign A plain-language summary before the legal text, scroll-gated review, per-item acknowledgements, a typed signature bound to the exact document digest, and step-up verification — decline and request-a-change are given equal weight with sign.
Documents Statements and letters to download; secure upload for requested documents, landing directly on the workflow that asked.
Messages Chat-styled conversation threads with your servicing team.
Assistance A structured entry point for hardship and payment help that opens a real servicing case — not a contact form that goes nowhere.
Notifications & settings Delivery preferences, profile, and security controls.

Messages are people, by design

Portal messaging is staffed by your team. Inbound messages become interactions on the borrower’s case, routed through the same smart queues as every other channel; Arya extracts intent and schedules the follow-up, Cookie drafts the reply — and a person decides and sends it, behind a per-recipient compliance check. Service-hours messaging sets honest expectations about when a reply will come.

Integrity details borrowers never see

The craft is in what cannot go wrong. The UI derives no money facts — every balance, due amount, and progress figure comes from the authoritative source, and the progress bar counts payments made rather than re-computing dollars. Payment submissions carry caller-minted idempotency keys reused across retries. Failure states are designed, not discovered: a payment hold, an agreement-digest mismatch, and an unavailable core each render a specific, honest state instead of a spinner. Past-due renders amber, not red, and no status ever rests on color alone.

Staff access without impersonation risk

Support staff can see exactly what a borrower sees through read-only masquerade: capability-gated, invisible to the borrower, fully audited, and delivered as a single-use staff-bound grant. Nobody types a borrower’s password, and nobody browses with write access.

Everything on this page runs on the self-service API — the same surface you would build on to replace any screen of it with your own.

Unified search across guides, recipes & the API referenceEsc