Improved

Wallet Balances table rebuilt

The WALLET_BALANCES table in your Data Warehouse now derives each wallet’s balance directly from its transaction history, and matches the balance returned by the Monta API’s GET `/api/v1/wallets/{walletId}` endpoint.

What’s new

  • Full wallet coverage. Every wallet in your scope now has a row, including wallets with no transaction history, which report a balance of 0. Expect a significant increase in row count.
  • New BALANCE_AT column giving the timestamp of the most recent completed transaction behind each balance, so you can see how current a row is.

Action required

  • ID values have changed. ID remains unique and stable per wallet, but values are not carried over from the previous version of the table. If you store or join on ID, please re-key on WALLET_ID — that’s the reliable identifier for a wallet’s balance.
  • Three columns removed: CREATED_AT, UPDATED_AT and NEGATIVE_BALANCE_AT. These described internal record-keeping rather than the balance itself and are no longer populated. Please remove any references to them.
  • Need a real-time balance? Use GET /api/v1/wallets/{walletId} in the Monta API. Note that the wallet list endpoint doesn’t include balances, so the Data Warehouse table remains the efficient way to read balances in bulk.