Appearance
Market Thesis
The core investment thesis: why on-chain recurring billing is a massive unserved market, why now, and why VelaPay is positioned to capture it.
The Core Thesis
On-chain businesses need recurring billing. No one has built it properly. Stablecoins are at payments scale ($3.2T annualized). What's missing is not the rails — it's the billing layer above them.
Stripe built the billing layer for traditional finance. It processes over $1T annually, charges 2.9% + $0.30 per transaction, takes 2–7 days to settle, and sees every transaction the merchant makes. Stripe is the ceiling for what trusted middleware can do.
VelaPay is what happens when you remove the need for trust entirely. The mandate is on-chain, the transfer hook enforces it, billing logic is encrypted via Arcium, and settlement happens in ~400ms. No intermediary sees merchant data. The subscriber knows exactly what they authorized because it's encoded in a mandate PDA that the validator checks on every transfer.
The subscription economy runs on $275B+ annually in traditional markets. Stablecoins process $3.2T in annualized volume. Zero of that volume runs through a protocol with chain-enforced billing authorization. That gap is the opportunity.
Archive Evidence for Timing
The signals are converging from every major crypto institution. This is not a single data point — it's a chorus:
a16z — February 2026
Sam Broner, "Tourists in the Bazaar":
"Stablecoins are programmable. Key features like arbitration, monthly billing, streaming payments."
Explicitly naming recurring billing as a core stablecoin unlock. This isn't a passing mention — it's a thesis statement from the largest crypto venture firm.
"Agents will behave like locals. The properties that make agents different from humans — infinite duplication, flexible resourcing, zero startup cost — mean that a small number of agents can win niches... Dominant agents don't need tourists' payment rails. They need vendor relationships, working capital, and credit."
Agent commerce needs recurring billing, not per-request payments. This is the demand signal for Vela's mandate system.
Galaxy Research — October 2025
"The Future of Payments":
"Subscriptions for frictionless, one-off payments... a sea change in the payments space."
"Stablecoin transaction volumes over the last 30 days [are] ~$265 billion (~$3.2 trillion annualized run rate). That is ~2x PayPal's payment volume in 2023."
The infrastructure is at payments scale. The billing layer is what's missing.
Galaxy Research — January 2026
"Agentic Payments and Crypto's Emerging Role":
"x402 is built for software paying other software... works well for APIs, data, and digital tools that agents use as part of their workflow."
Confirms agent payments as the dominant narrative for 2026+. x402 is per-request (tourist rails). Agents consolidating into platforms need pre-negotiated standing budgets — Vela's mandate system.
Pantera Capital — November 2025
HTTP 402 "Payment Required" was left undefined in the original HTTP spec. The web economy defaulted to ads instead of payments. Stablecoins can finally realize the original vision of protocol-native payments. Privacy + payments is the convergence.
a16z — May 2025
"The Month Fintechs Embraced Stablecoins":
Stripe acquired Bridge for $1.1B. Stablecoin-linked cards let users spend stablecoins anywhere Visa/Mastercard is accepted. Stripe/Bridge processing $1.5B/month in stablecoin payment volume on Solana.
Patrick Collison (Stripe CEO)
"Stablecoins are room-temperature superconductors for financial services."
The CEO of the biggest payment company in the world is betting on stablecoin infrastructure. That's the strongest possible validation of the market direction.
Helius Blog — May 2025
Stripe/Bridge processing $1.5B/month in stablecoin payment volume on Solana specifically. The volume is already flowing on the chain where Vela's transfer hooks operate.
Alliance Essays — July 2025
The agentic commerce tech stack has three layers: AI, payment, identity. The payment layer is the monetization chokepoint. VelaPay is this layer.
a16z — December 2024
Sam Broner, "How Stablecoins Will Eat Payments":
Stripe charges 2.9% + $0.30 per transaction. Most of that fee passes through to Visa/Mastercard networks. Stablecoins collapse this to near-zero.
"If there were a cheap, reliable alternative, expect these businesses to take advantage of it."
TradFi Comparison
Stripe Billing: the incumbent benchmark
Stripe processes over $1T annually. Stripe Billing specifically handles billions in recurring revenue for millions of businesses. The Stripe model:
| Dimension | Stripe | VelaPay |
|---|---|---|
| Trust model | Trusted intermediary (Stripe sees all) | Trustless enforcement (transfer hook) |
| Fee structure | 2.9% + $0.30 per transaction | 1% via Transfer Fee extension |
| Settlement time | 2–7 days | ~400ms (Solana finality) |
| Data visibility | Stripe sees every transaction | Arcium encrypts everything; no intermediary sees data |
| Geographic reach | Requires bank account, KYC | Borderless; needs only a wallet |
| Unbanked access | Excluded (1.4B people) | Included (needs only a phone) |
| Dispute process | Chargeback via card network | Unauthorized pulls fail at chain level — no dispute needed |
The pricing gap is structural
Stripe charges 2–3% per transaction because they sit between merchant and customer, processing through card networks. The fee pays for trust. VelaPay charges 1% via the Token-2022 Transfer Fee extension, built into the token transfer itself. The fee pays for protocol enforcement. When trust is removed from the equation, the cost of processing drops by an order of magnitude.
Revenue potential at scale
- 1% transaction fee on all billing volume
- At $1M monthly volume: $120K annual protocol fees
- At $10M monthly volume: $1.2M annual protocol fees
- At $100M monthly volume: $12M annual protocol fees
- Phase 3 lending margin: $500K–2M additional (est. 3–5% on MRR-attested loans)
- Marketplace fees: $100K–500K (credential marketplace, secondary market)
The unit economics are attractive: once a mandate is created, every pull generates fee revenue with zero marginal cost. The protocol doesn't need to acquire customers — it needs merchants to integrate @vela/sdk, and every one of their subscribers generates fees.
The Billing Gap in Crypto
What everyone built instead
Every existing approach to on-chain billing falls into one of three patterns:
Pattern 1: Manual approvals
- User manually approves each payment
- High friction, high churn, defeats the purpose of recurring billing
- Example: any wallet sending a transaction per billing cycle
Pattern 2: Unlimited allowances
- User grants unlimited token approval to a smart contract
- Merchant or relayer pulls on schedule
- If the merchant misbehaves, the blockchain doesn't stop it
- This is what 10 hackathon teams built — and what failed every time
Pattern 3: Centralized scheduling
- Off-chain cron job or backend service triggers payments
- If the backend goes down, payments stop
- Centralized infrastructure with blockchain branding
- Example: Bundl (NestJS + MongoDB + cron job)
The critical gap
All five shipping subscription projects (Aeon, DMANDATE, Bundl, Subly, DePlan) share the same fundamental architecture:
User delegates token allowance → Relayer or merchant pulls on schedule →
Application logic is supposed to enforce the agreementThe critical gap: if the relayer misbehaves, the blockchain doesn't stop it. The enforcement is in application code, not in the protocol. A compromised relayer, a buggy backend, or a malicious merchant can pull more than authorized, and the subscriber's recourse is a dispute — not prevention.
This is the allowance-wrapper pattern. Every subscription billing attempt on Solana has been an allowance wrapper. None achieve protocol-level enforcement.
The hackathon evidence
| Metric | Value |
|---|---|
| Colosseum projects analyzed | 1,997 |
| Recurring billing attempts | 10+ |
| Prizes won by billing projects | 0 |
| Accelerator spots for billing projects | 0 |
| Projects using TransferHook for billing | 0 (except VelaPay) |
| Projects combining Arcium + TransferHook | 0 (except VelaPay) |
| Subscription billing companies in C1–C4 accelerators | 0 |
The category has never been won because no one shipped a genuine on-chain billing primitive. The attempts were allowance wrappers, vault escrow systems, and concept submissions.
Why This Is the Right Time
Four converging signals make the timing optimal:
1. Token-2022 TransferHook became production-ready in 2024
The architecture was not buildable two years ago:
- Token-2022 with TransferHook deployed to Solana mainnet in 2023
- Orca Whirlpool integrated Token-2022 TransferHook support in May 2024 — the largest Solana DEX by TVL validating the primitive
- Anchor 0.32 (2024) added stable IDL building and Token-2022 extension constraints via
anchor-spl
Orca's production integration is the signal: if the largest DEX has integrated TransferHook, the primitive is no longer experimental. Building Vela in 2023 would have meant shipping against unstable infrastructure. Building now means shipping on a primitive that major protocols already depend on.
2. Arcium launched Mainnet Alpha in February 2026
Encrypted compute on Solana is now real, not theoretical. VelaPay's privacy layer builds on production infrastructure. Arcium's MPC network can validate billing logic as encrypted inputs: mandate amounts, plan prices, subscriber balances, timestamps, pull counts — all validated without any single node seeing plaintext.
3. Agent economy is the dominant narrative
Agent payments won 1st place in two tracks at the last Colosseum hackathon:
- MCPay — $25k in Stablecoins (x402 for MCP tools)
- Latinum — $20k in AI (MCP-compatible wallet for autonomous agents)
a16z, Galaxy Research, and Alliance all identify agent commerce as the key 2026+ narrative. VelaPay's agent mandates are the missing primitive: pre-authorized, cryptographically scoped spending contracts that the chain enforces on every pull.
4. Stripe validated the payment infra thesis
Stripe acquired Bridge for $1.1B. Patrick Collison called stablecoins "room-temperature superconductors for financial services." The biggest payment company in the world is betting on stablecoin infrastructure. The bet is on the rails. VelaPay is the billing layer above those rails.
The Agent Economy Opportunity
The a16z thesis
From "Tourists in the Bazaar" (Sam Broner, Feb 2026):
"Agents will consolidate... need B2B payment rails... stablecoins will get there first."
Agents need unified budget management, not per-service subscription management. They need vendor relationships, working capital, and credit — not per-request API payments.
Why existing tools are insufficient
MCPay (x402): Pay-per-call, one shot, no relationship, no spending caps. An agent with a wallet just pays whatever is asked. No budget enforcement.
Latinum (MCP wallet): Agent budgets managed in a Nuxt server. Budget limits depend on application code. If the server is compromised, budget limits are meaningless. No cryptographic enforcement.
The gap: Both tools treat spending limits as application logic, not protocol enforcement. Giving an AI agent a budget today means handing it API keys and a credit card number. There is no cryptographic cap on what it can spend.
VelaPay's agent mandate
Vela's mandate system is the first protocol where an agent's spend ceiling is enforced by the blockchain itself:
Create mandate: "Agent X can pull max Y USDC per period for service Z"
→ Every pull is validated against the mandate PDA inside the transfer hook
→ A compromised agent cannot exceed its mandate — the validator rejects the transfer
→ No human needs to watch the agentThis maps directly to what a16z describes as the missing primitive: pre-negotiated B2B terms enforced at the protocol level.
The complementarity angle
MCPay and VelaPay are complementary, not competitive:
- MCPay = pay-per-request (x402 headers, one transaction at a time)
- VelaPay = standing authorization (mandates, recurring, metered, budgeted)
An MCPay user who needs ongoing billing naturally becomes a VelaPay user. Vela's x402 adapter translates HTTP 402 "Payment Required" responses into mandate creation — any service already using MCPay's standard can upgrade to mandate-enforced billing.
Privacy as Economic Enabler
Privacy is not a philosophical feature — it's an economic necessity for on-chain billing adoption.
The business intelligence catastrophe
On-chain billing without privacy means:
| What Leaks | How Competitors Use It |
|---|---|
| Subscriber list (wallet addresses) | Target your customers directly |
| Revenue per period (pull amounts) | Know your exact MRR |
| Churn rate (cancelled mandates) | Time competitive offers to your churn cycles |
| Pricing tiers (different mandate amounts) | Undercut your pricing with perfect information |
| Largest customers (highest mandates) | Poach your highest-value accounts |
This is not theoretical. Every Solana explorer makes this data queryable in real-time. No serious B2B SaaS operates with these constraints in traditional finance — and it's the reason none use on-chain billing today.
Arcium MPC: enforcement + opacity
Arcium MPC on the Vela mandate system (Phase 1+) runs billing logic on encrypted data:
- No validator sees billing amounts
- No chain analyst sees customer counts
- No competitor sees pricing tiers
- Only the merchant sees decrypted analytics on their dashboard
- The mandate exists on-chain; the amounts inside it are encrypted
The two-phase architecture:
- Phase 1: Pre-validation — Arcium validates encrypted inputs (mandate amount, plan amount, balance, timestamps, pull counts). Only the boolean result (approved/denied) is revealed. A
PullApprovalPDA is stored via callback. - Phase 2: Transfer hook check — The hook checks that a valid
PullApprovalPDA exists. If it does, the transfer proceeds. If it doesn't, the transfer fails at the validator level.
Vela is the only architecture where recurring billing is simultaneously enforced by the chain and opaque to the chain.
The validation caveat
Honest constraint: at Cypherpunk (Sep 2025), four Arcium projects — ArxPredict, BlackBox, Flaek, and Unchain Protocol — won zero prizes. Privacy via Arcium has not been validated as a winning market pitch by judges or early adopters. Frame privacy as long-term defensibility (the reason serious B2B SaaS will eventually require encrypted billing), not as an immediate competitive moat until Phase 1 ships with real merchant usage.
Revenue Potential
Primary: Transaction fees
1% transaction fee on all billing volume via Token-2022 Transfer Fee extension. Built into the token transfer itself — not a separate charge, not a separate transaction. Collected automatically on every pull payment.
| Monthly Billing Volume | Annual Protocol Fees |
|---|---|
| $1M | $120K |
| $5M | $600K |
| $10M | $1.2M |
| $50M | $6M |
| $100M | $12M |
Phase 3: Revenue-backed lending
VelaPay's MRR Oracle computes aggregate monthly recurring revenue from encrypted billing data without exposing individual merchant revenues. Lenders see a threshold proof ("MRR > $X") rather than the actual number. Revenue-based financing is a $30B+ market in TradFi (Clearco, Pipe, Capchase). No DeFi protocol offers this because no protocol has on-chain proof of recurring revenue.
Revenue from lending margin: est. 3–5% on MRR-attested loans. At $10M in MRR-verified loans: $300K–500K additional annual revenue.
Later phases: Marketplace fees
Transferable subscription credentials create a secondary market. Merchants can sell or transfer subscriber relationships, and Vela earns a marketplace fee on each transaction. Premium SaaS tiers for advanced dashboard features add recurring revenue on top.
The Window of Opportunity
The opportunity window is defined by two boundaries:
- Token-2022 is production-ready — Orca integrated TransferHook in May 2024. The primitive is battle-tested.
- No one has used TransferHook for billing mandates — As of April 2026, across 5,400+ Colosseum projects, zero use transfer hooks for billing enforcement.
Between those two boundaries sits the open window. VelaPay is already shipping through it.
The window won't stay open forever. Transfer hooks are documented in the Solana program library, the Neodyme blog, and the sRFC forum. A well-funded competitor could copy the architecture. What they cannot copy:
- The Arcium MPC integration (requires Arcium cooperation + significant protocol-level work)
- The merchant data history (billing records encrypted under Vela's MPC scheme don't port)
- The execution velocity (529+ commits, 9 repos, 8 milestones shipped)
- The structural lock-in (mandate PDAs encoding customer relationships)
The race is to set the standard before someone else does. VelaPay is ahead.
Sources: a16z "Tourists in the Bazaar" (Sam Broner, Feb 2026), Galaxy Research "The Future of Payments" (2025), Galaxy Research "Agentic Payments" (Jan 2026), Pantera Capital (Nov 2025), a16z "How stablecoins will eat payments" (Dec 2024), a16z "State of Crypto 2025", Alliance Essays (Jul 2025), Helius Blog (May 2025), Colosseum Copilot corpus (1,997 projects), internal competitive analysis (pitch/competition.md).