Transactions executed through the SDK (Documentation Index
Fetch the complete documentation index at: https://docs.chipipay.com/llms.txt
Use this file to discover all available pages before exploring further.
transfer, purchaseSku, executeTransactionWithSession, etc.) are automatically recorded against the wallet. This page covers reading that history and recording transactions executed outside the SDK.
List transactions
getTransactionList returns a paginated history of transactions for a wallet. walletAddress is required; everything else is optional.
PaginatedResponse<Transaction>:
Filter by date
year, month, and day narrow the list to a specific calendar window. Useful for monthly reports or per-day audits.
calledFunction (e.g., "transfer", "approve").
Record an external transaction
recordSendTransaction stamps a transaction that was executed outside the SDK into Chipi’s records. Use it when a wallet sent a transfer through some other path (a wallet UI, another service) and you want it to show up in getTransactionList and the dashboard.
expectedAmount is a decimal string in human units (e.g., "1.5" for 1.5 USDC), not raw token units — different from getTokenBalance.balance which returns raw units.
The endpoint validates the on-chain Transfer event matches your expected* fields. If the tx hash isn’t yet confirmed, or the actual transfer doesn’t match what you claimed, the call rejects.
Putting it together
A monthly statement endpoint for a user’s gasless wallet:✅ Verified bystaging-integration/staging-transactions.test.tsat commitb0f8715(2026-03-21). Runs in CI on every PR fromstaging→mainagainst live staging — covers paginated list, date filtering, and recording an external transaction. Zero on-chain cost.
