Provider Boundary
Pine Labs Plural/P3P owns mandate and payment rail execution for the current verifier. Bank-owned, fintech, and custom provider rails are represented as provider-owned config refs until approved adapters exist.
No Raw Secrets
OACP artifacts and cache records must not store provider tokens, raw response bodies, card data, bank data, checkout URLs, or payment URLs.
Prepared Handoff
When evidence is fresh, AgenticOrg can prepare a handoff. When evidence is missing or stale, it returns an exact blocker.
Frequently Asked Questions
Does capability evidence mean a mandate was created?
No. It means capability metadata was verified for preparation.
Where does payment confirmation come from?
Only from approved provider and merchant systems.
Topics
Plural Pine OACPprovider-owned mandatepayment evidenceP3P commerce
Ready to try it?
Evaluate the workflow with your own approved data, integrations, review gates, and success criteria.
Read OACP boundaries