Regulated UK payments partner. Card processing runs through our FCA-authorised payments partner. Merchant funds sit in safeguarded accounts. Fluxa is the facilitator, not the holder of your money.
Read the regulatory modelCard payments for UK businesses, on UK rails. One flat percentage on every transaction, the fee returned in the API. Six payment states you can see.
Featured in FinTech Futures, March 2026Six things every UK card processor should ship. Tap a card to see the full product UI.
Card, Apple Pay, Google Pay across 13 languages. Hosted on our domain or embedded on yours with three lines of code. Your customers see your business, not ours.
No tiers, no add-ons, no surprises. Every feature on every plan. The fee returned in every API response, before the customer pays.
1.8% flat for UK businesses. Custom volume rate below 1.8% above £500k per month.
Our standard flat rate for UK businesses. Founding cohort members lock in 1.8% instead.
For UK merchants above £500k a month. Bespoke interchange-based rate by arrangement.
A workforce of agents watches your account at speeds no human team could match, spotting revenue leaks, drafting dispute responses, taking natural-language commands. Then handing every consequential decision to a human at Fluxa.
Tom is the agent merchants spend the most time with. Deep traceable access to every transaction, settlement, dispute and webhook on your account. Does the work a junior ops person would take a week to do, drafts in minutes.
James gets you live faster than any payments processor we know of. Runs every check the regulator cares about, walks you through the API in your stack, stays with you through the first month after go-live.
Sentinel is your eyes on the entire platform every minute of every day. Catches anomalies before they reach customers, self-heals what she can, only pings a human when one is genuinely needed.
Auditor is your double-entry conscience. Works through every transaction line by line, validates every fee against your contract, reconciles your settlement to the penny every twenty-four hours.
Compliance keeps you on the right side of the FCA, always. Tracks every document, watches every AML signal, reads every rule change, translates regulator-speak into specific actions for your business.
Five agents working at speeds no human team could match. They spot patterns, surface problems, and recommend actions. They don't decide on anything that moves money or changes your account.
Pricing, the API, the switch. Tap a card for the full answer.
Headline rates hide the real cost. Toggle the fees you’re paying and see the truth on your monthly volume. Numbers sourced from each processor’s published pricing and verified merchant statements.
We don’t charge for the things other UK processors meter, gate behind tiers, or bolt on as separate fees. 57 rows, 10 unique to Fluxa. Feature by feature, fee by fee.
“Other UK processors” describes typical UK market practice across the sector, not any specific named provider. Individual processors may price differently. Comparison reflects typical UK card processing practice as of May 2026 and is subject to change. Fluxa is not affiliated with, endorsed by, or partnered with any third-party processor.
Headline rates hide the real cost. Toggle the fees you’re paying and see the truth on your monthly volume. Numbers sourced from each processor’s published pricing and verified merchant statements.
Most processors say a payment is “processing” and leave it at that. Fluxa shows you which of six states it’s in, in real time, with every transition logged.
Strict transitions. CAPTURED can’t skip to SETTLED without going through SETTLING. The state machine refuses moves the card schemes wouldn’t allow.
A double-entry ledger runs in parallel. If state machine and ledger ever disagree, Fluxa alerts before any money moves. Audit trail on the dashboard, exportable as JSON, queryable via the API.
Other processors show you a percentage. Fluxa shows you the interchange, the scheme fee, the payments partner cost, and the margin we keep, on every transaction. Reconcile against Visa and Mastercard’s own published interchange and you’ll find we match it, line by line.
Every charge response itemises interchange, scheme fee, payments partner, and Fluxa margin as separate lines. The same breakdown shows in your dashboard, API response, and CSV export. Cards are priced from the public Visa and Mastercard interchange tables, refreshed monthly. Every penny on the record.
Live status for every payment. From card to bank, you see exactly where each penny is, and when it’s going to land. Not "pending". A specific time. Tomorrow at 06:00.
Live, not historical. ETA on every payment. Every state, every penny, including the bit Fluxa keeps, on its own line in the dashboard and in the API response.
103 pages, 87 components, 2,500+ automated tests. Built around the question UK businesses asks: where is my money, what is holding it up, who needs me right now.
Card details, Apple Pay, Google Pay across 13 languages including Arabic and Hebrew. Hosted on our domain or embedded on yours with three lines of code. Your customers see your business name, not ours, no co-branding, no Fluxa logo.
Three clicks for you. One branded email per customer, under your domain. Visa and Mastercard subscribers tap once to re-authenticate their card. Subscribers on Amex or other brands add a Visa or Mastercard. Fully automated. Most subscribers complete within a week.
In your Stripe dashboard, go to Developers, then API keys, then Create restricted key. Tick read-only permissions for Customers, Subscriptions, Prices, Coupons, Payment Methods and Invoices. Copy the rk_live_… key and paste it here.
Fluxa shows exactly what will happen for each customer before you commit. Most subscribers re-authenticate the card they already have. The few on unsupported brands add a Visa or Mastercard. Review the breakdown and click Approve to proceed.
Customise the email subject, body and button text with a live preview. Customers on Amex or other brands see a similar email asking them to add a Visa or Mastercard. Click Launch and the campaign sends from your domain with reminders day 3 and day 7.
1.8% flat for UK businesses, written into your merchant agreement. Same platform, same features, same people answering the email.
Open to UK businesses at 1.8% flat. Founding cohort open.
Same platform, same features, same people answering the email. The published rate after the founding programme closes.
The most-Googled processor problem is account freezes with no warning. Fluxa publishes the exact consequence ladder, monitored against scheme thresholds in real time. You always know where you stand.
Five tiers, predictable consequences from Healthy to Suspended, every tier with a defined settlement timing, reserve % and support SLA. Off-board within 5 days, no clawback: if you choose to leave, you keep your settlement schedule. We don’t hold your money to keep you.
One API call to go live. The fee comes back in the response, before the customer pays. HMAC-signed webhooks with rotation, idempotency keys enforced, 2,500+ tests across 37 suites keeping the state machine honest.
// Retrieve a paid checkout session curl https://api.fluxapay.co.uk/v1/checkout/cs_8f2a... \ -H "Authorization: Bearer sk_live_..." // Response { "id": "cs_8f2a...", "amount": 4999, "fee": 90, "state": "PAYMENT_RECEIVED", "captured_at": "2026-05-12T14:22:09Z" }
// server.js const fluxa = require('fluxa')('sk_live_...'); const session = await fluxa.checkout.create({ amount: 4999, currency: 'gbp', description: 'Monthly subscription', success_url: 'https://yoursite.com/thanks', }); // session.fee is in the response, not on an invoice console.log(session.fee); // → 90 res.redirect(session.url);
// Handle state transitions app.post('/webhooks/fluxa', (req, res) => { const event = req.body; if (event.type === 'payment.captured') { fulfil(event.data.checkout_id); } if (event.type === 'payment.settled') { markSettled(event.data.checkout_id); // event.data.fee available here too } res.json({ received: true }); });
Most processors will take any merchant they can. We won’t. Here’s the line, in full.
Not sure if you fit? Email paul@fluxapay.co.uk with a sentence about your business. If we can’t help, we’ll send you to the processor that can. No pitch, no funnel.
I’m Paul, and I founded Fluxa. For as long as I can remember I’ve been the sort of person who takes things apart to understand how they work, then puts them back together better. Systems, software, businesses, all of it. That curiosity has never really switched off, and it is the thread that runs through everything I’ve built.
Before Fluxa I started a company of my own and grew it, over several years, into one of the most established names in its field. I did it the unglamorous way: dealing with customers myself, taking the calls, sorting problems in person, and making sure people were genuinely happy before I called a job finished. It taught me that reputation is not something you can market your way to. You earn it one honest interaction at a time, and you keep it by being the person who does what they said they would.
At Fluxa, product and engineering are mine. The API, the dashboards, the hosted checkout, the SDK, and the fraud and anomaly work are all built and maintained in house, on top of thousands of automated tests so the parts you depend on keep behaving. Charlotte runs compliance and operations, and an AI workforce watches the system around the clock and flags anything unusual faster than a person could.
I started Fluxa because too many UK businesses were paying fees they could not explain and waiting in support queues that never cleared. I have been the small business owner on the other end of that, and I did not enjoy it. Everything we build here is meant to fix one or the other.
I’m Charlotte. Compliance and operations are mine to run.
I’ve spent my career on the inside of the systems most people never see: banking platforms, HR and people systems, and the compliance frameworks that sit underneath them. It taught me how money and information really move through an organisation, where the risk tends to hide, and why the careful, unglamorous work is the work that matters most. I’m the person who reads the rules properly and then makes them workable, rather than treating them as a box to tick.
At Fluxa that means FCA reporting, anti money laundering monitoring, know your business checks, the decisions on which merchants we take on, and the day to day relationships with our payments partner and gateway. It is the discipline that keeps a payments company standing, and I would rather we got it right quietly than make a noise about it.
My job is simple to describe and hard to do well: make sure that when your money moves through Fluxa, it moves through a company that takes the rules as seriously as you take your business.
Subscriber migrations used to be a project. Tokens moved by hand, SCA flows tested twice, customers churning during the changeover because the card-update emails landed wrong. The migration tool ends all of that.
Three clicks. Connect your existing processor: Stripe, GoCardless, Adyen, whoever you’re on. Pick the customers. Hit migrate. Branded card-update emails go out under your domain, SCA flows run where the new card needs them, and we chase non-responders on a reminder schedule you control.
Card data never touches your servers. Tokens move network to network and the whole flow is PCI-out-of-scope for the merchant end to end.
A daily progress digest lands in your inbox. A webhook stream tracks the moves as they complete, so your billing platform stays in sync without polling.
Available now to every Fluxa merchant at no additional charge.
v5.5 puts every internal queue into one workflow. Tickets, approvals, scheme remediation, settlement reconciliation exceptions, compliance flags. One inbox, full keyboard navigation, RBAC on 26 routes, dual-approval token validation on every action that moves money or changes merchant state.
Settlement reconciliation runs in the inbox. When an inbound file doesn’t reconcile to the penny, the discrepancy lands as a workflow item with a side-by-side breakdown, the likely cause auto-tagged by the 19-detector anomaly engine, and a direct route to raise it with the payments partner.
Scheme remediation works the other direction. Visa or Mastercard flag a transaction, it lands in the same inbox with the evidence pack already attached and the response window timed against the scheme deadline.
Numbers behind it: 204 API files, 124 dashboard files, 37 test suites green. Built for the team Fluxa will become, not the team it is now.
Every payment carries one of three explicit states. CAPTURED: funds authorised, committed, ours to settle. SETTLING: the payments partner is moving the money. SETTLED: cleared into the merchant’s bank account.
State transitions map to specific events: capture authorisation, batch send to payments partner, confirmed receipt of cleared funds. Visible in the API. Visible in the dashboard. Visible in every webhook payload.
No effective-rate fog. No “pending” that means six different things to six different people. No opaque float hiding where the money is on any given day.
Two terminal states close out the model: FAILED and REFUNDED. Five states total. The full lifecycle Fluxa exposes, and the full lifecycle a merchant needs to track.
The architecture is locked. Everything Fluxa ships from here builds on these five primitives.
1.8% flat on every transaction, for UK businesses. No plus-twenty-p, no card-type uplifts, no domestic-versus-EU surcharges, no monthly minimums. The rate is written into your merchant agreement.
The maths matters. Stripe’s UK 1.5% plus 20p headline lands between 2.3% and 2.8% effective for most UK B2B SaaS, once you factor in the real card mix and average order value (AOV) the business sees. 1.8% flat beats that effective rate at every realistic AOV, and it’s a single number you can plan unit economics around, on the way up and on the way down.
Founding merchants also get a direct line to the founder. Pricing question, technical edge case, weird thing at three in the morning. The email lands in a founder inbox. Not a queue, not a rep, not a chatbot.
For UK merchants processing £50k to £500k a month. SaaS, digital products, subscription businesses. Anywhere transparent pricing matters more than a rewards points programme.
FinTech Futures listed Fluxa among the UK’s notable new fintech launches in March 2026. Cameron Emanuel-Burns wrote the piece, covering the approach to UK SME card processing: flat-rate pricing, transparent payment states, and the choice to launch with the product working rather than the marketing loud.
Trade press read of a launch is the closest thing to a real-world signal you get this early on. This one came in unprompted.
The full piece is on FinTech Futures.
Fluxa builds a signed PDF from your real ledger. The Ed25519 signature covers every page, every value, every total. Tamper one cell and verification fails.
Banks, lenders, and payments partners verify it against our public key, and trust the numbers without ringing you back.
| Month | Volume | Net | Txns | Change |
|---|---|---|---|---|
| Mar 2026 | £52,400 | £51,310 | 324 | +8.2% |
| Feb 2026 | £48,420 | £47,418 | 298 | +3.1% |
| Jan 2026 | £46,940 | £45,983 | 289 | −1.4% |
| Dec 2025 | £47,610 | £46,650 | 293 | +5.6% |
| Nov 2025 | £45,080 | £44,170 | 277 | +2.8% |
| Oct 2025 | £43,840 | £42,950 | 270 | +4.0% |
Regulated UK payments partner. Card processing runs through our FCA-authorised payments partner. Merchant funds sit in safeguarded accounts. Fluxa is the facilitator, not the holder of your money.
Read the regulatory modelCompanies House 17028144. Fluxa Ltd is registered in England and Wales. Filings are public, directors are named, the registered office is traceable. Verifiable in real time on the .gov.uk register.
Verify on Companies HousePCI DSS SAQ-A, UK-resident. Card data never touches Fluxa or your servers. Tokenised inside a hosted iframe, processed through a Level-1 certified gateway. All infrastructure sits inside UK borders.
How the PCI flow worksThe dominant UK card processors advertise 1.5% + 20p headline rates, but effective rates for UK SaaS land between 2.3% and 2.8% once corporate cards, international cards, and dispute fees are added. Fluxa is a flat percentage, full stop. The fee comes back in every API response, the buy-rate breakdown sits in the dashboard on every transaction, and a transparency email at month-end shows what you paid versus what a typical processor would have charged on the same volume.
No. One percentage covers every supported card: UK consumer, UK corporate, international Visa and Mastercard, Apple Pay, Google Pay. Interchange and scheme fees do vary by card type, but those sit inside our buy rate, not on top of your fee. For comparison: Stripe adds 1.0% on EEA cards, 1.75% on non-EEA cards, and 2.0% on currency conversion, all on top of headline. Fluxa adds none of that. Your effective rate on a month with 30% international cards is the same as a month with 0%.
For most UK merchants, flat is simpler and more predictable. Interchange-plus is fairer at scale, but it’s a maths problem most teams don’t want: different rates for premium cards, corporate cards, EEA cards, non-EEA cards, plus scheme fees, plus the processor markup, all reconciled monthly against an invoice you can’t verify. We publish the full buy-rate breakdown so you can audit it line-by-line, then charge a single percentage so you can budget. For merchants above £500k a month, where the maths starts to favour interchange-plus, we offer a bespoke interchange-based rate by arrangement.
Yes. Refund a payment, the Fluxa fee is reversed with it. Full refund, full fee back. Partial refund, pro-rata fee back. Most UK processors keep the fee even when the original transaction is reversed, which quietly turns refunds into a cost centre. We don’t. The dashboard shows the reversed fee on the same line as the refund, the API returns it on the refund object, the month-end statement nets it off.
No. Statement descriptor is your trading name, set during onboarding and editable from the dashboard. Your customers see your business on the receipt, on the card statement, on the email confirmation. Fluxa never appears in the customer-facing path. Branded card-update emails for migrated subscribers come from your domain too. We’re infrastructure, not a brand your customers should ever know.
Fluxa processes payments under an FCA-authorised payments partner. All servers in London, double-entry ledger running independently of the state machine. Card data never touches Fluxa or your servers. Under PFaaS, Fluxa doesn’t hold your funds, settlements go from the payments partner direct to your bank account on the schedule published in your trust ladder.
The payments-partner relationship is the regulated one, and your funds never sat with Fluxa. Under PFaaS, settlements move from the FCA-authorised payments partner direct to your bank, regardless of what happens to us. If Fluxa stopped trading tomorrow, in-flight settlements still complete via the payments partner, your historical data is exportable from the dashboard at any time, and you move to another processor on a clean exit. We don’t hold your money, your customer relationships, or your data hostage.
None. The rate is 1.8% flat for UK businesses, written into your merchant agreement. Pass-through costs are shown clearly where they apply. No per-transaction fee, no monthly minimum, no termination clause.