Card and ACH
Credit and debit card acceptance through CyberSource, REPAY and Payliance; ACH debits with configurable retry and representment behaviour.
Payments & disbursal
Money in, money out — on one ledger
Cash, cheque, debit and credit card, ACH, Check21, prepaid load and instant card funding, with multi-disbursal on a single loan and return handling that posts itself. Every rail writes to the same balance.
21payment and banking integrations pre-built
$50B+in payments processed to date
$30B+disbursed to borrowers
Disbursal
Fund the way the borrower is standing in front of you
Cash at the counterDrawer-aware disbursement with branch cash control and daily close.
ChequePrinted cheque disbursement with the loan and document trail attached.
Debit card & instant fundingInstant card funding and prepaid card loading through TabaPay, REPAY, NetSpend, Insight and PayFi.
ACHStandard and same-day ACH origination via ACH Works, Advantage ACH and Payliance.
Multi-disbursalMore than one disbursement against a single loan — part cash, part card, part ACH.
Remote & onlineFund an online loan application without the borrower entering a store, on the same rules as the branch.
Collection of payments
Every rail, one posting model
Cheques and Check21
Borrower cheque deposit, Check21 processing, redeposit and bank deposit for garnishment — with scanner integration at the counter.
Cash and money transfer
In-store cash with drawer reconciliation, plus MoneyGram for remote cash payment.
Auto-pay
Scheduled auto-ACH and card-on-file with configurable retry, grace and notification behaviour.
Returns and reversals
Return-cheque and NSF handling, refunds, and time-bound rollback and void — each posting to the ledger and the GL automatically.
Servicing →Banking partners
Wells Fargo, Republic Bank, BOK Financial, First Horizon and Royal Bank of Canada among the pre-built banking integrations.
Partners →Reconciliation
The part nobody demos
Why one ledger matters here
When the payments gateway is a separate system, every settlement file becomes a matching exercise, and every NSF becomes a manual adjustment in two places.
In QFund the payment, the return, the fee and the accounting entry are one event. Branch close, daily settlement and month-end are reports rather than projects.
- Branch and drawer level cash reconciliation with daily close
- Settlement and return files processed against the originating transaction
- Automated accounting entries from every money movement
- Fee assessment and reversal under the state rule set
- Portfolio, regional and branch reporting from the same data
FAQ
Payments questions
Do we have to change payment processors?
Usually not. QFund has pre-built integrations with 21 payment processors, prepaid and banking providers — see the integration ecosystem. Where a processor is not on the list, it is handled through interface and integration services.
Can one loan be funded across two methods?
Yes — multi-disbursal is supported, so a loan can be part cash at the counter and part instant card funding, with both disbursements recorded against the same loan.
Can we post payments from our own system?
Yes. Payment posting, reversal, auto-pay setup and payment-method changes are all available as RESTful JSON APIs, so a portal or middleware you built can post to the same ledger the branch screens use, under the same permissions and audit trail. Webhooks fire back on the events your systems need — payment posted, payment returned, disbursal completed, status changed — rather than leaving you to poll or wait for a nightly file. API layer →
How are NSFs and returns handled?
As posting events. The return reverses the payment, assesses the fee your state configuration permits, updates the delinquency state, re-queues the account for collections if appropriate, and posts the accounting entries — without an agent touching three screens.
Test it with your own settlement file
Bring a day of real payment and return activity and we will run it through, including the accounting entries it produces.