> ## Documentation Index
> Fetch the complete documentation index at: https://docs.grantex.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Provider-Owned Mandate And Payment Evidence In OACP

> Payment and fintech partner explainer for OACP evidence boundaries.

# Provider-Owned Mandate And Payment Evidence In OACP

Canonical end-to-end flow: [OACP authority overview](../overview).

OACP can carry evidence references that a provider-owned capability check occurred. It does not store raw payment secrets or execute the rail.

```mermaid theme={null}
flowchart LR
  agentic[AgenticOrg verifier] --> provider[Pine Labs Plural/P3P]
  provider --> evidence[Redacted evidence ref]
  evidence --> artifact[OACP mandate_capability artifact]
  artifact --> handoff[Prepared handoff or blocker]
```

## Evidence Boundaries

| Item       | Allowed in OACP                 | Not allowed in OACP                                     |
| ---------- | ------------------------------- | ------------------------------------------------------- |
| Capability | Redacted provider evidence ref. | Raw credential or token.                                |
| Status     | Freshness and capability label. | Provider secret response body.                          |
| Payment    | Boundary state only.            | Capture, checkout URL, order success, mandate creation. |

## Partner Action

Provide a capability-verification endpoint or partner process that returns non-sensitive evidence refs, expiry, and environment state. Execution remains with the provider rail.