PHP2GO PAYMENT AND REFUND POLICY
This policy applies to paid plans, one-time builds, subscriptions, international payments, and refunds.
This is working public product text. Before real international payments and advertising, review it with counsel for your jurisdiction, company, payment providers, and tax rules.
This Payment and Refund Policy sets out the rules for paying for paid features of php2go, cancelling subscriptions, refunding payments, handling payment disputes and paying for digital technical services related to diagnostics and compilation of PHP projects.
php2go provides a digital service where the user may upload PHP projects, run diagnostics and compilation, and receive reports, logs and build artifacts. Because some functions consume computing resources immediately after an operation is started, refund terms differ from returns of ordinary physical goods.
This Policy does not limit any mandatory user rights that cannot be limited by agreement of the parties under applicable law.
---
1. General provisions
1.1.This Policy governs payment for plans, subscriptions, one-time services, additional limits and other paid features of php2go.
1.2.This Policy forms part of the Terms of Service and applies together with the Terms, Privacy Policy, Acceptable Use Policy, plans and documentation.
1.3.By making a payment or using paid features, the user confirms that they have read and accepted this Policy.
---
2. Terms and definitions
2.1.Paid features are service functions available after payment for a plan, subscription, one-time payment, limit package or another available payment option.
2.2.A plan is a set of service usage conditions, including limits, available features, billing period, storage amount, number of builds, support level and price.
2.3.Internal credit means a conditional amount, bonus or balance that may be used only inside the service to pay for future paid features and is not electronic money.
---
3. Paid features and payment model
3.1.php2go may provide project diagnostics, build execution, storage of projects and artifacts, extended reports, additional limits, priority queue and technical support.
3.2.Payment may be charged for access to the service, a billing period, number of builds, additional limits, an individual service, an enterprise plan or another paid scope.
3.3.Some features consume computing resources immediately after an operation is started, so starting diagnostics, a build or project analysis is considered when reviewing a refund.
---
4. Prices, currency and taxes
4.1.Prices are displayed on the website, in the personal account, on the plans page, invoice, payment form or another checkout interface.
4.2.The final charged amount may depend on currency, the user’s bank, payment provider, exchange rate, fees and the country where the payment method was issued.
4.3.Taxes, charges, payment system fees and bank fees may be included in the price or charged additionally depending on the payment method and legal requirements.
---
5. Payment methods and payment providers
5.1.Payment may be made by bank card, electronic money, bank transfer, payment aggregator, local payment services or other methods available on the website.
5.2.Payment transactions may be processed by third-party payment providers, banks, aggregators or other financial institutions that apply their own rules, fees and processing times.
5.3.The Administration does not store full bank card details where such details are processed by a payment provider; the service may store payment identifiers, statuses, amount, currency, date and plan.
---
6. Subscriptions, renewal and plan changes
6.1.If the service offers a subscription, by subscribing the user agrees to payment for each billing period until the subscription is cancelled.
6.2.A subscription may renew automatically if this option is clearly indicated during checkout and supported by the selected payment method.
6.3.When upgrading or downgrading a plan, an additional payment may be charged, a new billing period may apply, or internal credit may be granted as indicated in the interface or agreed with support.
---
7. Time when a paid feature is provided
7.1.A paid feature is considered provided in whole or in part from the moment access is opened to the plan, limits, builds, storage, reports, support or another paid capability.
7.2.If the user starts diagnostics, a build, project analysis, artifact generation or another operation, that operation is considered initiated by the user.
7.3.If access was opened but the user did not use it for reasons attributable to the user, this alone is not an unconditional ground for a refund.
---
8. General refund rules
8.1.A refund is possible in cases provided by this Policy, the terms of a specific plan or offer, mandatory legal provisions or a separate decision of the Administration.
8.2.A refund is not automatic and is reviewed individually considering the reason for the request, payment status, access provision, consumed limits and technical logs.
8.3.The Administration may offer a cash refund, partial refund, repeated provision of the service, repeated build, internal credit, transfer of limits or another reasonable remedy.
---
9. When a refund is usually possible
9.1.A refund is usually possible if funds were charged twice due to a technical error and the user did not receive the corresponding additional service volume.
9.2.A refund is usually possible if the paid feature was not provided due to the service’s fault and the Administration cannot provide it within a reasonable time or offer an equivalent alternative.
9.3.A refund may be possible if the user requests it before using the paid feature, provided access was not actually used, operations were not started and limits were not consumed.
---
10. When a refund is usually not made
10.1.A refund is usually not made if the user received access to a paid feature and used it, including starting diagnostics, a build, project analysis, artifact generation or consuming limits.
10.2.A refund is usually not made if a build failed because of project structure, unsupported PHP features, missing dependencies, errors in the user’s code or an incorrect entry point.
10.3.A refund is usually not made because the user changed their mind, no longer needs the service, cancelled too late, chose the wrong plan or did not use the paid feature.
---
11. Failed builds and disputed payments
11.1.The user understands that php2go is a technical diagnostics and compilation service, not a guarantee that any PHP project will be successfully built.
11.2.If a build failed due to a confirmed infrastructure or compiler error on the service side, the Administration may offer a repeated build, fix, internal credit, partial refund or full refund.
11.3.In case of suspected fraud, use of another person’s payment method, chargeback or bank dispute, the Administration may temporarily restrict access to paid features until the circumstances are clarified.
---
12. Requests, timelines, law and version priority
12.1.To request a refund, the user must contact support through the personal account, feedback form or email admin@p2g.dev and provide account email, payment date, amount, currency, payment identifier and refund reason.
12.2.Requests are reviewed within a reasonable time, usually up to 10 business days after necessary information is received; actual receipt of funds depends on the bank, payment provider and payment method.
12.3.This Policy is governed by the law of the Republic of Kazakhstan. In case of any inconsistency between translations and the Russian version, the Russian version shall prevail unless mandatory applicable law requires otherwise.
---
Short user summary
- A paid feature is considered provided when access is opened or an operation is started.
- A failed build does not always mean a refund if the service performed diagnostics or a build attempt.
- A refund is usually possible in case of duplicate charge, service-side technical error or failure to provide a paid feature due to the service’s fault.
- A refund request must be sent to admin@p2g.dev with payment details and a description of the situation.
- If service rules are violated, a refund may be denied.
If you need a copy of terms, a data request, a copyright complaint, or a payment question, contact support.
mailContact support