Introduction
Web3 billing is built on push payments. Every subscription renewal requires a fresh wallet signature, turning recurring revenue into a re-purchase and losing customers who never come back to approve. amser is the missing pull layer: users authorize spending once, and payments execute automatically on schedule.
What amser Does
- Users sign once to authorize future charges. No repeated wallet prompts.
- Payments execute automatically via the keeper network, on time, every cycle
- Funds never leave user wallets until each payment executes (non-custodial)
- Users can pause or cancel at any time, with no lock-in
How It Works
The merchant deploys a module, creates a plan with a price and interval, and sends users to the hosted checkout. The checkout handles wallet connection, the one-time Permit2 approval, and subscription signing in a single flow.
Once subscribed, the keeper network monitors due payments and executes them automatically. The merchant receives payment directly to their wallet, minus the protocol fee. No manual intervention, no cron jobs, no centralized scheduler.
The merchant's server receives a webhook on each payment event and can verify subscription status via the API or directly on-chain. Access control, dunning, and analytics are handled through the amser dashboard.
What You Can Build
| Use Case | Description |
|---|---|
| SaaS billing | Charge users monthly or annually in USDC, gate access on subscription state |
| API subscriptions | Recurring access to RPC nodes, indexers, and data feeds |
| Membership communities | Token-gate Discord roles, content, and features behind an on-chain subscription |
| On-chain services | Any protocol that needs reliable recurring revenue without custody |
For Developers
Under the hood, amser models recurring payments as authorization rather than money movement. Users grant a bounded, time-limited Permit2 allowance, and the protocol enforces it. This is why amser is non-custodial, why subscriptions are revocable without touching the merchant, and why the same primitive can eventually extend to agent spend management and usage-based credit systems. But the place to start is billing.
Reading Guide
- I want to accept recurring payments: Merchant Integration > Hosted Checkout > Webhooks
- I want to understand the protocol: RAI Concepts > Subscriptions > PaymentProcessor
- I want to integrate the API: API Keys > API Reference > Authentication
Quick Links
| Resource | Description |
|---|---|
| RAI Concepts | Core authorization model |
| Subscriptions | Time-based authorization |
| Usage Credits | Usage-based authorization |
| Smart Contracts | API reference |
| GitHub | Source code |