Master Google Play Billing & RBI E-Mandates for Indian Apps

By Sahil Chaudhary · Last updated 23 Oct 2026

For Indian start-ups, D2C brands, and enterprises, monetising mobile apps through subscriptions or recurring services is a powerful growth engine. However, this path is fraught with a unique dual challenge: adhering to Google Play’s strict billing policies while simultaneously complying with the Reserve Bank of India’s (RBI) comprehensive e-mandate framework for recurring payments. Get this wrong, and you risk app rejection, payment failures, or even regulatory penalties.

TL;DR: Successfully implementing recurring payments in Indian mobile apps requires a clear strategy to reconcile Google Play’s mandatory billing system with RBI’s e-mandate rules, particularly for Additional Factor of Authentication (AFA). This involves careful consideration of in-app vs. external payment flows and robust compliance with data protection laws.

Key takeaways

• Google Play Billing System (GPBS) is mandatory for digital goods and services within your app, but exceptions exist for physical goods or services consumed outside.
• RBI's e-mandate framework requires AFA for all recurring payments (card, UPI) above ₹5,000, along with pre-debit notifications and easy cancellation.
• A strategic decision between GPBS and external payment gateways is critical, driven by the nature of your service and the payment value.
• Implement robust user consent, data localisation, and clear payment disclosures to comply with the DPDP Act 2023 and build user trust.
• Thorough testing of payment flows, especially AFA and notification mechanisms, is essential to avoid app store rejections and ensure smooth user experience.

As a senior mobile engineer who has shipped numerous consumer and enterprise apps, I see this specific intersection as a common pitfall for Indian businesses. Generic global advice on in-app purchases often overlooks the unique regulatory landscape here. This article will provide a concrete runbook, outlining the trade-offs and technical considerations for making your Google Play billing India e-mandates compliant and efficient.

The Dual Challenge: Google Play Billing vs. RBI E-Mandates

At the heart of the matter lies a regulatory and platform dichotomy. Google Play mandates its own billing system (GPBS) for digital goods and services offered within Android apps, taking a commission on these transactions. This system is designed for a global audience, often abstracting away country-specific payment nuances.

Conversely, the Reserve Bank of India's Master Direction on Debit/Credit Card Transactions and E-mandates (as of 2026) imposes stringent requirements on all recurring payments processed in India. This includes an Additional Factor of Authentication (AFA) for transactions above ₹5,000, pre-debit notifications, and a clear mechanism for users to modify or revoke mandates. These rules apply regardless of the payment instrument – credit cards, debit cards, or even UPI AutoPay mandates.

The challenge for Indian app developers is to build a payment flow that satisfies both masters without compromising user experience or risking non-compliance.

Understanding Google Play Billing Policies for India

Google Play's policy is clear: for any digital content, service, or functionality consumed within the app, you must use GPBS. This includes subscriptions for premium features, cloud storage, digital publications, or in-game currency. Google charges a service fee, typically 15-30%, on these transactions.

However, there are critical exceptions relevant to the Indian market:

• Physical Goods and Services: If your app facilitates the purchase of physical goods (e.g., D2C products) or services consumed outside the app (e.g., cab bookings, food delivery, event tickets), you are generally permitted to use an alternative payment system.
• External Payments: For certain categories like utility bill payments, education fees, or government services, Google may allow external payment processing.
• Reader Apps: Apps that primarily provide access to purchased digital content or services (e.g., music, video streaming) may also direct users to an external website for subscription management.

Understanding these exceptions is the first step in designing your payment strategy. For most subscription-based digital services, GPBS is non-negotiable, which then brings RBI's e-mandate rules into play.

RBI's E-Mandate Framework: What it Means for Apps

The RBI's framework is designed to protect consumers by ensuring explicit consent and control over recurring payments. Key requirements include:

1. Additional Factor of Authentication (AFA): For any recurring transaction (including subscriptions) above ₹5,000, a one-time AFA (e.g., OTP) is mandatory at the time of initial mandate registration. For subsequent transactions, AFA is required only for amounts above ₹15,000, while transactions below this threshold can proceed without AFA if the initial mandate included it.
2. Pre-debit Notifications: Banks and payment aggregators must send a pre-debit notification to the customer at least 24 hours before the actual charge, giving them an option to opt-out or modify the mandate.
3. Easy Cancellation: Users must have a straightforward way to view, modify, or cancel any e-mandate at any time through their bank, payment aggregator, or directly within your app's subscription management interface.
4. UPI AutoPay: This NPCI initiative allows users to set up recurring payments via UPI, integrating AFA and mandate management directly into the UPI ecosystem. It's a key tool for developers. More details can be found on the NPCI website.

