Pesquisa verificada por fontes: Binance

Decision Matrix

Source Map

• Binance Support: What Is the Travel Rule? (binance-travel-rule)
• Binance Support: What Is Satoshi Test and Travel Rule Address Book Feature? (binance-satoshi-address-book)
• Binance Support: Crypto Deposit/Withdrawal FAQ (binance-withdrawal-faq)
• Binance Support: Travel Rule: Crypto Transfer Procedures (binance-travel-rule-procedure)

Control Notes

1. Official entry point

Official entry point is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means the Binance page or interface where the flow starts. The useful action is to type or bookmark official Binance pages rather than using social links. The unresolved edge is regional interface changes, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, official entry point 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. Transfer route

Transfer route is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means deposit or withdrawal and destination type. The useful action is to classify the route before filling details. The unresolved edge is intermediate VASP routing, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

3. Jurisdiction check

Jurisdiction check is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means whether Travel Rule rules apply to the route. The useful action is to read the current regional note. The unresolved edge is future region additions, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

4. Beneficiary data

Beneficiary data is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means required recipient information. The useful action is to enter only required fields inside Binance. The unresolved edge is counterparty accuracy, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

5. Originator data

Originator data is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means required sender information for deposits. The useful action is to ask the sender for accurate non-secret details. The unresolved edge is sender refusal, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

6. Self-hosted wallet proof

Self-hosted wallet proof is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means address-control evidence through Satoshi Test. The useful action is to perform only official small-transfer verification. The unresolved edge is network fee and timing, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

7. Address-book review

Address-book review is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means stored Travel Rule information for future transfers. The useful action is to review saved address details before reuse. The unresolved edge is stale recipient data, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

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

8. Security boundary

Security boundary is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means credentials and identity material that must never be shared externally. The useful action is to never disclose codes, seed phrases, private keys or API secrets. The unresolved edge is phishing impersonation, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, security boundary 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 official URL, date, route type and non-secret verification state. The useful action is to do not publish names, wallet addresses, IDs or transaction screenshots. The unresolved edge is privacy retention, 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 onboarding should stop. The useful action is to stop if official flow, counterparty type or address-control proof is unclear. The unresolved edge is future Binance process changes, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

Known Unknowns

• regional interface changes
• intermediate VASP routing
• future region additions
• counterparty accuracy
• sender refusal
• network fee and timing
• stale recipient data
• phishing impersonation
• privacy retention
• future Binance process changes

Practical Takeaway

The safest version of this article is the one that stays boring and exact. To verify Binance Travel Rule address-book and Satoshi Test requirements safely, treat the flow as recipient-information onboarding rather than a normal address paste. Start from Binance's official Travel Rule and Satoshi Test pages, confirm whether the transfer route is in a Travel Rule jurisdiction, classify the counterparty as another exchange, a VASP, a third party or a self-hosted wallet, and enter only the required beneficiary or originator information inside the Binance interface. If Binance requires a Satoshi Test, use only the official small-transfer verification path and never share codes, seed phrases, private keys or full identity documents with an external contact. Stop if the route, counterparty or address-control proof is unclear. 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.