Pull to refresh
Back to LoanHub website

Knowledge base

LoanHub Documentation Centre

Practical guidance for visitors, borrowers, institution owners and operating teams—without publishing deployment secrets, private customer data or internal security credentials.

Security information that visitors should know

Public documentation explains how users should operate securely without revealing private deployment details, credentials or sensitive internal diagnostics.

Mobile privacy notice

Tenant isolation

Independent institutions operate inside isolated tenant scopes with branch-aware business access.

Professional roles

Authorisation is separated across platform, institution, branch and specialist operating roles.

Encrypted storage

Managed files and chat text support authenticated AES-GCM encryption at rest.

Secure transport

The production public edge is designed to serve application and realtime traffic over HTTPS/WSS.

Audit evidence

Important business actions are designed to be attributable and reviewable through audit/transparency controls.

Safe error handling

Ordinary users receive safe error messages and request references while technical diagnostics remain restricted.

Operational checklists

Use a checklist before high-impact actions.

Before a borrower requests funding

  • Account registration is complete.
  • Employment and affordability information is current.
  • Banking information is reviewed.
  • Required supporting documents are available.
  • Consent choices are understood and recorded.

Before an institution starts lending

  • Institution registration and approval are complete.
  • Branches and staff memberships are configured.
  • Each staff member has the narrowest suitable role.
  • Loan products and calculation methods are reviewed.
  • Payment/integration dependencies are activated where needed.
  • Finance, collections and reporting responsibilities are assigned.

Before marking money as successful

  • The correct borrower and loan are selected.
  • The payment/disbursement channel is correct.
  • Provider status or approved manual evidence is available.
  • The user performing the action is authorised.
  • Any reconciliation evidence is retained for review.

Production boundaries

Know what requires external approval or professional review.

LoanHub can coordinate the workflow, but some capabilities depend on regulated providers, institution policy, infrastructure or specialist professional judgement.

Payment providers

LoanHub contains payment and gateway workflows, but live external channels still depend on provider onboarding, credentials, callbacks, authorisation and certification appropriate to the institution.

Controlled calling

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.

Accounting policy

The platform provides a double-entry accounting foundation. A qualified accountant should review the institution's production chart, recognition, tax and statutory reporting policies.

File storage at scale

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.

Need to report a problem?

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.

Troubleshooting guide

User documentation

Manual, role guidance, operating rules and checklists for people using LoanHub.

Technical API reference

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