The Google Play developer registration fee is a one-time US$25 charge, and it is generally non-refundable. Google explicitly states that if your identity information fails validation, the fee will not be refunded, and a policy-based account ban is not refunded either. The cases where Google does issue a refund are narrow: a duplicate charge, an accidental payment where you never completed registration, or closing an original account after transferring your apps. There is no fixed support timeline, so refunds are handled case by case through Google Play developer support.
Short answer
The registration fee is a one-time US$25 charge and is not refundable in most situations. Per Google's developer registration page, if your submitted information is determined to be invalid, the fee will not be refunded, and the same non-refundable treatment applies to accounts banned for policy violations. Google does refund narrow cases such as a duplicate charge, a payment where registration was never completed, or an original account closed after an app transfer, all handled by support with no guaranteed timeline. If your case is a duplicate or accidental charge, contact developer support with proof; if it is a ban or a failed verification, a refund is unlikely.
Is the $25 fee refundable?
In most situations, no. The US$25 fee is a one-time registration charge, and Google treats it as non-refundable by default. The registration page states directly that if the identity information you provide is determined to be invalid, the fee will not be refunded, which means a failed verification does not entitle you to your money back. Paying the fee and then changing your mind is likewise not a refundable situation.
Framing it that way sets realistic expectations before you contact support. The refundable cases are exceptions, not the rule, and they revolve around billing mistakes rather than dissatisfaction or enforcement. If you are looking for a refund because your account did not work out, was rejected, or was banned, the fee is almost certainly not coming back. If you are looking for a refund because you were charged twice or paid without ever completing registration, you have a real case to make.
Does Google refund banned accounts?
No, a policy-based ban does not come with a refund of the registration fee. If Google terminates your developer account for violating its policies, the one-time fee is treated as non-refundable, the same as it is for a failed identity verification. The fee pays for registration itself, not for a guaranteed outcome, so losing access through enforcement does not reverse the charge.
This matters because the fee is one-time, so a banned account does not stop a recurring charge; there is no recurring charge to stop. Some developers who are banned open a new account and pay the fee again, which is a second one-time charge rather than a refunded and re-billed one. If your account was terminated, plan around the fact that the original $25 is gone, and focus on whether opening a new, compliant account is worthwhile rather than on recovering the fee.
When Google does issue a refund
Google issues refunds in a few specific billing situations. A duplicate charge, where you were billed twice for one registration, is the clearest case and is normally refunded once you show support the duplicate. A payment where you never completed registration, for example you paid but the account was never activated, can also be refunded on a case-by-case basis. And per Google's app transfer documentation, if you transfer your apps to another account and then close the original, support can refund the original account's registration fee.
What these have in common is that they are billing corrections, not reversals of a decision. They involve a genuine mistake or a defined process, so Google has a reason to return the money. If your situation fits one of these, gather the evidence, such as order IDs and charge dates, before you contact support, because a clear, documented case is what gets these refunds processed.
How to request a refund and the support timeline
To request a refund, contact Google Play developer support through the Help option in the Play Console or the developer support contact form, describe your exact situation, and provide proof such as the order ID and the dates and amounts of the charges. Be specific about which of the refundable cases you fall into, since support handles these individually and a vague request is harder to act on. Submit one clear request rather than several, and keep the payment details ready.
On timeline, there is no published service-level guarantee, so treat it as case by case rather than expecting a fixed turnaround. Responses typically take days, and complex cases take longer, so follow up politely if you do not hear back rather than assuming it was denied. Set your expectation on the outcome by the category: a documented duplicate charge is likely to be resolved, while a request tied to a ban or failed verification is likely to be declined regardless of how long you wait.
One-time fee, not a yearly charge
A common source of confusion is whether the $25 recurs, and it does not. Unlike some developer programs that charge an annual membership, Google Play's registration fee is a single one-time payment, so you are not billed $25 every year. If you see the fee again, it is almost always because you are registering a second account, not because Google re-charged an existing one.
Clearing this up matters for refund questions, because people sometimes seek a refund believing they will be charged again next year. Since there is no recurring charge, there is nothing to cancel to avoid a future bill. If the Console is asking you to pay again on an account you already paid for, that points to a separate issue such as a payment that did not complete or a different account, which is worth resolving with support rather than paying twice.
Refund scenarios
Knowing which category you fall into tells you whether to expect a refund. The table below pairs common situations with their likely outcome.
| Situation | Refunded? | Notes |
|---|---|---|
| Failed identity verification | No | Google states the fee is not refunded |
| Account banned for policy | No | Treated as non-refundable |
| Duplicate charge | Usually yes | Show support the duplicate |
| Paid but never completed registration | Sometimes | Case-by-case via support |
| Original account closed after app transfer | Yes, via support | Support can refund that account's fee |
| Changed your mind | No | Non-refundable by default |
Read the table before contacting support: the "no" rows set the expectation that a refund is unlikely, while the "yes" and "sometimes" rows are worth pursuing with documentation.
Request checklist
Making a documented request improves your odds in the refundable cases. The checklist below covers the steps.
| Step | Action | Done? |
|---|---|---|
| Confirm eligibility | A billing mistake, not a ban | [ ] |
| Gather proof | Order ID, charge dates and amounts | [ ] |
| Contact support | Use Play Console Help or the contact form | [ ] |
| Explain clearly | State exactly which case applies | [ ] |
| Submit once | One clear request, not several | [ ] |
| Follow up | Allow days; no fixed timeline | [ ] |
The step that decides most cases is the first one: confirm you are in a refundable category before you invest time, since a request tied to a ban or failed verification is unlikely to succeed no matter how it is presented.
Protect the account you paid for
Because the fee is non-refundable and a policy ban does not return it, the practical way to protect your $25 is to keep the account in good standing rather than to recover the fee after the fact. Many refund requests come from developers whose accounts ran into enforcement, and avoiding that in the first place is worth more than any refund.
A scanner like PTKD.com analyzes your app build and reports issues such as risky third-party code, leaked keys, and over-broad permissions by severity, mapped to OWASP MASVS, so you can fix the kind of security problems that lead to malware or policy rejections before you submit. To be clear about the boundary: PTKD does not process refunds or contact Google on your behalf. It helps you avoid the rejections that put a paid account at risk.
What to take away
- The Google Play registration fee is a one-time US$25 charge and is non-refundable in most situations, including a failed identity verification.
- A policy-based account ban does not come with a refund; the fee is gone, and there is no recurring charge to cancel.
- Google does refund narrow billing cases: a duplicate charge, a payment where registration was never completed, or an original account closed after an app transfer.
- There is no guaranteed support timeline, so document your case with order IDs and dates, submit one clear request, and follow up patiently.
- Since the fee will not come back, protect the account you paid for by scanning builds with PTKD.com to avoid the rejections that lead to enforcement.
