Independent marketplace for cloud provider accounts across 22 providers

Refund Policy

How AllCloudShop handles order problems: what to check before buying, how to raise an issue with support, and how each case is considered on its own facts.

How refunds are approached here

This page describes, in general terms, what happens when something about an order is not right. It sets out no fixed time window and offers no guarantee, because the honest answer is that outcomes depend on the order, the provider and the circumstances. What it does promise is a process: raise the issue, give us enough detail to look at it properly, and get a considered answer.

Read it alongside the terms of service, which cover order acceptance, pricing and the limits of what this store is responsible for.

Check these before you order

Most disputes are avoidable, and nearly all of the avoidable ones come from a variant that did not match the plan. A few minutes on the product page prevents the majority of them.

  • Read the variant name literally. It states the compute quota, instance count, credit balance, trial status or capability being sold, and nothing beyond that is implied.
  • Confirm the provider is the one you meant. Several listings look similar at a glance, and platforms differ considerably underneath.
  • Check the exact price shown against the variant, and remember that it is in US dollars.
  • Make sure the account suits your workload, not just your budget. The Cloud Matrix and the Cloud Journal exist for exactly that question.
  • Enter contact details you actually monitor at checkout, and check the spelling before submitting.

If anything is still unclear, ask on Telegram or WhatsApp first. Questions asked before an order are quick to answer; the same question after payment is a much slower conversation.

Raising an issue with an order

Start with support rather than with a payment dispute. Open Telegram or WhatsApp and send one message containing four things: the order number, the provider, the variant you bought, and a plain description of what you expected against what you are actually seeing.

Add any evidence you already have. A screenshot of an error message, or of the screen that is not behaving as described, moves a case forward far faster than a paraphrase. Keep the conversation in one thread so the history stays together, and give us the chance to look before escalating elsewhere.

How a case is handled

Each case is looked at individually. We check the order record, compare it against what the product page said at the time you bought, and ask follow-up questions if the picture is incomplete. The aim is to establish what actually happened rather than to apply a template.

Where an order clearly did not match its description, the resolution is agreed with you, and possible outcomes include a replacement or a refund depending on what makes sense for that order. Where the difficulty turns out to be something else, for example a misunderstanding about what a variant name covers or a change made on the provider's side, we will explain what we have found and point you to the right next step.

Any refund that is agreed is returned by the route the payment arrived, as far as the payment method allows. Timing after that belongs to the payment processor and to your own bank, and neither is something this store controls.

Changes made by the provider

Once an account is delivered, it lives on the provider's platform and under the provider's rules. Providers can change limits, policies, pricing and availability, and they can take enforcement action under their own terms at any time. Events of that kind, occurring after delivery, are governed by the provider's terms rather than by this policy.

The same applies to what happens through ordinary use: consumption of credits, charges the provider raises for usage or renewals, and configuration made inside the console are all the account holder's side of the relationship. If you are unsure whether something you are seeing is provider-side, describe it to support and we will help you work out where the question belongs.

What this policy does not cover

It does not cover an account used in a way the provider prohibits, or in a way the terms of service prohibit. It does not cover a change of mind about which platform suits a project, once an account has been issued and used. And it does not promise a particular result for a particular workload, since no store can sensibly guarantee how infrastructure will perform in someone else's hands.

Where local consumer law gives you rights beyond what is written here, this page is not intended to override them.

Questions about an account or an order?

Ask about products, variants, availability or purchasing on either channel.