Checkout Money states Pricing Features FAQ Overview Talk to us

Now onboarding founding merchants

Watch your money move.

1.8% flat card processing for UK SaaS and digital product businesses that tracks every payment through seven explicit states so you always know exactly where your money is.

Visa, Mastercard, Apple Pay and Google Pay, with a full audit trail on every transaction.

This is what your
customers see.

A clean checkout with card details, Apple Pay and Google Pay all in one place. Fully hosted, so there's zero PCI scope on your end. One API call to create a session and your customer sees your brand name and a payment form on any device.

Fluxa hosted checkout

One API call to go live

Your server creates a checkout session, you redirect the customer to the URL we return and they pay. Fluxa handles the card form, security and state tracking. No frontend SDK, no PCI scope and no webhook maze.

// Create a checkout session
curl https://api.fluxapay.co.uk/v1/checkout \
  -H "Authorization: Bearer sk_live_..." \
  -d amount=4999 \
  -d currency=gbp \
  -d description="Monthly subscription"
{
  "id": "cs_8f2a...",
  "url": "https://pay.fluxapay.co.uk/cs_8f2a...",
  "state": "PAYMENT_RECEIVED",
  "amount": 4999,
  "fee": 90
}

The fee is in the response. You know what you're paying before the customer even enters their card.

Fluxa merchant dashboard

This is what you see.

Revenue, payouts and every transaction with its full timeline. You see the exact fee on every payment, the feed updates in real time and you get flagged when anything looks off.

Every penny, accounted for

Seven explicit states with only one valid action at a time, you can't skip steps and every transition is enforced, logged and permanent.

PAYMENT_RECEIVED
FUNDS_CONTROLLED
SETTLEMENT_APPROVED
PAYOUT_QUEUED
COMPLETED
REFUNDED
FAILED

Why explicit states?

Most payment systems treat money as either "in" or "out," and that's where the mistakes hide. Fluxa forces every stage to be acknowledged, so reconciliation is simple and disputes are easy to resolve.

1,325 automated tests across 16 test suites verify every state transition, every guard, every edge case and every concurrent race condition. The state machine is proven in code, not promised in a pitch deck.

One fee, no surprises

A flat percentage and nothing else, no per-transaction fixed fee, no cross-border uplift, no monthly minimum and no surprise add-ons. The number on the tin is the number you pay.

2%
flat per transaction

Standard rate after your founding year ends, with the same flat structure, same transparency and same terms. No lock-in and you can cancel any time.

  • Everything in the founding rate
  • Automatic transition, nothing to sign
  • Volume discounts available
Get started

What are you actually paying?

Put your numbers in and see the gap between Stripe's headline rate and what you're actually paying them each month.

£
£
30%
Percentage on business cards
10%
Percentage on non-UK cards
Based on 1,000 transactions per month
Stripe (estimated effective)
2.36%
Headline: 1.5% + 20p
+0.86% above headline
£1,180
Monthly fees
Fluxa (founding merchant rate)
1.80%
1.8% flat with no fixed fee and no extras
£900
Monthly fees
£280
saved per month with Fluxa
£3,360 per year

Based on Stripe UK published rates (1.5% + 20p domestic, +1.5% cross-border, +0.8% corporate card uplift, 2p Radar fee per transaction). Actual rates may vary. Want the exact number? Send your Stripe fees page to us.

Built properly

For companies that can't afford unreliable payments.

Deterministic state machine

Seven money states, each enforced and logged as they happen, you can't skip steps, you can't move backwards and the state machine is the single source of truth for every payment.

Double-entry accounting

Every financial movement is recorded as a double-entry posting, running independently of the state machine so you've got a second check on everything.

Operator controls

Token-based auth with role-based access, so every action is tied to a specific operator identity and shows up in the audit trail.

Anomaly detection

Spots failure spikes, volume drops, stuck checkouts and other patterns that look wrong, with 223 tests behind it.

Concurrent safety

If two operators try to approve the same payout at once, only one of them can actually send it. Row-level locking in Postgres makes sure of that.

Circuit breaker and dry-run

If an external service fails, Fluxa stops retrying and fails safely instead of cascading the problem. You can also preview any dangerous action before you commit.

Paul Jones, founder of Fluxa

Paul Jones

Founder, Fluxa Ltd

I built Fluxa because I got tired of payment systems acting like money is either in or out, when the bit in the middle is where the problems usually are. Every line of code in this system is mine, from the state machine and the double-entry ledger through to the checkout, the dashboard and the 1,325 tests that verify it all works.

My partner runs compliance and reconciliation, so when you email support@fluxapay.co.uk you're talking to the people who built it, and that's not going to change.

LinkedIn

Straight answers

Do customers need a Fluxa account?+
No, customers just pay normally with their card, Apple Pay or Google Pay without creating an account or doing anything extra. They won't even know Fluxa exists.
What payment methods do you support?+
Visa and Mastercard, which between them cover roughly 98% of UK card transactions, plus Apple Pay and Google Pay which tokenise existing Visa and Mastercard cards for contactless payments.
What is the fee structure?+
A flat percentage per transaction and nothing else, 1.8% for founding merchants which is locked for 12 months, then 2% standard after that, with no hidden charges, no monthly minimums and no per-transaction fixed fee.
How is this different from Stripe?+
Stripe UK charges 1.5% + 20p on the surface, but effective rates for UK SaaS typically land between 2.3% and 2.8% once you factor in corporate card surcharges and international card fees. Fluxa charges a flat percentage with no add-ons and you get clear money states, a full operator audit trail and human approval where it matters.
How do refunds work?+
Refunds are a first-class state in the system, so every refund requires a reason and gets logged to the timeline with double-refund protection built in. You can't accidentally refund the same payment twice and you can't refund after payout has already been sent.
Who is Fluxa built for?+
UK-based SaaS companies, digital product businesses and any company processing card payments where transparency, reliability and a clear audit trail matter more than having 200 payment methods you'll never use.
How hard is it to integrate?+
You make one API call to create a checkout session and get back a hosted payment URL, there's no frontend SDK to wrestle with, no PCI scope to worry about and no webhook maze to untangle. We'll walk you through it.
Can I test before going live?+
Yes, every merchant gets full sandbox access before going live so you can test the full flow with real API calls and simulated card processing.

A few founding spots left

1.8% flat, locked for 12 months, with the people who built the system answering your emails. Drop your address below and we'll talk properly.

Got it, we'll be in touch shortly.
Or email us directly: support@fluxapay.co.uk Follow: @fluxapay LinkedIn

Bootstrapped, no investors and answering every email ourselves.