Exchanger reserves in real time
Reserves show asset amounts exposed by SAIKYO’s public `/api/reserves`. Values are dynamic: the backend reads coins, amounts and `updated_at` from its database. They are not a promise of settlement at any time; check the direction, limits and freshness before ordering.
Start exchangeLive table
How to read a reserve
Match the asset and network: USDT and USDT_TRC20 may be separate rows. Check the update time and compare your order with the direction limit. If the asset is missing or stale, ask support.
Why reserve is not a guarantee
Reserves change after orders, deposits and internal operations. An order may also require AML/KYC or manual review. The public number is a state snapshot, not a promise to accept any amount.
Direction matters
Before an order
The value of a public reserve is freshness and context. If an asset has several networks, match the exact row rather than only the ticker. A reserve may exceed or fall below a direction limit, and some funds may already be committed to open orders. The updated_at field is a timestamp, not a queue disclosure. Do not use the table alone for a large payment; ask support about an unusual amount or direction.
Before publishing or paying, record the check date and separate static page facts from runtime API data. The explanatory text describes a process, while /api/rates, /api/reserves and /api/reviews change over time. An FAQ range is not a universal limit for every network, and an aggregate review count is not a substitute for the source reviews. If a parameter is absent from the checked source, the correct action is to ask support, inspect the order and wait for an answer. This avoids confusing an old screenshot, another domain or another direction.
For an independent check, open several sources, but do not turn them into a single guarantee. Terms describe general conditions, the FAQ lists published scenarios and ranges, the backend/API exposes current state, and a monitor provides its own direction snapshot. These layers may update at different times. Record the URL, date, network and amount so support can reproduce the question. Where a legal or financial interpretation is not published, this page keeps a neutral wording instead of guessing.
Before any transfer, verify the correct domain and the network named in the order. A crypto address cannot be corrected after sending, and a wrong network may delay or prevent crediting. Never share SMS codes, passwords, seed phrases or private keys with support. In a dispute, keep the time, order ID, rate screenshot and transaction hash, while removing personal data from public chats. Support may request additional KYC/AML information, but that is never a reason to disclose wallet secrets.
When comparing two orders, keep the conditions equal: the same asset, network, payment method and time. Changing one parameter can change the available rate or limit. Do not transfer a page’s terms to another domain, Telegram bot or partner interface without checking the address. Internal links are navigation aids; execution is determined by the current order form. Ask support about method availability and unusual amounts. Check the timestamp and exact network before relying on a reserve figure. This is only a snapshot.
FAQ
Откуда берутся значения?
Из публичного API `/api/reserves`, который читает динамические данные backend.
Как часто обновляется таблица?
Точное SLA обновления в checked legal-файлах не опубликовано; смотрите `updated_at`.
Можно ли заказать больше резерва?
Не делайте вывод по таблице; уточните лимит и возможность у поддержки.
Почему нет нужной сети?
Список зависит от активных направлений и текущего состояния сервиса.
Это гарантия выплаты?
Нет, публичный резерв не заменяет условия заявки и проверки.
Что делать при устаревшем времени?
Сохранить скриншот и уточнить у поддержки.