Flux gives lenders recurring billing, ACH for larger payments, and hosted fields with SAQ-D Level 2 PCI coverage that keep sensitive data off your systems.
Why lenders choose Flux
Recurring premiums and fees
Bill premiums and recurring fees automatically.
ACH for larger payments
Route larger payments over ACH for the friendlier economics.
Records that reconcile
A QuickBooks sync keeps the books clean without retyping.
How lenders get paid
Lenders run premiums and fees on recurring billing, accept ACH for larger amounts, and keep clean records through Flux with a QuickBooks sync.
A typical Flux setup for lenders
Repayment is the core flow: recurring ACH debits on the due date the borrower authorized, with debit cards as the fallback when a borrower wants to cure a missed payment immediately. Payoffs and large principal payments run as one-time ACH. On the outbound side, instant payouts via Visa Direct put approved funds on a borrower's debit card in near real time, which matters when the loan product competes on speed to disbursement.
Everything is driven through the REST API, so the servicing system stays the source of truth: it creates the debit, checks settlement status over the same API, and posts the payment to the loan ledger without manual entry. Card transactions cost a flat 2.9% plus 30 cents, ACH settles in 1-3 business days, and QuickBooks sync covers the entities that keep their books there. Higher-volume portfolios can move to custom interchange-plus pricing, with no minimums or contracts.
What lenders should watch
Recurring debits against consumer accounts sit under Reg E and Nacha rules, so keep the borrower's written authorization, honor revocations quickly, and remember that a returned debit can only be re-initiated a limited number of times. Returns for insufficient funds cluster around the same paydays your due dates do, so watch return codes daily and treat a rising return rate as a portfolio signal, not just an operations chore.
Card acceptance has its own wrinkle: network rules generally keep credit cards out of loan repayment, which is why the card option here means debit. Disputes skew ugly because the payer often disputes the debt, not the transaction, so every payment should link back to the signed authorization and the loan agreement. Card settlement in 1-2 business days and ACH in 1-3 also means payoff letters should account for settlement timing before a lien is released.
Simple, transparent pricing
Flux charges a flat 2.9% plus 30 cents per transaction, with volume discounts for higher-volume lenders and the option to pass the fee to the customer at checkout where local surcharging rules allow. No setup fees and no contracts. Accounts processing under $100,000 a year in card volume may be subject to a $20 monthly account fee.
Frequently asked questions
How do lenders accept payments with Flux?
Lenders accept credit and debit cards, ACH bank transfers, and stablecoins through one Flux integration, with drop-in hosted fields that keep card data off your own systems.
What does Flux charge lenders?
A flat 2.9% plus 30 cents per transaction, with volume discounts for higher-volume merchants and no setup fees or contracts. Accounts processing under $100,000 a year in card volume may be subject to a $20 monthly account fee. You can also pass the processing fee to the customer at checkout where local surcharging rules allow.
How fast do lenders get their money?
Card payments settle in one to two business days and ACH in one to three business days. Stablecoin payments go to your wallet instantly.
Can borrowers repay their loans with a credit card?
Generally no: card network rules restrict using credit cards to repay debt, so card repayment in practice means debit cards. A typical setup runs scheduled repayment on recurring ACH and keeps debit cards for one-time cures and payoffs.
Can we use Flux to disburse loan funds, not just collect payments?
Yes, instant payouts via Visa Direct push funds to a borrower's eligible debit card, which suits products where speed to funding is the selling point. Collections then run back through the same account, so disbursement and repayment share one reconciliation trail.
What happens when a borrower's autopay debit is returned?
The return comes back with its reason code, and you can retry within the limits Nacha places on re-initiating returned debits. Treat repeated returns as a servicing signal and move the account into your normal collections workflow rather than debiting indefinitely.
Ready to get lenders paid with Flux?
Cards, ACH, and stablecoins in one platform. Apply in about two minutes.
Get Started