Skip to content
AppDues
Log in
Contact salesSign up

India Subscription Rules for Google Play: A Developer Change Checklist

When India's central bank introduced an extra authentication layer for recurring card transactions, Google Play had to suspend new auto-renewing subscriptions, free trials and introductory pricing in the country. The timeline below reflects the 2021 rollout and its September 30 transition point. Use it as a historical reference for understanding the mechanics, then confirm current store and RBI requirements before changing a live app.

What changed and why

India's Reserve Bank of India (RBI) introduced rules requiring an additional authentication step for prepaid recurring transactions. From April 1, 2021, consumers in India had to manually authenticate recurring transactions above a certain amount. Payment processors were originally expected to comply by March 31, 2021; the deadline moved to September 30, 2021. Until a processor was compliant, it could not process new recurring transactions.

Google responded by suspending new auto-renewing subscriptions, free trials and introductory pricing in Google Play in India from May 4, 2021. On August 31, Google Play Console notices described the September 30 transition. The practical effects were:

  • Auto-renewing subscriptions, free trials and introductory pricing would again be purchasable in India after September 30.
  • Auto-renewing products would be capped below 5,000 INR.
  • Customers whose banks were not compliant with the new RBI rules could not purchase subscriptions.
  • Customers who bought auto-renewing subscriptions before May 4 would move to a grace period ending September 30.

Those four points are the core of the change. The rest of this guide turns them into decisions an Android team can act on.

The 5,000 INR price cap

From September 30, any subscription product priced at or above 5,000 INR was to be converted to a non-renewing subscription when offered to Indian customers. To keep auto-renewal, products needed to be priced under 5,000 INR. This was the single biggest change in the update.

A useful check before publishing a price: confirm the INR price of every subscription product, not just the base plan you test with. A product that looks fine in another currency can cross the threshold once localized.

Bank compliance and the non-renewing fallback

Compliance with the RBI rules sat with Indian banks, so adoption was expected to be gradual. Any bank that had not adopted the requirements by September 30 would not authorize purchases of new subscriptions. Affected customers would instead be offered a non-renewing variant of the subscription.

A key limitation: the app could not see this status when presenting the paywall. That meant you could not tell an affected customer in advance that their subscription would not auto-renew. The practical mitigation was to prepare support-page resources explaining the situation and the resubscribe path.

Grandfathered subscribers and the September 30 grace period

Customers who bought auto-renewing subscriptions before May 4 were grandfathered so they could keep renewing while their subscriptions stayed active. As the new rules took effect, even those users had to update billing information in Google Play so their card providers could authorize new auto-renewing subscriptions. Customers who did not verify their card details had their subscriptions cancelled and could not renew automatically.

The fix was for users to update their card details in settings, but not every user would do so. That raised the risk of a cancellation increase, especially among Indian customers. A sensible response was to watch subscriber retention, filter by country to India, and if the dip was significant, target those users with emails and promotions encouraging them to update billing details and resubscribe.

Android change checklist

If your app is listed on Google Play in India, work through these items in order.

  1. Paywall copy. Remove mentions of free trials, auto-renewals and introductory pricing for Indian users. Detect the currency of the SKU using getPriceCurrencyCode and, when it returns INR, switch the wording dynamically.
  2. In-app messaging. Tell Indian users their subscription will not renew automatically and prompt them to resubscribe when the period ends.
  3. Offering design. Rather than stripping trials and intro pricing from every market, create a separate offering for Indian subscribers that omits them, and display it according to the user's storefront. Replacing auto-renewing SKUs in India with one-time product SKUs is another option Google recommends, though for some apps it is simpler to keep subscriptions and let Google decide whether they renew.
  4. Eligibility logic. If your app shows introductory offers, treat INR users as ineligible. Reuse the same logic you already apply to current and former subscribers.
  5. Support resources. Prepare help content for customers whose banks cannot authorize auto-renewal.
  6. Analytics review. Expect churn, cohort, trial conversion and trial start charts to move for reasons that are not purely behavioral.

A caveat worth keeping in mind: the rules could technically reach Indian citizens using Play Store accounts registered in other geographies. Watch how the rules are interpreted as they roll out, and consult a qualified lawyer or compliance professional when in doubt.

Worked example: one paywall, two storefronts

Suppose an app sells a monthly plan at a price that converts to under 5,000 INR and a yearly plan that converts above it. A single paywall that advertises a seven-day free trial would be wrong for both Indian products: the trial cannot be offered there, and the yearly product would be converted to non-renewing.

A cleaner approach is to branch on currency. When getPriceCurrencyCode returns INR, show the India offering: no trial language, no auto-renew promise, and a clear note that the plan ends rather than renews. When the currency is anything else, keep the standard trial messaging. The eligibility check for introductory pricing should also short-circuit to ineligible for INR, mirroring the check already used for existing subscribers.

This keeps the non-India experience intact while matching what Google Play will actually deliver in India.

What about iOS?

At the time of writing, Apple had not announced changes tied to the RBI rules. One plausible explanation is that Apple was already compliant with the framework and therefore had nothing to communicate. If Apple later announced changes for apps on the App Store in India, the guidance would be updated.

Analytics and webhook effects

Entitlement status tracking was expected to keep working because it relies on purchase and expiration dates. Several metrics, however, could look unusual:

  • Auto-renew status could reflect the new non-renewing behavior.
  • Churn and cohort charts could show spikes and upward trends. The churn formula counts new purchases minus expired purchases per day; without auto-renewals, users may take longer than a day to resubscribe, which inflates apparent churn.
  • Trial conversion and trial start rate charts could dip or drop sharply, depending on exposure to the Indian market, because trials were paused.
  • New purchases and trials could shift as the mix changed.

Webhook listeners needed special care. When an Indian user purchased a subscription, Google indicated the subscription was cancelled by the system. A subscription platform that treats a system cancellation as a billing issue would emit a BILLING_ERROR cancellation notification. Because every subscription purchased in India was cancelled by Google in this way, billing issue notifications rose. The distinction that matters:

  • If the notification's currency field is INR and the reason is a billing issue, disregard it.
  • Alternatively, check the first purchase date. A purchase before May 4 made the billing issue legitimate and should enter the billing issue flow. A purchase after May 4 could be safely ignored, since it was likely generated right after an initial purchase of a subscription that could not auto-renew anyway.

A later update noted that upgrades and downgrades could not be performed during this period; users had to wait out the billing cycle before buying the next level up or down.

Frequently asked questions

What happened to subscriptions priced at or above 5,000 INR?

They were converted to non-renewing subscriptions when offered to Indian customers. To keep auto-renewal, products needed to be priced under 5,000 INR.

How can an app tell whether a user is seeing an Indian storefront?

Check the currency of the SKU using getPriceCurrencyCode. When it returns INR, adjust paywall wording and treat the user as ineligible for introductory offers.

Why did Indian purchases trigger BILLING_ERROR notifications?

Google marked each India subscription purchase as cancelled by the system. A subscription platform that reads that pattern as a billing issue would send a BILLING_ERROR cancellation notification. For INR notifications, or for purchases made after May 4, the notification could generally be disregarded; purchases before May 4 could represent a real billing issue.

Did existing auto-renewing subscriptions stop renewing immediately?

No. Subscriptions bought before May 4 were grandfathered and continued renewing while active, but users still had to verify their card details in Google Play. Those who did not verify had their subscriptions cancelled.

Did the same rules apply to iOS apps?

Apple had not announced changes tied to the RBI rules at the time. It was possible Apple was already compliant. Any later App Store India changes would have been communicated separately.