Nov 2026 Bitget Referral Code BTC9149 | Sign Up, KYC, 2FA | 20% Off

Contents

1. Three gates at a glance: materials, time, pass criteria
2. Gate one, sign-up: five steps
3. Gate two, KYC Level 1: the order of operations
4. Four reasons a KYC submission gets rejected
5. Level 2 and withdrawal limits: when you need it
6. Gate three, the five security items
7. The cost of changing security settings: 24-hour hold
8. Troubleshooting: codes, delays, retry limits
9. Three checks after you finish
10. FAQ
11. Risk warning
12. Bottom line

---

Three gates at a glance: materials, time, pass criteria

Seeing the whole path first prevents the classic mistake: finishing sign-up and only then discovering your document photos are unusable.

Gate	What you need	Roughly how long	Pass criteria
1. Sign-up	An email you can open, or a phone that receives SMS	3 to 5 minutes	Code accepted, login works
2. KYC Level 1	A valid government-issued ID and you	5 minutes to submit, review usually under 60 minutes	Status shows verified
3. Security	An authenticator app, a backup contact	10 to 15 minutes	2FA live, whitelist in place

The order is clear: sign-up, then KYC, then security. Security goes last not because it matters least, but because it touches your password and verification methods — set it once and leave it alone.

---

Gate one, sign-up: five steps

Step one: enter through the invite link. This solves two things at once — you land on the correct sign-up page, and the referral code is pre-filled. Sign-up link: https://partner.bitget.com/bg/8cp8dcqu, code BTC9149.

Step two: choose email or phone. You can only use one to register. Pick whichever you check regularly and will keep long term; the other can be linked later in security settings.

Step three: confirm the code field has a value. It is labeled optional, but it is the only place where fee benefits get attached. Enter BTC9149 and later trades carry up to 20% in rebates. Leave it empty and nothing breaks — it simply cannot be added afterwards.

Step four: set a password. Eight to 32 characters, with a number, at least one uppercase letter and one special character. Generate it in a password manager rather than reusing a birthday or a pattern you use elsewhere.

Step five: verify. Enter the six-digit code sent to your email or phone and the account exists. At this point you have an account, not a usable one — KYC is next.

---

Gate two, KYC Level 1: the order of operations

Bitget requires verification for its core services — deposits, trading, withdrawals and P2P. It is not optional. The standard route is Level 1 personal verification.

Step one: open the verification flow from the account or security menu after logging in.

Step two: pick two regions. One is your country or region of residence, the other the country or region that issued the document. Do not rush these dropdowns — a mismatch is a common rejection cause.

Step three: choose the document type. Accepted types vary by country — typically national ID, passport, driver's license or residence permit. Whatever the dropdown actually lists for your country is what counts, not what you assume.

Step four: upload and scan your face. Both sides of the document must be sharp, uncropped and unedited. For the face step, stand against a plain wall with light on your face rather than behind you, remove hats and glasses, center your head and follow the prompts.

Step five: submit and wait. The official line is that review usually completes within 60 minutes; if it runs longer, open a ticket with your UID instead of resubmitting repeatedly.

Two rules worth knowing: one identity verifies one account, so the same document on a second account gets rejected, and verification must be done on the main account — sub-accounts inherit permissions automatically.

---

Four reasons a KYC submission gets rejected

Reason one: the name does not match the document. Split it exactly as printed. For John Michael Doe on a passport, the first-name field takes John Michael and the surname field takes Doe. For Chinese names, follow the document, not a romanization you invented or an English name you prefer.

Reason two: the photo fails. Blur, cropped edges, glare over the data fields, a finger shadow or visible retouching all get bounced. Shoot with the camera directly — no screenshots, no low-contrast scanner output.

Reason three: the face scan environment is wrong. Backlight turns your face into a silhouette, glasses catch reflections, hats and masks fail outright. Front lighting, clean background, no accessories — usually passes first time.

Reason four: document type does not match the region. Selecting country A's document type while listing country B as the issuer is an automatic mismatch. This happens most to people working across borders or holding several documents.

---

