RETROSTRESS uses an account access key to sign you in. Save this key before leaving registration. You do not need to put an access key into a support conversation.
Complete the security check if it is shown, then create your account.
Save the generated account access key in a password manager. Treat it like a password.
Use your account access key on the sign-in page to open the workspace.
If registration reports that the security check failed, reload the page and complete the check again. If it still fails, contact support with the exact error, browser, and approximate time. Do not keep creating accounts to work around an error.
Find the right page
Dashboard: your workspace overview and Telegram connection.
Plans & billing: the active plan, expiry, and payment history.
API keys: credentials for integrations, separate from the key you use to sign in.
Support: create a ticket or continue an existing conversation.
An empty payment history does not itself indicate an error. It means this account has no payments in the displayed history. If you expected a purchase, check that you signed into the account used at checkout.
Before using the service
Use the service only for systems you own or have explicit permission to test. Confirm the scope with the system owner and read the current terms of service. If you are unsure whether your intended use is permitted, ask support before proceeding.
Your account access key is your sign-in credential. An API key is a different credential for integrations and will not replace your account access key on the sign-in page.
Paste the complete account access key from your password manager or saved registration details. Avoid extra spaces or line breaks.
Submit the form. A successful sign-in opens your account workspace.
If you see Invalid access key, check that you used the account access key rather than an API key or Telegram link code. Check the saved original instead of guessing or modifying characters.
My key works, but the page returns to sign-in
Use the same official website address throughout sign-in. Allow the site's essential cookies, reload, and try again. If the problem persists, record the browser, page address, time, and error text for support. Do not send browser cookies or authentication headers.
Signing out ends the browser session. Keep your saved key: you will need it to sign in again.
I lost my account access key
Check your password manager and any private place where you saved the key at registration. Creating a new account does not move the old account's purchases or data.
If you still cannot sign in, contact RETROSTRESS support on Telegram. Describe that you lost access and include any non-secret purchase reference you have. Recovery requires a human review; recovery eligibility and the evidence required are not guaranteed by this guide.
I may have shared my account key
Contact support promptly for account-security help. Do not paste the exposed key into the ticket or Telegram message. Removing a screenshot from one place does not establish that the key is safe again.
For an exposed API key, follow API key security, which includes controls available inside the workspace.
Open the bot link offered by the Dashboard. Use that link to identify the correct bot.
Follow the linking prompt or send /link CODE, replacing CODE with the temporary code shown in your Dashboard.
Return to the Dashboard and refresh to check the connection status.
A completed connection is shown as Connected to your account. Generating a code alone does not complete the connection.
The link code expired or is invalid
Link codes expire after five minutes and can be used only once. Generating a new code invalidates your previous unused codes.
Generate a fresh code from the Dashboard, then use the newest code in the offered bot. Do not reuse a code from an older tab or screenshot. Keep the code private while it is valid.
My account is already linked
An account or Telegram user can have only one active link. If you control the linked Telegram account and intend to disconnect it, send /unlink to the same bot. Wait for the unlink confirmation, then generate a fresh code from the intended website account to reconnect. Disconnecting changes the account association, so check which account you are using first.
If you cannot access the linked Telegram account or do not recognize the connection, ask human support to review it. Do not send your account access key or try to connect somebody else's account.
Include the exact linking error and whether it appeared in the Dashboard or Telegram. The assistant can explain these steps, but a general documentation answer cannot confirm or change your account's link.
Use the current pricing catalog and your signed-in Plans & billing page for plan information. Prices, included features, and availability can change; screenshots and documentation examples are not purchase quotes.
What the plan limits mean
Access length is the period for which the purchased plan is available.
Maximum test duration is the duration limit for an individual test. It is different from the plan's access length.
Concurrent tests is the number of tests the plan allows at the same time.
API access indicates whether the plan includes API use. Creating a key does not bypass the plan requirement.
Advanced methods / Chains is a plan capability. Availability should be checked in the current catalog and workspace.
Find my active plan and expiry
Open Plans & billing. The Your plan section shows the current subscription and expiry, or No active plan. Dates are displayed using the browser's local time.
If you expected an active plan after paying, open the relevant entry in Payment history and inspect its status. See payment status meanings before starting a second purchase.
Buy access or review an upgrade
Select View plans, choose the available plan or custom-plan options, and review the final checkout details before paying. Eligible remaining-plan credit is calculated by the server from the current purchase. A previously displayed estimate can change as time passes.
Credit toward a purchase is not a promise of a cash refund. Do not assume that a new purchase adds its access length to the old expiry; review the resulting plan details and ask support if the checkout does not make the outcome clear.
What happens near expiry?
Check the expiry in Plans & billing and review the current purchase options if you need continued access. Do not assume an automatic renewal or a grace period from this guide. For a question about a specific renewal or upgrade total, provide support with the plan name and checkout details, without credentials.
Checkout provides cryptocurrency payment instructions for your selected plan. The asset, network, amount, address, and expiry shown for that checkout are the instructions to follow.
Before sending a payment
Sign into the account that should receive the plan and open Plans & billing.
Choose the plan and review the final total, including any credit shown.
Select an available cryptocurrency option. Confirm both the asset and its network; matching the asset name alone is not enough.
Check the payment address, requested amount, and checkout expiry before confirming anything in your wallet or exchange.
Review wallet or exchange fees so you understand the amount that will arrive. Use the current checkout instructions, not an address or quote from a previous purchase.
If the checkout is expired and you have not paid, return to the purchase flow to obtain current instructions. If you already sent a payment, follow payment problems before sending any more.
After sending a payment
Save the transaction hash from your wallet or exchange. Open the payment entry from Payment history to check the site's status.
A wallet's successful send does not mean the website has finished processing the payment. Detection and network confirmation are separate stages. There is no guaranteed confirmation time in this guide.
When the site records the payment as Confirmed, check Your plan for the resulting access. A Paid status can still mean confirmation is pending. See all payment statuses.
Keep payment information safe
Never share a wallet seed phrase, private key, account access key, or API key with support. For help, a transaction hash, asset, network, approximate sending time, and the site's payment reference are useful. A transaction hash identifies a public blockchain transaction; share it through the official support channel rather than publishing your billing details unnecessarily.
Plans and payments
Payment statuses: Pending, Paid, Confirmed, and PartiallyPaid
The status in RETROSTRESS payment history describes the site's payment record. It can differ from the wording used by your wallet or exchange.
Pending
Pending means the checkout has not yet recorded a detected payment. If you have not sent funds, check the current instructions and expiry before paying. If you already sent funds, compare the asset, network, and transaction details with that checkout. Do not pay again just because the page still says Pending.
Paid
Paid means a payment has been detected, but confirmation or processing is not yet complete. It does not mean the plan is necessarily active. Keep the transaction hash and recheck the payment entry later. Network activity can affect timing; this guide cannot promise a completion time.
Confirmed
Confirmed means the site has confirmed the payment. Check the current plan in Plans & billing. If access is still missing, contact support with the payment reference and transaction hash so a human can check the account and activation.
PartiallyPaid
PartiallyPaid means the recorded payment is below the expected amount. A partial payment does not automatically activate the plan. Contact support with the original checkout details and transaction hash before sending an additional payment. Do not assume that a second transfer will be combined or that the old payment instructions remain valid.
Failed
Failed means the site could not create the payment checkout successfully. Do not send funds using incomplete payment instructions. If no funds were sent, return to Plans & billing and retry the purchase flow. If you already sent funds or the error repeats, contact support with the reference and error before trying another payment.
Expired or Cancelled
Expired means the checkout has expired. Cancelled means the payment record is marked cancelled. Neither status establishes that funds sent on a blockchain have been returned.
If no funds were sent, use the current purchase flow for fresh instructions. If you sent funds to an expired or cancelled checkout, contact support for review before paying again. See payment problems.
Plans and payments
Payment sent but plan missing, wrong network, or underpayment
If you have already sent a payment, collect its details before trying another purchase. Documentation can explain the workflow, but a human must investigate discrepancies in a particular payment.
My payment has not activated my plan
Confirm that you are signed into the account used for the purchase.
Open Plans & billing, then the payment's View details or Continue payment link.
Check the original wallet or exchange transaction for the asset, network, sending time, and transaction hash.
If the details do not match, the status is unclear, or a Confirmed payment has not activated the plan, open a support ticket.
Do not create a new account or pay again to resolve an unexplained activation issue.
I sent too little, used a different network, or paid after expiry
Request human support before sending more funds. Include what the checkout requested and what you actually sent. Recovery, combining transfers, and refunds depend on the transaction and require review; the assistant cannot promise any of them.
A wallet or exchange can show a completed withdrawal while the payment has not reached the intended checkout correctly. Keep the withdrawal record and transaction hash for the investigation.
What to include in the ticket
The plan name and payment reference or transaction ID displayed by the site.
The selected cryptocurrency and network.
The transaction hash from your wallet or exchange.
The amount sent and approximate time, including your time zone.
The payment status currently shown and the exact error, if any.
Redact credentials and unrelated personal information from screenshots. Never send a seed phrase or wallet private key. Continue the same ticket if you have additional information; this keeps the investigation together.
Select Create API key and enter a recognizable name for the integration.
Choose an expiration if needed, then create the key.
Copy the full key into your integration's secret storage before dismissing the confirmation.
The full API key is shown only when it is created. Later, the list shows a masked prefix. If copying fails, save the key securely while the reveal is still open. Do not paste it into a support ticket to check it.
I lost the full API key
The masked list is not a way to recover the full value. Create a replacement key, update the integration's secret, and disable or delete the old key when it is no longer needed. Coordinate changes with anyone who uses that integration.
Disable or delete a key
Select Disable beside a key to turn it off. A disabled key can be enabled again. Expand a key's details to find Delete key, then confirm deletion if you intend to remove it.
If a key was exposed, disable or delete it promptly and replace it in affected integrations. Do not re-enable an exposed key just to restore access.
My integration says the key is invalid
Check the key's status and expiration in the workspace, then check that your active plan includes API access. A key can be listed as Active while its expiration or your plan still prevents API authentication.
If the issue persists, contact support with the key's label or masked prefix, the approximate time, and the error message. Remove full keys, authorization headers, and cookies from diagnostic output. This article covers credential management; endpoint contracts belong in the API reference.
Use Support for account questions and ongoing issues. Sign in to create or follow a ticket. If you cannot sign in, contact RETROSTRESS support on Telegram.
Write a useful first message
Give the ticket a short, specific subject. Describe what you were trying to do, what you expected, what actually happened, and the exact error text. Include the page, approximate time, and time zone. For a payment issue, use the payment troubleshooting checklist.
Never include an account access key, API key, wallet seed phrase, private key, authentication cookie, or authorization header. Redact these from screenshots and copied logs too.
How the assistant helps
When the assistant is enabled, it can explain the published documentation and suggest the next documented step. AI replies are labeled. An explanation is not proof that your account changed or that a payment, refund, or recovery request was approved.
Read the reply and continue in the same ticket if the answer is incomplete. State which part remains unresolved. You do not need to repeat details already in the conversation.
Ask for human support
Use the human-support option in the support page, or say that you want a human in the ticket. A handoff request joins the support workflow; it is not a promise that someone is already looking at it.
Human review is appropriate for lost account access, payment discrepancies, refund requests, account changes, or an issue the documentation does not answer. If the assistant is unavailable, use the support-ticket form directly.
Continue an existing conversation
Open the existing ticket to read replies and add new information. A reply to a resolved ticket reopens the conversation. If the ticket is closed, select Reopen ticket before adding a reply. An AI answer alone does not establish that your problem is solved.
No response-time guarantee or live incident status is established by this guide. For an unresolved question, keep the discussion in the original ticket so the team can see its history.
Use RETROSTRESS only on infrastructure you own or have explicit permission to test. Read the current terms of service before using the service or purchasing a plan.
Is my intended use permitted?
Confirm authorization with the system owner and the scope of the planned activity. If the applicable rules or ownership requirements are unclear, ask support before proceeding. An assistant's reply does not grant permission to use somebody else's infrastructure or override service safeguards.
Can I request a refund?
Contact human support with the purchase reference, date, and reason for the request. Explain whether you could access the purchased service and what went wrong. Include relevant error text without credentials.
Refund eligibility, approval, amounts, and processing times must be checked against the applicable current policy and the specific purchase. This guide does not promise a refund, define a refund deadline, or authorize the assistant to approve one.
If you are still deciding whether to purchase and the terms do not answer your question, contact support before paying. Do not rely on a generic AI answer as a contractual promise.
Where do I ask about privacy or account data?
Read the current privacy policy, then contact human support with your specific request. Do not send credentials or unnecessary identity documents with an initial question.
The assistant can point to published information. Account recovery, data requests, account changes, and policy exceptions need a human review. This guide does not establish retention periods, recovery requirements, or a response-time guarantee.
A page that keeps loading does not by itself prove there is a service outage. The cause can be a browser issue, an expired sign-in session, a connection problem, or a server error.
Check the page without losing your message
Save any unsent support message or other unfinished text privately before reloading.
Reload the affected page and check whether it asks you to sign in again.
If redirected, use your saved account access key on the official sign-in page.
If only one page fails, record its address and the visible error. If several pages fail, note that in your report.
If an action has already been submitted, inspect its resulting record before repeating it. For payments, check Payment history before creating another checkout or sending more funds.
Give support a reproducible report
Include the page address without sensitive query values, browser name and version, device type, approximate time and time zone, and the steps that led to the problem. Quote the visible error exactly when possible.
Describe whether the issue happens consistently or only sometimes. A cropped screenshot can help when the layout or message is the problem. Remove account keys, API keys, payment details unrelated to the issue, and personal information first.
Do not send raw browser network exports, cookies, or authentication headers unless support has provided a secure, specific process for redacted diagnostics.
What happens next?
Use the existing ticket for follow-up observations and note if reloading or signing in changed the result. Support can investigate from the report. This guide and the assistant's general explanation do not confirm a live outage or provide an estimated repair time.
Getting started
Your first test
Start with a short test on a verified target.
1Choose your target
Use a system you own or have explicit permission to test. Complete ownership verification before continuing.
2Choose a method and duration
Select a method appropriate for your system and start with a short duration. Review the settings before launching.
3Start and observe
Monitor your own system during the test. Keep a stop condition in mind, review the impact, and save useful settings for the next run.
