Flux gives medical clinics cards, ACH, and recurring billing through one integration, with hosted fields and SAQ-D Level 2 PCI coverage that keep sensitive data off your practice systems.
Why medical clinics choose Flux
PCI coverage without the burden
Card data is captured in origin-isolated iframes, so your practice is not running an audited card environment.
Recurring and plan billing
Charge memberships and payment plans automatically instead of re-running cards by hand.
Real-time settlement
Card payments settle in one to two business days so the practice is not waiting on cash flow.
How medical clinics get paid
Medical Clinics typically take cards for copays and point-of-care payments, ACH for larger balances and plans, and can run recurring charges for memberships, all through Flux.
A typical Flux setup for medical clinics
Medical clinics collect at three moments, and each uses a different rail. Copays and known self-pay charges run card-present at check-in. Balances that appear after the claim adjudicates go out as emailed invoices with a hosted payment page, payable by card or ACH. For larger balances on high-deductible plans, a scheduled installment series against a stored card keeps the account current without monthly statement mailings.
The REST API connects payment events to your practice management system so posted payments match encounters, and QuickBooks sync carries daily batches into the books. Cards settle in one to two business days and ACH in one to three, which keeps cash predictable across the month. There are no monthly fees on qualifying card volume or minimums, so satellite locations and part-time clinics can run their own terminals without carrying overhead in slow weeks.
What medical clinics should watch
The structural problem in clinic collections is timing: the real patient responsibility is often unknown until the claim processes, weeks after the visit, and by then the patient relationship has cooled. Capturing a card at check-in with signed consent to charge the adjudicated balance up to a stated cap closes that gap. State the cap in dollars, notify before charging, and the consent holds up if the patient later disputes it.
Keep clinical detail out of payment records: receipts and invoice line items should show visit dates and amounts, not diagnoses. Flux hosted fields run in origin-isolated iframes under SAQ-D Level 2 PCI DSS, which keeps card numbers out of your EHR and front-desk workstations. When a copay turns out to be overcollected, refund to the original card promptly instead of crediting the account, because unexplained credits confuse patients and generate calls.
Simple, transparent pricing
Flux charges a flat 2.9% plus 30 cents per transaction, with volume discounts for higher-volume medical clinics 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 medical clinics accept payments with Flux?
Medical Clinics 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 medical clinics?
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 medical clinics 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 we collect estimated patient responsibility before a procedure?
Yes, and for scheduled procedures it is the cleanest moment to collect, since the patient is engaged and the estimate is fresh. Present the estimate in writing, take payment by card or ACH, and reconcile against the adjudicated amount once the claim processes. Refund any overage promptly to the original payment method.
How do we keep card data out of our EHR and reduce PCI scope?
Flux hosted fields run in origin-isolated iframes under SAQ-D Level 2 PCI DSS, so card numbers are entered into Flux, not into your systems. Your EHR stores a reference to the stored payment method, never the number itself.
What happens when a claim shows we overcollected a copay?
Refund the difference to the original card as soon as the adjudication posts, rather than parking a credit on the account. Prompt refunds prevent confusion, patient calls, and the occasional dispute from a patient who sees the charge but not the credit.
Ready to get medical clinics paid with Flux?
Cards, ACH, and stablecoins in one platform. Apply in about two minutes.
Get Started