Approved provider payment
An agent completes an API payment within the provider and amount defined by the owner.
Pilot concept demo · WIP
Payments with rules the agent cannot rewrite.
Let software and AI agents pay for services with clear, owner-defined financial boundaries.
One policy. Multiple payment outcomes. See an agent complete an approved provider payment while the owner keeps control of the remaining funds.
A policy-bound payment flowOwner → Agent → Funds → Provider
OwnerDefines policy
AgentInitiates payment
FundsEnforce policy
ProviderReceives valid payment
Owner-defined policy travels with the funds.
Policy in action
Same authority. Different result.
From policy to provider payment, with owner control preserved throughout the flow.
Useful autonomy, with policy carried through the payment flow.
For the critical comparison, use the same agent/signing authority twice. The approved transaction completes; the rules attached to the funds determine the permitted path for the second request.
01Owner defines policy
Set the approved provider, payment limit, and recovery path.
02Funds are prepared
Place funds under the policy-bound control path.
03Agent requests payment
Software asks to pay the approved provider.
04Approved payment completes
The same agent/signing authority pays within policy.
05Policy protects the boundary
The same authority tries a different transaction; the funds follow only a permitted path.
Foundation
Built across the stack
The pilot concept draws on Wallet delivery, Bitcoin Cash ecosystem experience, and controlled-payment research.
Released product
OPTN Wallet brings BCH, CashTokens, WalletConnect, and advanced transaction tools into one self-custody product.
Ecosystem experience
CashToken tooling, covenant workflow experience from FundMe.cash, and open Bitcoin Cash infrastructure.
Pilot exploration
Controlled payments, agent integration, monitoring, and organizational policy workflows for scoped pilot projects.
Value
Autonomy with owner control
Policy-based execution
The same agent/signing authority can request another payment, while the funds follow only a permitted transaction path.
Owner control
The owner keeps a defined recovery and control path for the remaining funds.
Resources
Explore the foundation
OPTN Wallet
The released BCH and CashTokens wallet at the center of the OPTN ecosystem.
FundMe.cash
Real-fund covenant workflows for contributions, claims, and refunds.
Open-source implementation
Review the public OPTN Wallet implementation and transaction tooling.
How enforcement works
See how programmable payment coordination and rule enforcement fit together on BCH.
Build with OPTN
Explore OPTN Wallet, review the public implementation, or contact us about a controlled-payment pilot project.