Refund Policy

Refund Window and Scope

The refund window starts when your account makes its first successful payment. It does not start when you create an account, install a client, or connect for the first time. Include the relevant order with your request so the payment and submission dates can be checked against the order record. A request submitted within the window remains valid even if verification or payment-provider processing extends beyond it.

This policy applies to refund requests for the first payment for a VPNXB subscription. Monthly subscriptions and data packages use different data billing methods, so identify the relevant order when applying. Renewal, duplicate-payment, and mid-term upgrade charges are reviewed individually. The first-payment refund window does not restart for every subsequent order.

Eligibility and Exclusions

Requests made within the refund window do not require an explanation about route performance, platform compatibility, or why you stopped using the service. Normal service use, importing a subscription, or regular data consumption alone are not grounds for denying a no-questions-asked refund. There is no limit on the number of devices connected at the same time, and device count alone should not be treated as evidence of account irregularities.

Requests submitted after the refund window are not covered by this page's no-questions-asked full refund commitment. Duplicate requests for the same refunded payment, or requests that cannot be matched to a successful payment on this site, require order-status verification first.

If records show unusual data use beyond the package allowance, suspected policy violations, or a dispute over account ownership, the relevant order and terms of service must be reviewed. A vague claim of “excessive data use” is not, by itself, a sufficient basis for a decision. The ticket should explain the verification result and relevant terms. This page does not establish any unpublished data deduction threshold.

How to Apply and What to Include

Sign in to the user panel, open the support ticket portal, and state that you are requesting a refund, identifying the relevant order. We recommend including the order number, payment date, amount, and payment method. For duplicate payments or upgrades, list each order separately to avoid mixing transactions.

If a payment record cannot be matched, provide supporting payment proof as requested in the ticket. Before sharing a screenshot, cover any personal information unrelated to that transaction. Do not send your account password, full subscription link, wallet private key, or recovery phrase. An account can be created without an email address, and refund communications can be handled in the signed-in user panel.

After verification, the ticket will explain which order the refund covers, the amount to be returned, and the processing method. You can add information and check progress in the original ticket; there is no need to submit the same request again. The handling of subscription benefits associated with the refund should also be explained during processing.

Refunds to the Original Payment Method

Supported payment methods are Alipay / WeChat Pay / USDT. Alipay and WeChat Pay transactions are returned through the original payment channel whenever possible. If that channel cannot process the refund, the reason and an available alternative should first be explained and confirmed in a support ticket. Do not request payment directly to an account with an unclear source.

USDT transfers are handled differently from Alipay and WeChat Pay and cannot be assumed to reverse automatically through the original transaction. Before processing, confirm the original order, transfer network, and receiving address through a support ticket, and verify the refund amount and any relevant channel details. If there are questions about the amount or fees, explain and confirm them first; do not change the full refund terms without notice.

The account holder should verify receiving details in the support ticket. If an address changes or the refund is to be sent to another account, ownership must be confirmed to prevent the funds from going to the wrong destination.

Refund Progress and Confirmation

Request verification, submission of the refund to a payment provider, and receipt of the funds are separate stages. Arrival time depends on the status of the original payment channel; USDT refunds also require confirmation on the transfer network. This policy does not specify a fixed arrival time that has not been confirmed by the payment provider, and acceptance of a support ticket does not mean the funds have arrived.

After receiving a processing update, check the original payment or receiving record. If the ticket says the refund has been submitted but the funds have not arrived, share the current transaction status in the original ticket so it can be investigated. Keep the relevant records for duplicate payments, discrepancies in the amount received, or failed payment-channel returns; these cases are handled according to the specific order.

This policy and the Terms of Service cover service and refund matters together. For information on how application details are handled, see the Privacy Policy. If you have questions about the refund window, order ownership, or the outcome, use a support ticket in the user panel to get details about your transaction.