Agentic payments · in development
AI assistants are starting to run billing tasks and to buy on a customer's behalf. Payware is building the controls that make this safe: keys that can only do what you allow, spending limits that are enforced with the charge, approvals the customer gives on a page we host, and a record of everything an agent did. Most of this is not released yet, and this page says which parts.
A support or billing assistant that looks up payments, customers and subscriptions, or starts a card enrollment. This ships first, because it depends only on Payware.
A shopper's assistant buys from your business within limits the customer set and approved. This comes after, and depends on NETOPIA Payments and on the standards settling.
These parts of Payware already work and are what agent features are built on.
Customers enter card details on NETOPIA Payments' hosted page. Payware stores only a reusable instrument token, never the card number, so an agent never handles card data.
After a customer enrolls a card once, your server can charge it later without the customer present.
Retrying a request with the same key never creates a second charge. Agents retry a lot, so this matters.
An OpenAPI description and test keys let you try an integration, or an agent, without moving money.
Payment and review events reach your server with a signature, so automation can react to what happened.
A payment that needs a decision is held for review and resolved explicitly, instead of being silently accepted.
In the order we plan to build it. None of this is released, and the order may change.
Keys limited to the actions you choose, with a cap per payment and per day, and a record of every payment an agent starts.
Let your own assistant use Payware as a tool. Read-only by default, with writes and money movement only where a key and an approval allow it.
A customer approves an amount, budget and expiry for an agent on a page Payware hosts. Payware enforces it with each charge and keeps the approval.
Checkout for assistants that follow the ACP and UCP standards, using NETOPIA Payments' card vault so card numbers stay out of Payware. Depends on NETOPIA Payments.
Agents pay per use for an API or resource in stablecoin, and Payware delivers once a licensed partner confirms settlement. Payware never holds the funds. Needs a partner and a regulatory review first.
Tool results never contain API keys, webhook secrets or card data. A card is collected only on NETOPIA Payments' hosted page.
The customer approves on a Payware page, not inside the conversation, so a hijacked prompt cannot approve itself.
A budget is consumed in the same step as the charge, so two requests at once cannot overspend it.
When the issuer asks for a challenge, the customer is redirected to complete it and the payment resumes. Payware does not decide exemptions.
Each payment records whether a person, the scheduler or an agent started it, and which key and approval were used.
Agent standards change often. They are supported behind version-pinned adapters, so the core API stays stable.
Everything an agent will build on is available in test mode now.