An unrecognized charge on a bank statement turns into a chargeback, and a chargeback costs you more than a refund

A customer scans a bank statement, lands on a line they don't recognize, and files a dispute with their bank instead of writing to you. That unrecognized charge is now a chargeback, not a refund, and a chargeback is the most expensive way a sale can come back. The frustrating part is how little of the label you get to control. Apple prints the same string, apple.com/bill, on every purchase and lets you change nothing. Google Play at least gives you one field. Here is what each store actually shows the customer, why the unfamiliar lines turn into disputes, and what it costs you when they do.

What each store actually prints on the statement

The descriptor is the short line your customer sees next to the amount. It is not marketing copy, and it is not your App Store listing. It is a fixed string the payment side sends to the card network, and the two stores handle it in opposite ways. One gives you nothing to change. One gives you a single field. Knowing which is which tells you where your effort can actually move the number.

Apple shows apple.com/bill, and your app name is nowhere on it

Apple's own help page is blunt about it. In Apple's words, apple.com/bill appears on your billing statement when you buy an app, music, movie, or other content from Apple, and it also appears when a subscription renews and when a family member buys apps or content from Apple. Your app name does not appear. Your developer name does not appear. Every one of your customers sees the exact label they also see for iCloud, Apple Music, and a movie rental. There is no setting in App Store Connect that changes this, because the charge is Apple's, not yours.

Apple also groups purchases. In its words, multiple purchases, including subscriptions, might be grouped onto one charge. So a customer can open a statement, see a single apple.com/bill line for $34.97, and have no way to tell it bundles your $9.99 subscription with four other things. To find out, they have to go to reportaproblem.apple.com and read the itemized receipt. Most people call the bank first.

Google Play shows GOOGLE* and a name you actually choose

Google's format is different, and part of it is yours to set. Google's payments help states that all charge descriptions begin with GOOGLE* followed by the product or service you purchased from. For Play purchases, the part after GOOGLE* comes from a field called the Credit card statement name, which you set in Play Console under your public merchant profile.

That field is the one real lever either store hands you. Google says plainly that the credit card statement name helps customers recognize the purchase they made from you. It is short, the statement shows GOOGLE* in front of it, and banks can shorten it further. Google warns that the display of some items may be shortened, depending on the format of the statement. So the name has to read clearly in very few characters, and it should be the brand your customer knows, not a holding company or an internal codename.

Why an unrecognized charge becomes a chargeback, not a refund

Here is where a labeling quirk turns into a line item on your books. When a customer recognizes a charge and wants their money back, they come to you or to the store, and the money returns as a refund, which is orderly and sometimes contestable. When a customer does not recognize a charge, the instinct is not to email support. It is to call the bank and say they didn't make it. That routes the money back as a chargeback, and a chargeback is a different animal.

This is the mechanism behind much of what gets called friendly fraud or first-party misuse: a real customer, a real purchase, and a genuine failure to recognize the line on the statement. A recurring subscription is the worst case. The customer signed up months ago, forgot, and is now scanning a statement for anything unfamiliar. An unlabeled renewal is exactly the kind of line that gets disputed on reflex.

On the App Store, that dispute is between the customer and Apple

Apple bills the customer directly, so a card dispute on an App Store purchase is resolved between the bank and Apple. You do not get a review window for it the way you do for a refund that fires a CONSUMPTION_REQUEST. That flow, the one Apple channel that asks you for evidence, gives you 12 hours to send consumption data. A pure bank chargeback on iOS is not that flow. It is settled without you, and a completed one is effectively bank-final.

On Google Play, that dispute now lands on you

Google Play sends a chargeback to you for review through orders.reviewrefund, and you have 24 hours to respond with a refund preference and usage evidence so Google can contest an illegitimate one on your behalf. Google records your first call and ignores the rest. That window matters more than it used to. For orders placed on or after August 3, 2026, a lost chargeback bills the developer the purchase price minus Google's service fee, plus the bank's chargeback fee. An unrecognized charge you could have prevented now costs you the sale and a flat bank fee on top.

What an unrecognized charge actually costs you

Walk the money on a single disputed subscription, because the label on the statement decides which of two very different numbers you pay.

Take a $9.99 monthly subscription. If the customer recognizes it and asks for a refund, the store reverses its commission along with the sale, so you lose your net proceeds, and the compute, API calls, storage, and any payout you already spent stay gone. That is the cheaper outcome, and it still is not free.

Now say the same customer does not recognize GOOGLE* on the statement and disputes it with the bank. For a Google Play order placed after August 3, 2026, you lose the same net proceeds, and you also pay the bank's chargeback fee, a flat charge the card network sets that often lands near $20. On a $9.99 sale, the fee alone can exceed what you netted. The identical unhappy customer costs you a little as a refund or several times the sale as a chargeback, and the only variable is whether they could read the charge.

• Lost proceeds: your net share of the sale, reversed either way.
• The bank's chargeback fee: a flat cost on Google Play orders after August 3, 2026, that a plain refund never carries.
• Wasted spend: the compute, third-party API calls, and storage the purchase already consumed, gone in both cases.
• Support and goodwill: the time to answer the ticket, plus any make-good refund you issue on top, this time with no commission coming back.

What you actually control, on each store

You cannot rewrite Apple's descriptor, and you can only set a short field on Google's. So the work is making the charge recognizable everywhere the customer looks, and making sure they can reach you before they reach the bank.

Set the Google Play statement name to your real brand

This is the one direct fix. In Play Console, open your public merchant profile and set the Credit card statement name to the brand a stranger would recognize, not your legal entity or an app codename. Keep it short, because GOOGLE* eats part of the line and banks truncate the rest. If a customer would hesitate reading it, pick a clearer name. This costs nothing and it is the only place either store lets you write your own name onto the charge.

Make the receipt and the reminder carry your brand

On both stores, the levers you fully control sit around the charge, not on it. Send an immediate in-app confirmation and an email receipt with your product name, so the customer has something to match against a vague statement line later. For subscriptions, send a renewal reminder before the charge, not after. A customer who got a heads-up does not dispute the line they were warned about.

Put your support contact where the bank would be the alternative

Google's merchant profile also carries your customer support email, phone, and website, and those surface in the payment help paths a confused customer follows. Fill them in. The whole goal is to give the customer an easy way to reach you instead of the bank, because the bank route is the one that becomes a chargeback with a fee attached.

Answer the one window Google gives you

When an unrecognized charge does become a Google Play dispute, you have 24 hours to answer orders.reviewrefund with evidence. Miss it and you forfeit the one chance to contest. A customer who truly never made the purchase is a real fraud case worth contesting. A customer who simply forgot is worth a fast refund before the bank fee attaches. Either way, the 24-hour window is where the outcome is decided, and it does not wait for business hours or weekends.

None of this changes the label Apple prints. It changes how many of your customers ever get far enough to be confused by it. RefundHalt watches the refund and chargeback notifications on both stores, answers the Google Play orders.reviewrefund review and Apple's CONSUMPTION_REQUEST inside their windows with the delivery and usage evidence you recorded at the time of sale, and keeps the unrecognized-charge disputes from quietly becoming the most expensive way you lose a sale.