Update, 20 October 2026. Grantex now binds the capability verifier’s redacted evidence object into the signed
mandate_capability artifact (verified, unavailable or unverified), and issues Intent, Cart and Payment mandates whose payment rail may be Plural. A mandate authorizes; Plural still executes the payment. Current status: OACP runtime launch closure PRD.Summary
Plural owns the mandate and payment rail. AgenticOrg verifies provider-owned capability metadata and Grantex binds the redacted evidence into the signedmandate_capability artifact.
Target Audience
Fintech partners, payment operators, and commerce risk teams.Architecture Diagram
End-To-End Flow
AgenticOrg checks whether provider capability metadata is available for the merchant and requested action. The result becomes a redacted evidence ref. Grantex OACP policy can require that evidence before a handoff is prepared.What Is Implemented Now
AgenticOrg has a Plural capability verifier and purchase-preparation blocker. Grantex models mandate capability as an OACP artifact family and marks provider execution authority as provider-owned.What Requires External Approval Or Config
Provider credentials, environment approval, webhook/reconciliation path, merchant approval, and rollback owner.Failure Modes
- Provider config missing.
- Sandbox/non-production environment mismatch.
- Capability evidence older than allowed TTL.
- Buyer asks to create a mandate from cache only.
Safe User Wording Examples
- “Provider capability evidence is present for preparation only.”
- “No mandate, payment, or order was created.”
- “Provider setup is missing; the request is blocked.”