We don't just build the rails for the agentic economy, we run on them. Learn more about how we build and ship code.
FloPay was started by operators who watched billions of dollars in payment volume route through human-shaped checkout flows that autonomous agents could not navigate. Whilst the next billion transactions will be machine-to-machine, we're building the rails for that world first.
We are gateway-agnostic. Our vault, tokenization, and orchestration layer were built to sit above the legacy networks, not on top of any single processor. That independence is what lets us route, fail over, and tokenize at the layer where AI agents actually transact.
We talk openly about the problems we are solving, the architecture we are betting on, and the lessons we are learning. The implementation details stay behind closed doors, but the foundations, the mission, and the story are public. We believe in the power of building in public.
FloPay does not just sell rails for the agentic economy — we run on them. Internally, we use an agentic harness and CLI called War Room to coordinate AI agents end-to-end: from triaging a GitHub issue, to planning the change, to writing the code, to running validation and opening the pull request.
War Room is the internal harness we built to coordinate teams of AI agents — triage, planning, implementation, validation, and review — against real GitHub issues in real repositories. It is the operating system for how FloPay ships code.
Every issue becomes a structured task with a sergeant, a repo, a branch, and validation gates. Agents pick up the work, run the validations, and hand back a PR. Humans set direction and review the output; the harness handles the scaffolding.
War Room lets a small team move like a much larger one — dozens of issues in flight, each with its own context, branch, and audit trail. The result is more shipped surface area per engineer, with the same correctness bar a senior reviewer would set.
Engineers here aren’t typists — they’re generals. The harness is the chain of command. The agents are the standing army. The work is the campaign, and the gates are the front line.
An engineer at FloPay is a general. You define what hill to take — the issue, the constraints, the definition of done. You do not type the keystrokes; you decide which battles are worth fighting.
The harness is your chain of command. It briefs each unit, opens the worktree, assigns the branch, runs the gates, and reports back when the objective is met or the line breaks.
Specialised agents — triage, implementation, test, review — move on the work in parallel. You command divisions, not lines of code. The army never sleeps and never breaks formation.
We talk publicly about agentic payments, building independent rails, and coordinating AI agents on production code. If your audience cares about any of that, we would love to be on.
For press, partnerships, or anything else, the same inbox works: hello@flopay.com.
The story is public. The harness is private. The invitation to build with us is open — to investors, partners, merchants, and the people who want to put us on a stage.