Pull up the receipt before you open the app. It may identify the account, order number, date, amount, and payment method. Then find the business that actually processed the payment. That might be Apple, Google Play, the developer, or another processor.
That name tells you where to ask for a refund first. If nobody authorized the purchase, secure the account and notify both the billing platform and your card issuer or bank. A refund request and a billing dispute are different tools.
This information is for U.S. consumers. It's general information, not legal advice.
First, classify the charge
Name the problem before you report it. The route changes with the facts.
| What happened | Best description | Start here |
|---|---|---|
| You don't recognize the purchase, and nobody authorized it | Unauthorized transaction | Secure the account, then contact the platform and your card issuer or bank |
| You authorized the purchase, but the item never arrived or didn't work | Delivery or service problem | Contact the platform or developer and save proof of the problem |
| A child or household member made the purchase | Accidental or household purchase | Request a refund with an accurate explanation |
| The same purchase appears twice | Duplicate billing | Compare order records, then contact the billed party |
| A subscription or trial renewed | Recurring billing issue | Check cancellation records and request a refund if appropriate |
| The statement points to a developer website or another processor | Direct merchant billing | Contact that business first, then use the card or bank dispute process if needed |
An app's name on your phone doesn't show who charged you. Match the statement to the receipt.
Which rule controls your dispute?
Turns out, one app-store chargeback rule doesn't cover every case. Apple and Google each apply their own refund process, while your card issuer or bank handles a payment-account dispute.
Credit card charges
For a credit card charge, the issuer's billing-error process is the formal route if the transaction was unauthorized or otherwise fits a billing-error category. The FTC's guidance on disputing credit card billing errors says written notice generally has to reach the issuer within 60 days after the first statement containing the error was sent.
Use the billing-dispute address in the issuer's instructions. Keep the letter and anything you included with it.
After receiving a qualifying written notice, the issuer generally has 30 days to acknowledge the complaint and 90 days to resolve it, unless it fixes the problem sooner. Those are credit-card notice rules. They don't make Apple or Google approve a digital-purchase refund.
Bank accounts and debit cards
Debit cards and bank-account transfers follow a different notice route. For an unauthorized transaction on a bank statement, the CFPB says you generally must notify the bank no later than 60 days after the statement was sent. Report it sooner if you can.
If you learn that an access device was lost or stolen, the two-business-day window matters. Under Regulation E, notice within that window can limit liability to the lesser of $50 or the amount transferred before you gave notice.
This protection is tied to a lost or stolen access device. It isn't a universal deadline for every unfamiliar debit. Later notice can bring a higher liability limit.
When the bank asks for written follow-up, meet its deadline. The CFPB says that failing to provide it within 10 business days can affect temporary credit during the investigation.
These rules govern the payment account, not the app store's refund decision.
Apple App Store and Google Play: what to check
Apple and Google may display similar charges, but their account records aren't the same. Start with the receipt.
| Check | Apple App Store | Google Play | Why it matters |
|---|---|---|---|
| Account record | Review the Apple Account purchase history and receipt | Review the Google account and Play order history | Confirms whether the purchase belongs to your account |
| Billing source | Check whether the receipt identifies Apple, the developer, or another processor | Check whether the receipt identifies Google Play, the developer, or another processor | Tells you who should receive the first refund request |
| Order details | Record the transaction or order information shown in the receipt | Record the order ID and purchase details shown in the receipt | Helps support staff locate the transaction |
| Security review | Check recent sign-ins and unfamiliar devices | Check recent sign-ins and unfamiliar devices | May reveal account access that you didn't approve |
If the receipt names a developer website, the app store may not have billed you. Ask the business named there about the charge.
An unfamiliar device, IP address, VPN, or travel location isn't proof of fraud. Those details can support a closer review, but they don't show who authorized the purchase.
Red flags that deserve a closer look
Red flags point to questions; they don't decide the case. Platforms and issuers may weigh device, IP, and usage data with the receipt, account history, and your explanation.
| Sign | What it may mean | Sensible response |
|---|---|---|
| Several unfamiliar purchases appear close together | Account takeover, stolen payment details, or duplicate processing | Secure the account and alert the issuer or bank |
| A new-device or sign-in alert appears near the purchase | Someone else may have accessed the account | Change the store and email passwords, then review account security |
| The statement name doesn't match the app name | The platform or a developer may use a different billing descriptor | Compare the statement with receipts before disputing |
| A charge appears after you tried to cancel | The cancellation may not have completed, or billing timing may overlap | Save the cancellation confirmation and ask the billed party to review it |
| A support message asks for your password or full card number | The message may be an impersonation attempt | Stop using that message and open support through the official account or receipt |
| The digital item was used before the dispute | The purchase may have been authorized, or an intruder may have used the account | Explain exactly what happened instead of guessing |
A practical dispute workflow
Keep one factual timeline for everyone you contact. It prevents the platform record and the bank record from drifting apart.
-
Save the transaction record. Note the date, amount, statement description, order ID, account email, and payment method. Keep the original receipt email, not only screenshots.
-
Describe the issue accurately. Call it unauthorized only if nobody with permission made the purchase. If you approved it but the item was missing, defective, duplicated, or renewed unexpectedly, name that problem instead.
-
Secure the accounts. Change the store password and the password for the linked email. Turn on multi-factor authentication, review signed-in devices, and remove anything unfamiliar. Tell the card issuer or bank promptly if the payment details may be compromised.
-
Contact the billed party. Use the refund or support route shown in the purchase record. Include the order details, explain the problem briefly, and say whether the item was delivered or used. If another company processed the payment, contact that company.
-
Notify the financial institution about unauthorized transactions. For a credit card, send the written dispute within the applicable 60-day period. For a bank-account or debit transaction, notify the bank as soon as possible and follow its instructions. Don't wait for a platform response if a payment account may be compromised.
-
Keep a paper trail. Save support ticket numbers, dispute letters, delivery confirmations, bank messages, and the platform's decision. Redact unrelated transactions and sensitive information before sending screenshots.
-
Tell everyone about a refund. If the platform later returns the money, update the issuer or bank. That helps prevent duplicate recovery and keeps the records accurate.
Evidence that makes a dispute easier to review
Support teams usually need a small, relevant record. Thing is, the receipt identifies the purchase while the statement may explain the billing descriptor, so keep both as you work out who billed you.
- The statement showing the date, amount, and billing description
- The store or merchant receipt with the order number
- The account email or username tied to the purchase
- Screenshots showing a missing item, error, duplicate charge, or cancellation attempt
- A short timeline of when you noticed the charge and what you did next
- Copies of support replies, delivery confirmations, and any refund decision
Never send a password, one-time security code, or full card number. Leave the relevant transaction visible, but cover unrelated account details.
Mistakes that can weaken a legitimate claim
To be honest, wording can derail a legitimate claim. A child purchase isn't automatically fraud, and a cropped screenshot may leave out the fact that matters. Check the account records before you file a bank dispute.
Deadlines can run while you're waiting. A platform reply doesn't necessarily pause a card or bank notice deadline, so use the same timeline with both and correct mistakes quickly.
Chargebacks aren't a general satisfaction guarantee. If you authorized the purchase but changed your mind, ask the platform for a refund and describe the circumstances truthfully.
Questions consumers often ask
Can I dispute an in-app purchase because I regret buying it?
Not automatically. An authorized purchase you no longer want is usually a refund or cancellation request, not an unauthorized-transaction claim.
Your card issuer investigates the facts. It doesn't turn every disappointing purchase into fraud.
Should I contact Apple or Google before my bank?
If the charge is unfamiliar or the account may be compromised, contact the issuer or bank promptly and contact the platform too. Don't wait for one response before warning the other.
For an authorized purchase where the item failed, start with the platform or developer. You can use both routes, but keep the explanation consistent.
Is there one deadline for every App Store or Google Play dispute?
No. Platform refund policies and account procedures can differ.
For U.S. credit card billing disputes, FTC guidance generally uses a written 60-day notice period. Unauthorized bank transactions have separate notice rules. Check the receipt and the issuer's instructions.
Open the statement and receipt now. Record the order details, decide whether the issue is unauthorized or a refund problem, and contact the right party before the relevant deadline passes.