2AYE
Guides, reference & supportCapability status

Documentation

AgentPay acceptance boundaries

Understand the separate authority, order, buyer-consent, capture and receipt gates.

One application, an independent authority boundary

AgentPay proposes and reviews purchases. 2AYE evaluates authority. The protected payment receiver must independently validate exact terms before execution. An AI recommendation never authorizes its own payment.

Four separate pieces of proof

Verify signed human authority, exact order binding, independent buyer consent, and protected execution with authentic evidence. Buyer consent alone does not establish 2AYE authority. A service-unavailable refusal does not prove an available service rejects an invalid grant.

Payment acceptance is still open

Do not infer an authorized payment from the public demo, unit tests or an application status. Protected capture remains disabled in the recorded production deployment; complete provider-backed success, replay, concurrency and uncertain-outcome acceptance remains outstanding.

Your governed workflow

Bring the next consequential action under control.

Show us the actor, protected resource, and action that must never execute without exact authority. We’ll map the decision and evidence path with you.

Discuss your workflow Read the implementation guide
AgentPay acceptance boundaries | 2AYE Documentation