Refund Policy

Refund Window and Eligibility

You may request a full refund without giving a reason within 14 days of your first payment. The order payment record determines whether a request is within the window. If you submit a ticket within that period, it should not be treated as late solely because review extends beyond the window.

You do not need to prove that a route is faulty or complete troubleshooting before requesting a refund. You can simply state that you want a refund; describing your experience is optional. A successful connection, subscription import or data usage is not, by itself, a reason to reject a request submitted within the window.

Monthly subscriptions and data plans are billed differently. A data plan remains valid until used and does not expire; this does not extend the refund window. Renewals, upgrades and later orders also do not automatically restart the window, which begins with the first payment.

Order Verification and Exclusions

Orders outside the application window are not covered by the no-questions-asked refund described above. You can still submit a ticket about duplicate charges, an unusual payment status or a disputed amount. Any refundable amount will depend on the actual payment and the outcome of the order review.

If data records appear unusual, usage may have exceeded the plan, or an account may have violated the terms, the records and relevant terms should be checked first. A vague claim of “high usage” is not a sufficient explanation. This policy sets no additional data deduction rate and does not automatically treat ordinary data use as a refund fee.

An amount that was not paid, was not successfully processed or has already been refunded cannot be refunded again. If there is a dispute about account ownership or a suspected violation, explain the basis for verification and the proposed next steps in a ticket. See the Terms of Service for the applicable usage rules.

How to Apply and What to Provide

1. Sign in to the user panel and open the support ticket page. Clearly state that you are requesting a refund so your intention is not mistaken for a connection issue.
2. Provide the order number, payment time, amount and payment method for the order in question. If you have multiple orders, identify each one separately to avoid selecting a renewal or upgrade by mistake.
3. If the order and payment records do not match, you may include proof of payment with unrelated details obscured. Do not submit your account password, subscription URL or personal information unrelated to order verification.
4. Check for replies and provide any necessary details in the original ticket. If you cannot sign in temporarily, restore access through the panel sign-in page and continue there. Do not post payment records in public comments.

No email address is required; an account can be created with a username and password. Refund communications are handled through ticket records in the panel. Keep your ticket and order information for future reference.

Refund Route and Tracking

Once the refund review is complete, refunds are generally sent back through the original payment route. The ticket should distinguish between “request received,” “refund initiated” and “funds received.” Submitting a request or receiving a reply does not mean the funds have been returned.

The time it takes for funds to arrive depends on the payment channel and the recipient’s processing, so this policy does not promise a standard processing time. If the ticket says the refund has been initiated but the funds have not appeared, add the details to the original ticket so the channel status can be checked and a duplicate request can be avoided.

The order status, subscription access and associated data handling after a refund should be confirmed in the ticket. Submitting a request does not complete the process, and you should not assume the subscription remains available until the outcome is confirmed.

Handling by Payment Method

VPN87 supports Alipay / WeChat Pay / USDT. For Alipay and WeChat Pay orders, the original transaction record and the channel’s refund status should be checked first. If a refund cannot be sent through the original route, explain why in the ticket and confirm the next steps; refunds are not automatically redirected to another account.

An on-chain USDT transfer is not the same as a refund through Alipay or WeChat Pay, and the original transaction cannot be directly reversed. For a return transfer, confirm the original payment record and the necessary details, such as the network and receiving address, through a ticket. Proceed only after an actionable route has been agreed.

Do not change a receiving address or send another transfer based only on messages outside the site. If the address, network or amount does not match, pause and check with the original ticket. This policy does not set an exchange rate, additional fee or promise to convert the amount received. See the Privacy Policy for how information is handled during refunds.