Исследование с проверкой источников: Binance CAAS KYC Subaccount

Decision Matrix

Source Map

• Binance Developer Docs: CAAS FAQ (binance-caas-faq)
• Binance Developer Docs: CAAS Integration Guide (binance-caas-integration)
• Binance Developer Docs: KYC SaaS Webhook (binance-caas-webhook)
• Binance Developer Docs: Binance Link Introduction (binance-link-overview)

Control Notes

1. Entity tag

Entity tag is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means which Binance entity governs the subaccount. The useful action is to confirm the tag with the account manager. The unresolved edge is entity tag not visible from country alone, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, entity tag 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. KYC status

KYC status is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether the subaccount can receive deposits, trade or use APIs. The useful action is to record KYC state before issuing keys. The unresolved edge is customer-specific review result, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

3. Travel Rule trigger

Travel Rule trigger is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether extra originator or beneficiary fields are required. The useful action is to route tagged accounts through the correct endpoint. The unresolved edge is future threshold changes, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

4. Withdrawal endpoint

Withdrawal endpoint is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means capital or localentity API path. The useful action is to choose the endpoint from entity status. The unresolved edge is integration fallback behavior, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

5. Master key

Master key is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means the key used for broker calls and withdrawals. The useful action is to separate master authority from trading keys. The unresolved edge is partner custody process, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

6. Subaccount key

Subaccount key is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means the key used for trading and user streams. The useful action is to issue after wallet and KYC readiness. The unresolved edge is key created before product enablement, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

7. Deposit address

Deposit address is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether a subaccount can retrieve a funding address. The useful action is to do not fund until KYC state is proven. The unresolved edge is old saved addresses, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

8. Rejected deposit

Rejected deposit is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means legacy funding into a non-KYC account. The useful action is to preserve non-secret recovery evidence. The unresolved edge is asset recovery outcome, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

9. Webhook URL

Webhook URL is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means the endpoint receiving KYC status updates. The useful action is to set a durable URL before submission. The unresolved edge is no-change path after submission, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, webhook url 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 conditions where operations should pause. The useful action is to stop on unknown tag, missing KYC proof or endpoint mismatch. The unresolved edge is private account facts, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

Known Unknowns

• entity tag not visible from country alone
• customer-specific review result
• future threshold changes
• integration fallback behavior
• partner custody process
• key created before product enablement
• old saved addresses
• asset recovery outcome
• no-change path after submission
• private account facts

Practical Takeaway

The safest version of this article is the one that stays boring and exact. Binance's CAAS FAQ turns subaccount operations into an entity, KYC and endpoint-routing problem. Binance says Travel Rule requirements depend on the entity a subaccount is tagged to, AU-tagged accounts require questionnaires for deposits and withdrawals with no minimum threshold, and IN-tagged accounts apply Travel Rule above a 1,000 USD threshold. It also says non-Travel-Rule entities should keep using the capital withdrawal endpoint, while tagged entities should migrate to the localentity withdrawal endpoint. For KYC restrictions, newly created non-KYC subaccounts cannot create API keys or retrieve deposit addresses, deposits into older non-KYC subaccounts can be rejected, and non-KYC subaccounts face trading and transfer limits. The safe user outcome is to map entity tag, KYC state, endpoint, API key owner and recovery path before treating a subaccount as operational. 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.