Live integration, real transaction
A customer asks an autonomous agent for a refund. Your policy decides if it is authorized.
This page walks through a working integration between a Phinite autonomous agent and Parmana: the agent proposes a refund, your policy determines whether it is authorized, and only an authorized path executes it against Paytm.
The walkthrough
The refund, end to end
A customer request in the Phinite agent, Parmana's authorization decision, and the execution evidence it produces.
Every request resolves to one of three outcomes
DENIED
Stop
Execution does not proceed. The agent cannot retry with altered parameters, fabricate trusted signals, or call the provider directly.
AMBIGUOUS
Verify
The final execution state cannot be established yet. The transaction is held for verification instead of being reported as success or failure.
APPROVED
Execute
The authorized path proceeds and the execution is preserved as verifiable evidence.
A real transaction from this integration
- Decision
- APPROVED
- Authorization ID
- 69abe6c1-48af-483a-8774-4783cb2ca31d
- Business transaction
- e8a7d9ed-7942-4a73-897d-d1b3577347ef
Parmana authorized this transaction. Provider side settlement is confirmed separately through provider evidence, Parmana does not claim it on the provider's behalf.
This is a working integration, not a mockup.
Read the docs to see how the authorization boundary works, or talk to us about running a pilot on your own agentic workflow.