Built for the way lenders actually operate
Storefront networks, digital-first lenders, tribal entities, check cashing operators and bank-model programmes ask different things of a lending platform. QFund is one core configured for each of them.
Storefront lenders
One store or a thousand locations. What separates a system that works in a branch from one that only works in a demo is cash control, close-of-day, and seeing the network without exporting anything. Then the interface: storefront turnover is high, and QFund’s screens share one layout across every module, so a new CSR serves customers on their first shift (one interface, every module).
What the branch needs
- Drawer-level cash control — disbursement, payment and check-cashing activity tied to a drawer, reconciled at close rather than counted twice.
- Daily close — a close process that produces the branch position and the accounting entries together.
- Counter hardware — signature pads (Topaz, Wacom), check scanners and card readers (MagTek, Digital Check) integrated into the workflow, not driven separately.
- Speed at the counter — the AI assistant lets an agent post a payment or start a refinance while still talking to the customer.
What the operator needs
Network visibility
Branch, district and regional roll-up reporting from the same data the branch posts — no nightly export, no separate BI extract for head office.
Consistent policy
Rate, fee and underwriting rules configured centrally per state and loan product, so a branch cannot quietly diverge from policy.
Store-level loan product control
Which loan products a location may write is configuration, so a new fee structure or a new loan product can be piloted in ten stores and rolled out to the network only when it has proved itself.
More than one brand
Several consumer brands can run off the same core, each with its own loan products, pricing and document set, while head office still reports across all of them from one data set.
Online / direct lenders
A fully digital lender does not need a smaller version of the branch system. It needs the borrower to complete the entire cycle — registration, loan application, decision, funding, servicing and payoff — without a human touching it, on a ledger the back office can still audit.
The full self-service cycle
- Borrower registration and loan application through QFund Online
- Separate loan products, pricing and paperwork per brand or per landing site
- Automated verification and decisioning against the configurable underwriting matrix
- eSignature and document management on the loan file
- Instant card funding or ACH disbursement without a store visit
- Self-service balance, payoff quote, payment and auto-pay setup
- Follow-on loans against existing repayment history
Your own site, or ours
QFund Online is a complete borrower-facing channel you can configure and brand. Digital lenders who would rather own the experience outright take the other route: every function QFund performs is available as a RESTful JSON API, so the loan application journey, the account view and the payment flow live in your own stack while QFund handles verification, decisioning, schedules, interest, fees and the ledger. Webhooks push loan and payment events into your marketing and analytics stack as they happen. API layer →
Risk on a digital channel
Online origination carries fraud exposure a counter does not. QFund’s verification waterfall is built for it: device and identity risk (iovation, MaxMind, Socure, IDology, Intellicheck), bank account existence and scoring (DecisionLogic, Plaid, AccountScore), and employment or payroll confirmation (The Work Number, Pinwheel, Argyle) — ordered so cheap checks eliminate bad applications before you pay for a bureau pull.
Tribal lenders
A tribal lending entity does not run on a state statute book. It runs on its own code, usually behind more than one consumer brand, and almost always online-first. QFund treats all three as configuration.
What the entity needs
- Your own rule sets — rate and fee structure, term limits, renewal, refinance and cooling-off behaviour configured to the code that applies to you, rather than assumed from a state statute.
- Several brands on one core — each brand with its own loan products, pricing, website and document set, and consolidated reporting for the entity behind them.
- Documents in each brand’s name — agreements, disclosures, authorisation letters and communications from your own templates, mapped to the values the system already holds.
- Digital origination end to end — verification waterfall, eSignature, instant card or ACH funding, and borrower self-service without a store.
One entity, many brands
Brand is the first dimension a loan product is configured against, so launching or retiring a brand is a configuration exercise, not a second installation.
Evidence for oversight
Every transaction attributed and timestamped, with SOC 2 Type 2 controls behind the platform and reporting your board or regulatory commission can be given directly.
Check cashing operators
At an MSB counter the fee schedule is the product. What decides the month is how precisely you can price a check and how little the platform costs you when volume dips.
At the counter
- Any check, any mode — payroll, government, insurance, personal and business instruments.
- Fee structure by check type, amount band, customer tier and store — configured, not hard-coded.
- Multi-disbursal — cash, prepaid or debit card, ACH, or split across more than one method in a single transaction.
- Counter hardware integrated — MagTek and Digital Check scanners and readers, drawer-level cash control and daily close.
Pay as you go, zero fixed cost
Per transaction, with no licence or seat fee — so seasonality and a new store’s ramp-up carry no advance commitment.
Same core as the loan book
One customer record, one store report and one general-ledger posting — not a separate cashing system nobody reconciles.
Bank-model lending
Many lenders now run a bank-model programme alongside their own book: the same operation and the same staff, under a different brand, with loans originated under a partner bank’s charter. On QFund that is another brand on the same installation.
How it runs on one core
- A separate brand, not a separate system — its own loan products, rates, fee structure and approval rules, configured alongside your own.
- The bank’s programme rules — credit policy, eligibility and limits configured to the bank’s requirements rather than to a state statute book.
- Paperwork in the bank’s name — agreements, disclosures and communications from a document set mapped for that programme.
- Programme-level reporting and reconciliation — the bank’s book reported separately from yours, from the same data.
- One agent desktop — servicing, payments and collections on the same screens, whichever brand the borrower came in under.
Evidence the bank will ask for
SOC 2 Type 2 controls, full attribution and timestamping of every transaction, automated general-ledger posting and a 99.99% availability SLA — the diligence pack a partner bank runs before it lends its charter. Security & compliance detail.
QFund provides the platform and the configuration. The programme itself — the bank relationship, the credit policy and its regulatory treatment — remains between the lender and the bank.
One platform, every operating model
Tell us how you operate
Brands, channels, states, stores and the loan products you run. We will show you the configuration that fits rather than a generic tour.