This policy explains how refund requests and payment processing work for VPNLM subscriptions. Submit requests through a user panel ticket and include the relevant payment order. Please also read the Terms of Service and Privacy Policy. Subscription prices and billing details are on the Pricing page.
Request Window and Refund Scope
You can request a full refund for any reason within 30 days of your first payment. The window begins with the first successful payment and is verified using the ticket submission time. You do not need to explain why you no longer use the service or troubleshoot connection issues first. Keep your ticket and order details so you can follow up on the request.
Monthly subscriptions and data packages follow different billing rules, but that difference does not change the refund commitment for the first payment. Renewal, duplicate payment, and mid-term upgrade orders are reviewed separately. A new order does not automatically reset the request window for the first payment.
Eligible and Ineligible Requests
Within the request window, factors such as route performance, access to a target service, device usage, or changing personal needs may provide context for your request, but none is required as a reason for a refund. Having used some data does not by itself remove refund eligibility. This policy sets no data-usage percentage or quota threshold.
Orders outside the request window are not covered by this policy’s refund-for-any-reason commitment. For an unsuccessful payment, an order already refunded, or a transaction that cannot be linked to the requesting account, the order status must first be confirmed. The same payment cannot be refunded twice.
If an order has records of excessive usage, an account violation flag, or a payment dispute, the relevant records should be reviewed rather than rejecting an in-window request based only on a flag. Account usage and ownership of the payment should be checked separately. If further information is needed or the request cannot be handled as submitted, explain the specific reason and next steps in the ticket.
How to Request a Refund
Sign in to the account used for payment and submit a request through user panel tickets. Include the order number, plan name, payment date, amount paid, and payment method, and identify the order you want refunded. If the account has multiple transactions, list each one separately to distinguish renewals or upgrades from the first payment.
If the order status does not match the payment result, you may attach proof of payment with unrelated personal information obscured. Do not provide your account password, complete payment account details, wallet private key, or recovery phrase. A VPNLM account does not require an email address; you can submit your request and discuss its progress through the ticket.
After submitting, add any supporting materials to the original ticket and check for replies there. Opening duplicate tickets does not change the request window. If you cannot access the account used for payment, restore access through the login page first, then link the order and submit your request.
Payment Methods and Refund Routes
VPNLM supports Alipay / WeChat Pay / USDT. Alipay and WeChat Pay refunds are generally sent through the original payment route when possible. Whether that route can be used depends on the transaction status and the payment provider. If the original route is unavailable, confirm the reason and an available method in the ticket before proceeding. You will not be asked to make another payment to receive a refund.
USDT transfers have a different refund process from Alipay and WeChat Pay and may require separate confirmation of the receiving address and network. Share only the necessary details in the related ticket, and verify that the address matches the network. A transfer may not be reversible once submitted; the original payment address should not be assumed to be the confirmed refund address.
Requests covered by the full refund commitment for any reason are not prorated based on data already used. Any checks involving payment records, asset units, or differences between payment channels must be explained before processing; undisclosed deductions cannot replace a full refund.
Refund Progress and Service Status
Reviewing a request, submitting a refund, and receiving the funds are separate stages. The time to receive funds depends on payment-channel processing or on-chain confirmation; this policy does not promise a fixed arrival time. After the ticket shows that a refund has been submitted, also check the original payment channel or the confirmed receiving wallet.
If the funds have not arrived, update the original ticket with the current status and any necessary transaction lookup details. Keep relevant records while the request is being handled. Once the refund is complete, the service benefits linked to the order should also be checked to prevent continued subscription use against a refunded order. Monthly data resets and the fact that data packages never expire are billing rules; they do not extend the refund window.