Product Checkout Real-time dashboard AI Workforce VCI verified identity Six payment states
Pricing
Developers Documentation API reference Webhooks SDKs Full docsComing soon Updates Changelog SandboxComing soon Migration toolComing soon
Compare Security
Company Our story Press Brand kit Updates Changelog
Live Try the demoComing soon Sign inComing soon Talk to us Get started

Changelog

What we shipped. And when.

The Fluxa changelog is the public record of what Fluxa has built. Every feature, improvement, security update and fix is dated and posted here. Continuous log, no marketing rollups, no "coming soon" entries. If it has not been built yet, it is not on this page.

May 2026.

Brand, public-policy and careers surfaces refreshed. Admin and merchant dashboard polish. The product surface is now feature-complete for the founding cohort.

  1. Careers page published.

    Public careers page with six baseline hiring competencies, full UK compliance factsheet citing the Equality Act 2010 and Data Protection Act 2018, no-agencies clause, and a single careers inbox. Pre-launch and honest about growing carefully today.

  2. Brand kit page full rebuild.

    Wordmark variants, colour palette with WCAG contrast pills, typography specimens, clearspace and minimum-size diagrams, six visible Do/Don’t examples, downloadable kit (SVG, PNG), Powered by Fluxa badge mockups, and a Trade Marks Act 1994 reference. Brand inbox set up at brand@fluxapay.co.uk.

  3. AI workforce page consolidated.

    Public AI workforce page now shows five production agents (operations support, onboarding assistance, platform health monitoring, revenue integrity checks, regulatory coverage) with a full disclosure log explaining what each agent can and cannot do. Internal-only agents removed from the public surface.

  4. Acceptable use policy.

    Public acceptable use page listing the merchant categories Fluxa serves, the categories Fluxa declines, and the basis for each decision. Aligned with UK Money Laundering Regulations 2017 and the FCA payments partner’s underwriting requirements. Sidebar navigation, prose-first layout.

  5. Accessibility statement.

    Public accessibility page committing to WCAG 2.1 level AA across the website, hosted checkout, and merchant dashboard. Named contact route at accessibility@fluxapay.co.uk with a one-working-day response target and P1 same-day commitment for cardholder-blocking issues.

  6. About page rebuild.

    Public About page covering founders, the working model, documented operational controls, Companies House registration (number 17028144), the FCA payments partnership arrangement, and the press feature in FinTech Futures. No marketing language, every claim links to a verifiable source.

April 2026.

Admin dashboard reached production maturity. Merchant dashboard pages rounded out. CRM, anomaly engine, and ledger reconciliation all stabilised.

  1. Admin dashboard v5 published internally.

    Operator console: 204 API files, 124 dashboard files, 37 test suites. Server-sent-event streaming for live ledger, bitwise CIDR IP allowlisting, RFC 4180 CSV parser, settlement file upload with paired ledger postings, scheduled export jobs. Zero merchant-facing labels containing partner names.

  2. Merchant CRM v3.

    Operator CRM consolidated playbooks, ownership routing, resolve and snooze states, and a due-today aggregation across every merchant queue. Replaces three earlier scratch surfaces with one canonical view.

  3. Anomaly engine: 19 detectors live.

    Production anomaly detectors covering velocity outliers, refund patterns, dispute escalation signals, mismatched settlement files, and KYB drift. Each detector runs on a defined cadence, posts to the operator inbox with severity, and writes to the immutable audit log.

  4. Merchant dashboard: 55 pages complete.

    Full merchant-side surface: payments, settlements, disputes, balances, reconciliation, refunds, customers, KYB documents, branding, webhooks, API keys, invoices, recurring billing, exports, audit log, team and roles. Every page is built; the only blocker on live data is payments partner sandbox sign-off.

March 2026.

