Missing an app store's usual refund window doesn't automatically end every option. It does mean you need to match the request to the reason for the charge, the platform that processed it, and the payment method.

There is no guaranteed late-refund period for every in-app purchase (IAP). Google's 120-day instruction applies to a specific type of unauthorized Google Play charge; it isn't a universal credit-card chargeback deadline. A 540-day extension isn't automatic either.

This information is for U.S. consumers and is general information, not legal advice. If a credit-card billing-error deadline may be running, don't wait for Apple or Google to finish reviewing your refund request before checking the issuer's procedure.

Match the dispute to the facts

Don't describe an authorized purchase as fraud simply because the app disappointed you. An inaccurate fraud report can send the complaint into the wrong process and may create account problems.

The deadlines are not interchangeable

Several clocks can apply to the same purchase:

• Apple's refund process: Apple says eligibility may vary by country or region. Its current support guidance does not establish a universal 90-day refund entitlement.
• Google Play's process: Google treats 48 hours as an important point. For requests older than 48 hours, it generally directs customers to the app developer.
• Unauthorized Google charges: Google says to report a purchase you didn't make, and that wasn't made by someone you know, within 120 days of the transaction.
• Credit-card billing errors: For many U.S. credit-card billing errors, the federal process generally requires written notice to the issuer so that it receives the notice within 60 days after the first statement containing the error was sent.
• Debit, prepaid, and bank-account payments: These use different rules and provider procedures. The credit-card 60-day process does not automatically apply.

A store deadline and an issuer deadline are separate. Missing one doesn't necessarily mean you've missed the other, but neither a platform refund nor a bank reversal is guaranteed. In particular, Google's 120-day reporting instruction doesn't turn every IAP into a 120-day card dispute, and 540 days isn't a universal deadline for these transactions.

How to make an older Apple refund request

Use Apple's official process even when the purchase is old:

1. Sign in at Apple's request-a-refund page.
2. Select I'd like to, then choose Request a refund.
3. Choose the reason, select Next, choose the app, subscription, or other item, and submit the request.
4. Check the request status through the same Apple Account.

Apple says refund eligibility can vary by country or region. It also says you can't request a refund while the charge is still pending. Wait until the charge posts and then try again.

If the item isn't listed, check the Apple receipt and confirm that you're signed in to the Apple Account used for the purchase. Search your email for an Apple receipt or invoice; it should identify the item and account connected to the transaction.

If the form doesn't resolve the problem, contact Apple Support with the receipt, transaction details, and a short timeline. State what actually happened: an unauthorized charge, an accidental family purchase, missing content, a technical failure, or a recurring charge. Apple may review an older request, but its guidance doesn't guarantee approval or create a requirement that your bank reverse a rejected charge.

How to request a Google Play refund after 48 hours

Start with Google's refund request process. Google's guidance says:

• When more than 48 hours have passed, contact the app developer about a refund.
• The developer may help with a purchase that wasn't delivered or doesn't work as expected and may process a refund under its policies and applicable law.
• A Google refund decision usually arrives within one day, although Google says it can take up to four days.
• An unauthorized Google Play charge that you didn't make, and that wasn't made by someone you know, should be reported within 120 days of the transaction.

The developer may be the quickest route for a missing or defective IAP. Keep the order number and copies of your messages. If the developer doesn't respond, contact Google Play Support and ask what escalation route applies to that order.

Google also distinguishes an unknown unauthorized charge from an accidental purchase made by a friend or family member using your account. For the latter, request a refund rather than making an inaccurate fraud report. Google Play's refund policies explain that the result can depend on what you bought, when and how you paid, and where you're located.

Can a credit-card dispute be filed after the platform deadline?

Possibly, but a credit-card dispute is a payment dispute, not an appeal of Apple's or Google's customer-service decision. The issuer will consider the facts under the payment account's dispute process; it isn't required to approve the claim because a platform denied a refund.

For many U.S. credit-card billing errors, the Federal Trade Commission's credit-card 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 shown by the issuer, and keep a copy of the notice and proof of delivery.

Include:

• Your name, account number, and contact information
• The transaction date and amount
• The statement description, such as Apple or Google
• The app, subscription, or digital item involved
• The specific problem, described truthfully
• The date you contacted the platform or developer
• Copies of the statement, receipt, screenshots, and any response

A short notice could read:

I am disputing the $[amount] charge dated [date], shown on my statement as [descriptor]. The issue is [unauthorized charge, item not delivered, or other accurate description]. I contacted [Apple, Google, or the developer] on [date] and received [result]. Please review this as a billing dispute. Attached are the statement, receipt, and supporting records.

