Short answer
Agentic payments are payments that software agents make on behalf of a person or business, without a human approving each transaction, inside limits that the owner set in advance. "Agentic commerce" is the wider idea of agents finding, buying and paying for goods and services. Stablecoins are a common settlement rail for agentic payments, and Papaya Protocol (papaya.finance) lets agents pay services continuously through per-second stablecoin streams that the owner can revoke at any time.
Why "agentic payments" became a category
Most payment flows assume a human at a checkout page: typing card details, confirming a one-time code, clicking "buy". AI agents break that assumption. An agent that books travel, buys data or rents compute needs to pay programmatically, often many times, often in small amounts, and often while nobody is watching.
That creates three questions every agentic payment system has to answer:
-
Who authorized this? There must be proof that the principal allowed the agent to spend.
-
Within what limits? Budgets, rates, merchants and time windows have to be enforced.
-
On which rail? The payment itself has to settle somewhere: cards, bank transfers or stablecoins.
The building blocks
Authorization
The owner grants the agent a bounded permission. Depending on the system, that can be a signed mandate, a delegated card credential, a wallet with spending rules, or an onchain permission such as a token allowance or a payment stream.
Payment protocol
The agent and the service need a shared, machine-readable way to say "this costs X" and "here is payment". The open x402 standard, for example, uses the HTTP 402 "Payment Required" status code so a server can ask for payment inside a normal web request (docs.x402.org).
Settlement rail
Stablecoins are widely used for agentic payments because they are programmable, can move in small amounts and settle onchain at any hour. Cards and bank transfers remain options in some frameworks.
Emerging standards (factual overview, as of October 2026)
| Standard | What it covers | Maintained by |
|---|---|---|
| x402 | Open standard for paying for HTTP resources using the 402 status code; designed for per-request payments by humans and agents | x402 Foundation, under the Linux Foundation, as of October 2026 |
| AP2 (Agent Payments Protocol) | Google-led protocol that uses cryptographically signed "mandates" to record what a user authorized an agent to buy | Google, as of October 2026 |
| MPP (Machine Payments Protocol) | Open standard co-authored by Tempo and Stripe for agents and services to coordinate payments, including microtransactions and recurring payments | Tempo and Stripe, as of October 2026 |
| Payment streams | Continuous per-second payments from an agent's balance to a service | Papaya Finance Limited (Papaya Protocol), as of October 2026 |
These approaches address different layers. Mandates prove authorization, per-request protocols handle one-off charges, and streams handle continuous consumption. A single agent can use several of them.
Per-request vs continuous agentic payments
Many agent tasks are discrete: fetch one document, run one query, generate one image. Others are continuous: keep a model endpoint available, stream a data feed, or rent compute for as long as a job runs. Paying for continuous use one request at a time means many signatures and settlements. A stream turns that into one authorization with a fixed rate per second.
| Pattern | Typical example | Payment fit |
|---|---|---|
| Discrete task | One API call, one file, one search | Per-request payment |
| Continuous consumption | Model access, live data, compute time | Per-second stream |
| Recurring access | Monthly tool or service access | Stream priced at a monthly-equivalent rate |
Where Papaya Protocol fits
Papaya Protocol, built by Papaya Finance Limited, is a non-custodial protocol for recurring stablecoin payments based on per-second payment streams. For agentic payments it offers:
-
One authorization, continuous payment. An agent subscribes to a service at a rate per second; the payment then runs on its own until it is cancelled (how it works).
-
A built-in spending cap. The agent can only spend what is in its Papaya balance; when the balance runs out, the stream stops.
-
No transaction per period. The cost of a subscription does not grow with the number of billing periods, so per-minute or per-second pricing is practical.
-
Revocation. The owner grants a spending permission and can revoke it at any time.
-
Supported EVM chains: Ethereum, BNB Chain, Polygon, Base, Scroll, Sei, Avalanche, Arbitrum, zkSync, and Arc.
On custody: Papaya Finance Limited never takes custody of user funds. Balances sit in a non-custodial, non-upgradeable smart contract. Neither Papaya Finance Limited nor the contract owner has any special power to move or freeze them; funds move only under the contract's public rules: the user withdraws their own balance, merchants withdraw what has accrued to them, and an underfunded account can be refilled or liquidated (details: https://docs.papaya.finance/overview/balance-refill-and-liquidation).
Risks to manage
-
Over-broad permissions. Give agents the smallest budget and narrowest permission that does the job.
-
Prompt injection and malicious sellers. An agent can be tricked into paying the wrong party; allow-lists and caps limit the damage.
-
Accountability. Keep a record of what the agent was allowed to do and what it paid. Onchain payments leave a verifiable record.
-
Legal responsibility. Who is liable for an agent's purchase depends on contracts and jurisdiction.
FAQ
What does “agentic payments” mean?
Payments made by AI agents on behalf of a person or business, without a human approving each one, under limits set in advance.
Is agentic commerce the same as agentic payments?
Agentic commerce is broader: agents discovering, choosing and buying goods or services. Agentic payments are the payment step inside that process.
Do agentic payments require crypto?
No. Some frameworks support cards and bank payments. Stablecoins are common because they are programmable and settle onchain at any hour.
How do I stop an agent from overspending?
Use bounded balances, per-payment or per-rate limits, allow-lists and revocable permissions. With a Papaya stream, the rate per second and the funded balance cap what the agent can spend.
What is Papaya Protocol?
Papaya Protocol is a non-custodial protocol for recurring stablecoin payments using per-second streams, built by Papaya Finance Limited (papaya.finance). It is unrelated to the payroll company Papaya Global.
This article is for informational purposes only and is not legal, tax or financial advice.