Payment infrastructure for

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.

  • SOC 2Type I · Type II in progress
  • PCI DSSSAQ-D Level 2
  • TokenizedCard data off your servers
  • Own accountNot 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.

Payments API · for developers

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, dueDate and ccEmails. 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.
  • 3charge.succeeded marks it paidCard payments send a signed webhook. Paid by wire or check? Call mark-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.
  • 2createToken() returns a card tokenSingle use, valid 10 minutes. A double-click can't authorize twice.
  • 3Charge it from your servercreatePaymentIntent prices from your products. Approvals send charge.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 planproducts: [{ id, quantity }]. Grant access on subscription.created.
  • 2Flux charges every renewalSame card each cycle, reported by subscription.charge_success.
  • 3Declines retry on their ownEvents carry willRetry and recovered. 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 endpointPOST /v2/webhook-endpoints returns its whsec_ 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 event id.

High volume or a custom integration? Talk to our team about custom interchange-plus pricing and dedicated integration support.

Talk to Sales
Invoicing · built for B2B

Invoices 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.

  1. 1Build itLine items with quantities, tax and discounts, under your logo. You set the due date, net 15 or net 30.
  2. 2Send itFlux emails it with a secure pay link and can copy their accounts payable contact. Resend it until it is paid.
  3. 3Get paidThey pay from the link by card, ACH or stablecoins, on any device, with no login.
  4. 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.

Built for high-risk businesses

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.

Tue 9:04A commercial order lands. 3x your usual ticket. Nothing is wrong.
Aggregator

Scored by a model.

  1. TUE 9:04A big order lands.
  2. TUEA risk model flags it.
  3. FRIThe payout is held for review.
  4. AFTERDocuments go into a ticket queue.
Flux

Known by a person.

  1. TUE 9:04The same big order.
  2. BEFOREA person underwrote you, so we know your normal.
  3. THENIf we have a question, it comes as a call, not a notification.
  4. AFTERIt's noted. The account carries on.

An illustration, not a service-level commitment. Automated scoring can go like the left, though not always. The right is how a review usually runs at Flux.

The honest part

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.

What we do promise is how
  • 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.

See the full story and how Flux compares

Chargeback evidence · built for high-risk

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

Explore resources

Common questions

Still have questions? Contact our team, we reply fast.

How much does Flux Payments cost?

Flux is a flat 2.9% plus 30 cents per transaction, or interchange plus 1% if you'd rather pay the card networks' actual cost plus a fixed markup. You can also run a cash discount program, so customers who pay by card cover the processing fee. Higher volume merchants can get custom volume pricing, and there are no setup fees or contracts. Accounts processing under $100,000 a year in card volume may be subject to a $20 monthly account fee.

When was Flux Payments founded and where is it based?

Flux Payments was founded in 2023 and is based in Dover, Delaware.

Which stablecoins and networks does Flux support?

Flux accepts stablecoins on the Solana and Ripple (XRP Ledger) networks, covering the leading stablecoins across both networks. Stablecoin payments settle to your wallet instantly.

What is Consumer Pass-Through pricing?

Consumer Pass-Through is a cash discount program, not a surcharge. Your card price includes the processing fee and customers who pay with cash or ACH get a discount, so the fee is not deducted from your payout. We handle the pricing display and disclosure automatically.

Are there any setup fees or monthly fees?

No setup fees, no minimums, and no cancellation penalties. Accounts processing under $100,000 a year in card volume may be subject to a $20 monthly account fee. Beyond that you only pay (or pass through) a transaction fee when a payment is processed.

How quickly do funds settle?

Card payments settle within 1-2 business days. ACH transfers settle in 3-5 business days. Stablecoin payments go directly to your wallet instantly.

Is Flux PCI compliant?

Yes, SAQ-D Level 2 PCI DSS certified. Card data is captured inside origin-isolated iframes hosted on payments.fluxpayments.com and never touches your servers, dramatically reducing your PCI scope and liability.

Can I negotiate rates for higher volume?

Yes. Interchange Plus at interchange + 1% is a standard plan, and if you're processing significant volume we can offer a custom interchange-plus rate. Reach out to sales and we'll build a proposal around your volume and industry.

What happens if Flux flags something on my account?

A person reviews it, not only a model. Flux underwrites each merchant into their own merchant account, so the review is done by someone who already knows your volume and your business. Where we have the choice, that means we ask you a question before we take an action. Flux still has card network and acquirer obligations and can request documents or hold funds when a rule requires it, but you will be told what is happening and why, and you can get a human on the phone about it.

Why do payment processors freeze merchant accounts?

Many of the best-known payment companies are aggregators: thousands of merchants share one underwriting book, so risk has to be scored automatically. When activity moves outside the model's expected pattern, such as a sudden spike in volume, a larger than usual ticket, a rise in chargebacks, or a product that maps to a restricted category, an automated rule can trigger a reserve, a held payout, or a termination before anyone at the company has looked at the business. Having your own merchant account with a human underwriting relationship is the structural alternative, and it is how Flux is set up: your own merchant account, underwritten and reviewed by a person.

Start accepting payments today

Join businesses using Flux Payments for faster settlement and volume-based pricing.