Activity and receipts

Activity lists the payments and the approval requests on the account you have selected. Open one to see its receipt.

#What you see

• An owner sees every payment on the account.
• A spender sees their own payments.
• Approval requests show where they are: waiting for approval, approved, payment pending, paid, declined, withdrawn or expired.
• A payment that settled an approved request shows once, as its receipt.

#Where the figures come from

Activity does two separate jobs:

1. Finding payments. Envio HyperSync is asked for every Paid event from every deployment of the account. Nuntio's main account has been redeployed over time, so older payments on earlier deployments still appear.
2. Proving them. Every payment shown is read again from its own transaction receipt over Monad's RPC, and decoded from the account's own Paid event. The amount, the payee and the service come from there, never from the index.

The amount on a receipt is the amount the contract measured leaving the account: its balance before the transfer minus its balance after. It is never a number someone supplied.

#Unknown is not zero

• A figure Nuntio could not read shows as a dash, never as $0. A dash is not zero.
• A payment the index found but the chain has not confirmed yet shows as verifying, without an amount. It is never dropped.
• If the history could not be fully read, the page says how far it got. An empty list only means "nothing has happened" when the history is complete.
• A receipt that cannot be read yet is pending. Do not send the payment again while it is pending.

#Team accounts

A team's history is read the same way. The index learns each team from the team factory's own record of creating it, so a team's payments are covered from the block it was made in. The team's owner, whoever the team's owner() names on chain right now, sees every payment on it. A member sees their own.

#Download a file

Download CSV, under the list, saves the payments you can see on the account as a CSV file: the date (UTC), the service, the amount, the spender, the note, whether it was paid directly or settled after an owner approved it, the approval request, the transaction hash and an explorer link. Approval requests that moved no money are not in it.

• Set dates in Filters to cut the file to those days.
• A file is built only when the whole history has been read and every payment checked against its receipt. If not, you are told why and nothing is downloaded.
• One file holds up to 500 payments. For more, choose a shorter date range.

#Checking a receipt yourself

Every payment is a Monad transaction. Look it up on Monadscan for mainnet or the testnet explorer for testnet. In the transaction's logs, the account's Paid event names the spender, the service, the payee and the amount, and the AUSD Transfer beside it moves the same amount.

#Cached figures

Balances and limits on screens like Home may be a few seconds old, because the app reuses recent reads. These figures are for display only. Every payment, simulation and owner decision reads the chain directly, and nothing authorizes on a cached figure.