About amser
Building programmable authorization for recurring payments
Building programmable authorization for recurring payments
amser is a protocol for time bound spending authority. It lets a user authorize rules once, then have those rules enforced over time, without custody.
The goal is to make subscriptions, access control, and just in time transactions reliable primitives that developers can build products on.
amser is a decentralized protocol designed to enable recurring, programmable authorization without custody.
As software systems become increasingly autonomous, particularly with the rise of AI agents, the ability to grant ongoing authority safely and predictably has become a foundational problem. Blockchains excel at one-off transactions, but they lack a native way to express bounded, ongoing permission. amser exists to address that gap.
Why amser exists
Why amser exists
Most systems still treat recurring payments and automated execution as an off chain problem. You end up with retries, edge cases, and a lot of trust in backend logic.
amser exists to make authorization explicit and enforceable. Systems should be able to answer:
what actions are permitted
for how long
under what limits
and under whose authority
That applies to subscriptions, access, agents, and infrastructure fees.
Most existing systems treat recurring activity as a payment problem.
In practice, recurring activity is an authorization problem.
Autonomous agents, long-running services, and on-chain applications need to know:
what actions are permitted
under what limits
for how long
and under whose authority
Relying on repeated approvals, custodial wallets, or unlimited allowances introduces risk and fragility, particularly when systems are designed to operate continuously.
amser was built to make ongoing authorization explicit, enforceable, and revocable.
Authorization as a first-class primitive
Authorization as a first-class primitive
Instead of signing every transaction, users authorize a bounded rule set that can be executed over time.
Budgets
Set a maximum spend over a time window. Execution is allowed only within those limits.
Budgets
Set a maximum spend over a time window. Execution is allowed only within those limits.
Budgets
Set a maximum spend over a time window. Execution is allowed only within those limits.
Budgets
Set a maximum spend over a time window. Execution is allowed only within those limits.
Units
Define execution in discrete units. Useful for subscriptions, usage billing, and quotas.
Units
Define execution in discrete units. Useful for subscriptions, usage billing, and quotas.
Units
Define execution in discrete units. Useful for subscriptions, usage billing, and quotas.
Units
Define execution in discrete units. Useful for subscriptions, usage billing, and quotas.
Vouchers
Issue permission scoped to a product or plan, with clear expiry and constraints.
Vouchers
Issue permission scoped to a product or plan, with clear expiry and constraints.
Vouchers
Issue permission scoped to a product or plan, with clear expiry and constraints.
Vouchers
Issue permission scoped to a product or plan, with clear expiry and constraints.
Payments are one outcome of authorization. Subscriptions, access control, and just in time execution are all the same model applied to different surfaces.
Who amser is built for
amser is infrastructure for systems that need to operate continiously without holding funds or unlimited permissions.
Subscription-based applications
Autonomous agents and services
On-chain protocols with recurring execution
Usage-based and metered systems
Who amser is built for
Who amser is built for
amser is for teams building products that need recurring execution without holding funds or relying on unlimited permissions.
subscription and membership products
access control and entitlement systems
usage based billing and quotas
agents and automation services
infrastructure providers charging predictable fees
If you are starting from scratch, adapters are the quickest way to integrate.
Who amser is built for
amser is infrastructure for systems that need to operate continiously without holding funds or unlimited permissions.
Subscription-based applications
Autonomous agents and services
On-chain protocols with recurring execution
Usage-based and metered systems
Authority should be explicit, bounded, and revocable.
amser is building toward that standard for recurring payments and just in time transactions.
amser is building toward that standard for recurring payments and just in time transactions.
© 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