QFund is a single configurable platform that carries a loan from the first application keystroke to the final collections payment — for storefront, online and omni-channel lenders, across every short-term loan type.
A typical short-term lender ends up with an origination tool bought for online growth, a servicing ledger inherited from the storefront business, a payments gateway bolted on for card acceptance, and a dialer the collections team chose themselves.
Each one holds a version of the borrower. Every night something reconciles them, and every month-end somebody explains the variance. Adding a loan type means asking four vendors for a quote. Entering a state means four compliance reviews.
QFund replaces that with one core. The same borrower record, the same balance and the same rule engine serve the branch, the website and the collections queue — because they are not separate systems pretending to agree.
Loan application through collections, with nothing handed to a second vendor in the middle.
In-store, online, by phone or from a lead provider — with duplicate detection and fraud screening on entry.
Origination →Address, contact, employment and bank verification, bureau and alternative-data pulls, a configurable underwriting matrix, and state-rule validation before an offer exists.
Origination →Cash, cheque, debit card, ACH, instant card funding or prepaid load — including multi-disbursal against a single loan.
Payments →Accruals, statements, partial payments with rebate and pro-rate maths, refinances, payoffs, modifications and automated GL entries.
Servicing →Risk-ranked queues, promise-to-pay tracking, notices, dialer and an agent desktop that shows the whole relationship.
Collections →Intake, verification, decisioning and offer generation for every channel — with an underwriting matrix you configure rather than commission.
The ledger that keeps the loan correct: simple- and fixed-interest accrual, fee schedules, statements, refinance and early payoff with rebate.
Queues driven by risk and age, notice generation, right-party contact tracking and post-judgment handling.
Money in and money out on one ledger: ACH, card, cash, cheque, Check21, prepaid load and instant funding.
A voice-assisted agent experience with intelligent navigation, so the agent talks to the borrower while the system does the clicking.
Storefront POS, QFund Online, converged omni-channel and the Texas CSO model — hosted by us or licensed to you.
The difference between a platform and a package is how much of it is yours to change. In QFund the loan products you offer, their economics, where they are offered and the paperwork they produce are all configuration — owned by your team, with QFund application support alongside when you want it.
A loan type is a container, not a loan product. Configure as many individual loan products inside each loan type as your market needs, each with its own characteristics and fee configuration.
Every loan product carries its own scope, so the same core serves a single-store pilot and a fifty-state roll-out without forking anything.
Fully configurable: agreements, receipts, authorisation letters, notices, statements and customer communications are your templates, not ours.
Standing up a loan product, re-pricing a fee band, opening a state or re-wording a receipt needs configuration and testing, by your team or by the QFund application support team, and then it is live. No code branch, no release train, no vendor development queue. Where something genuinely does need building, a dedicated team of QFund domain and technology specialists builds it in your priority order.
The interface your storefront CSRs and back-office agents use all day is a modern, consistent one. Every module follows the same screen layout, so the system stops being something staff have to be taught and becomes something they simply use — quickly, accurately, and without a training programme in the way.
Counter, origination, servicing, collections and check cashing are drawn from the same screen grammar — the same header, the same action rail, the same field placement. Nothing is a separate application bolted on.
Take a payment, run a refinance, cash a cheque, work a collections queue: the steps sit in the same place on every screen, so competence on one transaction transfers to the rest.
New starters and seasonal hires work live transactions from their first shift. Training and help manuals are available — they are simply not the thing standing between a new hire and a served customer.
Screen flow follows the conversation a CSR is actually having with a borrower, so the agent looks at the customer rather than hunting for the next field.
Short-term lending runs on high staff turnover, so learning time lands straight on payroll. An interface that takes weeks to learn means weeks of supervised handling per hire; one that takes minutes means a productive agent on shift one. The AI assistant sits on these same screens and shortens the work further.
The operations the screens perform are exposed as RESTful JSON APIs over HTTPS — 1,500+ published micro-APIs across 14 modules, from intake and decisioning to payments, collections and reporting — so your own borrower portal, agent interface or middleware can sit in front of QFund and run it purely as your lending core. Browse the live API reference →
Your online portal, your agent UI, your mobile app, your middleware.
Build the loan application journey, account view and payment flow in your own stack and brand; QFund handles verification, decisioning, schedules, interest, fees and the ledger. None of the lending maths moves into your code.
If your agents already work in a tool you built or a CRM you standardised on, keep it — call QFund for origination, servicing, payments and collections. The ready-made QFund screens stay available alongside it.
Webhooks fire on the events your systems care about — decisioned, funded, posted, returned, promise broken, status changed — so your warehouse, marketing stack or dialer reacts as it happens, not on a nightly file.
Every request runs through the same permission set, state rule sets and audit trail as the equivalent action on screen, attributed to the credential that made it. An integration cannot write a loan a CSR would have been stopped from writing.
Everything the screens do to a borrower, a loan or a payment, the APIs do. The configuration itself is not an API exercise — standing up a loan product, re-pricing a fee band or re-wording an agreement happens in QFund’s admin interface, because those changes carry state rule sets and document sets with them. If you need a vendor connected rather than a front end built, it is usually already done: see the 92 pre-built integrations.
State rule sets — rate and fee caps, cooling-off periods, rollover and refinance limits, state database reporting and disclosure requirements — are configured per state and validated during origination, before an offer is presented. Security & compliance detail →
One core with functional suites on top of it. The suites are not separately deployed applications with interfaces between them — they read and write the same borrower, loan and ledger data, which is why there is no nightly reconciliation between origination and servicing.
Yes. Lenders commonly start with the storefront POS and servicing core, then add the online channel, then collections automation. Because it is one core, adding a suite is a configuration and training exercise rather than a systems-integration project.
Yes — that is what the API layer is for. The operations the QFund screens perform are exposed as RESTful JSON APIs, so a lender can run its own branded borrower portal, or keep the agent tool its staff already use, and call QFund for verification, decisioning, origination, disbursal, servicing, payments and collections. Permissions, state rule sets and the audit trail apply to an API call exactly as they do to a keystroke. Configuration itself stays in QFund’s admin interface. See the API layer.
Check the integration ecosystem first — with 90+ pre-built connections across bureaus, verification, payments, communications and collections, most vendors a lender already uses are there. Anything not on the list is handled through interface and integration services.
Your team, the QFund application support team, or both. A new loan product, a fee change, a widened availability scope or a revised document template is configured, tested and live — no code branch and no release train in the path.
State behaviour is configuration, so a new state is set up as a rule set — caps, fees, notice requirements, database reporting — rather than a code change. That is the difference between entering a state next quarter and entering it next year.
We will configure a demo around the loan types, states and fee structures you actually run, and show the same borrower moving between store and online.