If an in-app purchase failed, you didn't mean to make it, or someone else used your account, start with the company that processed the payment. Contact the bank or card issuer too. Do that right away if the charge is truly unauthorized.
A store refund is a platform decision. A bank dispute follows the payment method's rules. Neither route guarantees a refund.
Who should you contact first?
Check the receipt, not just the app icon. Turns out, an iPhone app can be billed by Apple, while a Google Play purchase may move to the developer after Google's initial refund route. Direct website billing belongs to the developer or its payment processor.
The steps below assume a U.S. consumer. Store policies can be global, but bank protections and complaint channels depend on your country.
Start with the charge, not the app
Pull the order email, store receipt, or bank statement and match that source to the first contact in the table. The app icon is not enough.
| Receipt or charge source | First contact | Why it matters |
|---|---|---|
| Apple purchase or Apple receipt | Apple refund system | Apple controls the store billing record |
| Google Play order | Google Play refund flow | Google may send older requests to the developer |
| App developer or website charge | Developer or website support | The app store may not be the seller |
| Unrecognized bank or card transaction | Bank or card issuer, plus the relevant store | Payment-method deadlines can be shorter than store procedures |
A pending authorization may not be a completed charge. Check for duplicate transactions, another Apple or Google account, and purchases made by someone in your household. Save the receipt before you contact anyone.
State the problem accurately
Keep the explanation short. Refund forms work better when the reason matches what actually happened.
If you bought the item by mistake or did not intend to complete the transaction, say that, and call it an accidental purchase.
Missing content is a separate problem: explain what you paid for, what failed to appear, and when you tried to use it.
Describe the specific error, crash, missing feature, or material difference from the listing if the app or service failed. Keep it brief.
Unauthorized transaction is the right reason only when you did not make the purchase and did not give anyone permission to use the account or payment method. An authorized family purchase can look unfamiliar without being fraud. Do not describe a child's purchase as unauthorized unless that is accurate.
Apple App Store refund steps
Apple's main route is Apple's Report a Problem page. Use it even if the app itself has no refund button.
- Sign in with the Apple Account used for the purchase.
- Choose the option to request a refund.
- Select the transaction and choose the reason that best fits.
- Add a brief explanation, then submit the request.
Save the confirmation and transaction details. Apple may ask for more information.
Check another Apple Account, your email receipts, and your purchase history if the purchase is missing. A family member may have used a different account.
Contact Apple Support and ask what review options are available if the web form does not resolve the issue.
Submitting the form is a request, not a guaranteed refund. If the charge was truly unauthorized, contact the card issuer or bank as well. Don't wait for Apple's response if your payment dispute deadline is approaching.
Google Play refund steps
Google Play uses a timing split. For an app, game, in-app purchase, or subscription charged within 48 hours, the Play refund request is generally the first route. That window is a request path. It isn't a promise that every purchase will be refunded.
Open Google Play, tap your profile picture, go to Payments and subscriptions, open Order history, select the transaction, and use the available refund or problem-reporting option. Do this while you're still inside 48 hours.
After 48 hours, Google generally directs users to the developer for troubleshooting and possible refunds. Use the app's store listing or receipt to find the developer's support contact. Explain what failed and include the order number.
Google guidance has used a 120-day reporting window for certain card, debit-card, and PayPal charges that were not made by you or someone you know. Check the current instructions for your account and payment type. Contact the bank or card issuer promptly as well.
Keep Google's confirmation email. The developer and Google may ask for different details.
Subscriptions and accidental renewals
Thing is, canceling and refunding are separate actions.
Cancellation stops a future renewal when it takes effect but does not automatically reverse a charge that already posted, so cancel through the account that bills you, using the Apple or Google subscription page for store billing or the developer's website for direct billing, and don't count on deleting the app, which usually does not cancel the subscription.
Save the cancellation date and confirmation. Then submit a refund request for the renewal if you believe it was accidental, unauthorized, or not disclosed clearly.
U.S. consumers should not assume a 14-day cooling-off period applies here. It does not cover every digital purchase. Platform terms, the purchase facts, and applicable state or federal rules can all affect the result.
Unauthorized charge: protect the account and payment method
Treat an unauthorized claim differently from buyer's remorse. Move quickly.
- Verify the charge. Check whether it is pending, duplicated, tied to another account, or made by a family member.
- Secure the account. Change the Apple, Google, email, or developer password. Turn on two-factor authentication and remove unfamiliar devices or payment methods.
- Report it to the store and issuer. Tell the platform what happened, then contact the bank or card issuer using the number on the card or statement.
- Follow up in writing when requested. Keep copies of the dispute, receipts, screenshots, and every case number.
For an unauthorized electronic transfer from a U.S. bank account, the Consumer Financial Protection Bureau's guidance says to notify the bank no later than 60 days after the statement showing the transaction was sent, and waiting longer can increase your liability for later transfers.
If the bank asks for written confirmation, do it promptly. The CFPB notes that a bank may not have to provide temporary credit during its investigation if you fail to follow up within 10 business days.
Credit cards use a different billing-dispute process. For a U.S. credit-card billing error, follow the issuer's written instructions, generally within 60 days of the statement showing the error. Use the billing-dispute address if the issuer provides one.
Don't wait for the app store to respond if your bank deadline is close.
Match the dispute to the payment method
| Payment method | Next step | Important limit |
|---|---|---|
| Credit card | Submit a billing dispute to the issuer and attach the receipt and platform response | The issuer's billing-error process and timing apply |
| Debit card or bank-account transfer | Call the fraud department and follow its written-dispute instructions | Federal electronic-transfer rules can depend on when you notify the bank |
| Digital wallet | Open the wallet's dispute process and notify the linked bank or card if the charge is unauthorized | Wallet and underlying payment rules may both matter |
| Developer direct billing | Contact the developer first, then the payment provider if the issue qualifies for a dispute | The app store may have no control over the transaction |
To be honest, "chargeback" is often used as a catch-all term. A bank may handle a debit claim, credit-card billing error, and wallet dispute under different procedures.
Use accurate facts. A chargeback is not a guaranteed refund, and the issuer decides whether the evidence supports it. If the merchant later refunds you, tell the issuer so the records do not show a duplicate recovery.
Build an evidence file
Gather these items before submitting a complaint:
- The receipt, order number, transaction ID, date, amount, and currency
- Screenshots showing the missing item, error, cancellation, or misleading disclosure
- The account email and store account used for the purchase
- A short timeline of what happened and when you reported it
- Emails or chat records with Apple, Google, the developer, bank, or wallet
- A bank or card statement showing the charge, with sensitive numbers covered
Keep the original files. Redact full card numbers, passwords, and security codes.
If the first answer is no
A denial is not always the end, but repeating the same form rarely helps.
Ask the platform or developer which part of the request was not accepted. Add new evidence, not a longer argument.
Request the card issuer's written decision and the evidence it considered. Correct any mistake about whether the purchase was authorized, delivered, or canceled.
For deceptive advertising, a fake app, or a broader fraud pattern, review FTC Consumer Advice. A government complaint can create a record, but it does not guarantee an individual refund.
If a bank or card issuer mishandles the dispute, a complaint to the CFPB may be an additional option. Small claims court or arbitration may also be available, depending on the amount, contract terms, and state law. This is general information, not legal advice.
Your next move
Open the receipt now. Identify the seller, the payment rail, and the complaint type. Submit the matching request and save the confirmation. You'll want that paper trail if the first answer is no.