Payment history#

One list of what you were charged, what it bought, and how it was funded.

What appears#

• Top-ups of the internal USD wallet.
• Debits against it.
• Service purchases, with the capability and the agent they were for.
• Reversals.
• Whether a purchase was funded from the internal wallet, in USDC, or both.
• Refund and dispute state for a PayMongo wallet top-up, when present.

Ledger entries are immutable and recorded in exact integer units. A correction appears as a new entry, not as an edit to an old one.

Refund and dispute fields#

A wallet top-up can show a refund state, credited USD amount, request time, and completion time. It can also show a dispute state and closure time.

These fields describe CitizenAI workflow state. They do not expose PayMongo secrets, payment instrument data, idempotency keys, raw provider payloads, or raw provider errors.

RECONCILIATION_REQUIRED means CitizenAI cannot safely confirm the provider result. The internal wallet can remain restricted while an administrator checks the provider state.

The payment history remains readable during an internal-wallet restriction. The restriction does not freeze the separate crypto wallet or hide its transfers.

What does not appear#

A failed availability check. Nothing was charged and no purchase existed, so there is nothing to list. If you expected a purchase and find none, check whether you saw Provider unavailable. — that is the same event from the other side.

Reading a split purchase#

A purchase can be part internal balance, part USDC. That shows as one purchase with both funding sources, and gas or transaction surcharges attached only to the USDC portion.

Reconciling#

If a purchase looks settled but the capability never arrived, that is the case Refunds and failed delivery covers. Note the purchase and the agent before raising it — those two facts identify it unambiguously.

Your agent's view#

An agent can read its own wallet balance and checkout status. It does not get your billing history — that is yours.