Public launch positioning. Payments partnership confirmed. First press coverage. Founding-merchant programme opened.

  1. FinTech Futures coverage published.

    Cameron Emanuel-Burns covered Fluxa in FinTech Futures. The article covers the founding-merchant programme, the architectural approach to payment-state visibility, and the positioning for UK B2B SaaS.

  2. Founding merchant programme opened.

    1.8% flat per transaction for UK businesses, written into the merchant agreement. Hands-on onboarding for founding merchants. No setup fee, no monthly minimum, no scheme-fee passthrough. Application by direct email to the founders.

  3. Payments partnership signed.

    FCA-authorised payments partnership confirmed. Fluxa operates as a Referrer to the regulated firm under the Payment Services Regulations 2017 and does not hold or settle merchant funds. Settlement flows directly from the payments partner to the merchant’s UK bank account in GBP.

  4. Verified Commercial Identity (VCI).

    VCI is the per-merchant identity verification layer covering Companies House lookup, beneficial-owner identification, sanctions screening, and the documented underwriting trail the payments partner requires. Status is visible on the merchant dashboard and the operator console; never on the public site.

February 2026.

Core platform: the six-state payment machine, the double-entry ledger, and the embedded checkout SDK all stabilised.

  1. Six-state payment machine.

    Every payment progresses through six explicit states: PAYMENT_RECEIVED, CAPTURED, SETTLING, SETTLED, plus FAILED and REFUNDED as terminals. Each transition is logged, timestamped, and visible to the merchant in real time on the dashboard and to the API consumer via webhook.

  2. Double-entry ledger.

    Every monetary movement on the Fluxa platform writes a paired entry to the ledger: a debit and a credit on accounts that always balance. Reconciliation against payments partner settlement files runs nightly; any unmatched penny posts to the operator inbox before close of business.

  3. Hosted checkout (pay.fluxapay.co.uk).

    PCI SAQ-A scope hosted checkout live in sandbox. Card data is tokenised at the point of capture and never stored on Fluxa systems. Visa, Mastercard, Apple Pay and Google Pay supported; no American Express, no PayPal. UK card processing only for launch.

  4. Embedded checkout SDK.

    JavaScript SDK for merchants who want to embed the Fluxa checkout into their own pages rather than redirect to the hosted page. Same PCI scope, same token model, same payment-state events to the same webhook endpoint.

January 2026.

Public-facing API, recurring billing, and the merchant onboarding flow.

  1. REST API and SDK skeleton.

    First version of the public REST API: payment intents, customers, refunds, webhooks, and exports. Idempotency keys on every write, HMAC-SHA256 signed webhooks (X-Signature), standard problem-detail error responses (RFC 7807). Documentation at docs.fluxapay.co.uk.

  2. Recurring billing engine.

    Subscription plans, trial periods, prorated upgrades and downgrades, dunning rules for failed renewals, and a webhook stream covering every state change. Invoices are generated against the same ledger as one-off payments; the merchant sees a single account, not two.

  3. Merchant onboarding flow.

    End-to-end onboarding: business details, beneficial owners, bank account verification, Companies House lookup, signed merchant agreement, and the documented underwriting hand-off to the payments partner. Status visible on the merchant dashboard at every step.

December 2025.

Company registered. First commits. Project bootstrapped.

  1. Fluxa Ltd registered.

    Fluxa Ltd incorporated at Companies House, registered in England and Wales, company number 17028144. Private limited company, two directors, no outside investment.

  2. First commit.

    Initial repository scaffold: Node.js backend, Prisma ORM, Next.js operator and merchant dashboards, Tailwind for styling, Plus Jakarta Sans and JetBrains Mono. The shape was chosen on day one and has not changed since.

Want to know when something new ships?

A short email goes out when a meaningful change lands: a feature, a security update, a breaking API change, or a milestone. No marketing, no rollups, no “we miss you” resends. One line per entry with a link back to this page. Unsubscribe in one click.

Got it, you’ll hear from us when something ships.
Or follow on: X LinkedIn