A Google Play developer registration payment declined in India is almost always a card or banking issue, not a problem on Google's side. The two most common causes are a card that is not enabled for international transactions, which RBI rules leave off by default, and an unsupported card, such as a prepaid card or many government-bank debit cards. The fix is usually to use a credit card or an international-enabled debit card, turn on international use in your bank app, and complete the OTP step. Contact your bank, because that setting is on their side.
Short answer
The decline is a card and RBI issue, not Google. The one-time registration fee is charged in US dollars, and Indian cards are frequently blocked for international online payments unless you enable them in your bank's settings. Google's payment methods documentation notes that accepted cards vary by location and that prepaid cards are not accepted. Use a credit card or an international-enabled debit card from a supported bank, enable international transactions in your banking app, and complete the OTP or additional authentication that RBI requires. If a card keeps failing, try another and contact your bank; if you were charged but registration still failed, contact Google Play support.
Why the payment is declined
The core reason is that RBI rules and Indian bank defaults make international card payments harder than domestic ones. Many Indian debit and credit cards are disabled for international or online transactions out of the box, as a security measure, so a US-dollar charge from Google is refused until you explicitly enable that capability. The decline is your bank protecting the card, not Google rejecting you.
Two other factors add friction. International transactions require additional-factor authentication, usually an OTP, and if that step does not complete, the payment fails. And some card types are simply not supported for this kind of payment. None of these are unique to Google; they affect most international online purchases from India, but they surface here because the registration fee is a one-time foreign charge.
Which cards work and which do not
Not every Indian card can pay the fee, and using the wrong type is a common cause of a decline. Credit cards from major banks are the most reliable, provided international use is enabled. Many bank debit cards, such as those from HDFC, ICICI, and Axis, also work once enabled for international online transactions. What tends not to work are prepaid cards, which Google does not accept, and the debit cards of many government banks.
The table below summarizes the landscape.
| Card type | Works for registration? | Note |
|---|---|---|
| Credit card (Visa or Mastercard) | Yes, most reliable | Enable international use first |
| International-enabled bank debit | Often yes | Turn on international online use |
| SBI or most government-bank debit | Usually not accepted | Use a different card |
| Prepaid cards | No | Google does not accept prepaid |
| Virtual dollar card | Common workaround | Only if enabled for international |
If your current card falls into the rows that are usually not accepted, the fastest fix is simply to use a different card rather than fighting the one that will not work. A supported credit card with international use turned on is the path with the fewest surprises.
Enable international transactions on your card
This is the single most common fix. Most Indian banks disable international transactions by default and let you turn them on yourself, usually in the bank's mobile app or net banking, under card controls or settings. Enable international and online usage for the specific card you are using, and set a limit high enough to cover the fee.
The change is on your bank's side, not Google's, which is why retrying the payment without enabling the card just fails again. After you turn it on, the setting can take a short while to apply, and some banks enable it only for a limited window, so make the payment soon after. If you cannot find the option, your bank's support can enable it for you.
The OTP and additional authentication step
RBI requires additional-factor authentication for these payments, so expect an OTP or an in-app approval during checkout. If that prompt does not arrive, or you miss it, the transaction is declined even on a perfectly valid, internationally enabled card. Make sure the mobile number linked to your card is current and can receive messages.
If the OTP consistently fails to arrive, the problem is usually with the bank or the registered number rather than with Google. Confirm your number, check that international transaction alerts are not being blocked, and try again. Completing this step is mandatory; there is no way to bypass it, because it is a regulatory requirement, not a Google option.
Step-by-step fix
Work through the fixes in order rather than retrying the same card repeatedly, which can trigger temporary blocks. The checklist below moves from the most common fix to escalation.
| Step | Action | Why |
|---|---|---|
| 1 | Use a credit card or international-enabled debit | Most reliable for a US-dollar charge |
| 2 | Enable international transactions in your bank app | Off by default under RBI rules |
| 3 | Complete the OTP or additional authentication | Required for international payments |
| 4 | Check the billing address matches the card | Mismatches cause declines |
| 5 | Try a different card or bank | Isolates a single bad card |
| 6 | Contact your bank, then Google support | Escalate to the right party |
The first three steps resolve the large majority of India declines: a supported card, international transactions enabled, and a completed OTP. If those do not work, changing cards isolates whether the issue is one specific card, and contacting your bank addresses anything on their side.
If you were charged but registration failed
Sometimes the money leaves your account but registration does not complete, which is alarming but usually recoverable. This often happens when the charge is authorized but the session times out, or when a hold is placed rather than a final capture. Do not immediately pay again with another card, because you may end up with two charges.
Instead, check whether the charge is a pending authorization, which many banks reverse automatically within a few days, or a completed payment. Then contact Google Play developer support about the registration, and Google Payments support about the charge, with the transaction details. Keeping the date, amount, and any reference number makes it far easier for them to match and resolve the payment.
When to contact your bank versus Google
Knowing who owns the problem saves time. Contact your bank when the issue is the card itself: international transactions not enabled, an OTP not arriving, a low international limit, or an unsupported card. These are all bank-side settings that Google cannot change, and the bank can usually fix them on a single call.
Contact Google when the issue is on the registration or charge side: you were charged but registration did not complete, you see an error after a successful payment, or you need help with the developer account itself. Google's payment and registration help covers these cases. Sending each problem to the right party is the difference between a quick fix and a long loop.
After you register: the next gate is a secure app
Once your payment goes through and your account is active, the work shifts from billing to shipping, and the next gate is a policy-compliant, secure app. Payment problems are unrelated to app security, but they are the first of several checks between you and a live listing, and the later ones include Google's review of what your app actually does.
A scanner like PTKD.com analyzes your .apk and returns findings ordered by severity and mapped to OWASP MASVS, so once you are registered you can catch embedded secrets, insecure configurations, and risky permissions before you submit. To be clear about the boundary: PTKD has nothing to do with your registration payment or RBI rules, and it cannot resolve a declined card. It is simply the security step that comes after you are in the door.
What to take away
- A declined registration payment in India is almost always a card or RBI issue, not a Google problem.
- Use a credit card or an international-enabled debit card; prepaid cards and many government-bank debit cards are not accepted.
- Enable international transactions in your bank app and complete the OTP, both of which are bank-side and required by RBI.
- If you were charged but registration failed, do not re-pay blindly; check for a pending hold and contact Google support.
- After you register, scan your build with PTKD.com, because a secure, compliant app is the next gate to going live.
