Bybit Signup: Apple Relay, Telegram Identity, and Account Recovery

How do I identify an existing Bybit account created through Apple or Telegram?

Establish the Apple relay address or linked phone used at registration, then confirm the account by UID after login. Use the matching recovery route when access is missing rather than creating another account.

Build an account identity map before you try signup again

Bybit's current registration guide separates email, phone, Google, Apple, and Telegram signup. Google uses the email linked to the Google account. Apple with Share My Email uses the address linked to the Apple ID. Apple with Hide My Email creates a random address in the @privaterelay.appleid.com domain. Telegram signup uses the phone number linked to the Telegram account. Bybit also states that each email address and mobile number can be linked to only one account.

That distinction prevents a common mistake: the inbox receiving a message is not necessarily the address stored as the Bybit login identifier. An Apple relay message can arrive in a familiar personal inbox after forwarding. Likewise, a Telegram display name or @username is not documented as the Bybit registration number. Record each field separately.

Do not use the signup button on the current Bybit exchange page merely to test whether a second account can be created. That page provides a centrally maintained route for a genuine new registration; it cannot merge an older social-login account, move KYC, or rewrite referral attribution.

Apple Hide My Email: find the relay address, not just the inbox

When Hide My Email was selected during Sign in with Apple, the identifier stored for the Bybit account may be a relay address rather than the ordinary iCloud address you remember. Bybit's registration documentation says the relay address and its forwarding destination can be found in the Apple iCloud settings under Hide My Email for the BybitApp entry. Menu labels can vary by device language and iOS version, but the evidence you need is stable: the Bybit entry, its relay address, and the current Forward To destination.

Use a four-step check. First, confirm that the device is signed into the Apple ID used at registration. Second, copy the complete @privaterelay.appleid.com address from the Bybit entry. Third, verify which personal inbox currently receives forwarded mail. Fourth, try the Apple button on Bybit's login page before treating an ordinary email/password failure as proof that no account exists. If an email field is required in a recovery step, use the identifier actually associated with the account rather than guessing from the receiving inbox.

Bybit's email-code troubleshooting page specifically tells Hide My Email users to inspect relay forwarding. A missing code can therefore be a delivery-path problem, a spam filter, or a temporary request timeout; it does not by itself prove that the account has been removed. Preserve the relay value, the destination inbox, the last successful message time, and the exact error before changing anything.

Consider a hypothetical identity map. Messages reach kim@example.com, but the Bybit account was registered as abc123@privaterelay.appleid.com. Starting a new email registration with kim@example.com does not establish that the old UID will follow. The valid comparison is between the UID reached through the original Apple identity and the UID in prior trade, deposit, withdrawal, or customer-rebate records. This example illustrates the method; it is not an actual recovery outcome.

Telegram signup: verify the linked phone, not the username

Bybit's official registration guide says that Sign Up with Telegram uses the phone number linked to the Telegram account. A Telegram username can be changed, and an account can exist without a public username. The profile name is also not a durable exchange credential. For recovery purposes, record the phone number, country code, whether you still control it, and the UID produced after using the Telegram login button.

If you changed or lost the number, do not assume that pressing Telegram with a new number will reopen the old UID. The documented account path is to recover or change the registered security method. A replacement phone number may also be ineligible if it has already been registered on Bybit. Keep the old number masked in your notes so support can understand which credential stopped working without asking you to disclose one-time codes.

When Telegram login succeeds, open the profile immediately and capture the main-account UID. If an email login shows one balance and Telegram shows another, compare UIDs before blaming an app cache. Different UIDs indicate different account identities unless official support determines otherwise. Never send a password, SMS code, authenticator code, seed phrase, or API secret to TradePayback or to anyone claiming to perform referral recovery.

Use the UID as the stable checkpoint after login

Bybit's UID guide explains that the mainnet account UID is available in the account-information page and from the profile menu on the website. A successful login is not enough evidence if you have tried several identities. The UID turns a vague statement such as “my account looks empty” into a testable comparison.

Create a recovery evidence packet with these fields:

