Authorization boundaries
- Never accept a payment solely from an agent prompt without valid user-approved authority.
- Enforce per-payment and delegated spending caps, expiration and recipient scope.
- Separate quote, authorization, guarantee, payout and final settlement states.
- Protect against replay and duplicate payment execution using idempotency.
Operational integrity
- Verify network/asset identities and chain-specific finality thresholds.
- Reconcile solver payouts and source reimbursement through the payment ledger.
- Keep execution private keys and authorization services out of frontend code.
Operational availability and security controls must be verified by the production payment service; the public product site is a documentation surface.