available balance and is
required collateral for placing BUY orders. It is always a
user-initiated on-chain transaction — neither the platform nor a
partner API key can pull funds out of an EOA without the owner’s
authorisation.
Prerequisites
| Requirement | How to satisfy |
|---|---|
| Vault deployed for your EOA | Auto-deployed by the platform — see Backend auto-deploy. Verify with GET /api/me/vault (deployed: true). |
| USDC in the EOA | Buy / bridge on mainnet; on testnet call MockCollateral.mint(eoa, amount) (public). |
| ERC-20 allowance | Your EOA must have called USDC.approve(vault, X) for at least X = depositAmount. MaxUint256 is the standard one-time pattern. |
| Within deposit limits | The platform pre-initialises per-EOA daily / weekly / monthly caps — see Deposit limits. |
End-to-end flow
Step 1 — approve (once per vault)
MaxUint256 saves gas on every future deposit. Tighten to a per-deposit
allowance if your security model requires it — the trade-off is one
extra approve per deposit.
Step 2 — depositERC20
transferFrom(eoa → vault), increments
its internal collateral ledger by amount, and checks the deposit-cap
windows in DepositLimitRegistry before settling. If the cap would be
exceeded, the tx reverts with DepositCapExceeded() — see
Deposit limits.
Step 3 — wait for the platform to credit
After the deposit tx mines, the platform indexes the on-chain event and creditsexchange.balances.available for your associated EOA.
End-to-end latency from mined tx to credited balance is typically
under 5 seconds on testnet and similar on mainnet.
Two ways to observe it:
Idempotency and replays
Deposits are uniquely keyed by their on-chain(txHash, logIndex).
If you receive the same vault.deposit_confirmed event twice (network
retry, WS reconnect with replay), the platform credits the deposit
exactly once — replays are cheap no-ops. Safe to handle naively.
Withdrawing later
Funds in the vault stay liquid — withdraw any time via the dual-signed flow documented in Withdrawals overview. The vault also exposes a 7-day-timelocked emergency withdraw for recovery if the platform is unavailable; see Vault contract reference.Common failures
| Symptom | Cause | Fix |
|---|---|---|
ERC20InsufficientAllowance | Step 1 skipped or insufficient cap | Run usdc.approve(vault, MaxUint256) first |
Revert with selector 0x87138d5c | NotInitialized() — your code raced ahead of auto-deploy (the VaultCreated and cap-init txs land in adjacent blocks) | Wait one block and retry; or gate the deposit on GET /api/me/vault returning deployed: true |
Revert with DepositCapExceeded | The deposit would exceed your daily / weekly / monthly cap | See Deposit limits — wait for the rolling window or request a higher tier |
Tx mined but available still 0 in /api/me/balances after >1 minute | Indexer lag or transient incident | Check status page; if persistent, contact support with txHash |
Next
Deposit limits
Daily / weekly / monthly caps and how rolling windows are applied.
Withdrawals overview
Dual-signature flow, AML review, state machine.
Place your first order
Sign + POST a vault-backed order against any open market.
Vault contract reference
Full ABI for the vault, including the deposit entry point.