Refund Policy

You may request a full refund without giving a reason within 7 days of your first payment. The request window is based on the record of your first successful payment to the account. It does not restart based on when you install a client, import a subscription, or make your first connection. Submit a ticket within the window and keep a record of your request.

You do not need to provide proof of connection issues or complete troubleshooting before requesting a refund. You may simply state that you want a refund; details about your experience or any issues are optional. A renewal, upgrade, or separate traffic package does not create a new first-payment refund window. List each relevant order in your ticket.

A first-payment request submitted within the refund window is covered by the full refund commitment when the account and payment records can be verified. Importing a subscription, connecting to a route, or using traffic as intended is not, by itself, a reason to deny a refund. This policy does not impose an unpublished traffic-usage percentage or deduction standard.

Requests made after the first-payment refund window are not covered by this commitment. Orders that have not been paid for, or payments that did not succeed, have no received funds to refund. If your payment account shows a charge but the panel does not show a successful payment, check the transaction status first.

Disputes involving excess usage, accounts that violate the rules, or unclear transaction ownership require verification against the order and relevant records. An unconfirmed irregularity is not automatically grounds for denial. Account-use rules and refund reviews are handled separately. If there is a dispute, specify the issue and the basis for your request in the ticket.

1. Sign in to the account used for payment, open panel tickets, and clearly state that you are requesting a refund.
2. Provide the order number, plan or traffic package name, payment amount, payment date, and payment method for verification. If multiple orders are involved, identify the payment for each one.
3. If the order status does not match the charge record, you may attach transaction evidence. Redact personal information that is not needed for verification.
4. Check replies and provide any necessary materials in the original ticket. Avoid submitting multiple duplicate requests so the payment record and progress can be reviewed together.

You do not need to submit your account password, payment password, wallet private key, or recovery phrase. Do not post subscription links or complete payment records on public pages. If you cannot sign in, use the login page to resolve access issues, and keep your payment and request records safe.

Refunds are generally sent through the original payment method, not directly to another account that has not been verified. For Alipay and WeChat Pay, the original transaction and the provider's support for refunds to the original method must be checked. If the original route is unavailable, explain the reason in a ticket and confirm how to proceed.

On-chain USDT transfers cannot be reversed like ordinary payments. For a USDT refund, the original payment transaction, network used, and recipient details must be verified through a ticket before confirming how the refund will be returned. Do not provide someone else's address or send funds to an unconfirmed address.

Processing steps may vary by payment method, but this does not change the full refund commitment for eligible requests. Any return method that requires your confirmation should first be explained through a ticket to avoid delivery problems caused by a network or recipient-detail mismatch.

Submitting a request, completing a review, issuing a refund, and receiving the funds are separate steps. The time it takes for funds to arrive depends on payment-provider processing, account status, and on-chain confirmations. This policy does not promise a fixed arrival time. After a refund is issued, check both the ticket reply and the statement from the original payment method.

If the funds have not arrived, ask about the refund status or request proof of the return in the original ticket; there is no need to make another payment for verification. If you dispute the request date, refund amount, or outcome, provide the original order and transaction records and ask for an explanation of the review. Later policy updates should not be applied retroactively to add refund restrictions to existing orders.

See the Privacy Policy and Terms of Service for related rules. For specific order issues, keep all written communication in panel tickets.