Refund Policy
Last updated: October 2026
This policy applies to refund requests for VPNPen subscription services. Submit requests through a ticket in the user panel and include the relevant account and payment order. You may also wish to review the Terms of Service and Privacy Policy.
Refund Window and Scope
You may request a no-questions-asked full refund within 30 days of your first payment. The request window starts when the first payment is successful; eligibility is checked against the ticket submission time. You do not need to explain why you are dissatisfied to request a standard refund. Sharing connection details may help identify an issue, but troubleshooting is not required before submitting a request.
This commitment is based on the first payment and does not restart with a renewal, upgrade, or additional order. If your account has multiple orders, specify which one you want reviewed. Each order will be checked separately to ensure that different payments are not treated as a single refund.
Eligibility and Verification
You may request a refund within the refund window due to a change in your needs, your experience with a route, or other personal reasons, without providing additional proof. A successful connection, importing a subscription, or using plan data is not, by itself, grounds for an automatic refusal. This policy does not deduct refund amounts based on data already used or set an additional data-usage threshold.
Orders outside the request window are not covered by the no-questions-asked full refund commitment above. Unpaid orders and unsuccessful payments have no collected funds to return; the same payment cannot be refunded twice. Data packages do not expire, but this does not mean the refund request window remains open indefinitely.
For disputes involving use beyond plan limits, account violations, or uncertainty about who made a payment, the relevant terms, order, and payment records should be reviewed separately. Account status alone does not determine the refund outcome. Any additional verification required and the basis for it should be explained in the ticket; unpublished usage thresholds will not replace the stated refund commitment.
How to Request a Refund
- Sign in to the user panel ticket system, state that you are requesting a refund, and provide the relevant order number, payment time, amount, and payment method.
- If the order cannot yet be matched to the payment record, you may provide proof of payment. Redact personal information that is not needed for verification. Do not submit your account password, subscription link, or other access credentials.
- Add any further information to the original ticket and check for updates. If you need a renewal or upgrade before the refund is confirmed, explain this first to avoid affecting payment verification.
Your account does not require an email address. Refund-related communication takes place through tickets in the user panel. If you cannot sign in, start with the account help option provided in the panel. Do not give your password to anyone else to submit a request on your behalf.
Refund Method and Payment Differences
Alipay and WeChat payments are generally returned to the corresponding account through the original payment method. If the payment channel cannot process the refund that way, explain the reason in a ticket, verify ownership of the receiving account, and confirm an available method before proceeding. Funds will not be sent directly to another account without confirmation.
USDT refunds require verification of the original payment transaction, the network used, and the receiving address. The Alipay and WeChat process cannot be applied directly. If network fees or address requirements apply, these should be explained and confirmed in a ticket first. Do not provide an address based only on an external message, and do not confirm a transfer until the address and network have been verified.
Processing and Refund Tracking
Refund verification, initiating a return, and funds appearing through the payment channel are separate steps. The time it takes for funds to arrive depends on the payment channel, account status, and, where applicable, on-chain confirmations. This policy does not promise a standard arrival time. Ticket updates should distinguish between a refund being initiated and its receipt being confirmed.
After receiving a refund update, check the original payment account or the relevant transaction record. If the funds have not arrived, add the order number and refund status to the original ticket so this service can investigate further. When confirming a refund, the handling of related subscription benefits should also be explained; refunded payments no longer provide ongoing paid benefits.