Transactions are created automatically by the policy engine and payment verification flow — you never create them directly. Each transaction captures the full context of a payment attempt: which agent requested it, which mandate governed it, which merchant received it, the amount and resource involved, and the final outcome. Use this endpoint to build dashboards, reconcile charges, or investigate policy decisions.Documentation Index
Fetch the complete documentation index at: https://docs.usemandate.io/llms.txt
Use this file to discover all available pages before exploring further.
List transactions
Filter to transactions initiated by this agent.
Filter to transactions charged against this mandate.
Filter by transaction status. One of:
pending, approved, denied, paid, failed, refunded.Maximum number of results to return. Minimum
1, maximum 200.200
Array of transaction objects, ordered by
created_at descending.Example response
Transaction statuses
| Status | Description |
|---|---|
pending | Policy evaluation is in progress. Short-lived — resolves to approved or denied immediately. |
approved | Policy approved the payment. Awaiting proof verification to transition to paid. |
denied | Policy rejected the payment. See the audit log for the reason_code. |
paid | Payment proof was verified and the mandate budget has been charged. |
failed | An unexpected error occurred during policy evaluation or verification. |
refunded | Reserved for future use. |

