Subscriptions are a state machine, not a payment. A technical tour of what recurring revenue in Web3 actually takes. 👇

Introducing ArcenPay.com The protocol for on-chain subscriptions! Most Web3 products still sell access like it’s 2016. A wallet in a @discord. A spreadsheet. A DM when something breaks. No invoice. No receipt. No audit trail. The product went on-chain. The billing around it never did. AI agents made that gap worse. They can think, browse, and ship, but they can’t pay. No card. No bank. No standard way to prove a spend is authorized. @arcenpayhq is the billing and entitlement layer that closes that gap. We give teams one programmable stack to: • sell subscriptions & usage in stablecoins • gate features by real payment state • settle across chains • let humans and AI agents pay through the same rails Not a checkout bolt-on. Infrastructure for selling access. The problem we solve: Running a paid product usually means wiring together: payment processor → subscription manager → entitlements → usage metering → invoices → customer ops → webhooks Each piece drifts out of sync. Pricing changes become engineering projects. Access doesn’t follow payment. Agents get custom payment hacks that don’t scale. ArcenPay connects those pieces into one layer: Sell → Gate → Sync 1. Sell: embedded checkout, hosted payment links, agentic /spec, x402 micropayments, escrow 2. Gate: entitlements, feature flags, usage limits, credits 3. Sync: signed webhooks, invoices, lifecycle events What can you build? • Recurring subscription products • Usage-based APIs • Paid developer tools • Digital memberships & token-gated access • Credit packs & allowances • Agent-paid services & machine-to-machine commerce • Hosted payment links (human UI + machine-readable /spec) • Hybrid wallet-native billing without card-first checkout Built for SaaS, Web3 protocols, platforms, and AI/agent builders. How it works (humans)? 1. Configure plans, add-ons, credits, and features in the provider dashboard 2. Embed billing with @arcenpay/react (ArcenPayProvider → identify() → ArcenEmbed) 3. Customer connects a wallet and activates a plan on-chain 4. Subscription state updates · entitlements unlock 5. Your app checks access with hooks or server-side APIs 6. Signed webhooks keep your backend in sync Access follows entitlements - not the last checkout screen. How it works (AI agents)? Agents run on the same platform, without a human in the loop: 1. Fund a SessionVault with spend limits (maxAutoApprove, maxDailySpend) 2. Bound authority with ArcenAuth mandates (scope, chain, recipient, policy) 3. Discover pricing via payment-link /spec or hit a protected API 4. Receive HTTP 402 · sign a voucher · settle from session balance 5. Optional Verify-Then-Settle escrow - commit → verify deliverable → settle or auto-refund x402 middleware in @arcenpay/node protects paid routes. @arcenpay/agent + MCP tools plug into @claudeai, @cursor_ai, and LLM stacks. Same ledger. Same invoices. Same webhooks - whether a human or an agent paid. Multi-chain settlement Stablecoin settlement, one billing model: @solana @StellarOrg @arc @base On-chain surface: • SubscriptionRegistry - mint / renew / cancel subscription state • ERC-7579 Autopay - recurring allowances without card rails • PlanFactory - on-chain plan catalog • FeeCollector - protocol fees • SessionVault - agent balances, x402, escrow, revocation On Solana, one Anchor program fills every role. Dashboard owns the catalog. Chain owns the subscription. Non-custodial. Contracts settle. Platform manages state around it. Entitlements & metering Plans map to features, limits, and credits. • React: useFlag, useEntitlement, useConsumeEntitlement • Server: checkEntitlement, checkFlag, consumeEntitlement • Feature flags with rules, plan auto-rules, and company overrides UI can be optimistic. Anything that costs money should be enforced server-side. Optional ZKVUB - zero-knowledge usage proofs so metered settlement doesn’t expose per-consumer volumes. Developer surface npm install @arcenpay/react # embed + gate in the browser npm install @arcenpay/node # entitlements, webhooks, x402 npm install @arcenpay/agent # autonomous payments + MCP Also: • Stripe-style keys - sk_ · pk_ · rk_ · arc_tok_ • Hosted checkout - app.arcenpay.com/pay/… • HMAC-signed webhooks (lifecycle events) • Invoice builder + PDF delivery • Environments (dev / prod) with separate catalogs Docs: docs.arcenpay.com API: api.arcenpay.com Why teams choose ArcenPay 1. Wallet-native - billing designed for wallets, not card checkout adapted to crypto 2. Non-custodial - settlement stays on open contracts near your treasury design 3. Billing tied to access - plans and entitlements shape the product directly 4. Agent-ready - mandates, x402, escrow, MCP - not a human-only afterthought Protocol economics are usage-based fees. Value from real settlement volume, not emissions. Who it’s for • SaaS & API companies shipping subscriptions / usage • Web3 teams monetizing protocols, memberships, on-chain services • AI builders who need agents that can discover, pay, and settle • Platforms embedding billing & entitlements for their ecosystem Status Live settlement on production networks. Verified contracts. Dual-mode checkout (human + agent). Entitlement engine. Webhooks. SDKs. Litepaper with formal access & fee model. We’re working with design partners who have real billing problems - not demos. Start here - Website: arcenpay.com - Litepaper: arcenpay.com/litepaper - Docs: docs.arcenpay.com - GitHub: github.com/Arcenpay - SDK: docs.arcenpay.com/sdk/react/… - API: docs.arcenpay.com/api/overvi… - Demo Video: youtube.com/watch?v=Y5o8oTCU… - Telegram: t.me/arcenpay - Article: xitter.cf/arcenpayhq/status/2084… Every product sells access. Every agent needs to pay for it. ArcenPay connects the two. Book a demo from the site $ARCENPAY is now live on solana:So11111111111111111111111111111111111111112 via @Pumpfun CA: AGxb3YSQAQbd8iPx9SFucG6vWx2NYQ5Qfht493CVpump