Pesquisa verificada por fontes: Bybit

Decision Matrix

Source Map

• Bybit Help Center: Bank Triparty (bybit-bank-triparty)
• Bybit Help Center: Platform Collateral Limit (bybit-platform-collateral)
• Bybit Help Center: Borrowing, Interest and Repayment (Unified Trading Account) (bybit-borrowing-uta)
• Bybit Help Center: Floating Interest Rate System (bybit-floating-interest)

Control Notes

1. Bank collateral

Bank collateral is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means USD or T-BILL assets held with banking partners. The useful action is to identify the collateral record. The unresolved edge is bank-specific custody terms, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, bank collateral 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. Bybit liability

Bybit liability is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means USDT financing or outstanding principal. The useful action is to separate bank asset from exchange liability. The unresolved edge is private loan balance, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

3. Haircut

Haircut is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means adjusted value rather than face value. The useful action is to calculate with the documented haircut base. The unresolved edge is future haircut changes, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

4. Risk unit

Risk unit is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means the account group used for collateral and liability tests. The useful action is to map UTA and bank collateral together. The unresolved edge is account-specific risk-unit setup, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

5. Transfer ratio

Transfer ratio is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether assets can move out of the risk unit. The useful action is to check ratio before transfer. The unresolved edge is real-time risk-engine result, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

6. LTV threshold

LTV threshold is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means initial, margin-call and liquidation levels. The useful action is to pre-plan response levels. The unresolved edge is market gap behavior, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

7. Notification

Notification is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means margin-call and alert route. The useful action is to do not rely on alerts as sole protection. The unresolved edge is delivery delay, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

8. Liquidation path

Liquidation path is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means repayment, UTA assets and bank-collateral settlement sequence. The useful action is to know sequence before borrowing. The unresolved edge is settlement timing, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

9. Fee

Fee is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means liquidation fee treatment. The useful action is to include in worst-case planning. The unresolved edge is tax and accounting treatment, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

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 RWA-style collateral is not decision-quality. The useful action is to stop if custody, haircut, LTV or transfer ratio is unknown. The unresolved edge is future product changes, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

Known Unknowns

• bank-specific custody terms
• private loan balance
• future haircut changes
• account-specific risk-unit setup
• real-time risk-engine result
• market gap behavior
• delivery delay
• settlement timing
• tax and accounting treatment
• future product changes

Practical Takeaway

The safest version of this article is the one that stays boring and exact. Bybit Bank Triparty turns collateral review into a bank-custody, haircut and transfer-restriction question. Bybit says the product safeguards USD and T-BILL collateral through regulated banking partners while enabling USDT financing on Bybit. The help page defines risk-ratio LTV as outstanding principal divided by haircut-adjusted bank collateral value, describes a transfer-ratio test, and states that transfers from the Unified Trading Account inside the risk unit can be restricted when the transfer ratio is below 15 percent. It also lists initial, margin-call and liquidation LTV levels and a liquidation fee. The decision outcome is to map bank collateral, Bybit liability, haircut, risk unit, transfer ratio, notification path and liquidation sequence before treating T-BILL-backed collateral as cash-like liquidity. 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.