LendRails runs the whole life of a consumer loan or credit line: the application, the credit decision, the agreement, the payout, collections and the ledger. Lenders bring their brand, credit policy, wording and funding. The platform does the rest.
Each stage hands over to the next without re-keying. Select a stage for detail.
A phone-first application in the lender's brand.
Bureau, identity, fraud and affordability checks, decided in seconds.
Pre-contract information and the agreement, signed online.
Funds sent by Faster Payments after a two-person approval.
Direct Debit, retries, arrears and forbearance.
A double-entry loan ledger with journals to the general ledger.
Each lender runs its own instance under its own authorisation. LendRails supplies and operates the software. It does not lend, broker credit or hold customer money.
Each lender chooses which products it offers from a catalogue, with its own pricing, limits and terms. Applicants who don't qualify for one product can be offered another, in an order the lender sets.
Unsecured personal loans repaid in equal instalments by Direct Debit, with statutory early settlement figures available to the customer at any time.
A credit line that sits alongside the customer's existing current account. The customer draws funds into their own bank account and repays each draw within a period the lender sets.
The same platform serves the customer on their phone and the lender's staff at their desks, so a case never leaves the system to be worked somewhere else.
A short application built for a phone screen, in the lender's own brand and on its own web address.
Checks run automatically and the lender's credit policy decides the outcome. Cases that need a person go to a referral queue.
The offer, pre-contract information and agreement are produced from the lender's own wording and signed online.
Disbursement follows a maker-checker approval, with the payee's bank details encrypted at rest.
Repayments are collected by Direct Debit, either through a bureau or on the lender's own Bacs service user number.
Every movement posts to an append-only, double-entry loan ledger, reconciled to the payment providers.
A regulated lender has to show who did what, under which rules, and why. The staff console is designed around that.
Staff see and do only what their role allows. Sign-in has lockout and multi-factor authentication.
Payouts, manual ledger postings, write-offs and rule-set changes each need a second person.
Every decision, status change, document and notice is recorded with the person, time and version.
Referrals, arrears and tasks are assigned and tracked, with notes on each case.
Staff are notified on their phone when a case needs them, and can review and approve there.
Limits, utilisation, delinquency, income and margin, with drill-through to account and transaction.
A full customer file, subject access responses and retention with legal hold.
Freeze, block, interest stop and high-risk referral, each with a reason and an audit record.
A monthly credit reference file for review and approval before it goes to the bureau.
Customers install the lender's portal on their home screen. It opens with Face ID or a fingerprint and sends notifications when something needs their attention.
Balance, next payment, repayment progress and statements, in plain language.
Draw funds, change bank details, request a settlement figure or sign a document.
Secure messages and an assistant that answers account questions and hands over to staff, with the full conversation.
Each lender instance runs under a document and conduct regime. The regime decides the documents issued, the notices sent and the rights offered to the customer.
Designed around the Consumer Credit Act 1974 and the FCA's Consumer Credit sourcebook (CONC): pre-contract information and explanations, agreement content, the 14-day right of withdrawal, statements, arrears and default notices, and early settlement.
A separate document set for lenders registered under the Moneylenders Act 1991, with UK practice adopted as stated policy where Manx law is silent, and anti-money-laundering capture for a designated business.
The lender remains responsible for its own regulatory compliance. Agreement and notice wording is supplied or approved by the lender and its legal advisers; the platform checks that every required figure is present and calculated by the system.
Every lender gets its own instance and database. It can be hosted by LendRails or deployed as a container to the lender's own cloud.
Bank details encrypted at rest, secrets kept out of the code, CSRF protection on every form and rate limits on sign-in.
Nightly backups copied off-site, with a restore drill that proves each backup can be brought back.
Health checks, structured logs, scheduled-job tracking and email alerts when something needs attention.
| Area | Connectors built | Notes |
|---|---|---|
| Credit reference | Experian | Search at application; monthly credit reporting file |
| Identity | Sumsub | Document and liveness verification |
| Open banking | TrueLayer | Income and outgoings for affordability |
| Payouts | TrueLayer, Corpay, NatWest | Faster Payments, with maker-checker approval |
| Collections | GoCardless, Bacs direct | Bureau collection, or Standard 18 files on the lender's own service user number |
| General ledger | Xero, Infor SunSystems, Sage 50 | Daily journals by connector or file import |
| Notifications | Email and web push | Customer and staff notices, with each message audited |
The lender holds its own contract with each provider. New connectors sit behind the same interfaces, so a provider can be changed without changing the customer journey.
We run live demonstrations in two parts: the customer journey on a phone, from application to funds sent, and the staff console that runs the book behind it. Allow about an hour.