UNSUPPORTED_PROTOCOLThe declared source protocol is not supported.
OPEN TECHNICAL SPECIFICATION · V2.0.0
A common execution boundary for autonomous payments.
The Mandate Execution Boundary defines the minimum interoperable envelope, decision and enforcement rule an AI commerce system needs before money moves.
Required behavior
- Resolve the final amount, currency and merchant before evaluation.
- Bind the request to a stable mandate, agent and payment-attempt identifier.
- Require explicit consent and a finite authorization expiry.
- Return ALLOW, REVIEW or BLOCK with stable machine-readable reason codes.
- Consume idempotency durably in production to prevent replay.
- Execute payment only after ALLOW; never reinterpret REVIEW as approval.
- For the strict profile, verify signed authority evidence and its transaction bindings before policy evaluation.
- Issue a portable signed receipt that independently commits to both input and decision digests.
PORTABLE CONTRACTS
Use the same meaning across every protocol.
Purchase envelope JSON Schema/schemas/purchase-envelope.jsonDecision receipt JSON Schema/schemas/decision-receipt.jsonCryptographic evidence JSON Schema/schemas/cryptographic-evidence.jsonSigned decision receipt v2/schemas/decision-receipt-v2.jsonReceipt verification JWKS/.well-known/jwks.jsonPrivacy-thresholded threat intelligence/api/v1/threat-intelligenceCanonical reason-code registry/reason-codes.jsonReference HTTP implementation/openapi.json
STABLE REASON CODES
MISSING_MANDATE_IDNo stable identifier links the purchase to user authority.
MISSING_AGENT_IDThe acting agent cannot be identified.
MISSING_MERCHANTThe final seller or payee is absent.
INVALID_AMOUNTThe proposed amount is missing, zero, negative or malformed.
INVALID_CURRENCYThe transaction currency is not a three-letter code.
MISSING_SPEND_CAPThe user authority has no usable maximum amount.
SPEND_CAP_EXCEEDEDThe final amount is above the user-approved maximum.
REFERENCE IMPLEMENTATION