Payment infrastructure formodern business
Accept cards, ACH and stablecoins in one platform, on your own merchant account. Drop-in hosted fields keep card data off your servers, and stablecoins settle instantly.
Trusted by
- Chance2WinNonprofit raffle software
- VyaPayPayments platform
- PayLinkB2B payments and invoicing
- MVNX LinkPlatform for mobile brands
- PartnerSolveOperations consulting
- An underwriter reviews every application
- Certified to keep card data safe
- 3-D Secure checks with the buyer's bank
- Security checked by independent auditors
- Cards settle in 1-2 business days
- SOC 2 Type II in progress
- PCI DSS SAQ-D Level 2
- Card data is captured by Flux hosted fields and never touches your servers
- Each business gets its own merchant account, not a shared pool
Card details are typed into Flux's isolated frames and go straight to Flux. Your server only ever sees a single-use token.
Trusted by
- Chance2WinNonprofit raffle software
- VyaPayPayments platform
- PayLinkB2B payments and invoicing
- MVNX LinkPlatform for mobile brands
- PartnerSolveOperations consulting
Build payments into your own code.
Invoices, checkout and subscriptions from one REST API. Card fields that keep card data off your servers, and signed webhooks that tell your systems the moment a card is charged.
- REST + JSON API
- Basic auth, scoped keys
- Idempotency keys
- HMAC-SHA256 webhooks
- Sandbox on the same keys
Invoice a client with one POST.
POST /v2/payment-links with isInvoice: true and Flux emails the invoice with a pay link. Set a dueDate, copy their AP team with ccEmails, and send an X-Idempotency-Key so a retry never creates a second invoice.
- 1Create it with
isInvoice: trueLine items,dueDateandccEmails. Up to 100 invoices in one call. - 2Your client pays from the linkBy card, or by ACH when bank payments are on for your account.
- 3
charge.succeededmarks it paidCard payments send a signed webhook. Paid by wire or check? Callmark-as-paid.
Card fields on your page. Card data off it.
Hosted fields put each card input in a cross-origin Flux iframe, so card numbers never touch your page, server or logs. Your page gets a single-use token, and your server charges it at a price it sets.
- 1Mount the Flux card framesYour server mints a 15-minute browser token with
generateAuthToken. - 2
createToken()returns a card tokenSingle use, valid 10 minutes. A double-click can't authorize twice. - 3Charge it from your server
createPaymentIntentprices from your products. Approvals sendcharge.succeeded.
Recurring billing without a cron job.
Create a SUBSCRIPTION product billed MONTHLY, QUARTERLY or ANNUALLY, send one payment link, and Flux charges every renewal. A declined renewal is retried up to 8 times, on a schedule set by the decline reason.
- 1Send one link for the plan
products: [{ id, quantity }]. Grant access onsubscription.created. - 2Flux charges every renewalSame card each cycle, reported by
subscription.charge_success. - 3Declines retry on their ownEvents carry
willRetryandrecovered. Stop retries without cancelling.
Signed webhooks that don't get lost.
Every delivery carries a Flux-Signature header: HMAC-SHA256 over the timestamp and the raw body. Each event gets 9 attempts over about 3 days, is held while your endpoint is down, and can be replayed with one call.
- 1Register an HTTPS endpoint
POST /v2/webhook-endpointsreturns itswhsec_secret once. - 2Flux retries with backoff1 minute, 5, 30, then hours apart. Held, not lost, while you are down.
- 3Verify, de-dupe, answer fastConstant-time compare, 5-minute window on
t, de-dupe on the eventid.
High volume or a custom integration? Talk to our team about custom interchange-plus pricing and dedicated integration support.
Talk to SalesInvoices that look as serious as your business.
Bill another business the way it expects: an itemized invoice under your logo, with your terms, a secure pay link and their accounts payable team on copy. Every invoice is tracked from sent to paid, so you know what is overdue and what is on the way.
- 1Build itLine items with quantities, tax and discounts, under your logo. You set the due date, net 15 or net 30.
- 2Send itFlux emails it with a secure pay link and can copy their accounts payable contact. Resend it until it is paid.
- 3Get paidThey pay from the link by card, ACH or stablecoins, on any device, with no login.
- 4Track itOverdue, not due yet and paid at a glance. Paid by wire or check? Mark it paid with the reference number.
Sample invoice and dashboard with made-up companies and amounts.
Reviewed by a person, not a model.
Flux underwrites your business into its own merchant account, so the person reviewing it already knows your normal. When something looks unusual, you get a question before you get an action, whenever the choice is ours.
Scored by a model.
- TUE 9:04A big order lands.
- TUEA risk model flags it.
- FRIThe payout is held for review.
- AFTERDocuments go into a ticket queue.
Known by a person.
- TUE 9:04The same big order.
- BEFOREA person underwrote you, so we know your normal.
- THENIf we have a question, it comes as a call, not a notification.
- AFTERIt's noted. The account carries on.
Card networks and acquirers set rules we have to follow, so sometimes we will ask for documents or hold funds. We won't promise that nothing ever happens.
- A person who knows your account makes the call.
- You hear about it early, in plain language.
- You can get a human on the phone.
When a dispute lands, the evidence is already there.
Flux freezes the facts of every payment at the moment of the charge: what the customer saw, agreed to and paid with, where they paid from, and what they were sent. Each fact is labeled by who vouches for it, so you answer a chargeback with a record, not a scramble.
Frozen at the charge
Line items, the exact terms text, addresses and card details are copied the moment the payment happens. Editing an invoice later changes nothing in the record.
Labeled by who vouches for it
Gateway attested, server observed, customer asserted or merchant asserted, so it is clear which facts came back from the card processor and which came from the customer.
Names its own gaps
Anything Flux does not hold shows as not captured, with the reason, checked against the evidence card networks list for answering a dispute.
Sealed and portable
A PDF for the dispute and a machine-readable JSON copy, fingerprinted with SHA-256. The card number is never stored in full.
Sample record with illustrative data. Evidence supports your response to a dispute; the card issuer decides the outcome.How chargebacks and ratios work →
Payments, explained
Tax relief vs debt settlement: different rules, different underwriting
Who each one negotiates with, the federal fee rules that pull in opposite directions, and what payment processors look at when underwriting each model.
Nov 22, 2026FeesCredit card processing fees explained: what businesses pay in 2026
What you pay when a customer pays by card: interchange, network assessments, processor markup, pricing models and a hypothetical worked example.
Nov 22, 2026Gaming and bettingLottery payment processing: iLottery and courier payments explained
iLottery vs couriers: MCC 7800 vs 7995, state credit card bans, 18 U.S.C. 1301, New Jersey's courier money rules and 2026 W-2G reporting.
Nov 21, 2026Common questions
Still have questions? Contact our team, we reply fast.
How much does Flux Payments cost?
When was Flux Payments founded and where is it based?
Which stablecoins and networks does Flux support?
What is Consumer Pass-Through pricing?
Are there any setup fees or monthly fees?
How quickly do funds settle?
Is Flux PCI compliant?
Can I negotiate rates for higher volume?
What happens if Flux flags something on my account?
Why do payment processors freeze merchant accounts?
Start accepting payments today
Join businesses using Flux Payments for faster settlement and volume-based pricing.
