Customers charged twice for the same subscription usually paid on two platforms, and only one of those refunds is yours to give

Nothing in Apple's or Google's billing systems stops one person from paying both of them for your subscription in the same month. When a customer is charged twice for the same subscription, that's almost always what happened. They subscribed on an iPhone, then again on an Android tablet or on your website, and your app didn't recognize the first plan. The customer sees two charges and writes to you. The catch is that you can refund only one of them yourself, and only if it wasn't bought through Apple. Here's how each side works, what the duplicate costs you, and how to make sure it doesn't happen again.

Why customers get charged twice for the same subscription

Each store owns its own purchase. Apple bills the App Store subscription, Google bills the Google Play one, and your payment processor bills the web plan. None of them knows the others exist. Your server is the only place where the two purchases can meet, and only if both carry an ID that ties them to the same account.

The usual paths to a double charge look like this:

• The customer switches phones, from iOS to Android or back, and subscribes again because the new app shows a paywall.
• The customer subscribes on your website, installs the app, and isn't signed in, so the app sells them a store subscription on top.
• The customer uninstalls the app and assumes that ended the plan. Google's help says uninstalling an app doesn't cancel its Google Play subscription, and an App Store plan keeps renewing until it's canceled in the Apple account.

"Your app and website clearly aren't talking to each other"

That's the complaint you'll read in the support email, and from the customer's side it's fair. They paid for one product. Being asked to pay again for it feels like a trap, even when it was an accident on both sides. The quickest way to cool that down is to say plainly which purchase you can refund and which one they need to take to Apple.

Who can refund each charge

This is where most support replies go wrong. You can only promise what you control.

Can a developer refund an App Store subscription?

No. Apple handles every App Store refund. What you can do is shorten the trip. StoreKit's beginRefundRequest opens Apple's refund sheet inside your app, with the purchase details and a list of reasons already filled in. Apple's documentation says the App Store takes up to 48 hours to approve or deny the request. Outside the app, the customer signs in at reportaproblem.apple.com, picks "Request a refund", chooses a reason and selects the subscription.

Refunding the Google Play side yourself

On Google Play you're in control. In Play Console, open Order management, select the order and refund it. Play Console help is specific about subscriptions: refund the most recent order and the subscription is removed immediately, with future recurrences canceled. Refund an older order and the subscription stays active. If you automate this, the orders.refund API does the same job, takes a revoke flag to end access at once, and refuses orders older than 3 years.

What a duplicate subscription costs you

The duplicate was never revenue you got to keep. The money question is how much more it costs on top of the refund.

The clean case

Say a customer paid $9.99 a month on both the App Store and Google Play for three months before noticing. That's $29.97 of duplicate charges. If you refund the three Google Play orders yourself, you give back $29.97 and the problem ends that day. If the customer instead takes the App Store side to Apple, Apple decides how much to refund and you only find out through your server notifications. Either way, one platform's revenue for those three months goes back.

The expensive case

The real loss comes when the customer gives up on support and calls their bank. A chargeback is final once the bank decides. Google Play gives you one chance to argue, a chargeback review that you answer within 24 hours through orders.reviewrefund. For Google Play orders placed after August 3, 2026, a lost chargeback costs you the purchase price, less Play's service fee, plus the bank's chargeback fee. A $29.97 refund you could have issued in a minute turns into $29.97 plus a fee you don't control.

The cost you keep paying meanwhile

While both plans are active, your backend serves one person but sees two subscriptions. If you count seats, sync data or call paid third-party APIs per subscription, you may be paying twice for compute, storage and API calls on a single customer. Merging the two records ends that.

How to handle a double charge in support

Answer fast and in one message. Every extra round trip raises the odds of a bank dispute.

• Look up both purchases by the customer's account, not by the email address they wrote from.
• Ask which plan they want to keep. Usually it's the one on the device they use now.
• If the duplicate is on Google Play or your website, refund it yourself and tell them it's done.
• If the duplicate is on the App Store, send them to reportaproblem.apple.com, or to the refund button in your app if you've built one, and tell them to cancel it in their Apple account settings.
• If Apple then sends a CONSUMPTION_REQUEST and the customer consented, answer it within 12 hours with accurate usage. A duplicate plan that was never used is easy for Apple to approve.

How to stop the second charge before it happens

Prevention is cheaper than any refund, and the tools already exist in both stores.

Tie every purchase to your account ID

On iOS, generate a UUID per account and pass it as the appAccountToken purchase option. Apple returns the same value in the transaction and in the subscription renewal information. If a purchase happened outside your app, the Set App Account Token endpoint lets you attach or update the token later. On Android, pass a hashed account ID of 64 characters or less to setObfuscatedAccountId, never raw personal data.

Check entitlements before you show a paywall

Before the paywall appears, ask your own server whether the signed-in account already has an active plan from any platform. Show a sign-in prompt first, then the paywall only to accounts with no active plan.

Watch for two active plans on one account

Run a daily check for accounts with more than one active subscription across stores. Catching it in week one means a one-month refund instead of a three-month one, and a short email instead of a chargeback.

RefundHalt tracks App Store and Google Play subscriptions against your own account IDs, so a customer paying twice shows up as one person with two plans before their bank does.