For developers, this means building robust backend systems and user-facing interfaces that integrate these steps seamlessly. Simply relying on GPBS's default subscription management might not fully satisfy RBI's AFA and notification requirements for higher-value subscriptions.

Strategic Approaches for Recurring Payments in Indian Apps

Deciding between GPBS and external payment gateways (or a hybrid) is crucial. Here's a breakdown:

1. In-App Subscriptions (GPBS) for Digital Services

When to use: Primarily for digital content, premium features, or services consumed entirely within your app (e.g., ad-free experience, exclusive articles, cloud storage). If your subscription value is typically below ₹5,000 per transaction, GPBS might seem simpler.

RBI Compliance: Google Play's system handles the initial payment authentication. However, for recurring payments above ₹5,000, the onus is often on the app developer to ensure that the payment method linked to GPBS (e.g., a credit card) has an underlying e-mandate that complies with RBI's AFA rules. This is where it gets complex. While Google facilitates the transaction, the actual banking infrastructure in India needs to support the e-mandate. This often means relying on the user's bank to manage the AFA for card-based recurring payments within GPBS.

Developer Action: Ensure your app's terms of service and subscription flow clearly communicate how recurring payments work, especially regarding AFA. For higher value subscriptions, you might need to guide users towards specific payment methods or inform them about bank-level AFA processes. Ensure your data handling for user profiles and subscriptions complies with the Digital Personal Data Protection Act 2023, especially regarding consent and data localisation.

2. External Payment Gateways for Physical Goods/Services or Large Tickets

When to use: When your app sells physical products, facilitates services delivered offline, or handles high-value recurring payments (e.g., coaching, property rentals, large SaaS subscriptions) that fall under Google's exceptions. This is also ideal for leveraging UPI AutoPay directly.

RBI Compliance: This is where you gain direct control over RBI e-mandate compliance. Indian payment gateways like Razorpay, PayU, or Cashfree are built to handle AFA, pre-debit notifications, and mandate management as per RBI guidelines. You integrate their SDKs and APIs, which guide the user through the AFA process (e.g., OTP on bank page, UPI PIN for AutoPay).

Developer Action:

• Integrate a compliant Indian payment gateway SDK.
• Design deep linking flows to seamlessly redirect users from your app to the payment gateway and back after successful mandate registration.
• Implement robust webhook listeners to track mandate status and payment success/failure.
• Ensure your subscription management screens allow users to view and cancel mandates, potentially by linking them to the payment gateway's portal or via direct API calls.

This approach offers greater flexibility but requires more direct integration work and careful handling of payment status synchronisation.

When NOT to use this approach

Avoid using external payment gateways for recurring payments that are clearly for digital content or services consumed entirely within your app (e.g., unlocking premium app features). Google Play Store review teams are vigilant, and attempting to circumvent GPBS for these categories will lead to app rejection.

3. Hybrid Models & User Onboarding Flows

Many apps find a hybrid approach optimal. For instance, a D2C app might use GPBS for a small, digital-only premium feature (e.g., advanced analytics dashboard) but use an external gateway for recurring physical product subscriptions or high-value service packages. The user onboarding flow must clearly differentiate these options.

User Journey Design:

1. Clear Disclosure: Inform users upfront about the payment method and its implications (e.g., "This subscription will be processed via your bank's e-mandate system").
2. Seamless Redirection: If using an external gateway, ensure a smooth transition with deep links.
3. In-App Management: Provide a clear 'My Subscriptions' section where users can see active plans, payment dates, and easily initiate cancellations or modifications.

Here's a comparison table to guide your decision:

Feature/Criterion	Google Play Billing System (GPBS)	External Payment Gateway (e.g., Razorpay, PayU)
Primary Use Case	Digital goods, in-app features, content consumed within app.	Physical goods, services consumed outside app, high-value digital services.
RBI E-Mandate Compliance	Relies on underlying card network/bank for AFA. Developer needs to ensure disclosures. May be complex for >₹5,000 recurring.	Direct integration with RBI-compliant e-mandate flows (AFA, pre-debit notifications, UPI AutoPay).
Google Play Commission	Mandatory (15-30% on digital goods/services).	No Google commission (payment gateway fees apply, typically 1-2% + GST).
Payment Data Localisation	Google's global infrastructure; payment data may not reside solely in India.	Indian payment gateways ensure data localisation as per RBI directives.
User Experience	Integrated, familiar Google flow. May lack India-specific payment options (e.g., direct UPI AutoPay).	Can offer broader India-specific options (UPI, Net Banking, Wallets) with custom UI/UX. Requires deep linking.
Setup Complexity	Relatively simpler for basic subscriptions via Play Console. Complexities arise for RBI compliance.	More integration work (SDKs, webhooks, deep linking) but offers greater control over compliance.
App Store Review Risk	Low if used correctly for digital goods. High if external gateway used improperly.	Low if used for allowed categories.

