A swap support ticket should help an exchange identify one transaction and explain what happened. It should not give a stranger access to your wallet, create a second payment, or bury useful facts under threats and speculation. The safest ticket is narrow, factual, and sent through a channel you verified independently.
Summary: Never put a seed phrase, private key, password, recovery code, or arbitrary wallet-connection request in a swap support ticket. Send the original order details, transaction ID, network, amount, and relevant times through the official support route. Then wait for instructions tied to that order instead of sending more crypto or trusting recovery agents in private messages.
This checklist explains what to leave out of a crypto exchange support ticket and what to provide instead. It applies to delayed, failed, incomplete, or confusing swaps. Before submitting, review the official support channels checklist.
Blockchain transfers are usually irreversible. A support request cannot guarantee recovery or reversal. Its purpose is to give the operator enough information to investigate the original order without creating another security or payment problem.
How to use only the official ticket channel
Open the exchange website yourself or use a trusted bookmark. Confirm the domain and use its published support route. Do not move the case to an unsolicited Telegram, WhatsApp, Discord, or social-media conversation because the account uses a familiar logo.
RevBit’s legal documentation lists support@revbit.net as technical support. RevBit also lists an official Telegram account, but verify it through the official website rather than a search result or incoming message. An official-looking profile does not prove that the sender is staff.
- Open the website independently and check the published support route.
- Keep the original ticket and reference available.
- Use an email address or form published by the service.
- Do not send order details to several unverified agents or move the case to private chat.
Real support may ask for transaction information, but it should not require control of your wallet. Stop if anyone asks you to transfer funds, connect a wallet, sign an unexplained transaction, or pay a stranger for recovery. Compare requests with the official site, not links supplied by the sender. See the fake crypto exchange support scam checklist.
How to remove wallet secrets before sending
The answer to “should I put my seed phrase in a swap support ticket?” is no. A seed phrase is a master backup that can control a wallet, and a private key can control an address. A wallet password, recovery code, or two-factor authentication code can also enable account takeover. None belongs in a support ticket.
Support does not need a seed phrase to locate a blockchain transaction. A transaction ID, public address, and order information are intended for investigation and do not provide signing power like a secret key.
- Never include a seed phrase, private key, password, recovery code, or one-time login code.
- Never sign an arbitrary message or transaction to “verify ownership.”
- Never click a “connect wallet” link supplied by an unverified agent.
- Review screenshots for seed phrases, QR codes, private keys, balances, account names, and unnecessary addresses.
Crop sensitive areas or omit an image. If it is relevant, send only the smallest redacted image through the official route. A public receiving address and transaction ID are not secrets, but they can reveal financial activity. Share them only when relevant to the original order.
Avoid sending extra crypto while support investigates
Do not send more crypto to speed up support, unlock a swap, verify a payment, repair a failed order, or cover a fee requested in a private message. The transfer may be irreversible, go to the wrong destination, or have no connection to the original order.
Wait for instructions tied to the original order and verify any new address independently through the official support route. “Send a small amount first” is not proof of legitimacy. The same rule applies to claimed recovery specialists or managers.
A quote or deposit address can be specific to an order. RevBit’s fixed-rate guide describes a 12-minute quote lock. That is a reason not to improvise a new payment while support investigates, not a reason to pay twice. If you already sent funds, record the transaction details and report the original transfer.
- “Send more to unstick the order.” Do not pay; ask through the verified ticket route.
- “Pay a recovery fee to this personal wallet.” Do not pay a stranger; verify the request officially.
- “Connect your wallet so we can return the funds.” Stop; support can inspect a transaction ID without wallet control.
- “Use this new address for the same order.” Confirm the address and reason independently before transferring.
RevBit’s Terms of Use discuss memo or destination-tag recovery under specific conditions and warn that recovery may involve a charge, minimum, review period, or refusal. This is not permission to pay an unsolicited person or a general support fee. Ask through the published route if your issue concerns a memo or destination tag.
Build a factual packet and stop there
The best ticket answers which order is affected, what was sent, where it was sent, and when each event occurred. Use a short sequence. Avoid threats, speculation, and repeated messages that obscure the timeline.
- Write the order ID or exchange reference, if available.
- Copy the transaction ID exactly as shown by the wallet or explorer.
- Name the asset and network.
- State the amount sent and destination address when relevant.
- Add timestamps with the time zone for order creation, payment, and status changes.
- Describe the current result in one factual sentence.
Check every character in the transaction ID and address. Do not manually correct unusual values. Include a network fee only when it explains an amount difference. An explorer link can help, but keep the raw transaction ID in the ticket.
Use this compact structure:
Subject: Swap order status investigation
Order ID: [reference]
Asset and network: [asset, network]
Amount sent: [amount]
TxID: [transaction ID]
Created: [date, time, time zone]
Sent: [date, time, time zone]
Current status: [one factual sentence]
Question: Please check the original order and advise on the next verified step.
A confirmed transaction proves that it exists on a network, not that it can be reversed or redirected. It gives support a starting point for investigation.
Keep one clear follow-up if new information appears. Do not open multiple tickets for the same order unless the official channel tells you to. RevBit’s Terms state that claims on exchange applications should be submitted within 7 business days to support@revbit.net. Check the current wording and do not treat it as a promise of resolution.
- Verify the channel through the official website.
- Remove secrets and unnecessary wallet screenshots.
- Do not reuse a previous deposit address or make a replacement payment.
- Protect the ticket and redact details before asking a community for guidance.
Do not reuse an expired, previous, or one-time deposit address for a follow-up payment. It may no longer be valid, belong to another payment flow, or make matching difficult. Use instructions generated for the current order, not an address copied from chat history.
Unsolicited recovery messages may promise a refund or demand an upfront fee. Knowing your order ID or transaction ID does not verify the sender; those details can come from a public blockchain or compromised conversation. Stop replying, do not click links or connect a wallet, and report the contact if the platform allows it. Return to the official website and verify the route yourself.
Protect the ticket after sending. Do not publish its full contents, especially your email address, destination address, or account identifiers. The stuck crypto swap order status checklist can help organize a timeline, while the expired crypto swap after deposit checklist covers old deposit addresses. Once the ticket is complete, waiting is safer than experimenting.
Frequently asked questions
Should I put my seed phrase in a swap support ticket?
No. Never disclose a seed phrase, private key, wallet password, recovery code, or one-time login code. A transaction ID and order details are enough to begin an investigation.
Can I send more crypto to speed up support?
No. An extra payment may be irreversible and may not be linked to the original order. Wait for instructions tied to the original order and verify any address through the official route.
What should I attach to a RevBit support ticket?
Provide the order ID, transaction ID, asset and network, amount, destination address when relevant, timestamps, and a short status description. Remove secrets and unnecessary screenshots.
Is a wallet recovery screenshot OK?
Avoid it if it shows a seed phrase, QR code, private key, balances, account identifiers, or unnecessary addresses. Redact sensitive areas and send it only when directly relevant through the verified channel.
Should I follow up on Telegram while waiting?
Only use a Telegram account or group confirmed through the official RevBit website. Ignore unsolicited DMs asking you to move funds, connect a wallet, sign something, or pay a recovery fee.