Level 2 and withdrawal limits: when you need it

Level 1 covers most people. Level 2 adds proof of address: a bank statement or a utility bill for water, electricity, gas or internet dated within the last three months, with a name that matches your Level 1 document exactly. A household bill in a family member's name will be rejected.

When does Level 2 come up? Most commonly when applying for the Bitget Card, which requires both Level 1 and Level 2. Whether Level 2 is needed can also depend on which document you used for Level 1 — the official guidance prefers a local national ID or driver's license over a passport, which tends to make later steps smoother.

Withdrawal limits, meanwhile, are driven mainly by VIP tier rather than verification level. Verification unlocks features; the ceiling depends on your trading volume and VIP status. Check the account page for the current numbers, since third-party write-ups rarely agree with each other.

---

Gate three, the five security items

Click your avatar in the top right corner and open the security page. Do all five in one sitting.

One: Google Authenticator (2FA). Bitget shows a secret key; copy it, choose "enter setup key" in your authenticator, paste, then type the generated six-digit code back into Bitget and confirm via email or phone. From then on login needs that code too, so an intercepted SMS is not enough.

Two: link the other contact method. If you registered with email, add the phone, and vice versa. Recovery options are only as good as the channels you have attached.

Three: fund password. Used for withdrawals and transfers, set separately from the login password. Even if the login password leaks, assets cannot simply be withdrawn.

Four: anti-phishing code. Set a phrase only you know, and official emails will carry it. An "official notice" without your code is almost certainly phishing.

Five: withdrawal address whitelist and device management. Add your usual addresses to the whitelist so withdrawals can only go there. Review the device list periodically and remove anything you do not recognize.

---

The cost of changing security settings: 24-hour hold

The platform penalizes churn: changing your login password, swapping 2FA, or replacing a bound email or phone typically triggers a withdrawal hold of roughly 24 hours. Logging in from a new device comes with a shorter protection window.

That is why security belongs at the end, in one pass. Spread "change password → bind 2FA → add whitelist" across three days and you keep the account in a non-withdrawable state for three days straight.

The flip side is that the mechanism is also an alarm: if a withdrawal hold appears when you changed nothing, someone is touching your security settings. Change your password and contact support immediately.

---

Troubleshooting: codes, delays, retry limits

No verification code. Check spam and promotions first, confirm the email or number and country code, then wait a minute or two and retry once instead of tapping repeatedly. If it still fails, open a ticket — do not start a new account.

Review past 60 minutes. The official guidance is to open a ticket with your UID after that window. One caveat: different pages quote different timelines — 60 minutes in one place, one business day in another — so plan against the longer one.

Repeated rejections. You get up to five submissions within 24 hours, then a cooldown. Do not keep firing — each attempt burns quota. Fix the name format, the photo and the lighting first.

Thinking about a second account. One identity verifies one account. Extra accounts cannot pass KYC and may trip risk controls.

---

Three checks after you finish

Check one: is the rebate active? Open the fee or rebate page and see whether your rates sit at a discounted level. Bitget does not let you look up which code was used at sign-up, so this has to be inferred from rates, rebate history or support.

Check two: is 2FA really live? Log out and back in — you should be asked for the authenticator code. Store the backup key somewhere safe so a lost phone does not lock you out.

Check three: has the whitelist cooldown passed? A newly added withdrawal address usually needs time before it can be used. Build that into your cash planning instead of adding it on the day you need the money out.

---

FAQ

---

Risk warning

---

Bottom line

Getting a Bitget account from zero to usable is three gates: enter the code correctly at sign-up, pass the face and document check at KYC, and finish security in one pass. Only the first gate is irreversible; the second can be retried up to five times in 24 hours; the third punishes repeated changes.

Have materials ready, split your name the way the document does, shoot photos with the camera, and scan your face in front of a plain, well-lit wall. Do those four things and the whole process takes about half an hour with no back-and-forth resubmissions.

Sign-up link: https://partner.bitget.com/bg/8cp8dcqu; referral code: BTC9149. The field is pre-filled when you arrive through the link — confirm it has a value, then submit.