The FTC says the issuer generally must acknowledge a written complaint within 30 days unless it has already resolved it, and resolve the dispute within 90 days. Keep paying the rest of the bill as required and follow the issuer's instructions about the disputed amount.

If more than 60 days have passed, ask the issuer whether another dispute process is available under your card agreement or applicable network rules. The issuer may still review the matter, but don't present 120 days or 540 days as a guaranteed U.S. deadline. Those numbers don't apply uniformly to every card, issuer, transaction type, or reason for dispute.

If the 60-day window is close, you can tell the issuer that you first asked Apple, Google, or the developer for a refund. Seeking a merchant refund doesn't necessarily replace a timely written billing-error notice.

What if you paid by debit card, prepaid card, or another method?

The FTC credit-card procedure isn't a universal chargeback process. For a debit card, bank-account transfer, prepaid card, digital wallet, or platform balance:

1. Identify the actual payment provider on the statement or receipt.
2. Report an unauthorized transaction promptly.
3. If you authorized the purchase but the content was missing, defective, or not as described, ask which dispute category applies.
4. Follow the provider's documentation and response requirements.
5. Keep the platform case number and payment-provider reference number together.

Google's 120-day instruction may apply to its own reporting route for an unauthorized Google Play purchase. That doesn't automatically mean your bank or wallet provider uses the same deadline. Ask the provider for its specific process rather than borrowing the credit-card rule.

Subscription renewals need a separate approach

Cancel a recurring subscription as soon as you notice the problem. Save the cancellation confirmation, date and time, and any screen showing the renewal terms. Then request a refund for the specific renewal or renewals you dispute.

Cancellation stops future billing; it doesn't automatically refund an earlier charge. Your request has more useful detail when you can show that you canceled before renewal, were charged after a confirmed cancellation, or weren't given clear information about the recurring charge.

The FTC's negative-option materials address recurring subscriptions, automatic renewals, and free trials. They don't create a blanket refund route for every one-time IAP. The FTC's notice on negative-option practices concerns agency rulemaking and public comment; it isn't a refund form for Apple or Google purchases. State consumer-protection and automatic-renewal laws may provide additional rights, depending on the facts and the state involved.

Build one clear evidence file

A reviewer can act more easily when the dates and requests are in one place. Save:

• The Apple receipt or Google Play order confirmation
• The transaction ID and exact amount
• The account email used for the purchase
• The date the charge posted
• The merchant name or billing descriptor
• Screenshots of the app listing, error, missing content, or subscription terms
• Proof of cancellation and renewal notices
• Messages to Apple, Google, the developer, or the issuer
• The denial reason and all case numbers

Put the events in order: purchase, delivery or failure, cancellation if relevant, refund request, response, and payment dispute. Send only what the reviewer needs. Never send your password or an unredacted card number.

If the request is denied

Read the stated reason before sending an appeal. A useful follow-up adds a concrete fact, such as a missing delivery, incorrect amount, confirmed cancellation, or evidence that the transaction wasn't yours. Repeating the same request without new information rarely changes the result.

Use the route that fits the payment:

1. Ask the platform or developer to review the transaction again with the new evidence.
2. For an Apple purchase, check the refund status and use Apple's support options.
3. For a Google Play purchase older than 48 hours, contact the developer as Google directs.
4. If the payment was by credit card and the facts may qualify as a billing error, contact the issuer promptly and use its written-dispute procedure.
5. If the issuer mishandles a properly submitted dispute, preserve the notice, delivery proof, statements, and response before pursuing an appropriate consumer complaint or legal-help route.

A regulator complaint may document a broader billing problem, but it doesn't itself replace the platform refund request or payment dispute.

Frequently asked questions

Is Apple's refund deadline always 90 days?

No. Apple's current guidance says refund eligibility may vary by country or region and doesn't establish a universal 90-day entitlement. Submit the request and explain the facts even if the purchase is old.

Can Google Play refund an IAP after 48 hours?

It can still be worth asking. Google directs requests older than 48 hours to the developer, which may process a refund under its policies and applicable law. Approval isn't guaranteed.

Is there a 120-day or 540-day chargeback period for every IAP?

No. Google gives a 120-day reporting instruction for certain unauthorized Google Play charges. Credit-card billing-error protections generally use a written 60-day notice period, and issuer and payment-method rules vary. Neither figure is a universal deadline for every IAP.

Does Click-to-Cancel guarantee a refund?

No. Negative-option rules concern recurring billing and cancellation practices, not an automatic refund for every old Apple or Google purchase. Show the actual renewal or cancellation problem, then use the platform and payment-provider procedure that matches it.

Before submitting anything, write down the charge date, posting date, platform, payment method, and accurate reason for the complaint. Then file the platform request and, if it may be a credit-card billing error, send the issuer's written notice before the 60-day window closes.