Skip to main content
The Transactions page is a complete, read-only log of every payment your AI agents have requested through Pay3. Whether a transaction succeeded on-chain, failed a policy check, or expired in the approvals queue, it appears here. Use this page to audit AI spending, investigate failed payments, and verify on-chain settlement.

Reading the transactions list

Each entry in the list shows:

Transaction statuses

Every transaction moves through a lifecycle. The status field tells you exactly where in that lifecycle each transaction sits:
Transactions are immutable on the Stellar blockchain. Once a transaction reaches SUCCESS status, Pay3 cannot reverse or refund it. If an AI sends funds to the wrong address, you must contact the recipient directly. Always verify recipient addresses in your Contacts list.

Viewing a transaction on Stellar Explorer

When a transaction has a Stellar transaction hash (visible once the status reaches SUBMITTING or SUCCESS), click the hash to open it in Stellar Explorer. The explorer shows the full on-chain details: the source and destination accounts, the asset and amount transferred, the ledger it was included in, and the fee paid.
Pay3 supports both testnet and mainnet. The Stellar Explorer link automatically points to the correct network based on which network your smart account contract is deployed on.

Budget tracking and daily resets

Pay3 tracks cumulative spending per session against the daily budget defined in the session’s policy. The budget counter resets every day at midnight UTC. You can review current budget consumption per session from the Overview page.
Only transactions with SUCCESS status count toward the daily budget. FAILED and EXPIRED transactions do not consume budget. PENDING transactions reserve budget until they are approved (and succeed) or expire.
Once an AI session has reached its daily budget ceiling, Pay3 rejects any further transaction requests from that session for the remainder of the day, returning an error to the AI assistant. The budget resets at midnight UTC and the session can resume spending.
The Transactions page currently shows all transactions across all sessions. To filter by session, check the Action and timestamp columns — each session’s activity is logged in chronological order. Per-session filtering is on the Pay3 roadmap.

FAILED transactions — common causes

If you see transactions with FAILED status, the table below covers the most common reasons: