Skip to main content

Payment Rails

Money is a message. Payment is routing intention through infrastructure.

The Convergence Thesis

Payments are evolving exactly like telecom networks.

Mobile "G"Stablecoin PhaseWhat ChangedWho Captured Value
2GEarly stablecoins (Bitcoin, ETH)Basic transfers, fragile UXSpeculators, exchanges
3GEthereum + DeFiProgrammable money, composabilityDeFi protocols, wallets
4GTron/Solana/L2sEveryday usability, low feesFintechs, cross-border platforms
5GRollups, bank-grade chainsMachine-speed, 24/7, compliantApps, platforms, AI agents

We're in the 4G→5G transition now.


The Telco Trap

"The trillion-dollar companies will not be those that validate blocks."

Rails are crucial early, then commoditize. This pattern repeats:

EraRails BuiltValue Captured By
RailroadsTrain companiesRetailers, cities
InternetISPsGoogle, Meta, platforms
MobileTelcosApple, Uber, apps
StablecoinsBlockchainsWallets, agents, platforms

The strategic implication: Don't optimize to be the telco. Optimize to be the Uber of programmable money.


Payment = Telecom = Intent

The same pattern governs both:

INTENTION (what you want)

│ "Call this person" / "Send money here" / "Swap X for Y"

ROUTING (MEV/Solvers optimize)

│ Find best path: cost, speed, quality, compliance

INFRASTRUCTURE (carries the message)

│ Telecom: switches, spectrum, cables
│ Payment: blockchains, rails, settlement

SETTLEMENT (proof it happened)

│ CDR/Billing vs On-chain proof

FEEDBACK → Better routing decisions

A crypto wallet is just like a phone. You don't care about the network — you just want your intentions fulfilled.

See Telecom MEV for the parallel algorithm.


Where Value Accrues

As rails commoditize, power moves up the stack:

LayerCommoditizesCaptures Value
Rails (chains, settlement)Fast, cheap, interchangeableLow margin, regulated utility
Routing (bridges, solvers)Abstracted awayModest fees, competitive
Distribution (wallets, apps)Owns the userHigh margin, network effects
Experience (agents, workflows)Owns the outcomeHighest margin, defensible

The winning bet: Own the experience, not the rail.

Don't SellSell
"We're on chain X""Get paid instantly"
"Fast block times""Zero-FX global treasury"
"Low gas fees""AI that runs your cash ops"

The ABCD Payment Stack

How the thesis applies to payments:

LayerFunctionPayment Application
A (AI)Optimize routingMEV algorithms, risk scoring, FX timing
B (Blockchain)Prove settlementImmutable records, atomic execution
C (Crypto)Align incentivesToken rewards for liquidity, solver competition
D (DePIN)Physical infrastructurePOS terminals, ATMs, edge nodes

The synthesis: AI decides → Stablecoin executes → Blockchain proves → DePIN distributes.


Intent-Based Payments

The future isn't specifying HOW to pay. It's expressing WHAT outcome you want.

TraditionalIntent-Based
"Send USDC on Solana to 0x...""Pay Alice $100"
User picks chain, asset, routeSolver finds optimal path
Manual complianceAutomated checks
One railMulti-rail, auto-routed

Intents abstract complexity. Just like sending a text message today — you don't pick the carrier, the network routes optimally.

See Intent Protocols for the crypto implementation.


Machine-to-Machine Payments

The 5G phase enables AI agents handling money:

PatternWhat It Enables
Conditional paymentsRelease on verified delivery
Automated escrowTrust-minimized commerce
Just-in-time FXOptimal conversion timing
Risk-aware routingAvoid congested/expensive rails
Treasury automationSweep, allocate, report autonomously
AI Agent decides payment needed

Evaluates: amount, urgency, compliance, FX

Selects: rail, asset, timing

Executes: atomic settlement

Learns: outcome feeds back to model

The loop: AI decides, stablecoin executes, AI learns.


Architecture Implications

For builders: treat chains as swappable transport.

┌─────────────────────────────────────────────┐
│ EXPERIENCE LAYER │
│ Payroll, Treasury, Commerce, Agent Ops │
├─────────────────────────────────────────────┤
│ DOMAIN SERVICES │
│ ScheduleDisbursement(policy, context) │
│ ExecutePayment(intent, constraints) │
├─────────────────────────────────────────────┤
│ ROUTING LAYER │
│ Rail selection, compliance, FX, risk │
├─────────────────────────────────────────────┤
│ INFRASTRUCTURE ADAPTERS │
│ Solana | Base | Tron | L2s | Bank rails │
└─────────────────────────────────────────────┘

Hex architecture principle: Rails are adapters. Your domain and application services are where defensibility lives.


The Forest, Not a Ladder

Unlike mobile's neat 2G/3G/4G progression, crypto evolves like biology:

  • Overlapping generations
  • Specialization by use case
  • Forks and extinctions
  • Multiple winners in different niches
NicheOptimized For
DeFi railsComposability, liquidity
Consumer paymentsUX, speed, cost
Institutional flowsCompliance, custody, reporting
Machine moneyProgrammability, automation

Design for a forest: multiple settlement backends, multiple asset types, per-segment routing policies.


Attention + Intention

"Attention is all you need" — if you don't have a soul.

AloneResult
Attention without IntentionReactive, captured, extraction
Intention without AttentionDreaming, no execution, drift
TogetherResult
Intention + AttentionAgency, flow, value creation
Internet of Attention    →    Internet of Intent
─────────────────────────────────────────────────
Capture eyeballs Enable action
Platform extracts Protocol distributes
User is product User is agent
Optimize engagement Optimize outcomes

See Intentions for the philosophical foundation.


Payment Providers

Current landscape for crypto-to-business rails:

ProviderStrengthsBest For
Stripe CryptoIntegration, compliance, reachEstablished businesses
Coinbase CommerceTrust, UX, enterpriseBrand-conscious merchants
Now Payments300+ cryptos, non-custodialCrypto-native businesses
Sphere PayDeveloper-firstTechnical teams
BridgeStablecoin orchestrationB2B, treasury

Context


Resources