Programmable authorization for recurring payments
A protocol primitive for subscriptions, access, and just-in-time transactions
Non custodial, deterministic, adapter friendly
Non custodial • Time bound delegation • Deterministic execution
Time bound authority
Permissions include limits and expiry.
Time bound authority
Permissions include limits and expiry.
Time bound authority
Permissions include limits and expiry.
Time bound authority
Permissions include limits and expiry.
Deterministic windows
Executions happen only within defined windows.
Deterministic windows
Executions happen only within defined windows.
Deterministic Automation
Keeper nodes trigger charges on-chain, ensuring reliability without central servers.
Deterministic windows
Executions happen only within defined windows.
Idempotent execution
One execution per window. Safe under retries.
Idempotent execution
One execution per window. Safe under retries.
Transparent Fee Split
Every transaction distributes fees instantly to merchants, keepers, and treasury.
Idempotent execution
One execution per window. Safe under retries.
Multi chain
Designed to work across chains and tokens.
Multi chain
Designed to work across chains and tokens.
Cross-Chain Future
Designed for multi-chain expansion — one protocol, many execution layers.
Multi chain
Designed to work across chains and tokens.
Authorize rules, not transactions
Authorize rules, not transactions
Recurring payments often become a mix of signatures, retries, and off chain assumptions.
Amser makes the rule explicit. Authorize once, then enforce it over time with state that can be inspected and indexed.
Adapters apply the same primitive to real outcomes such as access control, billing events, and API gating.
Web3 still lacks a native standard for automated payments.
SubNetwork introduces an open, non-custodial protocol for recurring billing and automated payments — built for merchants, developers, and keeper operators.
Bridging Web2 simplicity with Web3 sovereignty, it brings familiar recurring payment experiences to a decentralized world — trustless, user-controlled, and seamless.
Define Rule
Create plans and constraints as explicit on chain state.
Define Rule
Create plans and constraints as explicit on chain state.
Define Rule
Create plans and constraints as explicit on chain state.
Define Rule
Create plans and constraints as explicit on chain state.
Authorize once
Users grant time bound permission without repeated approvals.
Authorize once
Users grant time bound permission without repeated approvals.
Authorize once
Users grant time bound permission without repeated approvals.
Authorize once
Users grant time bound permission without repeated approvals.
Enforce over time
Execution follows deterministic windows with clear failure reasons.
Enforce over time
Execution follows deterministic windows with clear failure reasons.
Enforce over time
Execution follows deterministic windows with clear failure reasons.
Enforce over time
Execution follows deterministic windows with clear failure reasons.
Authorization and execution become predictable building blocks.
Authorization and execution become predictable building blocks.
Protocol first. Products on top.
Subscriptions are one use case. Adapters are how the protocol integrates into real products.
Access adapter (Discord)
Grant and revoke roles based on paid status.
Billing events adapter (Webhooks)
Emit subscription lifecycle events to your backend.
API access adapter
Gate API keys and endpoints by paid access.
Subscriptions and memberships
Recurring charges enforced by deterministic execution windows.
Agents
Time bound spending authority for automations.
Infrastructure fees
Automate fee splits with predictable execution.
One execution model underneath. Multiple product surfaces.
Protocol first. Products on top.
Subscriptions are one use case. Adapters are how the protocol integrates into real products.
Subscriptions & memberships
Recurring access to products, protocols, or services — enforced automatically over time.
Smart contract access control
Gate functions, features, or mints based on active authorization state.
Autonomous agents
Agents that operate continuously with safe, delegated authority and strict execution rules.
Protocol infrastructure fees
Automated fees that execute predictably without manual intervention or cron jobs.
API & SaaS access
Time-bound authorization backing on-chain and off-chain services with expiring permissions.
Usage-based billing
Metered execution that runs within predefined limits, without repeated user signatures.
One execution model underneath. Multiple product surfaces.
Protocol first. Products on top.
Subscriptions are one use case. Adapters are how the protocol integrates into real products.
Access adapter (Discord)
Grant and revoke roles based on paid status.
Billing events adapter (Webhooks)
Emit subscription lifecycle events to your backend.
API access adapter
Gate API keys and endpoints by paid access.
Subscriptions and memberships
Recurring charges enforced by deterministic execution windows.
Agents
Time bound spending authority for automations.
Infrastructure fees
Automate fee splits with predictable execution.
One execution model underneath. Multiple product surfaces.
Protocol first. Products on top.
Subscriptions are one use case. Adapters are how the protocol integrates into real products.
Access adapter (Discord)
Grant and revoke roles based on paid status.
Billing events adapter (Webhooks)
Emit subscription lifecycle events to your backend.
API access adapter
Gate API keys and endpoints by paid access.
Subscriptions and memberships
Recurring charges enforced by deterministic execution windows.
Agents
Time bound spending authority for automations.
Infrastructure fees
Automate fee splits with predictable execution.
One execution model underneath. Multiple product surfaces.
Protocol guarantees
Protocol guarantees
Protocol guarantees
These are properties of the system.
These are properties of the system.
These are properties of the system.
Transparent and verifiable
All authorization and execution logic lives on-chain. Anyone can verify what is allowed, when it executes, and why.
Transparent and verifiable
All authorization and execution logic lives on-chain. Anyone can verify what is allowed, when it executes, and why.
Deterministic execution
Actions execute only when predefined conditions are met. Execution may be attempted multiple times, but can only succeed once, and only within valid execution windows — deterministic and on-chain.
Deterministic execution
Actions execute only when predefined conditions are met. Execution may be attempted multiple times, but can only succeed once, and only within valid execution windows — deterministic and on-chain.
Transparent and verifiable
All authorization and execution logic lives on-chain. Anyone can verify what is allowed, when it executes, and why.
Transparent and verifiable
All authorization and execution logic lives on-chain. Anyone can verify what is allowed, when it executes, and why.
Deterministic execution
Actions execute only when predefined conditions are met. Execution may be attempted multiple times, but can only succeed once, and only within valid execution windows — deterministic and on-chain.
Deterministic execution
Actions execute only when predefined conditions are met. Execution may be attempted multiple times, but can only succeed once, and only within valid execution windows — deterministic and on-chain.
Non-custodial by design
Funds never sit in an amser wallet.
Non-custodial by design
Funds never sit in an amser wallet.
Non-custodial by design
Funds never sit in an amser wallet.
Time-bound authorization
Permissions include explicit limits and expiry.
Time-bound authorization
Permissions include explicit limits and expiry.
Time-bound authorization
Permissions include explicit limits and expiry.
Deterministic execution windows
Executions happen only within defined windows.
Deterministic execution windows
Executions happen only within defined windows.
Deterministic execution windows
Executions happen only within defined windows.
Transparent and verifiable
Rules and state can be inspected and indexed.
Transparent and verifiable
Rules and state can be inspected and indexed.
Transparent and verifiable
Rules and state can be inspected and indexed.
These guarantees apply to every execution — without exception.
Built for developers
Built for developers
Built for developers
Predictable primitives for subscriptions and just in time execution.
Explicit state, clear failure modes, and clean indexing.
Predictable primitives for subscriptions and just in time execution.
Explicit state, clear failure modes, and clean indexing.
Predictable primitives for subscriptions and just in time execution.
Explicit state, clear failure modes, and clean indexing.
Clear, composable primitives with no hidden flows
Predictable behavior under retries, failures, and edge cases
On-chain authority with off-chain liveness support
Consistent guarantees across every execution path
Developers can rely on this behavior across all execution paths.
© Copyright 2026, All Rights Reserved by Amser Protocol LTD
© Copyright 2026, All Rights Reserved by Amser Protocol LTD
© Copyright 2026, All Rights Reserved by Amser Protocol LTD
© Copyright 2026, All Rights Reserved by Amser Protocol LTD