Refund Policy
Last updated: August 2026
This policy explains the refund scope, application method, review criteria, and return rules for VPNVB subscription services. Before submitting a request, confirm the order status, payment method, and account usage.
Refund Commitment and Scope
A full, no-questions-asked refund may be requested within 30 days of the first payment. No-questions-asked means the applicant does not need to prove a service fault or provide complex technical analysis; VPNVB will still review the account, order, payment record, and service usage to confirm that the request falls within this policy.
The refund window begins when the first paid order is completed and applies to the first payment on the same account. Renewals, plan upgrade differences, and separately purchased traffic packs do not create a new refund window. Monthly subscription traffic resets each month from the activation date; traffic packs remain available until used and never expire. Validity periods and traffic rules for different products do not change because a refund request is submitted. Whether service access is paused depends on the refund review status.
Eligibility and Exclusions
A refund request may be submitted during the refund window when the payment status is clear, account ownership can be verified, and no unusual usage has occurred. Connections that do not meet the needs of the user’s location, client compatibility that falls short of expectations, or international route performance that does not suit the current network environment may be provided as background, but the applicant does not need to state a specific reason.
The following circumstances are generally outside the no-questions-asked refund commitment: the request is submitted after the refund window; the same account has already received a first-payment refund; the account has been restricted for violating the terms of use; the order involves resale, profit from sharing, deliberate depletion of route resources, or other conduct clearly beyond normal personal use; traffic usage has exceeded a reasonable level needed to verify connections, routes, and client compatibility; the payment record cannot be matched to the applicant’s account; or the transaction has entered a dispute or reversal process through the payment channel.
These circumstances are reviewed against order and usage records on a case-by-case basis and are not determined solely by a failed connection, route switching, or normal test traffic. For accounts that violate the terms of use, VPNVB may complete an account and order review before deciding whether to accept the refund request.
Application Process and Required Information
Refund requests must be submitted through the ticket entry in the user panel. Include the username, relevant order information, payment method, payment proof that can be used to verify the transaction, and the order to be handled. If the order was upgraded, renewed, or supplemented with a traffic pack, specify the transaction requiring review so that separate orders are not treated as one refund.
After submission, the service team will verify the first payment date, order status, payment records, refund history, and account usage. If information is incomplete or the proof cannot be read, a request for additional materials will be sent through the ticket. Continue replying in the same ticket to prevent duplicate submissions from making the order status difficult to match. Continued heavy usage during review may affect the assessment of the refund scope.
Review Results and Refund Amount
Orders meeting the first-payment refund conditions receive a full refund of the original payment amount. The refund is based on the completed original transaction, not recalculated from the listed plan price, account balance, or unused traffic, and will not exceed the amount actually paid for that order.
If a request covers a first order, upgrade difference, renewal, or additional traffic pack at the same time, VPNVB will explain the result for each transaction according to its order relationship. Transactions not included in the refund retain their original order status; service benefits confirmed for refund may stop after the refund is submitted. If the review is unsuccessful, the ticket will state the relevant order status or policy clause.
Original Payment Return and Processing Time
Alipay and WeChat Pay payments are returned through the original payment channel where supported. After VPNVB submits the refund, the time to receive it depends on the payment channel’s processing status. Bank settlement, payment account status, or channel review may affect when it appears, so no fixed arrival time is promised. Applicants can check the refund record in the original payment account and report unusual statuses through the ticket.
USDT transactions require on-chain confirmation, and the original transaction usually cannot be reversed directly. After approval, the applicant must provide on-chain transaction details matching the order and confirm an address and network capable of receiving the corresponding asset. The arrival progress after submission depends on the on-chain confirmation status. Any request for a private key or recovery phrase is not part of refund verification.
If the original payment channel no longer supports a return through the original route, VPNVB will explain the restriction in the ticket and confirm an available method with the applicant. Without confirmation in the ticket, the refund will not be sent to payment details unrelated to the order.
Disputes and Policy Application
If you disagree with a review result, add the order proof, transaction status, or usage details to the original ticket. VPNVB will recheck the case using the refund policy in effect when the request was submitted, the terms of use, and the order records. Transactions for which the payment channel has already accepted a dispute should be handled through that channel’s process first, avoiding multiple refund routes for the same order.
This policy covers payment refunds for VPNVB subscriptions and traffic packs only. It does not cover fees arising from the applicant’s local network, third-party applications, or other services. Policy changes do not alter completed refunds; requests still under review will be assessed against the commitment and ticket records applicable when the order was created.