1. The social button or credential that opened the session.
2. A masked version of the registered email, relay address, or phone.
3. The UID visible in the profile.
4. The last known successful login date and device.
5. The exact security or verification error.
6. A screenshot of the Apple relay entry or proof that the Telegram-linked number is controlled, with unrelated personal data hidden.
7. The support case number if a request already exists.

This packet is not a way to bypass ownership checks. It helps official support identify the disputed credential and keeps separate UIDs from being mixed in the same case. Submit identity or facial evidence only through Bybit's official flow when requested. For a TradePayback customer review, provide the exchange name, confirmed UID, and the settlement question—never secret authentication material.

Follow the matching official recovery route

Bybit's password reset guide sends a logged-out user through Log In → Forgot Password and asks for the registered email or phone. It also notes that an account initially registered with Google can use the Google button first and then change the password from security settings. The same diagnostic principle applies to Apple and Telegram: first try the original social route so that you do not confuse a password issue with an identity mismatch.

If email, phone, or Google Authenticator access has been permanently lost, select “Having problems with verification?” in the security prompt. Bybit's self-service security guide documents separate choices for a failed authenticator, inaccessible mobile number, and inaccessible email. A new email or phone must be verified, and the request may require another code, facial verification, or support review. The feature may not be available to suspended or restricted accounts.

Do not treat a password reset as an immediate guarantee that every account function is available. Bybit's current password-reset documentation states that several functions are restricted for 24 hours after the login password is amended. Read the on-screen restriction before scheduling a withdrawal, internal transfer, P2P action, or card transaction around a credential change. That is a security control, not evidence that the wrong UID was recovered.

Prevent duplicate main accounts while recovery is unresolved

The safest decision is reversible: inspect identifiers and use recovery before creating another main account. Bybit's account-setting FAQ says an email address and a mobile number can each be linked to only one account. Its deactivation guidance also says a deactivated account's registered email or phone cannot simply be reused to create another account, and identity documents from a verified account cannot be used to verify another account under the same legal identity. Those constraints make “just sign up again” a poor diagnostic tool.

Use this decision table:

If a second UID already exists, do not move assets merely to make the screen look consistent. Preserve which deposits, trades, and rebate records belong to each UID and ask official support about the appropriate account action. A third-party cashback service cannot merge Bybit accounts or guarantee a referral transfer.

Complete recovery, then re-establish a secure account map

After access is restored, verify the UID against historical records before changing several controls at once. Then confirm the registered email, phone, authenticator, and trusted device settings. Update one factor at a time and save the confirmation for each change. If an old relay still forwards correctly, do not replace it solely because the address looks unfamiliar; decide based on future access and official account settings.

For TradePayback, compare the restored UID with the UID previously submitted for customer eligibility or settlement checks. A matching UID solves account identity, but it does not by itself prove a cashback rate, referral status, or payment amount. Those are separate records. Once identity is stable, consult the guides index for the relevant fee or reconciliation question rather than mixing it into the recovery ticket.

Frequently Asked Questions

Can I log in with my personal inbox instead of the Apple relay address?

Not necessarily. If Hide My Email was used, the relay address may be the registered Bybit identifier even though mail forwards to the personal inbox. Use the Apple login button or locate the Bybit relay entry in Apple settings, then compare the resulting UID.

Is my Telegram username the Bybit signup identity?

Bybit documents the phone number linked to Telegram as the signup value. A public username or display name should not be treated as the registered phone. Verify the number and the UID reached through Telegram.

Should I create a new account when verification codes stop arriving?

No account decision should be based on one missing code. Check relay forwarding, spam filtering, phone access, and Bybit's official troubleshooting. If access is permanently lost, use “Having problems with verification?” and identify the existing UID before considering any new registration.

What information should I send to TradePayback?

Send the exchange name, the confirmed UID, and the customer-settlement issue or date range. Do not send passwords, email or SMS codes, authenticator codes, API secrets, or Apple credentials. UID submission is not the same as recovery approval or cashback eligibility.

Does a matching UID mean my referral or cashback is confirmed?

No. A matching UID identifies the account. Referral attribution, eligible products, fee records, and customer payments must still be checked under their own terms. Keep account recovery and settlement review as separate cases.