GET /transactions

Flat list of payments and withdrawals attributed to the merchant's smart-wallets. Mirrors the shape the merchant wallet UI already renders, so backends that don't want to deal with the invoice abstraction can read this endpoint directly.

Request

GET /transactions?owner=0xMerchant…

Query	Required	Notes
owner	yes (auth modes)	The merchant address whose history you want. Subject to session-signed auth.
chainId	optional	Restrict to one chain. Omit to receive cross-chain history.
offset	optional	Pagination cursor (zero-based).
limit	optional	Page size. Clamped to 200.

The signed payload for owner-scoped reads is the request URI (path + query) — see Authentication.

Response

{
  "items": [
    {
      "type": "deposit",
      "txHash": "0x…",
      "logIndex": 0,
      "chainId": "1",
      "token": "0xdac17f958d2ee523a2206206994597c13d831ec7",
      "from": "0xPayer…",
      "amount": "100",
      "vsValue": 100.0,
      "timestamp": 1730393900,
      "guid": "29f3b386-…"
    },
    {
      "type": "withdraw",
      "txHash": "0x…",
      "logIndex": 0,
      "chainId": "1",
      "token": "0x0000000000000000000000000000000000000000",
      "from": "0xSmartWallet…",
      "to": "0xColdStorage…",
      "amount": "0.5",
      "vsValue": 1230.0,
      "timestamp": 1730450000
    }
  ],
  "total": 2,
  "offset": 0,
  "limit": 200
}

Deposits are tagged back to the invoice that matched them (guid). Withdrawals are attributed to the smart-wallet's owner — they are not associated with any single invoice.