Refund Policy

Refund Window and Eligibility

You may request a full refund for any reason within 14 days of your first payment. The account's first successful payment record is used to verify the refund window, and the ticket submission timestamp determines when the request was made. Proof of connection issues is not required, and troubleshooting does not need to be completed before a request is accepted.

This commitment applies to the first payment; it does not mean the refund window restarts with every renewal, upgrade, or additional order. Requests made after the window are not covered by the no-questions-asked full refund commitment above. For duplicate charges, unusual order amounts, or benefits not appearing after payment, you can still submit a ticket to review the specific transaction. These cases should not be confused with refunds based on general service experience.

Usage Records and Exceptional Cases

Connecting normally, switching routes, or trying a client does not, by itself, constitute grounds for refusing a refund. Monthly subscription traffic resets each month on the activation date; traffic packages remain valid indefinitely until used up. These traffic rules apply separately from the refund window: a traffic package's indefinite validity does not mean refund requests have no deadline.

Accounts with traffic usage above the allowance, unusual usage records, or suspected violations of the Terms of Service require verification against the order, account, and relevant usage records. This page does not introduce traffic deduction percentages beyond those in the fact sheet, nor treat “traffic already used” as a blanket exclusion. If a decision involves unusual activity or a violation, the specific basis must be explained in the support ticket; a label alone is not an explanation.

A transaction that was not successfully paid or has already been refunded cannot be refunded again for the same amount. If the requester cannot be matched to the payment record, order ownership must first be verified.

How to Request a Refund

1. Sign in to the user panel support tickets, explain that you are requesting a refund, and identify the order.
2. Provide the order number, payment time, amount paid, and payment method. If the order shows an issue, you may attach a redacted payment receipt.
3. Add any verification details to the original ticket and check the result there. Submitting the same request multiple times can split up the records, so it is best to continue in the original ticket.

A no-questions-asked refund does not require a detailed explanation of why you were dissatisfied; you may provide one if you wish. Do not send account passwords, complete subscription links, payment passcodes, or wallet private keys in a ticket. Keep only the parts of a receipt needed to verify the transaction, and redact unrelated personal information first.

Refunds to the Original Payment Method

Once verification is complete, refunds are generally returned to the original payment method and are not transferred to an unrelated third party. Refund processing completion and the funds appearing in your payment account do not happen at the same time. The arrival status depends on payment provider processing, account status, and transaction verification; no fixed arrival time is promised on this page.

For Alipay and WeChat Pay, first check the refund record for the original transaction. If the ticket shows that processing is complete but the funds have not arrived, add the order number and payment provider status to the original ticket for further review. If a refund to the original method fails, explain the issue first and confirm a workable option through a ticket to avoid duplicate refunds or misdirected funds.

Special Payment Methods and Review

USDT payments involve on-chain transactions and cannot simply be treated as reversals of Alipay or WeChat Pay transactions. Before processing, the original payment transaction, network used, and receiving address must be verified. The return route and amount are based on the original order records and the outcome confirmed in the support ticket; this page does not set exchange rates or promise fee terms.

Before providing a receiving address, confirm that it uses the correct network and is valid. If you disagree with the refund amount, applicable window, or verification outcome, identify the relevant records in the original ticket and request a review. Once the refund is complete, the benefits associated with that order will end. For future service needs, see the plan details. Refund status and reviews are handled through the user panel; refer to the records kept there.