Each renewal gets its own Google Play order ID, and that's the number to check before you refund anyone

Look at the end of the order number before you refund a Google Play customer. GPA.1234-5678-9012-34567 is the first charge on a subscription. GPA.1234-5678-9012-34567..2 is the third. They share a base, they're different payments, and Play Console treats them differently when you refund. The Google Play order ID is the only identifier your customer can see, so it's the one that ends up in your support inbox. Read it right and you refund the charge they're actually upset about, once.

What a Google Play order ID tells you

Google's Play Billing Library documentation gives the format by example. An order ID starts with GPA, then groups of digits. For subscriptions, each renewal gets the base order ID plus two dots and a counter that starts at zero. So the original purchase has no suffix, the first renewal is ..0, the second is ..1, and so on.

That makes the suffix a quick read on how long someone has paid. A customer writing in about GPA.3333-4137-0319-36762..11 has been renewed twelve times. A customer quoting the bare base ID either bought something once or is pointing at their very first payment.

Where the order ID shows up, and which version you get

This is where teams trip. Different surfaces hand you different forms of the same ID.

• The customer's Google Play receipt shows the order ID of the charge it's for, renewals included.
• In your app, Purchase.getOrderId() from the Play Billing Library returns the order ID of the initial order for subscription renewals. Google's own example: instead of GPA.1234-5678-9012-34567..0, you get GPA.1234-5678-9012-34567.
• On your server, purchases.subscriptionsv2 gives each line item a latestSuccessfulOrderId, the ID of the latest successful order for that item. Google added the field on May 21, 2025.
• In the Voided Purchases API, orderId uniquely identifies a one-time purchase, a subscription purchase or a subscription renewal. Google's docs say to use orderId, not the purchase token, to tell renewals apart.

What the purchase token is for instead

The purchase token identifies the purchase as a whole. For a subscription, one token covers the original charge and every renewal after it. That's why it's the right key for entitlement and the wrong key for a refund. Refunds and chargebacks happen to a single charge, and only the order ID names a single charge.

How to look up a Google Play order

In Play Console

Order management accepts either an order ID or the customer's full email address in its search box. Each order shows one of these statuses: Processed, Cancelled, Pending, Pending refund, Refunded, Pending partial refund or Partially refunded. If the customer gives you an email instead of a receipt, search by email and pick the charge by date, then confirm the suffix before you act.

With the Orders API

Since May 21, 2025, the Orders resource in the Google Play Developer API has orders.get for one order and orders.batchget for a list. A few limits matter in practice:

• batchget takes between 1 and 1,000 order IDs per request, and they must be distinct.
• If any one order ID isn't found or doesn't belong to the package, the whole batchget request fails.
• Orders API calls count against your Play Developer API quota, which defaults to 200,000 calls a day.

The Order you get back is the useful part. It has the order's state, its purchaseToken, createTime and lastEventTime, the total and the tax, a salesChannel such as IN_APP or PLAY_STORE, and an orderHistory with the processed, cancellation, refund and partial refund events. It also has developerRevenueInBuyerCurrency, which Google defines as your revenue in the buyer's currency, net of partial refunds, taxes and fees. When Google is the merchant of record, the buyer address carries only the country.

Refunding the right order

Once you know which charge the customer means, Play Console gives you a choice that depends on where that order sits in the subscription.

Through the API, orders.refund takes the package name and the order ID. Orders older than 3 years can't be refunded. The optional revoke parameter, set to true, ends access to the subscription or in-app item immediately. Google's help also notes that refunds can't be reversed once issued, so the order ID you pass is final.

Why does a $0.00 order show up for a subscriber?

Google's subscription lifecycle docs explain it. When a user signs up again from your app for the same base plan before their subscription expires, Google Play creates a $0.00 order. They aren't charged, because they already paid for the current period, and normal billing resumes on the original renewal date. It isn't a free trial or a promotion. There's nothing to refund on that order. If the customer wants money back, find the paid order before it.

What a wrong-order refund costs you

A refund returns the price. Partial refunds work the same way in proportion. Google's example: a 50% partial refund also takes back 50% of your payout and 50% of the service fee. What doesn't come back is everything you spent serving that customer, the compute, the third-party API calls, the storage, any affiliate payout. Refund the wrong order and you pay that twice.

Here's how that happens. A customer on a monthly plan writes in about the ..4 charge, the one from last week. Someone on your team searches by email, sees the first order at the top, and clicks Refund only on the base order from months ago. The customer now has money back for a period they used. The charge they complained about is untouched, and their subscription still renews. They can still ask their bank to reverse last week's charge.

That bank route is the expensive one now. For orders placed after August 3, 2026, Google says that when a chargeback goes through, the developer is responsible for the purchase price, less Play's service fee, plus the chargeback fees the bank charges. Chargebacks are final at the bank. One misread suffix can end as two refunds' worth of money gone, plus fees.

Which refunds never reach your inbox

Most Google Play refunds don't need you or the order ID at all. Google's refund policy says a customer may get a refund within 48 hours of purchase through Google Play, and after 48 hours should contact the developer. Google also refunds and revokes subscriptions you don't acknowledge within three days. You find out about those afterward through the Voided Purchases API, which reports the voidedSource (0 for User, 1 for Developer, 2 for Google) and a voidedReason such as Remorse, Chargeback or Unacknowledged_purchase.

Only one Google Play refund flow asks for your side. When a chargeback needs developer review, you have 24 hours to answer through orders.reviewrefund with a refund preference of APPROVE, DECLINE or NEUTRAL and purchase usage evidence. RefundHalt answers that review inside the window for you, using the usage data you already have, so a disputed order gets your evidence instead of silence.

A short checklist for order ID support tickets

• Ask for the full order ID from the Google Play receipt, suffix included.
• Look it up in Play Console or with orders.get and check its state first.
• Confirm the charge date matches what the customer describes.
• Use Refund and revoke only on the most recent order, and Refund only on older ones.
• Record the order ID you refunded, so a later chargeback on another order is easy to spot.