How we build, how we ship, and how we treat the people and machines that depend on us.
01
We rewrite the rules
We don’t do convention. When it comes to how to do business, we have torn up the rule book.
We don’t pay attention to what others are doing or how they are doing it, and we never have.
We are original and we do things our own way.
We are audacious. We are bold. We are Flo.
✓
GOOD Guardrails
Do this
Challenge Gateway Dictatorships: If Stripe or Worldpay says "that’s just how our API works," we build a vault or an abstraction layer to bypass their limitations. We own the customer experience, not the processor.
Design for Machines First: Assume the next million checkouts will be executed by autonomous AI agents, not humans with keyboards. We build APIs and MCPs for the future, not just web forms for the past.
✕
BAD Guardrails
Don’t do this
"Because Stripe does it this way." Never use a legacy competitor’s architecture as the justification for our product design. We don’t copy their homework.
Ignoring Hard Compliance: We rewrite industry conventions, but we never compromise PCI-DSS, data security, or financial regulations. Being audacious does not mean going to jail.
02
We Keep it Simple
Our success relies on keeping what we do simple. We take a straightforward, common-sense, no bullshit approach to everything we do.
Complexity creates confusion, destroys productivity, wastes time and drains the joy out of what we do. We don’t overcomplicate and we don’t create needless obstacles for ourselves.
We explore new possibilities and we try different things. We are not afraid to experiment and we are not afraid to fail. If it works, we keep doing it. If it doesn’t, we move on. Because business should be that simple.
✓
GOOD Guardrails
Do this
Abstract the Chaos: The payments industry is a mess of 3DS challenges, MIT flags, and cross-border declines. Our backend handles that chaos silently so the client only ever sees a clean, 2-line SDK integration.
Ship, Measure, Kill: If we think a new routing rule or AI prompt will increase authorization rates, we deploy it to a small segment, measure the data, and if it fails, we delete the code immediately without ego.
✕
BAD Guardrails
Don’t do this
Building "Just in Case" Architecture: Do not over-engineer a 10-step microservice if a simple database lock solves the problem today. We build for the volume we have and the step immediately ahead of us.
Exposing Complexity to the User: If a customer has to understand what a "Payment Intent" or a "Dunning Cycle" is to use our dashboard, we have failed. Hide the plumbing.
03
We evolve or die
We are never complacent in the face of success. Our hunger and drive keep us moving forward, seeking new opportunities and striving for more.
We learn, we develop, we adapt, we evolve. And we keep our eyes open to what the future may bring.
Our progressive, forward-thinking approach keeps us highly adaptable and responsive to the shifting demands of our rapidly changing industry.
✓
GOOD Guardrails
Do this
Automate Yourself Out of a Job: We aggressively use AI agents, LLMs, and the Warroom CLI to write tests, monitor logs, and scale development. If a human is doing a repetitive task, we engineer a way for a machine to do it tomorrow.
Cannibalize Our Own Features: If a new payment method (like GoCardless or Stablecoins) makes our legacy credit card routing obsolete, we push the new method immediately. We disrupt ourselves before the market does.
✕
BAD Guardrails
Don’t do this
"It’s working fine for now." A 75% authorization rate might be acceptable to the client today, but if we aren’t actively running experiments to push it to 85% tomorrow, we are dying.
Getting Emotionally Attached to Code: If an entire microservice or SDK version needs to be ripped out and rewritten to support M2M Agentic payments, we delete the old code without hesitation. Sunk cost is a myth.
These values are the rails.
Every line of code, every gateway we plug in, and every agent we ship is checked against them. Help us build the financial layer for the agentic economy.