About
A UK payment processor that gives businesses a card processor they can see. Founded by Paul Jones (engineering, product, design), with Charlotte Craig leading compliance and operations. Registered in England & Wales, built end to end in the UK.
I spent years around small UK businesses and kept seeing the same frustration on the merchant side: a complete lack of visibility once a card payment was taken. The customer pays, you get a confirmation, and then you wait for the money to show up. Nobody tells you where it is in between, or why it’s taking however long it takes.
The second frustration is hidden cost. UK SaaS sellers we’ve looked at are paying close to twice the headline rate of their processor by the time you add interchange surprises, currency markups, dispute fees and tiered pricing games. The advertised rate and the actual rate are rarely the same number.
Fluxa is what I wanted to use as a merchant: a processor that shows me where every payment is, and a rate I can settle on a calculator. The decision to bootstrap, to write the whole thing myself, and to wait for the payments partner sandbox before taking a live payment, all come out of that.
Paul Jones. As told to FinTech Futures, March 2026.
Founder. Product, engineering and design.
Led the product, engineering and design across the platform: the six-state machine, the double-entry ledger, the hosted checkout, the embedded SDK, the admin and merchant dashboards, the REST API, and the autonomous agents that run support and onboarding. Approves every commit. Reviews merchant feedback directly with the founding team.
Partner. Compliance, operations and reconciliation.
Owns operations end to end. Reconciles every transaction file against the ledger, handles merchant correspondence, and runs the regulatory controls the payments partnership requires. Writes and maintains the operational procedures the business runs on.
No outside investment, no board, no quarterly growth target. The product moves on its own timescale, not a fundraise cycle's. We ship slower than a funded competitor would. We also ship what the merchant needs, not what plays best to the next round.
The roadmap is on the changelog page. The status of every system is on the live page. When something breaks, it goes there within minutes, before we have drafted a comms plan. A processor that hides incidents is not a processor anyone should trust with settlement.
Registered in England and Wales. Operations, team and servers in the UK. No merchant data leaves the country. A second jurisdiction adds a year of compliance work, so it waits until the product has earned the right to expand on the home market first.
The platform has been ready to take a live payment for weeks. We are waiting on payments partner sign-off because the state machine, the ledger and the reconciliation engine have to hold up under load, not just on a happy path. A processor that loses a settlement does not get a second chance to lose one.
Every operational topic that touches a merchant runs on a written procedure rather than a verbal habit: onboarding, support, security, complaints, escalation. Documented means versioned, dated, and either published on this site or held by a regulated partner.
The regulated parts of the stack, card processing, settlement and scheme membership, sit with regulated firms. Fluxa builds the merchant-facing layer: the dashboard, the API, the hosted checkout, the embedded SDK, the operating tools, and the visibility into every payment state. The split is deliberate. Regulated activity stays with regulated firms. The merchant-facing layer is ours, and the list below is what we maintain in public.
“Fluxa is setting out to build a payment and settlement infrastructure specifically tailored to online businesses … the start-up offers UK enterprises a card payment processing model with a flat rate of 1.8% per transaction.”
Everything below is on the public record. Every link resolves to a register, a regulator, or a document on this site.
The payments partner is a regulated firm authorised by the Financial Conduct Authority. Fluxa is not in the merchant funds flow; the payments partner settles directly to the merchant. Names of partners are disclosed under NDA during onboarding and reflected in the merchant’s signed agreement.