Member digital assets: balances, deposits, on-chain withdrawals, transaction history and internal conversions.
Stablecoin Account Overview
Members hold digital assets with you. We maintain the ledger, not custody: you custody the assets, and our ledger records who owns how much.
Four core operations
| Endpoint | Summary | |
|---|---|---|
| Balances | GET /v1/balances | Member balances by asset and balance bucket |
| Deposits | POST /v1/deposits | You report incoming funds, increasing the member balance |
| Withdrawals | POST /v1/withdrawals | On-chain withdrawals, using a two-stage workflow |
| Transactions | GET /v1/transactions | All ledger movements |
There is also an operation that stays within the ledger: internal conversions.
POST /v1/deposits is the only endpoint that creates a balance credit without an existing ledger debit
It has six mandatory controls:
- Signature verification cannot be disabled.
- Idempotency includes your transaction reference.
- Per-transaction and daily cumulative limits apply.
- An asset allowlist applies; unknown assets are rejected without a ledger credit.
- Standard risk eligibility checks still apply.
- All activity is audited.
⚠ In particular, an unrecognized asset code does not create a new asset; the request is rejected.
You cannot enable a currency by reporting a deposit for it.
Balance buckets
A member balance is not one number. It is divided into buckets such as available, frozen, wealth and card balances. Only the available balance can be spent. State which bucket a displayed balance refers to. Showing the total as available would imply that frozen funds can be spent.