Quick answer
The form sends an enquiry for a published plan. It does not take payment or activate a viewing account. A stored reference and a confirmed transaction are different states.
Review the selected offer
The browser displays the chosen plan, while the server selects the approved amount from its own plan record. A price pasted into a query string is not an accepted payment amount. Check duration, total and connection scope before sending the enquiry.
Provide the details needed to respond
The enquiry asks for name, email, country, device/app and optional notes, with privacy consent. Use notes for the actual setup or billing question. Do not include card details, banking passwords, complete private playlists or activation keys.
Read the result literally
When online storage is configured and a request is saved, the response includes a reference. If storage is unavailable, the form reports that the request has not been stored and provides the contact route. A button click alone is not a successful submission.
Confirm payment and activation separately
Support must confirm the applicable payment route and account operation. Keep the private reference with any written payment and activation confirmation. Do not treat an enquiry message as a receipt, guarantee of a response time or automatic service start.
Avoid duplicate payments
If a result is unclear, follow up with the private reference or timestamp before paying again. Explain which stage you reached: enquiry, pending payment, verified payment or account activation. This lets support review the correct record instead of creating another unrelated request.

























