Active Frameworks
1 framework · More coming with each series
F-01 · Pillar 01 · Building the Rails
The Rails-First Framework
Build the payment rails before you build the product. Infrastructure decisions made on day one determine what is possible on day one thousand.
The Model
LAYER 3 — Product & Experience
(apps, UX, features, brand)
↑ built on top of
LAYER 2 — Business Logic
(credit, BNPL, KYC, fraud, limits)
↑ built on top of
LAYER 1 — Infrastructure (THE RAILS)
(ledger, wallets, routing, settlement,
provider abstraction, multi-currency)
Most teams start at Layer 3. The Rails-First Framework says: start at Layer 1, design Layer 2 before you touch Layer 3.
When to Apply It
Apply when:
— You will eventually need to control payment flows, merchant relationships, or credit products
— The dominant payment provider in your market is an aggregator, not a direct rail
— You are designing for multi-market or multi-currency from the start
— You want to white-label the infrastructure to others
Do NOT apply when you are validating a product idea in weeks — use the aggregator and swap later.
Source
"Financial Inclusion Is an Infrastructure Problem, Not an App Problem" — TechRoadmap Substack, May 2026
Coming Soon
F-02 · Extracting from the "Building the Rails" series · Estimated Q3 2026
F-03 · Extracting from the "AI-Native Platforms" series · Estimated Q3 2026
F-03 · Extracting from the "AI-Native Platforms" series · Estimated Q3 2026