Transactions
TrexWallet represents deposits, withdrawals, transfers, exchanges, investments, payments, and payouts as transactions with a type, amount, currency, state flags, and related operation details.
Observable lifecycle
- A request is validated before any financial effect is applied.
- Funds may move between free and locked sub-balances while an operation is pending.
- Applicable tariffs are selected by operation context and retained for that operation.
- State flags are additive and expose creation, confirmation, verification, cancellation, and completion.
- Balance and status changes are atomic. A failed request does not leave a partially applied operation.
- Idempotency and duplicate checks return an API error instead of applying the same operation twice.
Integrators should classify outcomes by the documented state bits, use transaction IDs as int64 strings in JavaScript, and submit financial changes only through documented APIs.