Cash

get_cash_balance_v2 reads your own cash, the figure a buy is checked against, and get_cash_movements the movements behind it. Your shares are the CETs in your wallet: the mints and burns say how they got there.

Your own cash

The broker account can carry other clients’ cash beside yours, so what you may spend is kept apart: what you deposited and withdrew, the fees charged to you, and what your orders spent and still hold.

{ "type": "get_cash_balance_v2", "requestId": "7c2e9a41b5d84f06a3e1c8b27d5f0e93" }

"balances": [
  {
    "currency": "USD",
    "deposited": "1000",
    "withdrawn": "0.5",
    "fees": "0.3",
    "bought": "500",
    "sold": "0",
    "netBalance": "499.2",
    "committed": "100.1",
    "available": "399.1"
  }
]

Field	Meaning
`deposited`, `withdrawn`, `fees`	The movements of your cash, as `get_cash_movements` lists them
`bought`	What your buys cost, as far as they executed
`sold`	What your sells brought in, as far as they executed
`netBalance`	`deposited − withdrawn − fees − bought + sold`: your balance
`committed`	Held and not spent yet: the unfilled part of your working buys at their limit, the fees of your trades not charged yet, and buys being placed
`available`	`netBalance − committed`: what a new buy can spend. Negative when overdrawn

There is one entry per currency you have moved, and an empty list before your first movement.

What a buy holds

A buy is a LIMIT order by quantity. When you place it, quantity × limitPrice plus its fees moves into committed, before the order reaches the broker; a buy your available does not cover answers INVALID_ORDER with your figures, and nothing reaches the broker. As it fills, what it executed moves from committed to bought, at the price it executed. When it ends, filled, cancelled or expired, whatever it did not spend is released. A sell adds to sold as it executes. A MARKET buy and an order by notional answer INVALID_ORDER: neither names the price its cost would be held at.

Movements

get_cash_movements lists the movements behind deposited, withdrawn and fees, newest first: deposits, withdrawals and fees, each with its id, amount, currency, status and bookedAt. Pass the id of the last one you hold as before for the next page, with limit up to 200. A movement is also pushed as cash_movement when it is recorded for you or cancelled. Delivery is at least once: every repeat of one change carries the same eventId, so drop what you have seen. CANCELLED is final for an id, and a movement that is cancelled no longer counts. The push carries no balance: read get_cash_balance_v2 for the totals, and get_cash_movements to catch up after a gap.

Fund your cash with crypto

You can fund your own cash by sending USDC on an EVM chain or on Solana to a Securitize wallet, then telling us the transaction. The chains offered are the ones get_crypto_funding lists in depositTo. Before the first deposit, ask Securitize to enable crypto funding for you and to register the wallets you send from. Only a deposit from a registered wallet is credited, and there is no message to register one: to add or remove a wallet, contact Securitize.

1. Read where to send it

get_crypto_funding answers depositTo, Securitize’s wallets, one per chain and token with the token’s contract, and fromWallets, the wallets Securitize registered for you. When it answers enabled: false, crypto funding is not enabled for you: contact Securitize. Read it again before each deposit rather than keeping the addresses: Securitize’s wallets can change.

{ "type": "get_crypto_funding", "requestId": "3b9e1c7a5d2f4e86a0c4b8d1f6e2a957" }

{
  "enabled": true,
  "depositTo": [
    {
      "chainId": 1952,
      "token": "USDC",
      "tokenAddress": "0x1a2b3c4d5e6f708192a3b4c5d6e7f8091a2b3c4d",
      "address": "0x8f3c6a1e9b2d4c7f0a5e3b8d1c6f9a2e4b7d0c35",
      "decimals": 6,
      "minConfirmations": 12
    }
  ],
  "fromWallets": [{ "namespace": "eip155", "address": "0x1111aaaa2222bbbb3333cccc4444dddd5555eeee" }]
}

2. Send the USDC

Send it from one of your fromWallets to the address of the chain you use. Only that exact tokenAddress counts (the token contract on an EVM chain, the mint on Solana): another token, or a transfer from a wallet that is not yours, is never credited. On Solana, send it from the wallet itself, not from a token account you hold for another wallet: the sender and the recipient are the wallets that own the token accounts.

3. Send the transaction hash

Send it with submit_crypto_funding, signed like place_order. A read-only key answers NOT_PERMITTED.

{
  "type": "submit_crypto_funding",
  "requestId": "8d4f2a6c1e9b4073b5a2c7e0d3f8b164",
  "timestamp": 1793631600,
  "payload": { "chainId": 1952, "txHash": "0xabab5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f6071829" },
  "signature": "3Kf9…"
}

txHash is 0x and 64 hex digits on an EVM chain, and the base58 signature on Solana, sent as it is: Solana signatures are case-sensitive. Once the transaction succeeded and is final, the ack carries status: "CREDITED", the amount credited in USD, one for one with the USDC that arrived, and movementId, the movement’s id in get_cash_movements. get_cash_balance_v2 counts it at once. The credit is not pushed as cash_movement: the ack is the confirmation. A transaction is credited once, whoever sends it: sending the same txHash again answers the same credit, so it is always safe to send it again.

`code`	Meaning	What to do
`DEPOSIT_PENDING`	The transaction is not on chain yet, or not final	Send the same `txHash` again later
`DEPOSIT_REFUSED`	It will not be credited as sent. `message` says why: crypto funding is not enabled on that chain, there is no USDC transfer from one of your wallets to Securitize’s, the transaction failed, or it was already credited to another account	Nothing to retry. Contact Securitize with the `traceId` if you think it should be credited
`UPSTREAM_UNAVAILABLE`	The chain could not be read, or no answer came in time	Send the same `txHash` again: it is never credited twice

submit_crypto_funding is served on the socket only. get_crypto_funding is also served over HTTP, as GET /v1/market-maker/crypto-funding: see Reads over HTTP.

Buying power

A buy is checked twice. First against your own available, before it reaches the broker. Then the broker checks the account it trades through, and a buy it cannot pay for answers INVALID_ORDER with the message Insufficient buying power. Either way, fund your cash or size the order down, and send it again. In sandbox, you can also fund it as Sandbox funding shows.

Get started

Sandbox only

Guides

Concepts

Help

API reference