# Complete UpScalp Premium Verification Without Breaking the Flow

**Last reviewed:** 2026-05-23.

Premium verification should be completed from the official Access Bot in one clean session. Do not mix Telegram accounts, unofficial links, or repeated parallel retries.

Use this page when Premium access fails, verification appears stuck, the Access Bot returns an unclear message, or you need to know what evidence support can review safely.

## Before opening the Access Bot

Check these first:

1. You are using the official Premium access bot: `https://t.me/upscalp_access_bot`
2. Your Telegram account is the one you want linked to Premium access.
3. You meet the current Premium gate shown by the official flow.
4. You have time to finish the prompts without leaving the session idle.
5. You can take screenshots of any error message.

The current public docs state the Premium Holder gate as `5,000,000 UPSCALP`. If the official announcements or Access Bot show a newer requirement, use the official current requirement.

## Complete the flow once, carefully

1. Open `https://t.me/upscalp_access_bot`.
2. Read the requirement text before submitting anything.
3. Follow each prompt exactly.
4. Keep the same Telegram account and device if possible.
5. Wait for the final confirmation or failure message.
6. Save the confirmation or error message.

Do not run the same verification attempt in multiple chats or accounts at the same time.

## What the flow should not ask for

Premium verification should not ask you to:

1. Share a seed phrase or private key.
2. Share an exchange password.
3. Send exchange API keys or API secrets through Telegram, email, or chat.
4. Enable withdrawal permission on an exchange API key.
5. Pay through an unofficial account, bot, or payment link.

If any prompt asks for those details, stop and verify the route from the Official Links page before continuing.

## What failed verification usually means

Verification may fail because:

1. The session timed out.
2. Required input was formatted differently from the prompt.
3. The Telegram account changed during the flow.
4. Access requirements were not met at the time of checking.
5. A temporary upstream service or bot issue interrupted the flow.

Retry only after checking the likely cause. Repeating the same broken attempt usually creates more support work.

## Retry only when the cause changed

Use this rule before a second attempt.

| Previous result                                         | Next action                                                                            |
| ------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| Session timed out                                       | Start a fresh official Access Bot session and finish it without leaving the flow idle. |
| Telegram account changed                                | Return to the account you want linked before retrying.                                 |
| Requirement not met                                     | Do not retry until the official flow shows the requirement is met.                     |
| Error message is unclear                                | Save the exact wording and contact support instead of guessing.                        |
| The bot or link looks different from the official route | Stop and verify from the Official Links page.                                          |

## What to send support

Send support enough information to diagnose the issue without exposing secrets:

1. Telegram username.
2. Product path: Premium verification or Private Beta request.
3. UTC timestamp of the latest attempt.
4. Screenshot or exact wording of the failure message.
5. Steps already tried.

Do not send seed phrases, private keys, exchange passwords, or API secrets.

## Premium verification and Private Beta are different

Premium verification confirms access to Premium delivery when the current gate is met. Private Beta API access is separate and controlled.

If you are requesting beta access:

1. Complete Premium verification first.
2. Use the Access Bot path for beta consideration.
3. Wait for approval.
4. Do not create exchange API keys before approval.
5. Do not assume API access is live until explicitly approved.

## Related

1. [UpScalp Lite vs Premium](https://upscalp.gitbook.io/upscalp-docs/start-here/upscalp-plans-and-access)
2. [Set Up UpScalp Telegram Alerts](https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-telegram-setup)
3. [How to Contact UpScalp Support](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-contact-support)
4. [How to Protect Your UpScalp and Exchange Accounts](https://upscalp.gitbook.io/upscalp-docs/trust-and-safety/upscalp-security-and-account-protection)
5. [UpScalp Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://upscalp.gitbook.io/upscalp-docs/setup/upscalp-premium-verification.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.