Tenant isolation
Independent institutions operate inside isolated tenant scopes with branch-aware business access.
Knowledge base
Practical guidance for visitors, borrowers, institution owners and operating teams—without publishing deployment secrets, private customer data or internal security credentials.
Fastest route
Read the complete user manualGuides
Every guide below points into the public manual so new users can learn the system without needing access to a private company workspace.
The full public operating guide for borrowers, institutions and specialist staff. It can be printed or saved as PDF from your browser.
Open manualRegistration, assessment profile, supporting evidence, consents, funding requests, offers and active-loan management.
Borrower guideCompany registration, governance, branches, staff roles, lending products, finance setup and operational training.
Institution guideFrom application and affordability assessment through approval, disbursement, repayment, restructure, settlement and recovery.
Lending guidePayments, treasury, collections, accounting, reconciliation and recurring reporting guidance for controlled financial operations.
Finance guideTenant boundaries, roles, audit evidence, encrypted storage, safe error handling and privacy-aware operating rules.
Security guidePublic documentation explains how users should operate securely without revealing private deployment details, credentials or sensitive internal diagnostics.
Mobile privacy noticeIndependent institutions operate inside isolated tenant scopes with branch-aware business access.
Authorisation is separated across platform, institution, branch and specialist operating roles.
Managed files and chat text support authenticated AES-GCM encryption at rest.
The production public edge is designed to serve application and realtime traffic over HTTPS/WSS.
Important business actions are designed to be attributable and reviewable through audit/transparency controls.
Ordinary users receive safe error messages and request references while technical diagnostics remain restricted.
Operational checklists
Production boundaries
LoanHub can coordinate the workflow, but some capabilities depend on regulated providers, institution policy, infrastructure or specialist professional judgement.
LoanHub contains payment and gateway workflows, but live external channels still depend on provider onboarding, credentials, callbacks, authorisation and certification appropriate to the institution.
Call records, recording policy and quality controls are built in. Reliable live recording/supervision requires approved WebRTC/SIP infrastructure and the required notice/consent process.
The platform provides a double-entry accounting foundation. A qualified accountant should review the institution's production chart, recognition, tax and statutory reporting policies.
The production stack supports managed files. Multi-server deployments should use appropriate object storage and malware scanning rather than treating one local VPS volume as a distributed storage system.
Capture the action you were performing, the friendly LoanHub business/request reference and the time of the problem. Do not send passwords, tokens, private keys or unnecessary borrower documents through uncontrolled channels.
Manual, role guidance, operating rules and checklists for people using LoanHub.
Authorised integrators can use the API documentation exposed by the LoanHub backend deployment, subject to the permissions of the endpoints they call.
Open API docs