Exchange Updates

Recherche vérifiée par sources: Binance

7 min

Le corps de l'article est affiché dans sa version anglaise vérifiée. La traduction sera ajoutée après revue des sources.

Verified Fact Boundary

1. Binance says UAH deposits and withdrawals via Fiat Trade UAH will no longer be supported after 2026-09-28 09:00 UTC+2. 2. Binance says the USDT/UAH spot trading pair will be delisted at 2026-09-28 09:00 UTC+2. 3. Binance says all open orders on the USDT/UAH spot pair will be automatically removed after trading ceases. 4. Binance says remaining eligible UAH balances will be converted to USDT by 2026-09-30 18:00 UTC+2 at 1 USDT = 46.5 UAH. 5. Binance says no action is required from users who want their remaining eligible UAH balance converted automatically.

Réduire

Decision Matrix

Tableau de l’article : faites défiler horizontalement ou placez le focus sur le tableau et utilisez les flèches.

CheckWhat it meansPractical actionUnknown to keep explicit
Deposit cutoffwhen UAH deposits stoprecord the UTC+2 deadlinelocal timezone misunderstanding
Withdrawal cutoffwhen UAH withdrawals stopwithdraw or accept conversion before cutoffbank-side processing time
Spot pair delistingUSDT/UAH trading stopcancel or inspect open ordersother UAH markets
Order removalautomatic cancellation after trading ceasesstop bots before cutoffbot retry behavior
Conversion asseteligible UAH to USDTseparate eligible balance from unsupported balanceeligibility edge cases
Conversion ratefixed 1 USDT to 46.5 UAH venue ratecite as venue process onlymarket-price comparison
No-action pathautomatic conversion if user accepts itdocument intent before doing nothingaccount-specific exceptions
Translated versionsEnglish source controls discrepanciesprefer original English textlocal-language wording drift
Evidence packetannouncement URL, deadline and account-free checklistavoid screenshots with balancesprivate account state
Stop rulewhen to escalate to supportstop if balance eligibility or order state is unclearsupport response timing

Source Map

Control Notes

1. Deposit cutoff

Deposit cutoff is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means when UAH deposits stop. The useful action is to record the UTC+2 deadline. The unresolved edge is local timezone misunderstanding, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, deposit cutoff should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material. The record can stay simple: the official source URL, the date checked, the product or network under review, and a non-secret note describing why the next step is acceptable. Screenshots should avoid balances, identity documents, API keys, recovery phrases, private keys, passphrases, verification codes and support-ticket private data.

2. Withdrawal cutoff

Withdrawal cutoff is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means when UAH withdrawals stop. The useful action is to withdraw or accept conversion before cutoff. The unresolved edge is bank-side processing time, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, withdrawal cutoff should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

3. Spot pair delisting

Spot pair delisting is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means USDT/UAH trading stop. The useful action is to cancel or inspect open orders. The unresolved edge is other UAH markets, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, spot pair delisting should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

4. Order removal

Order removal is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means automatic cancellation after trading ceases. The useful action is to stop bots before cutoff. The unresolved edge is bot retry behavior, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, order removal should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

5. Conversion asset

Conversion asset is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means eligible UAH to USDT. The useful action is to separate eligible balance from unsupported balance. The unresolved edge is eligibility edge cases, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, conversion asset should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

6. Conversion rate

Conversion rate is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means fixed 1 USDT to 46.5 UAH venue rate. The useful action is to cite as venue process only. The unresolved edge is market-price comparison, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, conversion rate should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

7. No-action path

No-action path is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means automatic conversion if user accepts it. The useful action is to document intent before doing nothing. The unresolved edge is account-specific exceptions, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, no-action path should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

8. Translated versions

Translated versions is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means English source controls discrepancies. The useful action is to prefer original English text. The unresolved edge is local-language wording drift, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, translated versions should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

9. Evidence packet

Evidence packet is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means announcement URL, deadline and account-free checklist. The useful action is to avoid screenshots with balances. The unresolved edge is private account state, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

10. Stop rule

Stop rule is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means when to escalate to support. The useful action is to stop if balance eligibility or order state is unclear. The unresolved edge is support response timing, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

Known Unknowns

  • local timezone misunderstanding
  • bank-side processing time
  • other UAH markets
  • bot retry behavior
  • eligibility edge cases
  • market-price comparison
  • account-specific exceptions
  • local-language wording drift
  • private account state
  • support response timing

Practical Takeaway

The safest version of this article is the one that stays boring and exact. Binance's UAH notice is a deadline-management problem for fiat balances and open orders. Binance's verified announcement says UAH deposits and withdrawals through Fiat Trade UAH will no longer be supported after September 28, 2026 at 09:00 UTC+2, the USDT/UAH spot pair will be delisted at the same time, open orders on that pair will be automatically removed after trading ceases, and remaining eligible UAH balances will be converted to USDT by September 30, 2026 at 18:00 UTC+2 at a fixed rate of 1 USDT to 46.5 UAH. The source also says no action is required if users want automatic conversion. The operational checklist is to record the deadline, inspect UAH balance and open orders, avoid new bot exposure to the delisted pair, and treat automatic conversion as a venue process rather than a market-price promise. The user outcome is a clearer next inspection step, not a promise that a platform, API, transfer route or tokenized asset will work under every future condition.

Sources

04
  1. Binance AnnouncementBinance Will Close UAH Deposits and Withdrawals via Fiat Trade UAH and Delist USDT/UAH Spot Trading Pair
  2. Binance AnnouncementBinance will close UAH deposits and withdrawals via Fiat Trade UAH and delist the USDT/UAH spot trading pair
  3. Binance SupportDelisting announcements
  4. Binance MarketsMarket opportunity announcements feed
Choisissez la prochaine étape de recherche