Refund Policy

Refund window and eligibility

The application window is based on your account’s first payment record. It does not restart when you install a client, connect for the first time, or import a subscription. Submit a ticket within the window and keep a record of your submission. The application date for requests submitted within the window will not be recalculated because of later order checks or payment processing.

You do not need to provide proof of connection issues or complete a route troubleshooting process to request a refund for any reason. Requests for monthly subscriptions or data packages should identify the relevant order. For renewals, upgrades, or multiple payments, list each payment separately; your account balance alone cannot establish the total refundable amount. Requests made after the window are not covered by this policy, but you may submit a ticket to check for payment irregularities.

Order checks and exceptions

Refunds apply only to amounts actually paid and not already refunded. Unpaid, closed, or previously refunded orders cannot be refunded again. If a payment is disputed, its status with the payment provider must be checked first to prevent duplicate processing.

This policy does not deduct fees based on data used or make refund eligibility contingent on avoiding excessive use. Importing a subscription or connecting to a route is not grounds for denying a request made within the window. Suspected violations, unclear payment ownership, or account use by another person require a separate review of relevant records. Account actions and refund reviews are explained separately; a general account issue is not a substitute for stating the reason for a decision. See the Terms of Service for usage requirements.

How to apply and what to provide

1. Sign in to the account used for payment, open a user panel ticket, request a refund, and list the relevant orders.
2. Provide the order number, payment date and time, payment method, and amount paid. If you were charged more than once or an order has not updated, you may attach proof of payment and redact unrelated information.
3. Add any details needed for verification to the original ticket, confirm where the refund will be sent, and check the result there. Keep follow-up messages about the same matter in that ticket to maintain a complete record.

You do not need to submit your account password, subscription link, or client configuration. If you cannot sign in, use the account recovery option in the panel first. Do not transfer funds to another account before payment ownership has been confirmed.

Refund destination and arrival status

Refunds are generally returned through the original payment method. Once the order check is complete, the ticket will explain the processing status. A refund being submitted and the funds appearing in the receiving account are different stages; check the payment provider’s records for confirmation.

Arrival time depends on provider processing, account status, and any necessary checks, so this policy does not guarantee a fixed timeframe. If the funds have not arrived, add the inquiry results to the original ticket so this service can check the refund record. Do not make another payment to follow up on the same request. If the original payment method cannot receive the refund, payment ownership must be verified and a workable option confirmed in the ticket.

How payment methods are handled

Alipay / WeChat Pay: Refunds are handled through the original transaction channel whenever possible. Check the channel’s statement for the refund destination. If the original account status has changed or the provider reports an error, keep the relevant notice for review.

USDT: An on-chain transfer cannot be reversed like a standard payment transaction. The original payment record, network, and receiving address must be checked in a ticket before a return can be arranged. An incorrect address or network may make funds unrecoverable, so verify these details carefully before submitting. Any network fee will be explained before processing; no unconfirmed deduction rules are assumed.

If you have questions about this policy or your order records, ask for a review through a ticket. This page and the Privacy Policy explain how information submitted with a request is handled.