Layla Haddad.
Designs the gateway architecture behind StablePay: state machines, indexing, and signing boundaries.
Principal Engineer, Payments Infrastructure
At the studio since 2020
What Layla does at the studio.
Layla leads the architecture of StablePay, the studio's self-hosted stablecoin payment gateway. Their work sits where distributed systems meet money: payment state machines, chain indexing, confirmation policy, and the boundary between an application and the keys that move value.
Before the studio, Layla spent several years on treasury and settlement systems, where the recurring lesson was that most payment incidents are disagreements between records rather than failures of any one system. That lesson shapes how the gateway records, reconciles, and explains itself.
Layla writes about the parts of payments infrastructure that are political even when the code is simple, and about what it takes to hand a system to the people who will operate it at 2am.
Posts by Layla.
Paying contractors in stablecoin: an operational playbook
Faster settlement is easy to promise. The hard part is approvals, records, and an ERP that still has to balance. Here is how a field-services company did it.
By Omar Farouk, Layla Haddad
Confirmation policy is a business decision, not a constant
How many confirmations is enough? The honest answer depends on the network, the amount, and what you release when you say yes.
By Layla Haddad, Mohamed Saad
Reconciling stablecoin payments: a treasury operator's guide
Three records, one truth. How to tell what is owed, what is confirmed, and what is still in flight — without opening three tools.
By Layla Haddad, Daniel Whitfield
Stablecoin integration gotchas: 22 tips from the field
Decimals, addresses, gas, testnets, approvals, and support cases — the practical surprises that catch teams integrating stablecoin payments.
By Layla Haddad, Mohamed Saad
Build, buy, or rent: a decision framework for payment infrastructure
Three options, six criteria, and a scoring sheet you can fill in before the next vendor call.
By Omar Farouk, Layla Haddad
How to accept stablecoin payments on your own infrastructure: a practical guide
A step-by-step walkthrough of the moving parts, the decisions you must make, and the mistakes that cost teams a weekend.
By Layla Haddad
Indexing blockchain payments reliably: cursors, reorgs, and failover
How to watch a network without missing a payment or counting one twice — polling versus subscriptions, cursor management, backfill, and surviving a bad RPC provider.
By Layla Haddad, Mohamed Saad
Why self-hosted payment software still wins
A hosted processor is convenient until the Sunday you need the ledger and the vendor is a ticket.
By Layla Haddad
Designing a payment state machine you can trust
States, transitions, guards, and invariants for a payment intent — with the SQL and TypeScript to enforce them, and the tests that keep them honest.
By Layla Haddad
Signing boundaries in self-hosted gateways
The interesting question is never 'can it sign.' It is 'who is allowed to, and how do you prove it later.'
By Layla Haddad, Mohamed Saad
More authors.
Daniel Whitfield
Staff Engineer, Platform & Reliability
Owns webhooks, PostgreSQL, deployment, and the operational habits that keep self-hosted software boring.
Emily Sinclair
Head of Product
Leads Northframe and Meridian, and the discovery work that turns shadow spreadsheets into products.
Omar Farouk
Engagement Lead, Services
Scopes and leads selected client builds, and helps startups and agencies decide what to build first.
Mohamed Hasan
Design & Frontend Lead
Leads interface design and frontend engineering across the catalog, with a focus on dense, calm operator UIs.
Mohamed Saad
Smart Contract Developer
Works on the on-chain side of payments: token transfers, event interfaces, and contract review for products that touch a chain.
El Sayed Abd Almohaymen
Mobile Developer
Builds mobile experiences that put approvals, queues, and payment status in the hands of people who are not at a desk.
Have a system like this to run?
Explore the catalog, or write down the problem and the constraints. We respond when the fit is real.