Flux gives online stores one integration for cards, ACH, and stablecoins, with drop-in hosted fields that keep card data off your servers and a checkout customers actually trust.
Why online stores choose Flux
Same-day and next-day settlement
Card payments settle in one to two business days, so cash is not stuck for a week while you restock.
Hosted fields, less PCI to worry about
Card data is captured in origin-isolated iframes on payments.fluxpayments.com, so it never touches your store.
Volume discounts as you scale
Higher-volume online stores can move to custom interchange-plus pricing as monthly volume grows.
How online stores get paid
Most online stores lead with cards for speed at checkout, add ACH for larger or recurring orders, and can accept stablecoins for customers who prefer it. All three run through one Flux integration.
A typical Flux setup for online stores
Everything is card-not-present, so the build starts at checkout. Hosted fields drop into your existing cart pages inside origin-isolated iframes, which keeps card data off your servers while the page still looks like yours. Cards carry the bulk of orders and settle in 1-2 business days. For larger carts, ACH is worth offering and settles in 1-3 days, and stablecoin payments on Solana or Ripple (XRP Ledger) settle instantly to your merchant wallet.
Orders arrive around the clock, so settlement rhythm matters more than store hours. Refunds run back through the same rails as the original charge, and the REST API lets your order system trigger them the moment a return is scanned at the warehouse. QuickBooks sync keeps payouts, fees, and refunds reconciled against orders without manual matching, which starts to matter once daily order counts pass what a spreadsheet can absorb.
What online stores should watch
Card-not-present volume means chargebacks are your main exposure. The most common disputes are item-not-received and item-not-as-described, and both are won or lost on evidence: tracking numbers, delivery confirmation, and the product page as it looked at purchase. Keep that trail attached to the order record, because a dispute filed sixty days later is hard to fight from memory. Flux surfaces disputes through the dashboard and API so responses go out before deadlines pass.
The other quiet leak is failed payments. A decline at checkout is a lost sale, and it is not always the customer's fault, so give shoppers a second rail: ACH for the cautious, stablecoins for customers who already hold them. Mirror your stated refund policy in practice, since a generous policy with a slow refund queue is how disputes get generated. Refunds post back to the original card, and the shopper's issuing bank controls when they appear, so say that plainly on the policy page.
Simple, transparent pricing
Flux charges a flat 2.9% plus 30 cents per transaction, with volume discounts for higher-volume online stores 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 online stores accept payments with Flux?
Online Stores 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 online stores?
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 online stores 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 I add Flux to my existing cart without rebuilding checkout?
Yes. Hosted fields embed inside your current checkout pages in origin-isolated iframes, so card data never touches your servers and the page keeps your design. For fully custom flows, the REST API covers the entire payment lifecycle.
How does Flux help when a customer files a chargeback?
Disputes surface in the dashboard and through the API with their response deadlines, and you submit evidence such as tracking and delivery confirmation there. The outcome still depends on the strength of your records, so keep tracking numbers tied to every order.
Is it worth offering stablecoin payment to ordinary shoppers?
For most stores it is a secondary option, not a replacement for cards. Payments on Solana or Ripple (XRP Ledger) settle instantly to your merchant wallet, and the customers who use it tend to already hold stablecoins and prefer paying with them.
Ready to get online stores paid with Flux?
Cards, ACH, and stablecoins in one platform. Apply in about two minutes.
Get Started