The Flux Payments API gives developers a single integration for cards, ACH, and stablecoins, with hosted fields, tokenization, and webhook events. Documentation and a dashboard live at the developer portal, so you can go from test to live without stitching together three vendors.
Why businesses use it
One integration, three rails
Cards, ACH, and stablecoins behind a single API instead of three separate vendors.
Secure by default
Hosted fields and tokenization keep card data out of your stack from day one.
Real-time webhooks
Subscribe to events so your systems react the moment a payment changes state.
How it works
You authenticate with your API keys, drop in hosted fields for card capture, and call the API to charge, refund, tokenize, or schedule payments. Webhook events keep your systems in sync in real time.
Simple, transparent pricing
Flux charges 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.
Frequently asked questions
What can I build with the Flux API?
Charges, refunds, tokenized and saved payments, recurring billing, payouts, and more, across cards, ACH, and stablecoins.
Where are the docs?
API documentation and your keys live in the Flux developer portal at portal.fluxpayments.com.
Do I still handle card data?
No. Hosted fields and tokenization keep raw card data off your servers.