Implementation Checklist for E-Mandate Compliant Apps

Here’s a practical runbook for developers:

1. Define Your Monetisation Strategy

   Clearly categorise what you sell: digital, physical, or service. This dictates your billing system choice. For subscription and recurring payments, consider working with Krapton to build a robust subscription payment system compliant with Indian regulations.

2. Integrate Google Play Billing Library (if applicable)

   For digital goods, use the

   dependencies {
       implementation 'com.android.billingclient:billing:6.0.1' // Or latest version
   }

   to manage in-app purchases and subscriptions. Handle purchase flows, subscription states, and entitlements carefully.

3. Integrate Indian Payment Gateway SDK (if applicable)

   For external payments, integrate an Indian payment gateway that supports RBI's e-mandate framework, including UPI AutoPay. Ensure their SDKs are up-to-date and handle AFA flows.

4. Implement AFA for Recurring Payments

   If using an external gateway, the gateway will guide the user through AFA (e.g., for UPI AutoPay or card e-mandates). For GPBS, verify that the user's linked payment method supports the required AFA for amounts over ₹5,000. For example, if a user tries to subscribe to a ₹6,000/month plan via GPBS with a credit card, the underlying bank/card network must process the AFA correctly.

5. Automate Pre-Debit Notifications

   If managing external mandates, your backend system must send pre-debit notifications to users at least 24 hours before the charge, as per RBI rules. This can be via SMS, email, or in-app notifications. Ensure these notifications include an easy opt-out link.

6. Provide Easy Mandate Management

   Within your app, create a 'My Subscriptions' or 'Manage Payments' section. For GPBS, this links to Google Play's subscription management. For external mandates, provide links to the payment gateway's portal or implement API calls to allow users to pause, modify, or cancel mandates directly.

7. Ensure Data Protection & Localisation

   Comply with the DPDP Act 2023 for all personal data, especially payment-related information. Ensure consent mechanisms are robust, and data localisation requirements (for payment data, as per RBI) are met by your chosen payment partners.

8. Thorough Testing

   Test all payment flows end-to-end, including mandate registration, AFA, pre-debit notifications, successful recurring charges, and cancellations. Simulate failures and edge cases. This is critical for avoiding app store rejection and ensuring user trust.

FAQ

What is UPI AutoPay and how does it help with RBI e-mandates?

UPI AutoPay is an NPCI feature allowing users to set up recurring payments via UPI. It streamlines the e-mandate process by integrating AFA directly within the UPI app, making it a highly compliant and user-friendly option for Indian mobile app subscriptions.

Can I use a third-party payment gateway for all my in-app purchases in India?

No. Google Play policy mandates GPBS for digital goods and services consumed within the app. You can only use third-party gateways for physical goods, services consumed outside the app, or specific exempted categories.

What happens if my app violates Google Play's billing policy in India?

Violations can lead to app rejection during review, removal from the Play Store, or even termination of your developer account. It's crucial to understand and adhere to both Google's policies and RBI regulations.

How do I handle GST for in-app subscriptions in India?

For GPBS, Google typically handles the GST collection and remittance for transactions it processes. For external payment gateways, your business is responsible for collecting and remitting GST as per Indian tax laws. This is general information, not tax advice; consult a tax professional.

Ship Your Mobile App with Krapton — Hire React Native and Flutter Developers

Navigating the complexities of Google Play Billing and RBI e-mandates for recurring payments in India requires deep technical expertise and a keen eye for regulatory compliance. At Krapton, our senior engineers specialise in building robust, compliant, and performant mobile applications for the Indian market. Whether you're building with React Native or Flutter, we ensure your payment integrations are seamless and compliant. Ready to build your next-generation app? Share your mobile app project brief with Krapton today.

About the author

Krapton Engineering is the team behind Krapton's web, mobile, and AI software solutions. We specialise in crafting scalable, secure applications, focusing on the intricate technical and regulatory challenges faced by businesses in India and globally.