Request Window and Eligibility
You can request a full, no-questions-asked refund within 14 days of your first payment.The request window is based on the record of your first successful payment. If you submit a refund ticket within that window, the time needed for subsequent verification does not change the submission date. You can simply state that you want a refund; a connection issue or explanation of your experience is not required.
This commitment applies to the first payment and does not mean that every renewal, upgrade, or additional order comes with a new request window. “Traffic packages never expire” refers to the validity period of the traffic, not to an unlimited period for requesting a refund. For orders outside the scope of this commitment, you can submit a ticket with the details, and customer support will review the transaction and respond.
Eligibility and Verification Limits
For a first-payment order within the request window, you may request a refund if your circumstances change, the service does not meet your needs, or the connection experience falls short of expectations. Having connected to a route or used some traffic does not, by itself, mean you automatically lose eligibility for a full, no-questions-asked refund. This policy does not impose an unpublished traffic-usage percentage or deduction threshold.
Unsuccessful payments, transactions that have already been refunded, and orders that cannot be confirmed as belonging to the requesting account are not eligible for duplicate refunds. If a case involves unusual traffic, account violations, or a payment dispute, the order ownership and relevant records must first be checked. An alert alone is not grounds to assume that you have lost refund eligibility. If a request cannot be handled under this commitment, the specific basis will be explained in the ticket, and you may provide additional materials for a review.
How to Apply and What to Provide
Sign in to the user panel and submit a request on the ticket page. Identify the order to be refunded, the payment method, and any payment records needed for verification. If your account has multiple transactions, specify which order the request concerns to avoid affecting services you want to keep. You do not need to provide a reason, but make your refund request and the relevant order clear.
VPNKZ does not require an email address to create an account; a username and password are all you need. Keep and check your ticket replies in the original account. Verification materials only need to show the information relevant to the transaction; you may redact unrelated account details. Do not submit your login password, a complete subscription link, or sensitive authorization details from payment records. If more information is needed, add it to the original ticket; submitting duplicate tickets may scatter the conversation history.
Refund Methods and Payment Verification
Once verification is complete, refunds are generally returned through the original payment channel. Alipay and WeChat Pay transactions are handled according to the refund capabilities of the relevant transaction. If a return through the original channel is unavailable, the reason must first be explained in a ticket and the alternative arrangement confirmed with you. An unconfirmed alternative is not considered a completed refund.
USDT refunds require a separate check of the transaction record, receiving network, and address; the Alipay or WeChat Pay process does not apply. Provide the requested information only in the original ticket, and proceed after it has been confirmed. Processing and settlement times vary by payment channel, and this policy does not guarantee a fixed arrival time. Verify the refund submission and the actual receipt separately. If the funds have not arrived, check the progress in the original ticket.
After a Refund and Dispute Resolution
Once a refund is completed, the plan benefits associated with that order end accordingly. If you want to keep other orders, make that clear in your request. For upgrades or related transactions, the relationship between orders must first be clarified; refund amounts, service balances, and traffic benefits must not be counted more than once.
If you disagree with the verification result, refund amount, or payment status, add the order records to the original ticket so the case can be reviewed in context. For connection issues, you can also refer to the frequently asked questions, but troubleshooting is not a required step in a refund request. This policy, the Terms of Service, and the Privacy Policy explain the service arrangements together. Applicable statutory consumer rights are governed by the relevant laws.