For a disputed in-app purchase, start by identifying who processed the payment. Save the official App Store or Google Play record, the matching bank or card statement, the relevant app or account details, and your support messages. That combination is usually more useful than a screenshot alone.

The remedy depends on what happened:

• Refund or failed purchase: Contact the app store or developer that processed the payment.
• Unauthorized charge: Secure the account, then contact the app store and your bank or card issuer promptly.
• Credit-card billing error: Follow the issuer's written-dispute process and its deadline.
• Regulatory complaint: Preserve the records first. A complaint may help an agency identify a pattern, but it usually does not produce an immediate individual refund.

This article is for U.S. consumers. App-store policies, card procedures, and legal protections can differ elsewhere.

Decide what kind of dispute you have

Use a precise description. "I don't recognize this charge," "the item was never delivered," and "I changed my mind" are different claims and may be handled by different organizations.

An unrecognized charge isn't automatically fraud. Before reporting it, check for a family member's purchase, a second Apple Account or Google Account, a subscription renewal, a different billing descriptor, or a temporary authorization hold. The app's name may not be the name shown on the statement.

The evidence that matters most

A useful evidence packet answers five questions:

1. What was charged? Identify the product or subscription, amount, tax, currency, and date.
2. Which account was used? Record the Apple Account, Google Account, or app account connected to the transaction.
3. What happened afterward? Show whether the item, credits, or subscription benefits appeared.
4. Why are you disputing it? State whether the issue is unauthorized use, duplicate billing, non-delivery, a technical failure, or something else.
5. What have you already done? Include refund requests, cancellation attempts, and support responses.

Official store records

The receipt email and account purchase history are usually more useful than a typed summary or an isolated image. Save:

• The receipt email or purchase-history entry
• The Apple transaction information or Google Play order ID
• The product name and SKU, if shown
• The purchase date and time, including the time zone when available
• The amount, taxes, currency, and billing descriptor
• Subscription renewal details
• The Apple Account, Google Account, or app account involved

A purchase token or server receipt can help a developer locate a Google Play or Apple transaction. Consumers may not have access to every technical field, though. A token generally identifies a purchase record; it does not, by itself, prove who authorized or used the account.

Bank and card records

Save the transaction detail from your online account and the relevant statement page. Look for:

• Posted date and amount
• Merchant descriptor
• Currency
• The last four digits of the payment method, if available
• Whether the transaction is pending, reversed, or completed

A statement shows that a charge posted. It doesn't establish who made the purchase. Match it to the store record even when the descriptor uses Apple, Google, a developer's legal name, or a payment processor instead of the app's name.

Before sending records to a developer or public agency, redact the full card number, security code, passwords, one-time codes, and unrelated transactions.

Screenshots and recordings

Screenshots can show a purchase confirmation, missing credits, an error message, or an attempt to cancel a subscription. They provide useful context, but they may be edited and often don't include the underlying transaction record.

Keep the original file. If you need to remove sensitive information, make a separate redacted copy. When possible, capture:

• The app name and relevant account area
• The purchase or error message
• The device date and time
• The order or transaction reference
• The subscription status or in-app balance

An on-screen timestamp is supporting evidence, not independent verification. Pair it with the official receipt and statement.

Account, device, and access facts

Write down facts that may explain how the purchase was authorized:

• Who controlled the device and account at the time
• Whether Family Sharing or a shared Google Account was enabled
• Whether a child or another household member had access
• Whether a password, PIN, Face ID, Touch ID, or other biometric approval was required
• When you first noticed the charge
• Whether the account showed unfamiliar sign-ins or changed security settings

Keep this description neutral and accurate. A device-authentication setting may show that approval was required, but it may not identify the person who completed the purchase.

Gather the records in the right order

1. Preserve the account and transaction records

Save the receipt email, purchase-history page, statement detail, and relevant app screens before changing anything. Export emails or statements as PDF files when available, but keep the original message or account record too.

Don't rely on a link in an unexpected "refund" email. Open the app store or financial institution through its official app or by typing the known website address yourself.

2. Check the Apple or Google purchase history

For an Apple purchase, sign in to Apple's official refund and purchase support page. Apple says refund eligibility can vary by country or region. It also says that a pending charge can't be submitted for a refund until it posts.

For Google Play, check the Play Store order history and the receipt sent to the Google Account used for payment. Record the order ID and the exact account. If the purchase doesn't appear, check other accounts on the device and consider whether payment went through a carrier, a developer's website, or another service rather than Google Play.

The app's name isn't enough to identify the refund route. Confirm the payment processor shown on the statement. A store's procedure may not control a checkout completed outside that store.

3. Match the store record to the statement

A simple comparison can expose a time-zone, currency, or descriptor difference:

Explain any mismatch instead of treating it as proof of fraud. Common explanations include a time-zone difference, currency conversion, a grouped subscription charge, or a legal merchant name that differs from the app's name.

4. Document a missing item or technical problem

Record what you expected and what actually happened. Include:

• The item or number of credits purchased
• When the purchase completed
• The account or character profile that should have received it
• The balance before and after the purchase
• Error messages and troubleshooting steps
• Whether you tried "restore purchases" or a similar feature

Avoid deleting the app, resetting the device, or altering account data until you've saved the relevant information. Some records may no longer be visible after an account reset or subscription change.

5. Contact the organization that controls the remedy

Use the official Apple, Google Play, or developer support channel. Keep the ticket number, sent message, attachments, and every reply.

A short request gives the reviewer the facts needed to locate the transaction:

