If the charge wasn't yours, start with the company that processed the payment. For an Apple or Google Play transaction, request a refund from the platform or developer promptly. If the billing problem remains, contact your card issuer or bank.
A purchase you made and now regret is different. Approval usually depends on the platform's policy, the purchase type, and whether you used the item.
A chargeback is a separate billing review. It isn't an automatic second appeal.
This guidance is for U.S. consumers. Apple, Google Play, the developer, and your financial institution may each handle a different part of the problem. Turns out, the payment path often matters more than the phone you used.
Choose the right complaint route
Match the receipt to the card statement before choosing a route. Check the relevant purchase history too. The company named on the statement may not control the app account, so identify the payment processor first.
| What happened | Start here | Main reason |
|---|---|---|
| Nobody in your household made the purchase | Contact the card issuer or bank promptly, secure the account, and notify the platform | This may be account or payment fraud rather than an ordinary refund request |
| A child used your saved payment method | Ask the platform and developer for a refund, describing exactly what happened | A child purchase may be unauthorized from your perspective, but the issuer may classify it differently |
| The app or digital item did not work | Contact the platform or developer with screenshots and the order number | The seller or platform may be able to fix a delivery or technical problem |
| A subscription renewed after you tried to cancel | Contact the company that billed you and preserve the cancellation record | The timing and your proof of cancellation matter |
| You paid on the developer's website or through another store | Contact that merchant or payment provider | Apple or Google may not control an outside payment |
Don't call an ordinary change of mind fraud. A truthful account gives the platform, developer, or issuer a cleaner record to review.
Pros and cons of filing an in-app purchase complaint
A complaint can help with an unrecognized charge, a duplicate payment, missing content, or a child's purchase. It can also take time. You may have to repeat the timeline.
| Possible benefit | Cost or limit |
|---|---|
| A platform refund request is usually the simplest first step | Approval depends on the policy and the facts |
| A clear complaint creates a useful record | You may need to explain the timeline again to the developer or bank |
| A card billing dispute provides a separate review process | Credit and debit transactions follow different rules and deadlines |
| A regulator complaint can help document a wider problem | Regulators generally do not act as a personal refund service |
To be honest, there isn't a reliable blanket success rate for Apple or Google Play. A child purchase, a used game item, a subscription renewal, and a charge through a developer's website can receive very different treatment.
Your request is less promising when the purchase was authorized, delivered, used, and then simply became disappointing.
What rule actually controls the outcome?
Your route determines the rulebook. A store refund request, a developer support case, and a bank dispute may concern the same charge without being the same process.
| Process | What controls it | Evidence that helps |
|---|---|---|
| Platform refund request | The store's refund policy, purchase path, transaction age, and sometimes whether the item was used | Order number, receipt, reason for the request, and screenshots |
| Developer refund or support request | The developer's terms and its ability to verify or reverse the transaction | Account name, in-app details, error messages, and earlier support messages |
| Card or bank dispute | The payment method, issuer procedure, applicable billing rules, and whether the charge fits a recognized error category | Statement, transaction date, written explanation, and proof of contact with the merchant |
| Regulatory complaint | The agency's jurisdiction and whether the issue suggests a broader marketplace problem | A concise timeline and copies of earlier complaints |
A store denial doesn't require your bank to reverse the charge. A bank dispute doesn't require the app store to refund it. Use the same dates, amounts, and facts in every request.
Apple App Store refund requests
The Apple route fits most directly when the transaction appears in the purchase history for the Apple account that paid. Match the charge before you submit anything.
- Find the receipt. Compare the Apple account, date, amount, and app.
- Open the refund-request option shown for that transaction.
- Choose the reason that best matches the event. Say if a child made the purchase, the charge was duplicated, or the item did not work.
- Save Apple's confirmation, case number, and response.
- If the charge is missing from the purchase history you checked, contact Apple Support and explain that it appears on your statement.
Apple may ask for more information. It may also deny the request. Don't send conflicting versions of the same story hoping one will work.
Before calling a charge completely unknown, check family members' Apple accounts. That detail can affect the platform's review and the issuer's classification.
The FTC's 2014 action involving children's in-app purchases is historical context, not a standing refund promise. In 2014, the FTC announced Apple's agreement to provide at least $32.5 million in full consumer refunds to settle allegations involving children's in-app purchases made without parental consent. That settlement addressed the conduct and period covered by that case. It doesn't guarantee a refund for every later purchase.
Google Play refund requests
For many app and in-app purchase requests, Google Play is the initial place to ask during the first 48 hours. That period provides a request route, not a promise that every transaction will be approved.
Open the Google Play order history for the account that paid. Select the transaction and use the refund option if it appears. Give a specific reason. "I want my money back" gives the reviewer little to work with.
If the purchase is more than 48 hours old, or the request option is unavailable, contact the developer as well. Include the order number, the account identifier the developer requests, the date, and a short description of the problem. The developer may be able to check delivery, account access, or a technical failure that Google Play cannot see.
Payment source matters here. A purchase made on the developer's website, through another app store, or through a separate payment service may not be reversible through Google Play. Contact the company named on the receipt.
Eligibility and response can depend on the product, account, purchase date, and payment route. Treat 48 hours as a request window, not a guaranteed refund deadline.
When a card dispute makes sense
Thing is, a chargeback isn't simply a more forceful refund request. It asks the issuer or bank to examine a billing problem under the rules for that payment method.
A credit-card dispute may fit an unauthorized charge, a duplicate transaction, or a purchase for which the merchant did not provide what you paid for. For a U.S. credit card, federal billing-error rules generally require written notice within 60 days after the statement containing the error was sent. Follow the issuer's instructions and keep proof that you submitted it.
An email to the app developer may not satisfy that notice requirement. Ask the issuer exactly where and how to file the dispute.
Debit cards don't automatically receive the same protections or deadlines as credit cards. Contact the bank quickly and ask which unauthorized-transaction procedure applies. The credit-card timeline may not carry over to a debit card, prepaid card, or payment app.
Describe the transaction plainly. If your child used a saved card, say so. If someone outside the household accessed the account, explain what you know and when you discovered it.
False fraud claims can damage your credibility and complicate the investigation. The issuer may ask whether you contacted the merchant first, and it may provide temporary credit while reviewing the case.
A payment reversal can also lead the platform to review the account or purchased content. That risk varies. Save a chargeback for a genuine billing problem rather than ordinary buyer's remorse.
Child purchases and parental controls
A child's purchase can be serious without being a classic stolen-card transaction. The clearest request says who had access, what was bought, and what you did after finding the charges.
| Record | What to capture |
|---|---|
| Receipt and statement | Order number, billing descriptor, date, amount, and currency |
| Account access | The account and device used, plus who had access |
| Parental settings | Purchase authentication or spending settings that were active |
| Discovery timeline | When you noticed the charges and what you did next |
| Product evidence | Screenshots of the item, error, missing content, or misleading description |
| Support history | Dates, names or case numbers, and the responses you received |
Start with the platform that processed the payment. If it says no, contact the developer. Consider the card issuer next only if the facts support a billing dispute.
Parents can reduce repeat charges by requiring authentication for purchases, reviewing saved payment methods, and checking subscription settings. Controls help with future purchases. They don't decide whether an earlier charge qualifies for a refund.
How to escalate a rejected complaint
A rejection doesn't call for a new story. Keep the same dates, amounts, and explanation as you move to the next route.
- Ask the platform or developer to review the decision. Include the original case number and name the specific reason you believe the decision was wrong.
- Contact the card issuer or bank. Use this route for a genuine unauthorized charge or billing error, and meet the issuer's deadline.
- Use the CFPB when the issue involves a covered financial company. The CFPB complaint process accepts complaints involving products such as credit cards, checking and savings accounts, and money services. Companies generally respond within 15 days, and you can review the response and provide feedback within 60 days.
- Report broader deceptive conduct to the appropriate regulator. That can help document repeated problems, but it isn't a guaranteed individual refund route.
The CFPB is not an app-store appeals court. If Apple or Google made the refund decision, a complaint about your card issuer may not change it. It can still matter if the financial company mishandled a covered billing dispute.
A clear message to send
Keep the first message short and specific:
"On [date], I was charged [$amount] for [app or item], order [number]. The purchase was [not authorized by me / made by my child without my permission / duplicated / not delivered]. I noticed it on [date] and contacted you on [date]. Please review the transaction and confirm whether you will issue a refund."
Attach the receipt and relevant screenshots. Don't send your full card number. The last four digits are usually enough when a company asks you to identify the payment.
FAQ
Does a complaint guarantee an in-app purchase refund?
No. The platform or developer applies its own refund policy. The issuer reviews a card dispute under the rules for that payment method. Neither route guarantees approval.
Can I dispute a purchase after Apple or Google Play says no?
You can contact the issuer if the facts show a genuine billing error or unauthorized charge. Tell the issuer that you already sought a merchant or platform resolution, then act within its deadline. A refusal based only on buyer's remorse may not support a chargeback.
Is a child's purchase automatically an unauthorized charge?
No. The facts matter, including who made the purchase, whether the child could use a saved payment method, and what permission or controls were in place. Use an accurate description instead of a generic fraud label.
What if the purchase was made outside the app store?
Contact the merchant or payment processor listed on the receipt. Apple or Google may not have authority to reverse a payment they did not process.
How long will the complaint take?
There is no dependable single timeline. A platform may decide quickly, while a developer review or card investigation can take longer. Save each confirmation and watch the deadline given by your issuer.
This is general consumer information, not legal advice. Before submitting a request, download the receipt, match it to the statement, and write a one-sentence timeline. Use the platform or developer route for a policy refund and the issuer route for a genuine billing error. Start by saving those three records.