Binance's Emergency Contact and One-Time Backup Codes (OTP) serve as the ultimate insurance for your account in case of theft, loss of contact, or unexpected passing. Once properly configured, you can designate a trusted person to submit freeze requests, use a set of 16-digit one-time codes in place of 2FA for login, and pre-set asset inheritance instructions. The configuration entry is located at the Binance Official Website Security Center → Emergency Contact; the mobile app also supports this, provided you install the Binance Official App first. This article is structured into 8 sections: mechanism, setup steps, generating backup codes, usage scenarios, inheritance strategies, legacy planning templates, trust chain design, and FAQs.
I. What is an Emergency Contact?
Functional Comparison
| Function | Emergency Contact CAN | Emergency Contact CANNOT |
|---|---|---|
| Submit Account Freeze Request | ✅ | — |
| Prove Loss of Contact to Support | ✅ | — |
| Log in to Account | ❌ | No |
| Trade Assets | ❌ | No |
| Modify Password/2FA | ❌ | No |
| Check Account Balance | ❌ | No |
| Submit Inheritance Claim Materials | ✅ (Initiate process) | — |
Key Understanding: An Emergency Contact ≠ an Authorized Agent. They are simply a "friend who knows your account exists and can help pause it if something goes wrong"; they have no direct control over your funds.
Why You Need One
| Scenario | Standard User | User with Emergency Contact |
|---|---|---|
| Account stolen while you're in the hospital | Funds continue to drain, no one to stop it | Contact calls support → Emergency freeze |
| Unexpected passing | Account unknown to anyone, remains dormant until declared "lost" | Contact initiates inheritance claim process |
| Traveling without internet | No response to suspicious activity notifications | Contact can verify on your behalf |
II. Setting Up an Emergency Contact
Prerequisites
- Completed KYC L2 or higher
- Enabled Google Authenticator or YubiKey 2FA
- Verified email and phone number
Setup Steps
- Log in to binance.com → Security Center
- Locate the Emergency Contact section → Click Add
- Enter the contact's information:
- Full Name: The contact's legal full name (matching their ID)
- Relationship: (Parent/Spouse/Sibling/Close Friend)
- Email: Contact's email address
- Phone: Contact's phone number (including country code)
- Country: Contact's country of residence
- Additional fields (Recommended):
- ID Document Type: ID Card/Passport
- ID Number: Providing the last 4 digits is sufficient for future verification
- 2FA Verification → Submit
- Binance will send an Invitation Email to the contact, who must click the confirmation link to accept.
- Once accepted, your Security Center status will show as Active.
Obligations of the Contact
After accepting the invitation, Binance sends the contact an "Emergency Contact Agreement", which clarifies:
- They should only contact support when you are unreachable or in an emergency.
- they cannot perform any trades on your behalf.
- They must cooperate in verifying their identity when receiving a call from support.
- They must maintain your privacy and the confidentiality of your asset information.
III. One-Time Backup Codes (Backup Codes)
Backup Codes are a set of 8–10 16-digit one-time passwords used for emergency login if you lose access to your 2FA. Each code can be used only once and becomes invalid thereafter.
Generation Steps
- Security Center → Backup Codes (On some accounts, this is under 2FA management)
- Click Generate Codes
- Enter your password + 2FA verification
- The page will display 10 16-digit codes at once, for example:
1. a3f8-9d2c-bk4m-xy7p
2. hg82-4n5w-tq1v-m9ok
3. e71k-j2d3-phg6-9c4x
4. s0ab-45fg-k8mn-xytq
5. 2jwl-6hpq-39yz-b4ud
6. r5tk-v9b2-n7c1-mqxl
7. 8aef-xs2t-g4h9-k1wp
8. nc62-y85z-47hm-pq3a
9. bjky-23nd-9x5c-f8wo
10. lzmx-6yho-1k3v-d7qr
Backup Methods
- Download TXT Immediately: Save to 1Password or a local encrypted drive.
- Print a Copy: Print on A4 paper and store in a safe.
- DO NOT: Email them, send them via messaging apps (like WeChat/Telegram), or take a screenshot to upload to cloud albums.
After using a code, it is immediately invalidated. When you have used 8 codes, return to the Security Center to Generate 10 new ones, which will invalidate any remaining old codes.
IV. Backup Codes Usage Scenarios
| Scenario | Role of Backup Codes |
|---|---|
| Lost phone, no 16-digit TOTP key | Use a Backup Code in place of 2FA login, then rebind 2FA inside |
| Lost YubiKey, no Backup YubiKey enabled | Use a Backup Code to log in |
| Traveling abroad and unable to use Authenticator temporarily | Use a Backup Code for emergency access |
| Proving "I am who I say I am" during support audit | Provide an unused Backup Code as proof of ownership |
Usage Flow
- Log in to binance.com → Enter email and password
- On the 2FA page → Click Unable to use Authenticator?
- Select Use Backup Code
- Enter any of your 16-digit codes
- Login successful; the code is immediately invalidated
- Once logged in, immediately rebind 2FA and generate a new set of Backup Codes.
V. Asset Inheritance Strategy
Cryptocurrency inheritance is an issue that has gradually taken shape after 2020. Binance currently lacks an official "Designated Heir" feature, but this can be achieved through a combination of an Emergency Contact and legal documents.
Four Pillars of Inheritance Planning
- Asset Inventory: UID, asset types, approximate value, KYC name.
- Access Credentials: Password, 2FA backups, and instructions on where Backup Codes are stored.
- Legal Documents: Clearly state the attribution of crypto assets and executor authority in your will.
- Operations Manual: Provide the executor with a step-by-step guide.
Document Template
Store this in a physical safe that family members can find (do not store in an online cloud drive):
================================
Binance Account Emergency Guide v2026.04
================================
Holder: Zhang San (ID: XXX-XXX)
Account Email: [email protected]
UID: 123456789
Estimated Assets: ~$50,000 (Quote as of 2026-04-14)
Emergency Contact: Li Si (Spouse)
Phone: +86 138xxxxxxxx
--------------------------------
Scenario A: Holder unreachable for over 48 hours
--------------------------------
1. Li Si logs into 1Password; the master password is: "Memo on the slip inside the safe"
2. Locate the [Binance Backup Codes] entry
3. Contact Binance live support and present Emergency Contact identity
4. Request "Emergency Freeze" to lock the account
--------------------------------
Scenario B: Holder Passing
--------------------------------
1. Obtain Death Certificate + Notarized Will
2. Email [email protected] to initiate inheritance claim
3. Submit: Death certificate, will, heir's ID, holder's ID
4. Processing cycle: 30-90 days
5. Assets transferred to designated heir's address or fiat account
--------------------------------
Storage Checklist
--------------------------------
- Safe: Ledger hardware wallet + 24-word seed phrase (Titanium plate)
- 1Password: Binance password, Backup Codes, API Keys
- Paper Filing Cabinet: Printed version of this guide, KYC ID copies
- Legal: Attorney Wang, XX Law Firm, +86 138xxxxxxxx
--------------------------------
DO NOT
--------------------------------
- Do not attempt to log in and operate yourself (may trigger risk lock)
- Do not disclose account information publicly
- Do not contact strangers claiming to be "Binance Support"
VI. Trust Chain Design
Multi-layered Trust Architecture
Layer 1 (Self): Master Password + 2FA + Backup Codes
↓
Layer 2 (Spouse/Direct Relative): Knows safe location + Copy of Backup Codes
↓
Layer 3 (Attorney/Executor): Has will authorization + Legal docs to contact Binance
↓
Layer 4 (Binance Support): Verifies death certificate + Executes asset transfer
Each layer holds only enough permission to perform its role, without giving any single layer full control.
Example: Sharded Backup
Split the Ledger 24-word phrase using Shamir's Secret Sharing (SSS) into 3 shares:
- Share A: Kept by spouse
- Share B: Kept by parents
- Share C: Kept by attorney
- Recovery requires any 2 shares
This way, a compromise of any single holder won't lose the coins, yet two people can collaborate to recover them in an emergency. The Trezor Model T natively supports SLIP-0039 Shamir backup.
VII. Emergency Contact Communication Manual
Give your contact a card like this:
## Emergency Contact Card (Binance)
Holder UID: 123456789
Holder Email: [email protected]
Emergency Code: FV-SKY-7W (Anti-phishing code)
Contact Info:
1. Live Support: support.binance.com
2. Phone (International): Check official website
3. Email (Legal Dept): [email protected]
Verification Info (Support will ask):
- Relationship to holder: Spouse
- Holder's registration date: Around 2021-03
- City of last login: Shanghai
- Last 4 digits of holder's ID: XXXX
MOST IMPORTANT: Never provide account passwords or 2FA to support; real support will never ask.
VIII. Integrated Security Model
Emergency Contact + Backup Codes + Hardware Wallet + Will = A complete security loop for crypto assets:
| Layer | Defense Target | Tool |
|---|---|---|
| L1 Login | Account Theft | Password + YubiKey + Authenticator |
| L2 Operation | Phishing | Anti-phishing code + Withdrawal whitelist |
| L3 Account | Loss of Control | Emergency Contact + Risk notifications |
| L4 Legacy | Loss of Access | Backup Codes + Will + Emergency Contact |
| L5 Cold Storage | Exchange Failure | Ledger + Trezor + Sharded backup |
FAQ
Q1: Can I change my Emergency Contact? How often should I do so?
A: Yes, you can change it at any time. Go to Security Center → Emergency Contact → Edit/Remove → 2FA Verification. It is recommended to review this every 2 years (or sooner if the contact moves, divorces, or passes away). Changes take effect immediately once the new contact accepts the email invitation.
Q2: Can a minor be an Emergency Contact?
A: No. Binance requires the contact to be at least 18 years old, hold a valid ID, and accept the "Emergency Contact Agreement." Minors lack full civil capacity and cannot fulfill the obligations of a contact.
Q3: Will Backup Codes automatically regenerate once used up?
A: No. Once all codes are used, the "Use Backup Code" option for 2FA emergency recovery will be disabled. You must manually go to the Security Center and click Regenerate to create a new set. It is recommended to regenerate when you have only 5 codes left.
Q4: If the holder passes away, will Binance automatically transfer assets to the contact?
A: No. The Emergency Contact is strictly for "emergency communication," not an heir. A true asset transfer requires a Death Certificate + Will + Legal Notarization + Heir's ID, following the inheritance claim process via [email protected], which takes 30–90 days.
Q5: Can I use the same Emergency Contact across multiple exchanges (e.g., Binance + OKX + Coinbase)?
A: Yes. A contact is platform-independent. You should give them a unified "Multi-Exchange Emergency Manual" listing the UID, support entries, and freezing scripts for each exchange. However, you must set up the contact individually in the security center of each platform.
Keep reading: Return to Categories and enter the "Security Hardening" category for tutorials on 2FA recovery, hardware wallets, and more.