Refund Policy
Last updated: August 2026
This policy applies to subscriptions and data packages purchased through the RqVPN user panel. It explains refund eligibility, verification, and how funds are returned. Before submitting a request, confirm that the order, payment record, and account status match. Refund reviews only require information related to the actual order; your account password and subscription link are not required.
Refund Window and Eligibility
A full, no-questions-asked refund may be requested within 7 days of the first payment. The window starts when payment for the first paid order is completed. Eligible users do not need to explain their personal experience, but the order owner, payment status, and account usage must still be verified as necessary.
The first paid order may be a monthly subscription or a data package. Monthly subscriptions include ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB; data packages include ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. Data packages remain valid until used and never expire. Refund eligibility is based on the first order for which payment was completed, not an order that was created but left unpaid.
Once a refund request is approved, the corresponding order will be refunded in full. A no-questions-asked refund does not remove the need to verify the account and transaction; verification helps prevent refunds for the wrong order, duplicate processing, or payment to an unrelated record.
Exclusions and Further Verification
A request falls outside this policy's full, no-questions-asked refund commitment if it is submitted after the refund window following the first payment or concerns an order other than the first paid order. Requests involving duplicate purchases, abnormal order status, or payment records that cannot be matched will be handled separately based on verifiable transaction records.
If an account has violated the Terms of Service, a refund request may be declined. This includes reselling subscriptions, sharing or publicly posting subscription links, interfering with network facilities, fraudulent transactions, or unusually concentrated use of service resources. If data usage clearly exceeds normal testing and evaluation purposes, RqVPN may request additional information and review account records for possible abuse.
Orders involved in a payment dispute, chargeback, or other funds-handling procedure must wait until the relevant channel confirms its status before further processing, to prevent the same funds from being returned twice. Processing will pause until the required materials are complete if order ownership cannot be confirmed, the payment proof does not match the order, or the request contains significant omissions.
Application Process and Required Information
Refund requests should be submitted through the ticket center in the user panel. Include your username, the order to be refunded, the payment channel, and payment proof that can be used to verify the transaction. The reason may be brief, or you may simply state that the request is made under this policy without stating a reason.
After submitting the request, keep the original order and payment records, and watch the ticket for additional verification requests. Do not submit your account password, client subscription link, or personal information unrelated to the order. If an order was upgraded during its term, the upgrade difference will be converted into remaining days; the final order and payment records shown in the panel will be used for review.
Continue adding information to the original ticket instead of creating duplicate requests, which can split the transaction records. Once the materials are complete, the refund status and next steps will be updated in the ticket.
Refund Route and Settlement
Refunds are generally processed through the original payment route. Alipay payments are returned to the corresponding Alipay transaction, and WeChat Pay payments are returned to the corresponding WeChat transaction. The arrival time depends on the payment channel's acceptance, settlement, and account status. RqVPN does not make an additional promise about the exact time the payment channel will complete the credit. If the original transaction has been closed or the channel requires further verification, the available handling options will be explained through the ticket.
USDT transactions involve on-chain confirmation and cannot be reversed, so they cannot be returned directly in the same way as Alipay or WeChat Pay transactions. The applicant must confirm in the ticket the transaction record matching the original order, the network used, and a wallet address that can receive the refund. The address and network details must be accurate; once the refund transaction is completed and confirmed on-chain, results caused by an incorrect address or network cannot be reversed.
No payment method will require your account password. If the payment channel shows that a refund has been accepted but has not yet arrived, first check its processing status using the channel's transaction record, then add the relevant proof to the original ticket.
Service After Refund and Account Status
After a refund is approved, the subscription benefits provided by the corresponding order will stop. Unused data and the validity period associated with that order will no longer be retained. Subscription information imported into Windows, macOS, iOS, Android, or Linux clients may continue to appear in the local client, but it no longer indicates that the corresponding service remains active.
A refund does not replace action for Terms of Service violations. If an account has been restricted for violating the Terms of Service, that status will continue to be handled under those terms. An account that completes a normal refund may retain its username and password; to use the service again, follow the plans and order status displayed in the user panel at that time.
If you have questions about the refund result or transaction ownership, add details directly to the original ticket. RqVPN will use order records, payment records, account usage records, and this policy for verification, helping prevent duplicate or conflicting handling across different channels.