Refund policy

Start with the actual purchase problem

Before asking about a refund, identify whether the concern is a completed delivery, a missing item, an unexpected transaction or a purchase you no longer want. These situations require different information and may involve different services. A single sentence such as “the completed transaction has no matching item in my collection” gives support a practical starting point.

Do not treat this guide or another player's experience as approval for your case. Any outcome depends on the relevant transaction, delivery record and applicable process. VALOSTRIKE support should explain the available next step after reviewing the facts rather than having you assume a refund or replacement has already been granted.

Identify who processed the transaction

Check the receipt or purchase history and note the platform or store that handled payment. That service may operate the payment or refund process. VALOSTRIKE can investigate game-specific delivery and explain relevant records, but it should not be assumed to control every transaction handled by Roblox or another provider.

If the transaction was an in-game spend of account currency, distinguish it from the earlier purchase of that currency. Include both actions only when they are relevant and explain the sequence. A refund request for a payment and a question about an item purchased with an existing balance are not necessarily the same action.

Confirm delivery before describing the remedy

Inspect the correct account, balance and collection view. Note whether the product is absent, partly delivered, owned but not equipped, or present in an unexpected variant. These distinctions can change what needs investigation. If a transaction is still shown as pending or canceled, include that state rather than calling it a completed payment.

Do not buy the same product again as a test. Repeated purchases can create additional valid transactions and complicate the original question. Preserve the first record and describe the missing result through Purchases & items. If the item arrives later, update the case so the team reviews the current state.

Prepare the transaction evidence

Keep the affected username, product, quantity, date, transaction reference and state together. Attach the relevant receipt with card numbers, billing addresses and unrelated purchases hidden. Include the expected and observed delivery result. If you do not know the exact time, label it approximate instead of inventing precision.

If a parent or another authorized purchaser handled payment, ask them to use the appropriate service process and provide the relevant record safely. Do not send their full financial history or account credentials. The support conversation needs a connection to the transaction, not access to the payer's account.

Explain what happened in order

A useful timeline starts with the purchase attempt, then the transaction result, then the inventory or balance check. Add any later spending, delivery or contact with the store that affects the question. If you already submitted a request elsewhere, state which service and the general status so that the same transaction is not discussed as though no prior request exists.

Keep observations separate from your preferred outcome. You can explain that you would like a refund while still describing the actual product and delivery state honestly. Do not claim non-delivery when the real concern is dissatisfaction with a delivered item. Accurate information gives support the best chance to explain the applicable process.

Example: a delivered item differs from your expectation

Suppose a cosmetic is present in your collection, but you expected an additional variant. Record the product description and the variant actually delivered. Explain the misunderstanding directly. This is different from saying nothing arrived, and the team needs the distinction to review the right information.

Avoid using or changing unrelated items to demonstrate the issue. A focused comparison of the product description and collection state is enough to begin. If you do not have the original description, say what you remember and label it as memory. Support can assess available records without a fabricated screenshot or an invented promise.

Handle unfamiliar purchases through the right channels

If you do not recognize a transaction, review account security and use the platform or store's support process for the payment concern. Preserve the relevant record and secure the underlying account through its legitimate controls. Do not continue using a suspicious link or respond to a private message offering a refund in exchange for credentials.

You can separately report VALOSTRIKE activity related to the transaction. Explain what you observed and which security steps are complete. Account recovery, payment investigation and game-item delivery are separate tasks even when they arise from the same incident. Keep their timelines connected without assuming one team can perform every action.

Frequently asked refund questions

Does opening a ticket approve a refund? No. It begins a review of the question and relevant records. Wait for the actual outcome communicated in the case or by the service handling payment.

Can another player's refund prove my purchase qualifies? Cases can involve different products, services and circumstances. Provide your own transaction information.

Should I submit many requests to speed things up? Continue in the existing case when possible. Duplicate reports split the evidence and do not improve the underlying transaction record.

What if the item arrives while the case is open? Update the ticket promptly with the new state and when you noticed it. The team should assess the current facts.

Record the response you receive

Keep the outcome and any reference supplied by the service handling the request. If you contact game support afterward, summarize that result accurately and explain which game-specific question remains. This avoids treating an earlier decision as though it never happened.

Ask for a specific next step

Choose Purchases & items, identify the transaction and describe the problem. Say which result you are asking about and include the evidence that connects the purchase to the account. If the payment service must handle the request, follow its current process rather than relying on a player-created form or copied old instructions.

Keep the conversation factual and private. Do not share credentials, threaten another player or invent a policy to strengthen the request. A complete, accurate record lets the team explain what can be investigated and which service controls the next action.