Appearance
Investor Talking Points
Organized by conversation stage. Each talking point has a headline, a concise explanation, and a data point or proof point. Use these to guide investor conversations from opening to close.
Opening Hook (30 seconds)
"$3.2T in annualized stablecoin volume flows through Solana. None of it is private, and none of it is scoped. VelaPay is the only protocol that fixes both."
Solana's stablecoin volume is nearly 3× Visa's total payment volume. Stripe's Bridge acquisition ($1.1B) validated that stablecoin payment infrastructure is a generational opportunity. But every protocol moving that volume — Sphere, Helio, Superfluid, Solana Pay, Bridge itself — publishes every transaction in plaintext, and none enforce recurring authorization at the chain level. Every subscription dollar on-chain today either leaks business metrics, relies on trust (unlimited allowances, centralized schedulers, manual billing), or both. VelaPay is the only payments protocol with a privacy architecture, and the only one where the Solana validator itself enforces the billing mandate.
Data points:
- Galaxy Research: $3.2T annualized stablecoin transfer volume on Solana
- Stripe acquired Bridge for $1.1B (stablecoin payment API)
- a16z State of Crypto 2025: "Stablecoins are programmable. Key features like arbitration, monthly billing, streaming payments"
The Problem Statement (2 minutes)
An entire Colosseum cluster of 202 projects has produced zero billing winners.
Colosseum's ML-derived cluster v1-c16 — "Stablecoin Payment Rails and Infrastructure" — contains 202 projects across four hackathons. Zero have won prizes. Zero made accelerator spots. Cluster v1-c26 ("Simplified Solana Payment Solutions") adds another 223, same result. Aeon Protocol (6 people) built a vault escrow system with no transfer hooks and no SDK. Subly hardcoded their Arcium privacy check to true. Bundl built a NestJS + MongoDB backend with cron jobs — centralized infrastructure with blockchain branding. LinkWave, MISK.FI, DMANDATE, Debyth, BlockSub, Pistis Pay, Sola — all ship variants of the same architecture. The category is not contested. It is structurally unclaimed, because the allowance-wrapper pattern has an architectural ceiling.
Data points:
- Colosseum cluster
v1-c16: 202 projects, 0 billing-protocol winners - Colosseum cluster
v1-c26: 223 projects, 0 billing-protocol winners - 10+ named recurring billing attempts across Radar, Breakout, Cypherpunk, Renaissance — 0 prizes, 0 accelerator spots
- DePlan (usage-based payments, no subscriptions, no caps) won $5k in Consumer Apps — billing primitives can win when executed well
No payments infrastructure on-chain has privacy architecture.
Every existing on-chain payment protocol — Sphere, Helio, Superfluid, Solana Pay, Stripe's Bridge, every failed Colosseum billing attempt — publishes subscriber count, revenue, churn rate, and pricing tiers in plaintext. Every competitor, investor, and chain analyst can read them in real-time on Solana Explorer. This is not a theoretical risk. It is why no serious B2B SaaS uses on-chain billing today. The private-payments layer does not exist as a competitive option anywhere in crypto. VelaPay builds it, and the only two Colosseum projects that even touch the Arcium + Token-2022 intersection — incognito-protocol (marketplace) and zenlok (vesting) — apply it to smaller use-cases.
Data points:
- Helius, Triton, Shyft — real on-chain SaaS companies with real MRR, all leaking business intelligence
- Zero B2B SaaS companies use on-chain billing for recurring payments today
Current approaches are all trust-based.
Manual approvals (chase payments, high churn), unlimited token approvals (subscriber takes security risk every time), centralized schedulers (if the backend goes down, payments stop). Every existing solution requires someone to be trusted — the merchant, the relayer, the backend server. VelaPay removes trust from the equation.
Data point:
- Every hackathon billing project uses the same architecture: user delegates token allowance → relayer pulls on schedule → application logic is supposed to enforce the agreement. If the relayer misbehaves, the blockchain doesn't stop it.
The Solution (2 minutes)
Transfer hook mandates: unauthorized pulls fail at the chain level, not after a dispute.
Token-2022's TransferHook extension lets VelaPay intercept every token transfer and validate it against an on-chain mandate PDA. The mandate encodes: merchant, subscriber, amount, frequency, cap, expiry. When a merchant pulls, the transfer hook checks the mandate in real-time. An unauthorized pull doesn't trigger a chargeback — the validator itself rejects the transfer. The money literally cannot move. This architecture is Solana-native and cannot be replicated on EVM chains.
Proof point:
- Protocol deployed on devnet. Live demo shows: (1) successful pull within mandate, (2) overpull attempt rejected at the validator level. The overpull-fails moment is the "aha" that no competitor can replicate.
Arcium MPC: billing logic runs on encrypted data, only the merchant sees results.
All billing computation happens inside Arcium encrypted compute. Mandate amount, plan amount, subscriber balance, timestamps, pull counts — all validated as encrypted inputs. Only the boolean result (approved/denied) is revealed. Billing records are encrypted blobs that only the merchant can decrypt. On-chain observers see nothing useful.
Proof point:
- Two-phase architecture designed around Arcium's async computation model — nobody else has solved this constraint.
4 billing models in one SDK: recurring, streaming, usage, agent budgets.
| Model | Use case |
|---|---|
| Recurring pulls | Monthly SaaS subscriptions, membership fees |
| Per-second streaming | Compute rental, bandwidth, real-time services |
| Usage metering | API calls, storage, compute units — pay for what you use |
| Agent budgets | AI agent spending caps — cryptographically enforced on-chain |
Proof point:
@vela/sdkv0.1.0 ships all four models; every downstream surface (dashboard, checkout, portal, widget, admin) consumes it as the canonical integration path.
Why Now (1 minute)
Four converging signals make this the right time.
Arcium launched Mainnet Alpha in February 2026 — private compute on Solana is no longer theoretical. For the first time, encrypted billing logic is a shipping technology, not a whitepaper. VelaPay is the only payments protocol that builds on it. a16z, Pantera, and Galaxy Research have all publicly called privacy + payments the 2026 convergence; VelaPay is the only shipped answer to a thesis the top-tier funds already hold.
Token-2022 TransferHook is production-ready. Orca integrated transfer hooks in May 2024. The extension is battle-tested. VelaPay is the only project in Colosseum's 5,400+ corpus using it for billing enforcement.
Agent economy is the dominant 2026 narrative. Agent payments won 1st place in two tracks at Colosseum Cypherpunk (MCPay $25k, Latinum $20k). a16z, Galaxy, Alliance all identify agent commerce as the year's defining thesis. Both winners treat spending limits as middleware that can be bypassed. VelaPay's agent mandates are cryptographically enforced by the validator itself — the missing primitive.
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. They are building the trusted-intermediary version. VelaPay is the trustless, private, protocol-native version of the same bet.
Traction (1 minute)
Shipping velocity that speaks for itself.
| Metric | Value |
|---|---|
| Milestones | 8 shipped (v1.0 → v1.8, all shipped) |
| Phases | 48 |
| Plans | 210+ executed |
| Commits | 628+ since March 29, 2026 |
| Commit velocity | ~33 commits/day |
| Repos | 11: protocol, SDK, dashboard, admin, web, docs, checkout, portal, widget, synthetic, webhook |
| Documentation | 68 MDX-page developer docs site |
Solo founder, AI-assisted development. No other subscription-billing project in the Colosseum corpus has shipped more than 2 surfaces. VelaPay has shipped all 11 — from on-chain protocol and Arcium circuits to subscriber portal, hosted checkout, embeddable widget, devnet synthetic load, and a published webhook library.
Proof point: @vela/sdk v0.1.0 is packaged and consumed across 9 downstream surfaces. The protocol is live on devnet with real program IDs. A developer can integrate billing in an afternoon, not a quarter.
Business Model (1 minute)
1% transaction fee via Transfer Fee extension.
The fee is not a separate charge — it's built into the token transfer via Token-2022's Transfer Fee extension. Every pull payment generates fee revenue with zero marginal cost. At $10M monthly billing volume, that's $1.2M annualized in protocol fees.
Phase 3 adds revenue-backed lending. VelaPay's MRR Oracle computes aggregate monthly recurring revenue from encrypted billing data. Lenders see threshold proofs ("MRR > $X") without seeing actual numbers. Vela earns lending margin on MRR-attested loans.
Marketplace fees from transferable credentials. Merchants can sell or transfer subscriber relationships through VelaPay, creating a secondary market with protocol fees.
Revenue projection at scale:
- $10M monthly billing volume → $1.2M annual fees
- Revenue-backed lending → lending margin (est. 3-5% on MRR-attested loans)
- Credential marketplace → transaction fees on secondary market
The Moat (1 minute)
Four layers that compound over time.
Layer 1: Transfer hooks are Solana-native. EVM cannot replicate this architecture. ERC-20 doesn't support execution hooks at the token program level. Every competitor is an allowance wrapper by necessity — they physically cannot build what VelaPay builds on EVM.
Layer 2: Arcium custom circuits, shipped. The encrypted billing logic requires custom MPC circuits validating mandate amount, plan amount, subscriber balance, timestamps, pull counts — all as encrypted inputs. Building these requires deep cryptographic engineering. The closest competitor (Subly) couldn't get encrypted comparison working and hardcoded their check to true. VelaPay's circuits are live in the protocol today, with test_arcium_validation.rs covering the path end-to-end. Nobody else in the Colosseum corpus applies Arcium to billing.
Layer 3: Switching cost is structural. Once a merchant's billing is tied to Vela mandate PDAs, migrating means re-creating mandates with every subscriber. The PDA encodes the customer relationship on-chain. You don't switch billing providers — you rebuild your subscriber base.
Layer 4: Shipping velocity as execution moat. 628+ commits in 19 days across 11 repos — a pace that compounds faster than any competitor can spin up. A well-funded team starting today inherits a 628-commit deficit on a protocol that is already live on devnet, with encrypted billing compute, a packaged SDK, hosted checkout, and a subscriber portal already consuming it. The technical moat is Solana-native; the execution moat is what keeps it uncatchable while the technical moat ossifies.
Risk Awareness (30 seconds)
Honest about what's hard.
GTM is the hardest problem, not the protocol. On-chain billing merchants are rare today. Need named design partners with real MRR before scaling. Targeting on-chain SaaS companies (Helius, Triton, Shyft) who already feel the privacy pain.
Arcium dependency is mitigated by fail-closed design. If Arcium goes down, pulls are blocked — not degraded to plaintext. Privacy is never optional. The protocol is architected so the billing core can operate without the privacy layer, but in production we treat encrypted compute as a hard requirement — that's the whole differentiation.
Token-2022 adoption is a bet on where stablecoins are going. New stablecoins (PYUSD, USDY) are choosing Token-2022 for its extension support. The trend supports this bet.
Close (30 seconds)
"Token-2022, Squads, VelaPay — the third primitive in Solana's infrastructure lineage."
Token-2022 gave Solana programmable tokens. Squads gave it programmable multisig. VelaPay is programmable recurring value, private by architecture — the third primitive in that sequence, and the last missing layer before on-chain businesses can actually run on-chain. The question isn't whether private on-chain billing will exist. The question is who builds the primitive. VelaPay has already shipped it: 11 repos, 628+ commits, live on devnet, with Arcium encrypted compute wired through the protocol today.