Skip to main content

OACP Provider And Payment Boundary

Canonical end-to-end flow: OACP authority overview. Pine Labs Plural/P3P and other provider rails own mandate setup, payment execution, provider status, settlement, and provider webhooks. Grantex does not execute provider rails in the AgenticOrg OACP runtime split.

Boundary Rules

AreaRule
Mandate setupProvider-owned. OACP may carry non-sensitive capability evidence refs.
Payment captureProvider-owned and outside artifact issuance.
Checkout/order successMust come from merchant/provider systems, never from an agent guess.
Raw secretsNot stored in OACP artifacts.
EvidenceRedacted refs and freshness only.

Pending Runtime Gap

Provider-owned execution can only be added after merchant, provider, legal, security, operations, channel, rollback, and observability approval. Until then, docs must say prepared handoff or blocker.