1. List the wallets visible to the authenticated account and select the returned public wallet ID and currency.
2. Read that wallet's current recorded balances.
3. Fetch its ledger and match relevant entries to the order, settlement or funding reference in your own reconciliation record.
4. Read the holds and distinguish active reservations from completed or released states as represented by the response.
5. Compare the related order and payment evidence before deciding whether the discrepancy is a pending operation, unpaid funding invoice or a completed settlement.

No. The wallet list uses its collection pagination. The current wallet-ledger helper returns a server-driven result and does not consume page or page_size controls. The holds helper requests up to 250 holds and also ignores those page controls. Do not assume a second page request proves you have retrieved older holds beyond that bound.

Use the meaning of the balance fields returned by the installed contract. A balance already representing spendable funds must not have reservations subtracted a second time. Keep decimal currency values exact and avoid merging wallets in different currencies into one unlabeled total.

First reconcile the original order, invoice and settlement. Do not edit ledger rows directly or create another top-up because a paid invoice has not yet appeared as credit. Provide the wallet, order and payment references to authorised billing support if the records disagree.

A custom dashboard should distinguish recorded balance, reserved work and completed charges clearly. It should also show its data freshness so a delayed job is not misrepresented as lost money or a duplicate charge.

• Track domain orders and cancel only work that remains cancellable
• Create funding invoices and configure an automatic top-up policy
• Request a settlement refund and track its decision separately from domain status
• What happens when my domain reseller purchase balance is low?