On [date], order [ID] charged [amount and currency] for [item]. The problem is [unauthorized charge, duplicate charge, non-delivery, or other specific issue]. The store record shows [relevant fact], and my statement shows [matching fact]. I contacted support on [date]. Please review the transaction and explain the refund or correction decision.

Don't exaggerate or speculate about hacking. If you know that someone in the household made the purchase, don't describe it as unauthorized merely because the item was disappointing.

6. Keep a dated timeline

A timeline helps you give the same account to the store, developer, and issuer.

Use the time zone shown by the device or account. If records use different time zones, say so rather than silently changing the dates.

Apple, Google Play, or an external checkout?

The payment processor matters more than the app's logo.

Don't assume Apple and Google use identical refund windows or that a developer can reverse every store-billed transaction. First establish where the charge was processed.

If you need a credit-card dispute

A chargeback is a card-issuer and payment-network process. It isn't a court decision or an automatic refund, and the issuer decides which dispute procedure applies.

For a qualifying U.S. credit-card billing error, the FTC's credit-card dispute guidance says to send written notice so the issuer receives it within 60 days after the first statement containing the error was sent. Use the billing-dispute address and instructions on the statement, not just a general customer-service address.

Include:

• Your name and account information, using only the necessary digits
• The transaction date, amount, and descriptor
• The factual reason for the dispute
• Copies of the store receipt and relevant correspondence
• The correction or refund you are requesting

Keep a copy and proof of delivery. The FTC says the issuer generally must acknowledge the complaint within 30 days and resolve the dispute within 90 days, subject to the applicable rules and circumstances.

The 60-day written-notice rule isn't a universal deadline for every payment method. Debit cards, prepaid cards, digital wallets, and card-network chargebacks can follow different procedures and time limits. Contact the issuer promptly and ask for the exact deadline and required form.

If the store, developer, or platform refunds the charge after you open a dispute, tell the issuer. Don't seek duplicate recovery without explaining the refund.

If the purchase may be unauthorized

Take these steps promptly:

1. Change the passwords for the Apple Account, Google Account, and app account.
2. Turn on two-factor authentication where available.
3. Review signed-in devices and remove unfamiliar access.
4. Check family members, shared accounts, and subscriptions before reporting the transaction.
5. Report the charge through the relevant app-store process.
6. Contact the bank or card issuer using the number on the card or statement.
7. Save confirmation numbers and respond to follow-up requests.

Tell the issuer exactly what you know. If a family member made the purchase, say that. Whether the purchase is treated as authorized depends on the account, payment method, and applicable issuer or platform rules.

A suspicious email or text isn't proof that a store charged you. Sign in directly to the store account and check the financial statement. Never send passwords, verification codes, or full payment details to someone claiming to be app-store support.

What evidence is useful if a lawsuit is possible?

No receipt, screenshot, or blockchain record is automatically admissible in court. A court may consider authenticity, relevance, reliability, hearsay, and the rules of the applicable jurisdiction. A platform refund review or card dispute usually uses a less formal process than litigation.

If a court case is genuinely possible:

• Keep original emails, PDFs, screenshots, and exported records in their native form.
• Don't edit the original files. Create a separate copy for redaction.
• Record when, where, and how each file was collected.
• Preserve the device or account state when practical.
• Keep a file index and note who handled each item.
• Save support messages with their dates and ticket numbers.
• Ask the platform or developer to preserve relevant server records if they may expire.

For a routine refund or billing dispute, a matching receipt, statement, account record, and support history are usually more practical than specialist forensic tools. An immutable log can show that data was recorded at a certain time, but it doesn't prove that the original data was truthful or that a particular person authorized the purchase. For a significant lawsuit, ask a qualified attorney or digital-forensics professional about the rules that apply.

What the FTC can and can't do

The FTC can investigate patterns of deceptive billing and use consumer reports to inform enforcement. It generally isn't an individual refund desk. Filing a complaint doesn't guarantee that Apple, Google, a developer, or a bank will refund a particular charge.

The FTC's historical Apple in-app purchase settlement shows that regulatory action can lead to a specific consumer refund program. It didn't create an automatic refund rule for every later in-app purchase.

If you receive notice of an official refund program, verify it through the FTC's refund information page. Don't pay a fee or provide remote access to claim a refund.

Mistakes that weaken a dispute

• Sending only a screenshot: Add the official receipt and the relevant statement.
• Calling a charge fraud without checking: Review family accounts, subscriptions, and alternate billing descriptors first.
• Confusing an order ID with a bank reference: Include both and identify which system issued each number.
• Assuming the 60-day credit-card rule applies everywhere: Ask the issuer about debit, prepaid, wallet, and network deadlines.
• Providing excessive personal data: Redact full card numbers, security codes, passwords, and unrelated purchases.
• Deleting the app or resetting the device too soon: Preserve the relevant records first.
• Using inconsistent explanations: Keep the timeline and dispute language factual and consistent.
• Expecting a regulator to decide a refund: Contact the platform and issuer directly about the individual transaction.

Before you submit the request

Check that you have:

• The official Apple or Google Play receipt
• The transaction ID or order ID
• The matching bank or credit-card statement
• The product, amount, date, and currency
• Screenshots of errors, missing items, or account status
• Accurate facts about account access and authorization
• Your support ticket and the company's response
• A dated timeline
• A copy of everything submitted
• The correct deadline and dispute channel

Start with the official purchase record, match it to the financial statement, and send a short factual request to the organization that processed the payment. If that route doesn't resolve a qualifying credit-card billing error, send the issuer's written dispute before its deadline.