App Store refund processing time runs from two days to two months, and a slow refund can become a chargeback

Two days after your customer asks Apple for a refund, they get an email with the decision. The money can take another month to show up on their card, and on some payment methods two. That gap between approved and landed is the App Store refund processing time nobody warns you about, and it is where a quiet refund turns into a loud support ticket, or worse, a chargeback. Here is exactly how long a refund takes on the App Store and on Google Play, broken down by payment method, why you cannot make it go faster, and what the wait actually costs you when an impatient customer calls their bank instead of you.

What refund processing time actually measures

How long does a refund take has two answers, because a refund crosses two finish lines. The first is the decision: the store approves or declines the request. The second is settlement: the money actually moves back to the payment method the customer used. On both stores the decision is quick and the settlement is slow, and the two are almost never the same day. Read any timeline knowing which line it describes.

The decision comes first, and it is fast

On the App Store, a customer requests a refund at reportaproblem.apple.com, and Apple, not you, decides. Apple says the customer gets a status update by email within 48 hours of the request. On Google Play, a refund request typically returns a decision in one to four days. So within a day or two, everyone knows whether the refund was granted. That is the fast part, and it is the part customers assume is the whole story.

Settlement comes second, and it is slow

Being told approved is not the same as having the money. Once a refund is granted, the funds go back to the original payment method, and how long that takes depends entirely on the method and the bank behind it. Store credit is nearly instant. A card can take weeks. Carrier billing can take two monthly statements. None of that is under the store's control once the refund is issued, and none of it is under yours.

App Store refund processing time by payment method

Apple publishes the settlement ranges, and they are wide. The refund goes back to the same payment method used for the purchase, and the wait scales with how slow that method is to post a credit.

Two things to underline. Apple states plainly that contacting it by phone or chat will not speed up the request or the processing of the funds, so there is no escalation that makes the money move faster. And the email decision within 48 hours is the fast clock while the up-to-30-days card settlement is the slow one, so a customer can hold an approval email for weeks before the credit actually posts.

Google Play refund processing time by payment method

Google splits the same journey into a decision, typically one to four days, and a settlement that Google says usually completes within 10 business days but varies by method. These are Google's own published per-method ranges.

The pattern matches Apple's. Money returned to a store balance is fast, money returned to a bank or a phone bill is slow, and the slowest methods stretch into months. A customer refunded to postpaid carrier billing may not see the credit until two billing statements later, no matter how quickly Google approved it.

Why a slow refund is a money problem, not just a support problem

Here is the part that turns a timeline into a cost. Between the moment a customer is told approved and the moment the money lands, they are looking at a charge still sitting on their statement and no refund in sight. Some of them will not wait. They call their bank and dispute the charge, and a bank dispute is a chargeback, which is a different and more expensive animal than the refund they were already getting.

Walk the money. When the store refunds a purchase, it also returns its own commission, so what actually leaves your account is your net proceeds, the 70 or 85 percent you kept, not the full price. A chargeback does not work like that. The customer's bank pulls the full amount and adds a flat fee that does not scale with the purchase, and the decision is final, with no appeal once the bank rules. On a cheap purchase the fee alone can cost more than the sale. And on Google Play, for orders placed on or after August 3, 2026, the chargeback moves the purchase price plus the bank's fees onto the developer, so a dispute you could have avoided now lands the whole bill on you.

The double-hit risk

There is a sharper version. If a customer disputes with their bank while a store refund is still settling, you can land on the wrong side of both processes at once: the store refund in flight and a chargeback opened on the same charge. Untangling that is slow and manual, and on Google the chargeback fee is now yours. The clean way to avoid it is to make sure the customer knows the refund is coming and roughly when, so they do not reach for the bank in the gap.

What you can and cannot do about the clock

Be honest with yourself about the levers, because most of this timeline is not yours to move.

What you cannot do

• You cannot speed up settlement. Apple states directly that contacting support does not accelerate processing, and the delay is the payment network's, not the store's.
• You cannot issue the refund yourself on the App Store. Apple decides and processes every App Store refund, and there is no developer button. On Google Play you can refund an order yourself from the Console, which at least lets you start the clock immediately.
• You cannot change the payment method the refund returns to. It always goes back to the original method, at that method's speed.

What you can do

• Set expectations in your own support replies. Tell the customer a refund can take up to 30 days on a card and longer on carrier billing, and that the store, not you, controls the timing. A customer who expects a month does not call the bank on day three.
• On Google Play, refund promptly from Order management once you have decided to refund, rather than letting a request sit. Starting settlement sooner shrinks the window in which a chargeback can begin, and refunding before a chargeback also saves you the bank fee.
• Attach a stable account id to every purchase so a refund arrives with history. Apple's appAccountToken is a UUID, and Google's setObfuscatedAccountId is a hash of up to 64 characters, never cleartext.

The evidence clocks are a different thing entirely

Do not confuse settlement time with the two windows where you actually get a say. Apple's CONSUMPTION_REQUEST gives you 12 hours to return usage data through Send Consumption Information before Apple decides a consumable refund. Google Play's chargeback review gives you 24 hours to respond through orders.reviewrefund with a refund preference and usage evidence. Those clocks decide whether money moves. The processing time decides how long it takes to move once the decision is made. They are unrelated, and missing the 12-hour or 24-hour clock is a far more expensive mistake than a slow payout.

A short checklist for refund timing

• The App Store decision arrives by email within 48 hours, and Google Play's decision typically takes one to four days.
• App Store money lands in up to 30 days on cards and up to 60 days on mobile phone billing, while store credit is near instant.
• Google Play money lands in about 1 business day to a store balance, 3 to 5 business days on cards and PayPal, and up to two monthly statements on postpaid carrier billing.
• No one can speed up settlement, so tell customers the real range before they ask.
• A slow, silent refund is the most common on-ramp to a chargeback, which is bank-final and, on Google from August 3, 2026, billed to you.
• Keep the 12-hour CONSUMPTION_REQUEST and 24-hour chargeback-review clocks separate from payout timing, because those are where you win or lose the money.

The refund your customer is waiting for was probably approved days ago. What they are watching is settlement, and settlement is slow by design, up to a month on a card and two on a phone bill. You cannot make it faster. What you can do is make sure the wait is expected instead of alarming, because the alternative is watching a refund you could have absorbed turn into a chargeback you cannot contest. On the App Store that is a support cost. On Google Play, after August 3, 2026, it is your bill.