Receipts and purchase history

Match the receipt to the purchase you need help with

A receipt or transaction record should identify the purchase involved in your question. Start by writing down the product, approximate time, account and amount or quantity you expected. Then find the corresponding entry in the platform or store that actually processed the purchase. The VALOSTRIKE inventory view and a payment receipt describe different stages.

If you bought account currency and later used it for an item, those may be separate actions. Preserve the relevant sequence rather than assuming one receipt describes both. A support report about the later item purchase should still explain how the currency and item actions relate, especially if the current balance no longer matches the original purchase amount.

Use the correct transaction history

Open the account or store through its normal website or app and inspect its purchase history. Follow the labels shown by that service; history locations and receipt formats can differ across platforms. Do not use a third-party “receipt finder” that asks for account credentials. If you are unsure which service handled the purchase, compare the purchase confirmation you already have with the account you used.

On a shared device, confirm the purchasing account before searching. If an authorized parent or guardian made the payment, ask them to locate the relevant record through their own account. Do not sign in to somebody else's payment service or ask them to send a complete account export when one focused receipt would answer the question.

Look for the details that connect the records

Useful fields can include transaction reference, date, product description, quantity and transaction state. Keep the text exactly as it appears where practical. If an entry shows pending or canceled, preserve that status rather than calling it completed. A bank notification and the store's transaction state may describe different points in the payment process.

If there are several similar purchases, compare each one separately. A repeated amount does not establish that two entries are duplicates. Note the reference and time for each record you believe is relevant. Support can then investigate the right transaction instead of matching a receipt to the wrong missing item.

Redact unrelated personal information

Before attaching a screenshot, hide card numbers, bank details, billing addresses, unrelated purchases and private account information. Keep the relevant product, date, reference and transaction state readable. Do not obscure the very field support needs to connect the purchase with the case, but begin with the smallest useful record.

Never provide passwords, verification codes, recovery codes or session cookies as purchase evidence. A receipt should not require another person to enter your account. If the available record contains more sensitive information than you can safely separate, describe the fields in the private ticket and ask what additional redacted evidence is appropriate.

Keep account identity and payer identity distinct

The game account receiving an item and the account paying for it may not have the same displayed name. Explain the relevant relationship without publishing the payer's private details. For example, say that an authorized parent made the purchase for the named Roblox account and that the relevant transaction record is attached.

Do not assume that a receipt alone proves every requested account action should be approved. The team must connect the purchase, destination account and issue. Ownership or recovery checks for Roblox remain part of Roblox's own process. A VALOSTRIKE purchase ticket cannot bypass account authentication just because you have a financial record.

Example: two purchases with the same amount

Imagine you made two purchases on the same day and only one appears missing. Find both transaction references and note the times, products and states. Identify which corresponding delivery is present and which is not. If you cannot determine that confidently, say so instead of choosing an arbitrary receipt.

Send the relevant records in one organized explanation with private fields hidden. “Two completed entries, one observed delivery, references A and B” is a useful starting point. The team can ask for a narrower follow-up without you repeatedly attaching the same full history.

If no receipt can be found

Check the service and account used for the purchase, the approximate date range and any confirmation already available to you. A purchase made on a different platform will not necessarily appear in the history you are currently viewing. Do not invent a transaction reference or reuse another person's receipt to make the form look complete.

Tell support which records you checked and what you could confirm. Include the affected username, item, approximate time and observed balance or inventory state. The team can explain what evidence is needed next. A missing receipt is a reason to clarify the transaction, not to expose unrelated account credentials.

Frequently asked receipt questions

Is a screenshot of my inventory a receipt? It shows the inventory state. Pair it with the appropriate transaction record when the issue concerns a paid purchase.

Should I send my whole payment history? Provide the relevant entry with unrelated and sensitive information hidden. More private data does not automatically make a report more useful.

What if a parent paid? Ask them to locate the record through the appropriate service and provide the relevant evidence safely. Do not access their account yourself.

Can I delete the original after submitting a screenshot? Keep your own purchase records as appropriate. A cropped support image may omit details needed later by the store or payment provider.

Make the attachment readable

Check that the relevant reference and status remain legible after redaction. A heavily compressed image can hide the exact field needed to match the transaction, so preserve a clear focused copy.

Submit a clear purchase-history question

Choose Purchases & items and state what you want to establish: finding a record, matching a delivery or understanding an entry. Include product, affected username, approximate time, service used, transaction state and reference if available. Explain any uncertainty about multiple purchases.

Use the same ticket for follow-up and identify each new attachment. If the store changes a transaction's status, record the new state and time. This preserves the connection between the purchase record and the game issue without turning the conversation into an unstructured collection of screenshots.